| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 155.1 | SynNet 3: TNG proposed outline | DBLDOG::DONHAM | Progress Through Tradition | Tue Jul 21 1992 11:42 | 324 |
| Mission statement for SYSNET III:
Establish, support and customize clusters and networks.
Chapter 1: Understanding the VMS Environment
In order to understand the VMS cluster and network environment, the
system and network manager should be able to:
- Identify advanced process states
- Identify modes of operation
- Explain working set concepts
- Describe and explain advanced cluster topics (TBD)
- Identify and plan cluster configurations
- Describe and explain advanced network topics (TBD)
----------------------------------------------------------------------------
1. Understanding the VMS Environment
- Advanced process states
- Modes of operation
- Working sets
- Advanced cluster topics
- Configuration Planning
Configuration of systems
- Advanced network topics
Chapter 2: Installing the VMS Operating System
In order to install the VMS Operating System, the system and network
manager student should be able to:
- Current Install chapter from SYSNET needs to be reviewed
for chapter objectives
- Perform a conversational boot
----------------------------------------------------------------------------
2. Installing the VMS Operating System
- Notes from IPF say to use chapter as-is
- Using registers at boot time
Chapter 3: Adding a Node to a Cluster
In order to add a node to a cluster, the system and network manager
student should be able to:
- Describe what happens when you add a node to a cluster
- Add a CI node using CLUSTER_CONFIG
- Add an NI node using CLUSTER_CONFIG
- Modify group passwords and numbers using SYSMAN CONFIG
----------------------------------------------------------------------------
3. Adding a node to a cluster
- What happens when you add a node
- Adding a CI node to a cluster
- Adding an NI node to a cluster
- Modifying group characteristics using SYSMAN
Chapter 4: Backing Up Disks
In order to back up a disk, the system and network manager student
should be able to:
- Explain why a disk is backed up
- Perform a standalone back up
- Perform a disk back up
----------------------------------------------------------------------------
4. Backing Up Disks
- Explain why a disk is backed up in a VMS system
- Using standalone back up
On a cluster
- HSC back ups
Chapter 5: Understanding File Formats and Disks
In order to understand file formats and disks on a VMS system, the
system and network manager student should be able to:
- Explain the Files-11 format
- Describe how special files are used by VMS
- Describe the attributes of various disk products
- Create a shadowed volume
----------------------------------------------------------------------------
5. Understanding File Formats and Disks
- Files-11 format
- Special files
BITMAP.SYS
INDEX.SYS
- Understanding disk attributes
MSCP
HSCs
ISEs
- Setting up shadow sets (TBD if this belongs here)
Chapter 6: Customizing LAT
In order to customize the LAT, the system and network manager student
should be able to:
- Identify the components of a LAT
- Set terminal characteristics
- Create a reverse LAT service
- Install modems on a terminal server
- Define LAT group codes
- Define a LAT service (Alias)
----------------------------------------------------------------------------
6. Customizing LATs
- Understanding the components of a LAT
- Setting terminal server characteristics
- Creating a reverse LAT service
- Installing modems on a terminal server
- Defining LAT group codes (for load balancing)
- Defining a LAT service (alias)
Chapter 7: Customizing the Network
In order to customize the Network, a system and network manager student
should be able to:
- Describe the advantages of customizing a network
- Set up customized nodes
- Use NETCONFIG to create advanced routing configurations
- Set Executive routing parameters
- Set circuit and line parameters
- Examine network objects
----------------------------------------------------------------------------
7. Customizing the Network
- Advantages of customizing a network
- Setting up customized nodes
- Creating advanced routing configurations
Exec routing parameters
Circuit and line parameters
- Examining network objects
Chapter 8: Managing System Security
In order to manage system security, the system and network manager
should be able to:
- Explain why system security is necessary
- Monitor system security using auditing
- Set file security
- Set up Network security
- Gain access into a VMS system (break in)
----------------------------------------------------------------------------
8. Managing System Security
- Why system security is necessary
- Setting up security auditing
ACE alarms
LGI system parameters
- Setting up file security
High water marking
Erase on delete
Erase on allocate
- Setting up network security
Proxies
Default network accounts
Incoming/outgoing algorithms
- Gaining access to a VMS System (breaking in)
Chapter 9: Introduction to Performance
In order to understand VMS system performance, the system and network
manager student should be able to:
- TBI chapter needs to be reviewed for objectives
- Explain how networks affect performance
- Monitor system usage
- Explain disk performance and how striping affects it
----------------------------------------------------------------------------
9. Intro to Performance
- IPF notes say that the TBI chapter is OK
- Network performance
- Monitoring system usage
Using MONITOR CLUSTER
Using SHOW CLUSTER/CONTINUOUS
- Disk performance
Striping
|
| 155.2 | Some comments based on IPF | TEACH::SHERRY | Sherry Butler - DTN 341-2289 | Tue Jul 28 1992 00:04 | 375 |
| My comments/additions/modifications are lines starting with a > or |
-Sherry
-----------------------------------------------------------------------------
Mission statement for SYSNET III:
Establish, support and customize clusters and networks.
Chapter 1: Understanding the VMS Environment
In order to understand the VMS cluster and network environment, the
system and network manager should be able to:
- Identify advanced process states
- Identify modes of operation
- Explain working set concepts
> - Explain working set adjustment
- Describe and explain advanced cluster topics (TBD)
- Identify and plan cluster configurations
- Describe and explain advanced network topics (TBD)
----------------------------------------------------------------------------
1. Understanding the VMS Environment
- Advanced process states
- Modes of operation
- Working sets
> - Working set adjustment
| - Advanced cluster topics
|
| - Configuration Planning
|
| Configuration of systems
|> Reorder these as:
>
> - Advanced cluster topics
>
> Selecting Votes
>
> Configuration Planning
- Advanced network topics
Chapter 2: Installing the VMS Operating System
In order to install the VMS Operating System, the system and network
manager student should be able to:
- Current Install chapter from SYSNET needs to be reviewed
for chapter objectives
- Perform a conversational boot
----------------------------------------------------------------------------
2. Installing the VMS Operating System
- Notes from IPF say to use chapter as-is
- Using registers at boot time
Chapter 3: Adding a Node to a Cluster
In order to add a node to a cluster, the system and network manager
student should be able to:
- Describe what happens when you add a node to a cluster
- Add a CI node using CLUSTER_CONFIG
- Add an NI node using CLUSTER_CONFIG
- Modify group passwords and numbers using SYSMAN CONFIG
> - Modify cluster passwords and group numbers using SYSMAN CONFIG
----------------------------------------------------------------------------
3. Adding a node to a cluster
- What happens when you add a node
- Adding a CI node to a cluster
- Adding an NI node to a cluster
- Modifying group characteristics using SYSMAN
> - Modifying cluster password and group number using SYSMAN
Chapter 4: Backing Up Disks
> Chapter 4: Specialized Backup and Boot Procedures
In order to back up a disk, the system and network manager student
should be able to:
- Explain why a disk is backed up
> - Explain the different ways to back up a volume
- Perform a standalone backup
- Perform a disk back up
> - Perform an HSC backup
> (add)
> In order to startup the system in a non-standard, the system and
> network manager should be able to:
>
> - Boot standalone backup
>
> - Perform a mimimum startup
>
> - Perform an alternate startup
----------------------------------------------------------------------------
4. Backing Up Disks
> 4: Specialized Backup and Boot Procedures
- Explain why a disk is backed up in a VMS system
> - Explain the different ways a volume is backed up in a VMS system
> (add)
> On-Line
> Standalone
- Using standalone backup
On a cluster
- HSC backups
> (add)
> - Booting standalone backup
>
> - Performing a mimimum startup
>
> - Performing an alternate startup
Chapter 5: Understanding File Formats and Disks
> Chapter 5: Advanced Disk Concepts and Procedures
In order to understand file formats and disks on a VMS system, the
system and network manager student should be able to:
- Explain the Files-11 format
- Describe how special files are used by VMS
- Describe the attributes of various disk products
> What disk products?
- Create a shadowed volume
----------------------------------------------------------------------------
5. Understanding File Formats and Disks
- Files-11 format
- Special files
BITMAP.SYS
INDEX.SYS
- Understanding disk attributes
> - Understanding disk and tape attributes
> (add) Allocation Class
MSCP
> (add) TMSCP
HSCs
ISEs
- Setting up shadow sets (TBD if this belongs here)
> If not here, it should be somewhere in the course.
Chapter 6: Customizing LAT
In order to customize the LAT, the system and network manager student
should be able to:
- Identify the components of a LAT
- Set terminal characteristics
- Create a reverse LAT service
- Install modems on a terminal server
- Define LAT group codes
- Define a LAT service (Alias)
----------------------------------------------------------------------------
6. Customizing LATs
- Understanding the components of a LAT
- Setting terminal server characteristics
- Creating a reverse LAT service
- Installing modems on a terminal server
- Defining LAT group codes (for load balancing)
- Defining a LAT service (alias)
Chapter 7: Customizing the Network
In order to customize the Network, a system and network manager student
should be able to:
- Describe the advantages of customizing a network
- Set up customized nodes
- Use NETCONFIG to create advanced routing configurations
- Set Executive routing parameters
- Set circuit and line parameters
- Examine network objects
> - Examine and add network objects
----------------------------------------------------------------------------
7. Customizing the Network
- Advantages of customizing a network
- Setting up customized nodes
- Creating advanced routing configurations
Exec routing parameters
Circuit and line parameters
- Examining network objects
> - Examining and adding network objects
Chapter 8: Managing System Security
In order to manage system security, the system and network manager
should be able to:
- Explain why system security is necessary
- Monitor system security using auditing
- Set file security
- Set up Network security
- Gain access into a VMS system (break in)
----------------------------------------------------------------------------
8. Managing System Security
- Why system security is necessary
- Setting up security auditing
ACE alarms
LGI system parameters
- Setting up file security
High water marking
> High water marking (Erase on Allocate)
Erase on delete
Erase on allocate
> (delete) Erase on allocate
> It is High water marking
- Setting up network security
Proxies
Default network accounts
Incoming/outgoing algorithms
- Gaining access to a VMS System (breaking in)
Chapter 9: Introduction to Performance
In order to understand VMS system performance, the system and network
manager student should be able to:
- TBI chapter needs to be reviewed for objectives
- Explain how networks affect performance
- Monitor system usage
- Explain disk performance and how striping affects it
----------------------------------------------------------------------------
9. Intro to Performance
- IPF notes say that the TBI chapter is OK
- Network performance
> - Network performance concepts
- Monitoring system usage
Using MONITOR CLUSTER
Using SHOW CLUSTER/CONTINUOUS
- Disk performance
Striping
|
| 155.3 | | BRSTR3::MEERSMAN | All kids on dec | Wed Jul 29 1992 08:09 | 52 |
| Hi,
we would like to make the following remarks about this proposal:
* chapter 1: - working sets, ok if in-depth (AWSA + all related sysgen pars. and
UAF quota)
- "advanced cluster topics" should be fairly detailed in order
to support chapter 3
- "advanced network topics": because chapter 7 deals with routing,
circuit and line parameters an in-depth knowledge of DNA is
needed
* chapter 2: - should be named Installing and upgrading the VMS Operating System
Most customers only upgrade...
- what about "post-installation/upgrade" activities ?
* chapter 3: - should be supported by an in-depth chapter 1
- why only adding nodes, i.e. why not cover the complete
functionality of CLUSTER_CONFIG ?
* chapter 4: - explain why a disk...: this should be known by now; maybe we,
should explain how a disk is backed-up (cfr. quorum article)
(Ref.: Feb 1991)
* chapter 5: - Setting up shadow sets doesn't belong here
- add the "responding to problems" from sysnet II here ( ana/disk,
mount verification)
* chapter 6: some topics seem to be too advanced (reverse LAT, install modems)
* chapter 7: requires a lot of theoretical foundation (chapter 1 ?) Do we have
time to cover these topic completely or do we remain
superficial ?
* chapter 8: - auditing; the whole audit environment should be explained
- cluster security ?
- incoming/outgoing algorithms: shouldn't be too detailed (takes
otherwise 1 day to teach...)
* chapter 9: - is show cluster/cont seen as a performance tool ? It is very
good for supporting the cluster concepts theory.
- disk performance should say also something about shadowing and
RAID in general.
Many Regards from
mia dobbeni
chris klein
christian meersman
Learning Services Belgium
|
| 155.4 | | DBLDOG::DONHAM | Progress Through Tradition | Mon Aug 31 1992 14:46 | 10 |
|
Some of the tasks and topics in the SN3 outline are along the lines of
"Advanced <something> topics". I'd like to start talking about what
those advanced topics are, in detail.
What would you include under "Advanced Cluster Topics" and "Advanced
Network Topics", or any other "advanced" topic you happen to see in the
outline?
Perry
|
| 155.5 | A few thoughts... | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Thu Sep 03 1992 02:11 | 27 |
| |What would you include under "Advanced Cluster Topics" and "Advanced
|Network Topics", or any other "advanced" topic you happen to see in the
|outline?
Some ideas...
Clusters: o LOCKDIRWT (and it's different values and meanings over the
latest few VMS releases - i.e. pre-V5.0, V5.0, V5.2, etc.).
o Cluster State transition, timing changes since V4 (lots of
people still think it several minutes for a transition).
o FDDI, DSSI and other 'advanced' configurations. Advantages
and disadvantages. Difficult tasks such as modifying
allocation class and unit numbers on DSSI devices.
DECnet o Objects, their use, definition and maintenance. Also,
detailed explanation of the TASK and '0' objects.
o Contents of an 802.x packets.
o FDDI impact, type of controllers.
o more details on ethernet bridges (also 3rd party HW that
we sell, like VITALINK).
$
|
| 155.6 | | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Thu Sep 03 1992 02:20 | 10 |
| Additional thoughts...
Since VAXcluster are being renamed to VMSclusters, then we need to
discuss the Alpha differences and restrictions as of the first release
of VMS for Alpha.
Also, intro to TCP concepts, similarity and differneces when compared
to DECnet (we get a lot of questions even today).
$
|
| 155.7 | Where's the .PS files for SN3:TNG?? | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Thu Oct 29 1992 23:02 | 10 |
| Since the pilot is only a few days away.....WHERE IS THE NETWORK COPY?
Folks (those in course development on the SysNet project), we really need
to get a look at the material a couple of weeks *BEFORE* the pilot, or
the only comments you will get will be from the pilot instructor. We
can't help with the material unless we have enough lead time to print
and review it!
$
|
| 155.8 | | DBLDOG::DONHAM | Progress Through Tradition | Fri Oct 30 1992 10:26 | 4 |
|
Buck, I'll start posting chapters today.
P
|
| 155.9 | | DBLDOG::DONHAM | Progress Through Tradition | Thu Nov 05 1992 14:36 | 15 |
|
The following three chapters are available for review:
SUPER::ES$REVIEW:[SYSNET_III]
SN3_INSTALL_NODE_IG.PS;4 950
SN3_INSTALL_VMS_IG.PS;1 507
SN3_NETWORK_IG.PS;3 357
These are instructor guide chapters. Pagination will be fixed next week; the
student guide chapters have 'clean' pagination.
More to follow...
Perry
|
| 155.10 | | DBLDOG::DONHAM | Progress Through Tradition | Wed Nov 11 1992 08:08 | 10 |
|
The full SN3 Student Guide is at
SUPER::ES$REVIEW:[SYSNET_III]SN3_SG.PS
I'll post the individual chapters later today.
Regards,
Perry
|
| 155.11 | Sorry, Perry. No time now to review. Maybe after Thanksgivings. | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Fri Nov 13 1992 00:43 | 0 |
| 155.12 | | GDAY::DONHAM | Progress Through Tradition | Fri Nov 13 1992 11:30 | 12 |
|
That brings up a point I want to make. The latest plan is to keep the SysNet courses 'open' for the
next few months so that we can make changes based on the first few teaches of each course. We'll also
be adding V6 information, more Alpha VMS info, and so on. We're working on a process that will let us
rev the course 'on the fly'.
Review comments are encouraged throughout this period of time. The best place for them is in this notes
conference.
Regards,
Perry
|
| 155.13 | Sysnet III pilot results | SUPER::WTHOMAS | | Wed Nov 18 1992 15:01 | 12 |
|
The summary of the System and Network Management III pilot held in
Maynard, MA during the week of November 09, 1992 is posted in:
SUPER::$1$DUA6:[ES$REVIEW.SYSNET_III]SYSNET_III_PILOT.PS
Please post any comments regarding the pilot results here or send
them to me by mail at SUPER::WTHOMAS.
Wendy
|
| 155.14 | | DBLDOG::DONHAM | Progress Through Tradition | Mon Nov 23 1992 14:08 | 10 |
|
The most current file for SN3 is at:
SUPER::ES$REVIEW:[SYSNET_III]SN3_SG_PROFILE.PS
An IG will be posted as soon as possible.
Regards,
Perry
|
| 155.15 | Edited Student Workbook Ready | SUPER::PONCE | Editors are always write | Wed Dec 09 1992 14:35 | 7 |
| The most current file for SN3 Student Workbook is at:
SUPER::ES$REVIEW:[SYSNET_III]EY-G988E-SG-0002.PS
Regards,
Karen
|
| 155.16 | Sysnet III Instructor Guide Ready | SUPER::PONCE | Editors are always write | Thu Dec 10 1992 21:25 | 7 |
| The latest Instructor Guide for Sysnet III can be found at:
SUPER::ES$REVIEW:[SYSNET_III]EY-G988E-IG-0002.PS
Regards,
Karen
|
| 155.17 | Differences old vs revised | TEACH::SHERRY | Sherry Butler - (301)743-7160 | Mon Dec 21 1992 15:28 | 18 |
| The fine detail of differences between the old and new SYSNET III wasn't
as clear cut as SYSNET I. I've included the major areas of new or modified
material below.
Chapter 4 Managing Disk Volumes - More detailed information on Disk Striping
- Added Setting ISE Parameters
Chapter 5 Gathering System Information - Added Diagnosing System Hangs in the
section of Introduction to Troubleshooting
Chapter 6 Intro to Performance Mgmt - Most of the same information but laid
out a little different
Chapter 7 Maintaining System Security - Added Breakin Detection
If you find more differences, please post them in notes.
|
| 155.18 | Minor <<FLAME>> on the "New and Improved" SysNet III | SOAEDS::TRAYSER | Seniority: Big Shovel, Less Breaks! | Sat Feb 13 1993 02:05 | 71 |
| Well, I just picked up my new SysNet III material and am prepping for a
1st teach next week with the new material. In my humble opinion...it
stinks. (Sorry, Perry. Brutalizing follows...nothing personal.)
SysNet III obviously got the short end of the stick when it came time to
'fix' it. The material a) contains many of the same mistakes that I have
entered in various notes (mostly in topics between 94 and 106) in this
conference, it b) still contains a Performance Module entirely too detailed
considering we have a complete 5-day course to follow it and c) the
Instructor's manual is a waste of paper and my good time.
I'll try to write up the technical mistakes that are still in the book
later this week/month -- for the benefit of the other instructors --
because it has become obvious that course development has little or
no intention of including these 'fixes' either in this course or in
instructor notes.
For now, what has me really shaking my head is the instructor's guide.
o The number of instructor's notes is minimal. Considering all the notes
we posted in the conference, not many of those ideas or comments got
onto the instructor's pages.
o The page numbering makes the material useless for lecturing. The
facing-page material had 2 distinct advantages 1) lots of room to
write stuff on the blank instructor's pages and 2) the page numbers
and text were normally aligned with the student's material...
"Uh, Instructor, I have a question on the example command
procedure on page 3-21. I don't understand the line about the
swap file size. Oh?! The page in your book doesn't have an
example on page 3-21? Which example am I talking about? I
don't know. It doesn't have a diagram number in my book. Oh,
so you found it on page 3-24. Good. Now, the last line talks
about the swapfile being 12000 blocks...yes, the last line...
Oh, so it is the first line on your page 3-25...I understand."
Because the pages are not aligned I *MUST* now lecture from the
student book, so if I find any useful tips in my ONE-AND-ONLY
prep from the Instructor's book, I have to copy them over to the
student's guide -- this is a real waste of my time.
o Chapter terms are 1) in the instructor's manual only and 2) at
the beginning of the chapter? WRONG book and WRONG place. The
students should see the terms and definition as a review of the
module, after we've explained what they mean.
"Logging Component -- The process or device that receives event
information from the DECnet event logger."
"Logging Monitor -- A process that acts as the logging component"
So...Logging Monitor really means:
"A process that acts as the process or device that receives event
information from the DECnet event logger."
That's real clear. Nothing like defining the term with the term --
especially since we haven't talked about any of it yet!
"Quantum -- the maximum time that a process can remain current."
Gads! What am I, the instructor, going to do with this at the
beginning of the module? They don't know what Quantum is, much less
the real meaning of 'current' is still obscure! All this belongs AFTER
the lecture and in the STUDENT's book, not mine.
Sorry to say it, but previous note by Sherry states the case here pretty
well...Other than reformatting what was already in the course (and adding
paragraphs to the bullets), not many improvements here.
$
|
| 155.19 | 1st pass at module #1...same old problems (some fixed) | SOAEDS::TRAYSER | Seniority: Big Shovel, Less Breaks! | Mon Feb 15 1993 02:03 | 39 |
| Most of the mistakes in chapter one are the same problems from the previous
chapter two (the old chapter one was dropped from this course), so instead of
writing it all up again, I'll just refer to the previous notes (shown in
parenthesis)...
Student Guide:
1-31 - 1-24 -- belongs in a different module or course (97.9, 2-20; 97.2, #1;
97.3, 1-21)
1-37, 3rd bullet -- need more details, instructor notes ((97.2, #2; 97.7)
1-10, 1st bullet -- no details on VMSTAILOR (97.3, 1-8, #5)
1-22, typo (?) -- the item numbers don't line up with the "headers"
1-34 -- Example doesn't match previous figure. SWAPFILES.COM is only good if
your page/swap files are on the system disk in [SYSEXE], all others are
ignored.
1-41, figure -- Same Junk as last time (97.6, 2-25; 97.8, 2-25; 97.9, last
paragraph)
Example on bottom of page -- we told you it didn't match the figure,
but you put it in anyways! (97.8, 2-26)
1-45, SET BOOT -- not supported on uVAX II and uVAX 2000s (97.6, 2-31)
Instructor's book:
1-41 -- I'm confused. Is this a class exercise? A Demo? An Instructor tip?
A lab exercise that's out of place. This needs better documentation.
I may find others as I teach it this week....
$
|
| 155.20 | Module 3, VAXclusters, nothing really changed except format | SOAEDS::TRAYSER | Seniority: Big Shovel, Less Breaks! | Wed Feb 17 1993 02:37 | 65 |
| This chapter has almost *NO* changes. I only noticed 2 things that got
changed from the last version. References in parenthesis are the note
numbers and the 'entry' in that note that are the same problem with
the previous version of this course. Sigh!!
I haven't rechecked these page numbers, some might be the instructor's
manual and I forgot to note it as such. Wouldn't be a problem if the
page numbers in the instructor's manual and the student manual lined up.
3-10 -- Last bullet is overly optimistic. If we are configuring another
CI node or a DSSI node we need to modify its boot values -- see
chapter 1, pages 35-44.
3-11,3-12 -- Why are these lists so different? Building LAVc's, DSSI and
CI clusters are amazingly similar! Try merging the lists - minimal
rewording of a line would make it be suitable for either type of cluster.
- step 1 from each can be merged
- step 2 from each can be merged
- step 3 from CI is needed for both
- step 3 from LAVc can be reworded for both
- step 4 from LAVc is unique to LAVc *****
- step 4 from CI should be merged with step 5 from LAVc
- step 5 from CI can be reworded for both
- step 6 from each can be merged
- step 7 from each can be merged
- step 8 from each can be merged
Also, last two steps are pretty poor (99.7, 4-12)
3-15, last question -- With DSSI you *should* enable Ethernet (99.10, 4-15)
3-17 -- 2nd question from the bottom implies that only QBus machines have
DSSI buses. 6000s & 7000s have DSSI but not on QBus (99.10, 4-15)
3-19 -- The 2nd bullet isn't needed, we never refer to Tiger and Bear.
Also, get rid of the shaded part of the diagram. (99.7, 4-19)
3-19 (Instr) -- Noticed that the instructor's notes for the page were
eliminated and the comments in the notes file for improving it
were not used. (99.7, 4-17a)
3-23 -- Use Lion and Tiger or Bear (99.7, 4-23)
3-27 -- Word wrap problem. Same in old SN3, same in the VAXcluster course!
Please fix it. (99.7, 4-27)
3-31 (Instr) -- (99.7, 4-23)
3-26 -- (99.7, 4-34)
3-46 - 3-47 -- Hasn't this been adequately covered in another course? If so,
why is it here? If not, why is it in the VAXcluster topic? If it
stays somewhere make sure there is a commented added about the DEC
Internal licenses with Unlimited Units. (99.7, 4-41)
3-50, 2nd bullet -- Done automatically! (99.7, 4-41)
3-50 - 3-52 -- (99.7, 4-41 - 4-43)
That's it for clusters for now, I'll put DECnet stuff in next.
$
|
| 155.21 | | BROWNY::DONHAM | Progress Through Tradition | Wed Feb 17 1993 20:49 | 11 |
|
Buck, I appreciate your thorough comments, and I'll do my best to make
whatever changes make sense in the next few months.
I do want to point out that it's been said over and over and OVER that
especially SN3 is a reformat, that there is minimal new material.
Think about what new material you would add, and what you might take
out to make room for it...
Perry
|
| 155.22 | (Maybe this should be in the ESDP conference...) | SOAEDS::TRAYSER | Seniority: Big Shovel, Less Breaks! | Thu Feb 18 1993 01:25 | 86 |
| Hi Perry! Good to see you're still here and ready to work on updating
SN3. My first suggestion is to see the note I entered late last week
(4 or 5 replies ago that talks about 'brutalizing') and reread the 2nd
paragraph -- that is what I'm after: Fixed errors, minimal redundancy
with other courses in the string and useful instructor's notes.
I don't have any specific Major changes in mind for SN3, but let me
get just slightly off the topic and give you (and all the other course
writers) some suggestions for improving SN3 and other courses:
o Reply to our notes!!! For the technical critiques, if you don't
understand what we are saying, ask for clarification. Even if it
is just an occasional note that says "thanks, I understand what
you are asking for", maybe paraphrase it so we believe you. If
we don't see the course writers (and managers) occasionally writing
we get tired of talking to other instructors!
o Fix any errors specified in the conferences -- I'll keep posting
them. If at all possible, post what will, won't, can't, might
be used in the next rewrite. Notes 98.14 & 100.10 are examples.
o Keep the 'main-line' discussions in the chapters and put the
marginal stuff (Striping, VAXsim, etc.) in appendices for those
who need or choose to teach it. Keep to the basics.
o Look at OpenVMS for VAX Internals for a reasonable format for an
instructor's guide -- if we can't keep the pages looking identical
to the students with the same page numbers (and facing page guides
are really gone), separate the Instructor's guide from the student
material. Current format for SN3 is not usable except for prepping
then throwing away.
o Don't feel you need to put everything on the student's pages. Put
comments, optional topics, on the instructor's pages. If a topic
is marginal, or it's a good time to jump to the appendix, mention it
in the instructor's guide. If you have a good source of info for
a topic, tell us in the instructor's guide.
[I think Emmalee has done an exceptional job with Instructor's
notes on the last few courses -- detailed, extensive, references
to other materials, teaching tips, etc. They aren't perfect, but
they're the best I've worked with in 5 years in Ed. Services. I
think the course writers should look at her material for content
ideas.]
o Sit in parts of the course AFTER the pilot, watch a different
instructor than the one that did the pilot and use their 'comments
and explanations' for Instructor notes. Or get a video of the
course -- many training centers (i.e. Landover, MD) video some of
their courses. Put the good ideas, comments and analogies (or even
some jokes) in the next set of Student/Instructor books.
o Bring back some of the written exercises that have been removed from
the courses. Although LAB exercises are the MAJOR part of teaching
style, the written exercises are a great form of review. These can
be used for Seminar versions of these courses, worked 'interactively'
with the instructor, or be a life saver when the HW isn't working
right.
o Terms -- I like them. Still think they should be in the back of the
student materials. Get the reviewers to Highlight the important
terms in the module AFTER the module has been piloted. Might even
get the students in the pilot to highlight them -- some of the terms
currently in the SN3 material I didn't even mention and others, more
important terms, weren't listed.
o Get materials posted as early as possible, try to give us at least
two weeks to review a module -- teaching and travel schedules don't
really permit anything less getting any reasonable numbers of reviews.
Also, many of us spend a lot of time on the road, away from our
Postscript printers (I just recently returned from 5 weeks at
Microsoft -- no Easynet connection except my PC via Kermit!), so
we need the new chapters or modules occasionally posted in a TEXT
format.
o Contact local training centers, ask the Delivery or Unit managers to
give you an instructor contact for your courses. Talk to them on the
phone (not just mail or notes) about the materials, use them as a
sounding board for teachability (did I make a word?) and technical
issues. No, we aren't all experts, but many of use have years of
expertise with various parts of VMS or other products. Maybe pick out
the noisy instructors in the conferences to help with the rewrites --
It's good marketing to get some of the noise-makers on your side!
Hope this helps...
$
|
| 155.23 | Back to the topic at hand...Chapter 2, DECnet. | SOAEDS::TRAYSER | Seniority: Big Shovel, Less Breaks! | Thu Feb 18 1993 01:54 | 69 |
| Chapter 2 rereview. Mostly Instructor notes issues...
2-4 -- objectives mention SHUTDOWN of DECnet, this wasn't taught here,
but definitely needs to be reviewed near STARTNET.COM.
2-6 -- node name Instructor's note (98.16, 3-6)
Also, need routing and terminology pages inserted here from the old
SN3 book (pages 1-27 - 1-30, even if they are in SN2 now). We are
about to configure the net so we need the review for SN2 folks and
the basic information for non-SN2 students.
2-12 (Instr) -- Instructor note is wrong. Not everything is purged. It
leaves NETNODE_REMOTE.DAT untouched. (98.16, 3-10a)
2-13, 6th bullet (Instr) -- incorrect (98.16, 3-11a)
2-15, 1st sentence -- incorrect (98.16, 3-16a)
2-18, 3rd bullet (Instr) -- incorrect (98.16, 3-12a)
2-22 -- notice the version and date on display. I don't think we've
ever had a T5.5-4, much less in 1991!
2-23, 2nd and 3rd paragraphs from bottom (Instr) -- incorrect (98.16, 3-15a)
2-23, 1st sentence -- An End node knows his router. See last line on
2-24. If you can set host to your router then your system is
properly configured. If you see node "0" as your router, then
you probably aren't configured right (and set host will probably
fail unless you're in an Ethernet LAN with *only* end-nodes and no
routers.)
2-24 (Instr) -- Instructor note incorrect (98.16a)
2-24 -- Need output from an Area Router as well. From the Area Router
in our classroom...
$ SHOW NET
VAX/VMS Network status for local node 63.428 ATLANA on 18-FEB-1993 01:40:56.17
Area Cost Hops Next Hop to Area
1 98 9 MNA-0 -> 33.115 SSTA2
2 64 5 MNA-0 -> 33.115 SSTA2
3 66 5 MNA-0 -> 33.115 SSTA2
....
59 101 7 MNA-0 -> 33.115 SSTA2
60 37 2 MNA-0 -> 33.115 SSTA2
63 0 0 (Local) -> 63.428 ATLANA
Node Links Cost Hops Next Hop to Node
63.428 ATLANA 0 0 0 (Local) -> 63.428 ATLANA
63.52 HELEN 0 4 1 MNA-0 -> 63.52 HELEN
63.53 MACON 0 4 1 MNA-0 -> 63.53 MACON
63.59 CANTON 0 4 1 MNA-0 -> 63.59 CANTON
63.91 SMYRNA 0 4 1 MNA-0 -> 63.91 SMYRNA
63.109 LANIER 0 4 1 MNA-0 -> 63.109 LANIER
....
2-25 (Instr) -- Need reference to LTLOAD in Instructor's note (98.16, 3-17)
2-26 -- summary contains more info on NCP commands than was actually in
the lecture material!!
2-28 (Instr) -- Instructor's note (98.16, 3-18a)
$
|
| 155.24 | And chapter 4...Disk stuff (really a ragged module!) | SOAEDS::TRAYSER | Seniority: Big Shovel, Less Breaks! | Thu Feb 18 1993 02:51 | 28 |
| From one of my notes about 1 year ago, still true...
| Chapter 6 is mostly lifted from the existing SysMgr II course. It jumps
| around an awful lot and doesn't have a focus of "This is a System Manager
| course". A good deal of information is included in this course that is
| best put in programmer courses, Internals courses, Hardware courses, etc.
4-11 -- How about using a disk people recognize, like and RA9x, RA7x or RF7x?
4-19 -- "DISPLAY" is misspelled in the dump (and actually in the hex code as
well)
4-20 (Instr) -- (101.10, 6-15a)
4-20, 4-21 -- (101.10, 6-20, 6-21)
4-26 -- Assign hung out in the 'gutter' -- Ugly.
4-28 (Instr) -- Excellent Instructor's note -- Bravo!
4-30 (Instr) -- Ditto!
4-30 -- Find another home for this stuff -- SN2? SN1? VMS Operator? It
doesn't really belong in this chapter.
4-39 - 4-49 -- (101.8; 101.9; 101.10, 6-41)
|
| 155.25 | Chapter 7 | SOAEDS::TRAYSER | Seniority: Big Shovel, Less Breaks! | Fri Feb 19 1993 01:28 | 77 |
|
Security module...
7-8, 7-9 -- It isn't clear how this info can be discussed at this point.
We haven't really explained how to add identifiers and we are already
concatenating them! We are also removing and adding Rights dynamically.
these are both advanced topics and need to be moved further back in the
chapter.
Move 7-8 back near 7-18
Move 7-9 back near 7-30
7-13 -- (104.5, 8-13)
7-22, 1st dash -- (104.5, 8-19a)
7-24, 3rd bullet -- Shows "another way" to do ACL Editor. However, I can't
seem to find where we showed them the FIRST way yet! This seems to
be discussed in the middle of page 7-25.
7-25, 5th bullet -- Too many parentheses! Should be "(IDENTIFIER="
7-28 -- haven't we already told them about the ACL editor adequately on
pages 7-24 & 7-25?
7-29 -- We need to discuss how (ACCESS=NONE) affects this page. Where does
it fit and how does it work?!
also, we could use some instructor notes here (104.11, 104.12, 104.13)
7-33 -- (104.10)
7-35, 2nd bullet -- we are defining "access control string" on this page, but
we've already introduced it and used it in an example on page 7-34.
7-40 -- (104.8, 8-34)
7-43 -- (104.8, 8-40, 2nd comment)
Also, put back the reference about not using a LOGIN.COM in the
default directory in LGICMD. The only part that was questionable
was the reference to "NL:". (104.6, 8-39, 2nd comment)
7-66 -- Get rid of this page. You pulled it from the SysMan2 course, so here
are the comments from 2 years ago regarding this very page..
<<< SUPER::WORK4:[NOTES$LIBRARY]VMS_SYSMGT_II.NOTE;2 >>>
-< VAX/VMS System Management II >-
================================================================================
Note 50.7 V5.4 SYSMAN II Comments 7 of 19
SOAEDS::TRAYSER "C J 'Buck' Trayser, VMS Tuna" 27 lines 22-JAN-1991 13:36
-< Some more thoughts on module 2 >-
--------------------------------------------------------------------------------
...
The new PASSWORD sysgen parameter belongs in the Security course
along with the other security programs (like the one that replaces
the ERASE patterns which is also found in sys$examples). Move it
to an appendix if necessary, but it is out of place and requires
programmer intervention to work properly.
...
================================================================================
Note 50.8 V5.4 SYSMAN II Comments 8 of 19
51370::APON "dubito ergo sum" 93 lines 23-JAN-1991 09:40
-< answers >-
--------------------------------------------------------------------------------
...
> The new PASSWORD sysgen parameter belongs in the Security course
> along with the other security programs (like the one that replaces
> the ERASE patterns which is also found in sys$examples). Move it
> to an appendix if necessary, but it is out of place and requires
> programmer intervention to work properly.
I fully agree. At that time it was stated that this parameter
HAD to be included in the material, and as a compromise we placed
it there (as bad a place as any other, because it should really NOT
be in this course). Perhaps we may leave it out in the next release.
...
|
| 155.26 | | DBLDOG::DONHAM | Progress Through Tradition | Fri Feb 19 1993 09:31 | 5 |
|
Buck, how are the labs going? Do you have enough equipment to build an MI
cluster?
Perry
|
| 155.27 | Labs: we need more labs and those we have need work! | SOAEDS::TRAYSER | Seniority: Big Shovel, Less Breaks! | Fri Feb 19 1993 16:03 | 8 |
| Actually, the labs this week got pretty poor ratings, not much left
after major portions were moved to the other courses. I've been doing
a lot of demos, configured LAVc systems, run through a DECnet config
while explaining all the steps. I even copied som eof the labs from
SysNet 2 and handed them out (only 1 of my students had taken the 'new'
SysNet 2 course recently).
$
|
| 155.28 | Captiol Ideas | TEACH::LYNN | | Fri Feb 26 1993 17:17 | 4 |
| I think it is a great idea to put the chapter terms in the student
guide. I am very flexible as to whether it is in the front of the
chapter or at the end, the reason...I can introduce the chapter
terms whenever I feel it is appropriate for each individual class.
|
| 155.29 | Capitol Ideas | TEACH::LYNN | | Fri Feb 26 1993 17:24 | 13 |
| I really haven't completely prepped for SN3 (just 3 days) so I haven't
taught this new edition. I do have some concerns I hope you can
address now for me.
Page 1-39 An idication that a larger page/swap file is needed when
"free" value drops to a fraction of the total. Just what does this
very vague statement mean???
Page 1-51 Totally new page for my eyes and mind. How about something
on the instructor's page to inform me how to present this stuff?
Help!
Thanks in advance.
Lynn White
Washington D.C.
|
| 155.30 | Check out VMSTUNING on VMSDEV::, notes 434, 1018, 993, etc. | SOAEDS::TRAYSER | Seniority: Big Shovel, Less Breaks! | Sun Feb 28 1993 00:34 | 34 |
| The phrase 'fraction of the total' is pretty weak. Basically the VMS
page writing/removing algorithms can only use a portion of the page file
before the free space becomes fragmented, possibly degrading performance.
There are various good discussions in the VMS_TUNING conference on this
topic, but are are the basics:
o Reservable space is an indication that *eventually* there may be a
problem because of potential over-commitment of the file, but it may
not be an issue at this time. Usually we ignore the Reservable
value, even if it goes Negative since it is only an indication that
we've 'overbooked' but not 'overused' the page file.
o Rule of thumb...keep the page file 40-50% free. This minimizes
the chance that fragmentation of the free space is causing a
degradation of performance by making multiple 'passes' on the file
to get the proper sized 'slots'. If the file is very fragmented
then the cluster size has to be cut on-the-fly to fit in the
available space. Better that we waste a little file space and be able
to write out up to MPW_WRTCLUSTER number of pages than cutting up the
requests.
Please note that it is possible to run a page file upwards to 80% or 90%
(or higher) utilization without adverse side effects given a 'perfect'
page writing environment where the clusters are written and then removed
in uniform 'chunks'. In practice this is very unlikely, more commonly
there are numerous holes from small cluster writes, pages removed from
the pagefile, etc. The compromise we make since we can't dictate the
activity of the pagefile is to provide MORE than adequate space so
fragmentation poses no problem to the files ability to service the
requested cluster size demands.
Hope this helps.
$
|
| 155.31 | | DBLDOG::DONHAM | Progress Through Tradition | Mon Mar 01 1993 10:39 | 41 |
|
Buck, if you don't mind, I'll add your explanation as an instructor note to that
block.
Regarding p.1-51 in the IG (Determining XMI and VAXBI Information):
The XMI is the system bus, similar to the Qbus. It has a number of slots,
some for CPUs some for memory, and the rest for peripherals. One of the
peripherals that you can pop into the XMI is a BI adapter.
The BI adapter itself has a number of ports, off of which you can hang
things like Ethernet adapters and disk controllers.
To boot a machine such as the 6000 from a device hanging off of a BI port,
you must determine two things:
1. The location of the BI adapter on the XMI bus
2. The port number on the the BI adapter that is attached to
the device
The console command SHOW CONFIGURATION will give you this information.
Unfortunately the sample boot command on page 1-51 is not related to the
SHOW CONFIG command just above it...I'll try to remember to fix that.
Using the example of the SHOW CONFIG command given at the top of the page,
you can see that there is a BI adapter in slot 0D of the XMI. On port 0 of
the BI is a KDB50, which is a disk controller for RAxx disks. If you wanted to
boot the machine from unit 0 on that KDB50, the command would be something
like:
BOOT/XMI:0D/BI:0 DU0
In this case there are no HSCs involved, so you need not supply the HSC node
numbers, such as is shown in the example boot command on 1-51.
I hope this helps...
Regards,
Perry
|