| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 98.1 | Chapter 3 draft available for review
| SUPER::MORGAN | | Thu Jul 18 1991 16:24 | 18 |
| A draft of the third Sysnet III chapter entitled:
Setting Up a Network Node
is available for review in:
SUPER::ES$REVIEW:[SYSNET_III]SYSNETIII_CHAP3.ps
Bonnie
Comments on this chapter:
Pg. 1-6 Has a table on the Configuration Database Files. We are looking into
modifying the description column to include a definition.
Pg. 1-26 We are looking for comments on whether the section "Running DECnet
over Terminal Lines" should be removed. The section is currently
5 pages long.
|
| 98.2 | protection problem | NWGEDU::WIERSMA | Drive a BENTLEY or walk... | Fri Jul 19 1991 04:55 | 8 |
| Hello Bonnie,
Could you please change the PROTECTION mask of this chapter.
Because now I'm not allowed to get me a local copy.
Thanx
Arjen.
|
| 98.3 | protection has been fixed | SUPER::MORGAN | | Fri Jul 19 1991 10:41 | 3 |
| Sorry for the mixup. The file protection has now been set correctly.
Bonnie
|
| 98.4 | Review from Holland | 51370::WIERSMA | Drive a BENTLEY or walk... | Mon Jul 22 1991 08:37 | 155 |
| This is the review of chapter 3:
[1mSETTING UP A NETWORK NODE[0m
Page 1-4 RESOURCES
Bullets 3,4,5 There are still the Postscript codes.
What you mean (?) are:
General User Subkit Volume 4, VMS DCL Dictionary
System Management Subkit Volume 5B, VMS Network Control Program Manual
System Management Subkit Volume 5A, Guide to DECnet-VAX Networking
VMS Networking Manual
Perhaps you can also mention:
System Management Subkit Volume 1A, Guide to Setting Up a VMS System
System Management Subkit Volume 1B, VMS LAT Control Program (LATCP) Manual
Page 1-4 This is again page 1-4(?)
TOPICS
Fourth bullet: LOADNET.COM and RTTLOAD.COM are executed by the
STARTNET.COM procedure.
And you forgot to mention the LTLOAD.COM procedure
under starting the LAT network.
We (some colleagues and me) prefer the following layout:
. STARTING THE NETWORK
- STARTNET.COM
- LOADNET.COM
- RTTLOAD.COM
- Starting the LAT Network
- LTLOAD.COM
Page 1-6a First line TAB setting problem.
OR do you want everybody taking care of this security problem.
I like that one.
Page 1-6 Suggestion.
Change head desription into CONTAINS. And then you can take the
comments of the instructor page to fill in the table.
Page 1-7 There is no figure.
Page 1-19a There are several postscript codes.
line 4,7,8,9.
Page 1-20 There is no figure.
You're not explaining the notes. Only on the instructor page.
Page 1-21 There is no figure.
Page 1-23 Here are the figures:
Figure 1-5 SHOW CLUSTER Display from Node PARIS
View of Cluster from system ID 56324 node: PARIS
+-------------------+---------+----------------------------------+
| SYSTEMS | MEMBERS | CIRCUITS |
+--------+----------+---------+-------+--------+---------+-------+
| NODE | SOFTWARE | STATUS | RPORT | RP_TYP | CIR_STA | CABLE |
+--------+----------+---------+-------+--------+---------+-------+
| PARIS | VMS V5.4 | MEMBER | 5 | CIXCD | OPEN | A - B |
| | | | | ETHERN | OPEN | |
| WINE | HSC V400 | | 0 | HSC50 | OPEN | A - B |
| CHEESE | HSC V400 | | 1 | HSC50 | OPEN | A - B |
| LOUVRE | VMS V5.4 | MEMBER | 4 | CIBCA- | OPEN | A - B |
| | | | | ETHERN | OPEN | |
| FRANCE | VMS V5.4 | MEMBER | 2 | CIBCA- | OPEN | A - B |
| | | | | ETHERN | OPEN | |
+--------+----------+---------+-------+--------+---------+-------+
Figure 1-6 SHOW CLUSTER Display from Node LOUVRE
View of Cluster from system ID 56323 node: LOUVRE
+-------------------+---------+----------------------------------+
| SYSTEMS | MEMBERS | CIRCUITS |
+--------+----------+---------+-------+--------+---------+-------+
| NODE | SOFTWARE | STATUS | RPORT | RP_TYP | CIR_STA | CABLE |
+--------+----------+---------+-------+--------+---------+-------+
| PARIS | VMS V5.4 | MEMBER | 5 | CIXCD | OPEN | A - B |
| | | | | ETHERN | OPEN | |
| WINE | HSC V400 | | 0 | HSC50 | OPEN | A - B |
| CHEESE | HSC V400 | | 1 | HSC50 | OPEN | A - B |
| LOUVRE | VMS V5.4 | MEMBER | 4 | CIBCA- | OPEN | A - B |
| | | | | ETHERN | OPEN | |
| FRANCE | VMS V5.4 | MEMBER | 2 | CIBCA- | OPEN | A - B |
| | | | | ETHERN | OPEN | |
+--------+----------+---------+-------+--------+---------+-------+
Hope this what you want.
Page 1-28a Do mention the sysgen parameter TTY_DEFCHAR2. You should give him
the value of %X20000. Otherwise you don't have the disconnect
characterictic. Best way to do is in MODPARAMS.DAT with the
following line
ADD_TTY_DEFCHAR2 = %X20000
Page 1-30 Reasons ........
You can also mention the parameter mentioned above.
Page 1-37 Your only explaining the notes on the instructor page.
Page 1-38 Your only explaining the notes on the instructor page.
So far the review.
You asked also comments about the Page 1-26 .....
I had some little discussion with our Curriculum Networkmanager (Joop
Rodenburg) and one of our networkspecialist (Kees Ootes). They both said that
you could leave these pages away.
They said that you easily can mention it in a page. And then that's it.
What they really missed was the following:
You never mentioned the CLUSTER-alias name. And how it works with the objects
for instance:
- MAIL
- FAL
- VPM
And of course the executor. Maybe this is discussed in another chapter, but
they would have it mentioned here.
Another thing they told me is the procedure NETNODE_UPDATE.COM. The procedure
necessarry updating network data after adding a satellite. (see System
Management Volume 1B, Vaxcluster Manual page 5-11,5-12)
And this is it. See you in the next chapter.
Bye Arjen.
|
| 98.5 | amendment reply 4 | NWGEDU::WIERSMA | Drive a BENTLEY or walk... | Thu Jul 25 1991 06:55 | 14 |
| Hello again,
This is updating reply 4.
May be it's better to use the new names of the LTLOAD.COM. Because
in the VMS V5.4 it's optional, but in VMS V5.4-3 they make it
obligatory.
The new names are:
SYS$SYSTEM:LAT$STARTUP.COM and
SYS$MANAGER:LAT$SYSTARTUP.COM.
Perhaps this is better.
Then we don't have to update the new material so early.
Bye Arjen.
|
| 98.6 | Adding LAT-startup procedure | NWGEDU::RODENBURG | Ed. Services, The Netherlands | Fri Jul 26 1991 05:20 | 30 |
|
Sorry Arjen,
but to update your entry:
> The new names are:
> SYS$SYSTEM:LAT$STARTUP.COM and
> SYS$MANAGER:LAT$SYSTARTUP.COM.
Better is to say:
(quote)
The LAT-software is loaded and started by the procedure
SYS$STARTUP:LAT$STARTUP.COM. In VMS-versions previous to V5.4-1 this
was done by the procedure SYS$MANAGER:LTLOAD.COM
Using the procedure LAT$STARTUP two other commandfiles are activated:
- SYS$STARTUP:LAT$CONFIG.COM
Loads the LAT-driver and creates the process LATACP
- SYS$STARTUP:LAT$SYSTARTUP.COM
Sets the LAT-characteristics for you system.
LATservice- and LATnode-characteristics can be set in the file
LAT$SYSTARTUP.COM, or by adding parameters to the command
@SYS$STARTUP:LAT$STARTUP.
(end quote)
|
| 98.7 | General comments | SAHQ::HILLMAN | Network partner excited!... | Thu Aug 15 1991 12:42 | 53 |
| Just a few "general" inputs / suggestions...
[page 1-5] We used to explain how NCP>SET/CLEAR and NCP>DEFINE/PURGE
affect the respective databases.. doesn't show up here
until page 1-35a.
[page 1-8] Should we include either on instructor's page OR SG page,
(under END NODE) "doesn't know reachability status".?
<illustrated on page 1-33>
And (under Routing Node) "Consumes more memory (NPP)"
[page 1-11 or 1-11a] Should we remind students that Netconfig.com uses
generated passwords for x$server accounts, and
the possibility exists they MAY NOT be compatible
with other (previously existing) systems?
[page 1-16a] Should we mention that DECnet must set up the device
driver..( and therefore be started first?)
[page 1-18] might mention on instructor's page that a routing node
in a large network might need these values set higher.
[page 1-22] need to explain "port value" - C.I. node address from
large decal on cabinet front. REF [1-22a] - and .i & .j
reflect port address of REMOTE system, as seen from
THIS node...
[page 1-24] I can appreciate using a modified prompt for reference
to show what node we're on, but how about including a
"$" at the end for clarification?
[page 1-25] Should we explain just how we "selected" the C.I.
circuit versus the Ethernet circuit?
[page 1-28a] I experienced errors when I didn't use "TX" device type
if in fact there is a "TXnn" device on the system. I
think NCP complains about "unknown circuit type".
[page 1-31] Why don't we mention that OPCOM reports "circuit up" right
away? (also on page 1-40)
[page 1-34] I usually need to write on the board:
NCP>SET EXECUTOR STATE "x" (because it's not really
obvious from the table)..could it be included in the
table to show syntax??
[page 1-40] 5th bullet: I take exception to "must" in this sentence.
(simply because it works even if you don't - "designated
router"/ "end-node cache" come into play)
7th bullet: OPCOM also notifies us right away.
|
| 98.8 | Capitol Ideas | TEACH::LYNN | | Thu Aug 29 1991 19:16 | 15 |
|
SYSNETIII - SETTING UP A NETWORK NODE
CHAPTER 3
Overall question - Are you assuming the students already have a
background in networking. This chapter appears to be written with
a previous understanding of network concepts/terms. For example on
page 6 you talk about executor node, circuits, lines, objects, sinks,
and X.29/X.25. On the next page you make reference to end-nodes and router.
I don't have a networking background and for me this
is all meaningless. Please supply more background information for the
student.
Lynn White
Washington D.C.
|
| 98.9 | comments from DC (Jim Powers) | TEACH::WENDY | | Fri Sep 13 1991 13:30 | 51 |
|
A. I've reviewed Module 3 "Setting Up A Network" and Module 5 "Managing
Terminal Servers".
B. Both Modules are put together very well. The only problem was with
Module 3, the figures 1-1 thru 1-8 where not in the module as was stated. But
as you and I talked about this on Friday, I'm sure the developers are aware of
that already.
C. The real issue is not with the information in the Modules as much as
what is NOT in the course at all.
The utility that is used to add, modify, change, or monitor the network
is N.C.P. (Network Control Program). There needs to be an introduction to NCP in
the course. They utilize the utility in Module 3 as if you have prior knowledge
of NCP and I'm sure there is going to be alot of students who dont.
The introduction need not be extensive, just the syntax used and some
understanding of what the commands effect. Some of the commands effect the
permanent database and others effect the volatile database.
In the Network Management I course the module on NCP takes maybe an
hour to discuss.
Maybe the developers are already planning the module but since we are
reviewing bits and pieces at a time I felt it important to bring up. Everything
else looks good. The idea of having a review or seminar on the network related
modules for the instructors not up on Networks was a good one and I would be
happy to offer my services if needed.
I hope this was helpfull input. If you need anything else just let me
know.
Jim Powers
|
| 98.10 | The last note | TEACH::WENDY | | Fri Sep 13 1991 13:33 | 5 |
| That last reply was put into notes by me. Jim powers mailed it to
me and I can see I should have edited it before putting it into
notes. Sorry
Wendy M.
|
| 98.11 | | SUPER::MATTHEWS | | Sun Sep 15 1991 12:42 | 6 |
| Feedback from Sys/Net II indicated that students want the introductory
material on NCP there, so we are adding it. Therfore they will have
seen NCP by the time they get to Sys/Net III.
Val
|
| 98.12 | UK's halfcrowns worth... | UKEDU::HARMER | Geoff Harmer U.K. Edu (830) 6229 | Wed Sep 18 1991 12:02 | 68 |
| Generally this is looking good. Previous replies have noted
errors.
We agree with comments about ASYNC in an earlier reply.
You should remove all reference to ASYNC Decnet it is a specialist
topic ( and is not in PHase V in any case so we should discourage its
use)
You could also remove the CI section...this is rarely used now that
all acces to systems is via Decservers. So if your Ethernet fails there
is no point in having a failover CI Decnet link. Keep this sort of
stuff for the Network Specialist Course which will still be needed !!
Minor stuff
-----------
p 1-33 Add "SHOW NETWORK can be used as a diagnostic aid to check
if your node can reach other nodes. In the case of an END NODE the
SHOW NETWORK display should show the address of a Routing node and NOT
0 "
-----------------------------------------------------------------------
Major concerns
---------------
A concern of Phil Stothart and myself in UK is that the module is
entitled Setting Up a Network Node; yet important areas like Network
OBJECTS and Event LOGGING are exluded.
Is it your intention to put these topics in SYSNET IV ? We think that
is too late.
In our experience incorrectly set up OBJECTS in a Cluster environment
is a most frequent reason why MAIL, FAL etc don't work...
...i.e. failure to understand the mechanism by which network objects are
invoked.
We're not asking for the Net security chapter from Netman I; but just a
simple discussion of:
a. What an object is.
b. Figure showing how objects look when you take defaults at NETCONFIG time
(output of NCP>SHOW KNOWN OBJ CHAR from a BYPASS account )
Notes on what FAL , MAIL etc. are for.
c. Mention that if there is not an account on an object then the object
can only be used if there is an EXECUTOR NONPRIVILEGED USER and
EXECUTOR NONPRIV PASSWORD set up.
-------------------------------------------------------------------------
On EVENT LOGGING
Some simple discussion of Event Logging should also be included:
3 or 4 pages only.
a. What it is. EVL process, Event class and type and sample event
message. Mention of logging MONITOR,CONSOLE and FILE very briefly
b. What you get at NETCONFIG time
( output from SHOW KNOWN LOGGING)
c. How to alter standard logging.
NCP> PURGE/CLEAR LOGGING MONITOR EVENT 0.9 for example
NCP> DEFINE/SET LOGGING MONITOR EVENT 7.0-11
How to control logging:-
NCP> SET LOGGING MONITOR STATE OFF
NCP> SET LOGGING MONITOR STATE ON
|
| 98.13 | Review Cutoff Date
| SUPER::MORGAN | | Thu Sep 19 1991 17:28 | 10 |
|
In order to make the pilot schedule, Monday 9/23/91 will be the
review cutoff date.
Any comments entered after that date will be considered after the
pilot.
Thanks for all of your comments,
Bonnie
|
| 98.14 | Comments from The Netherlands | NWGEDU::RODENBURG | Ed. Services, The Netherlands | Fri Sep 20 1991 07:12 | 169 |
|
I have already put some remarks about the general setup of this chapter
in entry 94.*
I hope, you read that entry too.
To work with the current chapter, here my remarks:
1-6 Title is: The Network Configuration Database,
must be: The DECnet Configuration Databases
first line: see above
Include also on the student page in table:
NETX25.DAT X.25 database and X.25 server
information. Only available when
PSI software has been installed.
NETX29.DAT X.29 server information. Only
available when PSI software has been
installed.
1-11 Include comments on the instructor page how to address the questions
about the objects.
Include comments that for the level of the students of this course you
have the choice:
create a default DECnet account
or
create a default account for the different network
applications.
Why to create different default accounts for the objects?
Only when you want to disallow default network access for some
objects, then you have to answer NO for the default DECnet account, and
YES to only those accounts, allowed to be used accross the network.
1-17/18 Why to include all these steps? Is not usefull, as the student is not
knowledgeable at this level or does not need al this info.
Is absolutely not usefull at this level.
How does he know about SCS node etc., where did you tell him about
this?
Too much information.
Better:
(quote)
STARTNET.COM
STARTNET.COM performs the following tasks:
1. Checks for sufficient privileges.
2. Executes @SYS$MANAGER:LOADNET
to load the drivers needed, and to start the NETACP-process
3. Configures the volatile database using the information in the
permanent database
4. Defines logicals needed for down-line loading
5. Executes @SYS$MANAGER:RTTLOAD
to start the process REMACP, to accept incoming remote terminal
requests.
(endquote)
1-18 Skip it.
1-19 Starting the LAT Network
Already said by me in entry 98.
Update this page for V5.4-1 and later by adding the lines:
(quote)
In VMS-versions from V5.4-2 LTLOAD.COM only displays an informational
message and submits the command @SYS$STARTUP:LAT$STARTUP.COM.
Using the procedure LAT$STARTUP two other commandfiles are activated:
- SYS$STARTUP:LAT$CONFIG.COM
Loads the LAT-driver and creates the process LATACP
- SYS$STARTUP:LAT$SYSTARTUP.COM
Sets the LAT-characteristics for you system.
LATservice- and LATnode-characteristics can be set in the file
LAT$SYSTARTUP.COM, or by adding parameters to the command
@SYS$STARTUP:LAT$STARTUP.
(endquote)
page 1-20
Title of topic is OK.
Contents can be better by mixing it with the info on page 1-36.
and by changing point 1. By the way: it is not required to be
an adjacent node.
Change the two points on this page as follows:
(quote)
1. Look for a reachable node having an up-to-date remote-node
database.
2. When 55.4 is such a node, then copy the permanent remote-nodes
database from the remote node:
NCP> COPY KNOWN NODES FROM 55.4 TO PERMANENT
NCP> COPY KNOWN NODES FROM 55.4 TO VOLATILE
NCP> COPY KNOWN NODES FROM 55.4 TO BOTH
(endquote)
In my opinion information about CLUSTER Alias need to be included,
and information about the use of the FAL- and VPM-object.
1-20/1-39
Has been completely copied from the course EY-A946E
Is the old product-oriented style usefull? In my opinion:NO
Use only the items usefull for the intended audience in the
scope of this course.
More specific:
1-21/1-25
Leave it out this course. Only interesting for network specialists.
See previous comments in the notesfile.
1-26/1-30
Leave it out this course. Only interesting for network specialists.
See previous comments in the notesfile.
1-31
Title perfect.
The paragraph about NCP commands are not usefull:
What can a student in this course see with the command
NCP SHOW EXECUTOR CHARACTERISTICS?
NCP SHOW KNOWN CIRCUIT CHARACTERISTICS?
NCP SHOW KNOWN LINE CHARACTERISTICS?
He will get a lot of information that is unreadable-for-him/her.
What is usefull for him/her:
(quote)
NCP SHOW EXECUTOR
NCP SHOW KNOWN CIRCUITS
NCP SHOW KNOWN LINES
(unquote)
Here the state of the component is visible. The deeper
characteristics are only interesting for the network specialist.
1-32
need to be updated for V5.4-2, because of the LATACP process.
In comments on point 3 can better be included:
- Used for incoming requests by SET HOST
1-33
EXAMPLE 1-5 need to be filled in with nodenames, as the NCP COPY
command has been issued.
1-34 Not interesting for the student of the intended audience.
1-35/1-39
Is exactly the same info with the same errors as already included
into SYSNET II.
Skip it here!
Changing network characteristics (node name/address) of the
executor must be done by a network specialist. If you don't
believe, just type in the example and explain the errormessages...
Joop
|
| 98.15 | Remarks concerning the networking chapter | NWGEDU::RODENBURG | Ed. Services, The Netherlands | Fri Nov 08 1991 09:49 | 56 |
|
Here are my comments about the new materials. I am very positively
suprised. Several remarks have been used to change this chapter.
I appreciate the way our comments are used to make the materials
better. This way is very stimulating for us to make time available to
review the material.
However, I still have several remarks:
- The list of DECnet has disappeared. I don't see why this
has been done. In my opinion a paragraph about DECnet Configuration
databases is still usefull to start with.
- repeated again: 3-10
Include comments on the instructor page how to address the questions
about the objects.
Include comments that for the level of the students of this course you
have the choice:
create a default DECnet account
or
create a default account for the different network
applications.
Question:
Why to create different default accounts for the objects?
Answer:
Only when you want to disallow default network access for some
objects, then you have to answer NO for the default DECnet account, and
YES to only those accounts, allowed to be used accross the network.
- 3-14/17: Very good: a very few number of steps listed, only those steps
which are usefull for the student
- 3-18: positive changes have been made
I saw that the CLUSTER ALias is discussed in the Cluster
Chapter
- Looking back to the previous pages: talk very globally about objects,
just to make clear to the students why to choose a default account or
not for that specific object.
Do NOT include object information to do troubleshooting, because is
NOT the goal of this course, and must be done by a networking
specialist.
- Looking at the last pages: perfect!
With this information the system manager can understand how to handle
with network specific items, important for him as a system manager.
Several items are not discussed, but need to be discussed seperately
for the network specialists.
Ok, thats my comment. Looking forward to the new review...
Joop
|
| 98.16 | Reviewing continues -- the *DECnet* chapter | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Wed Feb 19 1992 02:59 | 155 |
| Well, well, well, this chapter is just full of small mistakes and oddities.
Overall a usable chapter, but a bit thin in details -- I sure hope they
remember everything they were SUPPOSED to have learned from SysNet II!! This
chapter really needs to have the title changed to reflect that it is a DECnet
topic. The word NETWORK is terribly misleading, as it could imply LAT, TCP/IP,
or anything.
3-4, 3-5, Objectives --
Anyone notice the TOPICS are just rewordings of the OBJECTIVES? Is
this intentional?
What happened to "A Common Sense Guide to Network Management" in the
reference list?
3-6, 1st bullet --
"(1 to 6 characters)" needs to be ALPHA-NUMERIC characters. Dollar
signs, questions marks, etc. are CHARACTERS. Also, mention either
here or on the instructor's page that the name MUST include at least
one alphabet character - a node name of all numbers is illegal, because
of how node numbers are stored/used.
2nd bullet --
The address ALSO must be UNIQUE, just as was stated for the name in the
previous bullet.
3rd bullet --
Phrases like "lower overhead" and "consumes more memory" will only lead
to the obvious question of "By how much?" Please put quantitative info
on the instructors guide - ball park type guess would be fine! Just need
something after these 'global' statements.
3-7, 2nd bullet --
So? Priv's? What about them? What are we aiming to get across here?
We need the list (rather short) of the priv's that each requires. I'd
take it on either this page or instructor's page. Chapter 3 in the Net
Mgt I course has the info.
3-9a, 3rd bullet --
This says that DECnet must be stopped prior to registering the license.
Sorry, not correct. The license can be installed at any time. DECnet
doesn't LOOK for the license except when trying to activate the Lines
and Circuits. Install it anytime, but don't really expect DECnet to
run "right" until you restart DECnet.
3-10a, 2nd bullet, 1st sentence --
Wrong & conflicts with first 2 points on top of page 3-7, which are a
more accurate statement.
3-10, 3rd bullet --
This says "NETCONFIG.COM does the following:", which is misleading.
NETCONFIG builds a temporary file, based on user input, and when it's
executed, will perform steps 1-6. THEN, after building the file,
NETCONFIG shows it to us, and THEN will do steps 7 (run the file) and
step 8 (turn it on). Item 7 references a file, and if you read down
the page you are not aware that none of those items actually get done
until step 7. We need to get this "rewritten" to let them know, up
through step 6 nothing has been done, it all gets done at step 7.
number 3 --
Incomplete list, misleading. Adding "such as:" to the end of the sentence
will help.
3-11a, 1st bullet --
Incorrect. It does save NETNODE_REMOTE.DAT.
4th bullet --
Incorrect. SET HOST 0 will work as well as most NCP commands that don't
try do deal with the Data Link/Physical Layers. Lack of a license keeps
the circuit/line pairs from being activated.
5th bullet --
Duplicate of 2nd bullet on previous instructor's page.
3-11, example, 1st question --
Why is there a node name offered of S15VMS? This implies that a node name
has been placed in SCSNODE. Under normal circumstances we shouldn't
encounter this. And if we do, we should have SCSNODE and the DECnet name
set the same. Eliminate the default of S15VMS from the first question.
3-12a, 3rd bullet --
Incorrect. NETCONFIG.COM (as of V5.4-2) tells me NOTHING of how to deal
with the circuit. It only sets up the line and give me no hint or tip
on setting up the CI circuit.
5th bullet --
Use this with care if in a VAXcluster. The details are on the top of the
next page, I'd suggest moving 3-13a into this bullet.
3-15a, 3rd bullet from bottom
"...or an Ethernet node..." is incorrect. I boot numerous end nodes on
Ethernet and I don't get the VOLUMINOUS "adjacency" messages that I will
normally get on my routers. Please define a bit more clearly what is
intended here? Are you saying Routers and Ethernet Routers? All endnodes
and no routers?
2nd bullet from bottom --
Same as 2nd bullet from top.
3-15, 1st line --
"...(if you have purchased...", actually DECnet will start REGARDLESS of
whether you have purchased it or not. It has has nothing to do with a
PURCHASE. If you run STARTNET, DECnet starts. If you have a license,
you have access to more/all of the DECnet features than if there is not
a license installed. Nothing to do with a purchase; nothing to do with
a license. Yes, MORE works with a license, but DECnet does start without
one.
3-16a --
Not entirely correct. DECnet must gain access to the Ethernet device
and get the line and circuit set up *before* LAT does. Specifically, I
have my STARTNET submitted and then 45 seconds later I submit my LTLOAD.
After 45 seconds (seen by testing on my system) STARTNET is finished with
the LINES, CIRCUITS, etc. and is now doing SET KNOW NODE ALL, which can
take 10-20 minutes on various nodes in my VAXcluster.
3-17, 1st line --
"@SYS$STARTUP:LAT$STARTUP.COM" is for the LAT-Master product. On V5-4
it was OPTIONAL software. It is now the standard software for V5.5. For
the previous software @SYS$STARTUP:LTLOAD.COM was the command. We need
to keep the references for this on the instructors page for a year or so.
Last line --
You can also customize the file LAT$SYSTARTUP.COM, as it is a template file
for System Managers to work with, much like LTLOAD used to be.
3-18a, Last line --
Please note:
1) This file is usually protected with NO world access.
2) Sys$System is a search list, and this command will put the file in
Sys$Specific:[SYSEXE] -- not normally the desired result in a cluster
where it is often put in Sys$Common:[SYSEXE].
3) The COPY KNOW NODES commands (on the student page) is the preferred
way as it only copies the node name/number pair. The NETNODE_REMOTE
file contains hardware addresses, remote node usernames/passwords,
verification passwords, etc.
...so this is not the best choice, but is an option.
3-21, ex 3-3 --
These COSTS are abnormal. Ethernet costs are normally 3 or 4, why are
these set to 1? Please give a normal, standard display here.
Lots of little nits, but nothing too terrible. If you know how DECnet really
works you can teach from this material. But the new instructors to this course
will find this module somewhat confusing and contradictory to how DECnet really
works. I'm concerned about what is NOT in this module (datafile names and
locations, NCP commands and displays, architecture information, etc.).
I'm planning on merging the last 1/2 of module 1 into this chapter or I'll
discuss it after this module (not sure yet), so it might be fat enough to
feel like I've actually taught the students DECnet stuff!
$
|
| 98.17 | Spotted one during lecture... | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Wed Feb 26 1992 01:35 | 6 |
| 3-12, 20th line --
"DEFINE OBJECT PHONE..." is not preceeded by "$ RUN SYS$SYSTEM:NCP".
I suspect it was deleted during editing, because the commands as
they are listed will not define the Phone object correctly.
$
|
| 98.18 | | SUPER::MATTHEWS | | Tue Mar 03 1992 15:26 | 12 |
| >I'm concerned about what is NOT in this module (datafile names and
>locations, NCP commands and displays, architecture information, etc.).
Check out the network chapter in Sys/Net II. I guess we should get the
unwritten implication into writing: instructors should learn these
courses from I through III if possible, because of the dependencies
each has on the previous. (Might you be in a similar situation if you'd
had to teach System Mgt II without having done I before?)
Good points all; we're using this info to fix the TBI version.
Val
|
| 98.19 | SN2, maybe. SN1, probably never. | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Tue Mar 03 1992 22:35 | 20 |
| Good point Val, but reality strikes...
What level skill (course background) is required for an instructor to
teach SysNet 3 sucessfully? Well, by the time you have all the proper
background, you find yourself actually teaching those high-level courses
*only* and not having 1) the desire, 2) the time, or 3) your manager's
blessings to study and teach courses already covered adequately by other
instructors. For example, except for a custom course I taught last
January (14 months ago!) I have not taught or SysMgr I in over two
years, and U&C getting close to 3 years.
I doubt I'll ever teach SysNet 1 (unless a business need forces me), I
might teach SysNet 2 once or twice, but I'll be teaching SN3 once a month
for the next 4-6 months until we get others trained on the course.
PLEASE put in the instructor's guide what background info has been
covered. Yes, I reviewed those courses before prepping for SN3, but I
didn't study them close enough to remember how deep the various
discussions on all these topics went.
$
|
| 98.20 | give us more, more, more.... | MELKOR::SWIERKOWSKIS | | Wed Mar 04 1992 21:46 | 38 |
| >I'm concerned about what is NOT in this module (datafile names and
>locations, NCP commands and displays, architecture information, etc.).
> Check out the network chapter in Sys/Net II. I guess we should get the
> unwritten implication into writing: instructors should learn these
> courses from I through III if possible, because of the dependencies
> each has on the previous. (Might you be in a similar situation if you'd
> had to teach System Mgt II without having done I before?)
>
> Good points all; we're using this info to fix the TBI version.
>
> Val
I still think this point is valid. Yes, SYSNET II does have bits and pieces in
the network chapter; however, there is no architecture information and it only
mentions NETNODE_LOCAL.DAT and NETNODE_REMOTE.DAT. Unless the instructor adds
the rest (page 3-5 from NETWORK MANAGEMENT I), the students really don't get a
good idea of what the SHOW/LIST CLEAR/PURGE SET/DEFINE commands do later in the
module. Most people don't make the connection between the network components
and the file names unless you hit them over the head with it. Page 3-5 should
be added to both SYSNET II (for clarification) and SYSNET III (for quick
refresher).
I really don't know where the architecture should go. If we stick to the
cookbook model, it doesn't belong anywhere; however, most of my smarter students
have already noted that without the "why", they won't be as good at
troubleshooting later on. In fact, the more advanced students normally state
during the introductions on Monday morning that they came to class specifically
to get the "why", that they've been doing the "what" for a long time now without
any understanding, but that opens up the whole philosophy question again....
The third point: yes, we do have NCP commands and displays in SYSNET II, but we
still need some examples in SYSNET III. I'm prepping for my first teach of this
class and expect to spend a lot of time at the copy machine making handouts to
supplement the material.
Susan Swierkowski
|
| 98.21 | Network lab that worked. | MELKOR::SWIERKOWSKIS | | Thu Apr 23 1992 15:23 | 88 |
| Buck,
As promised, here is the lab I used last week. It isn't perfect, but it
WORKED! Just put it through RUNOFF if you want to use it....
Susan
_______________________________________________________________________________
.NO NUMBER
.NO PAGING
.LITERAL
Configure DECnet Lab
Work with your assigned team on this project.
1. Elect a typist. The typist must agree to only enter commands as directed
by the team. The typist is, of course, a team member and should
participate in the discussions.
2. On the system(s) assigned to your team:
A. What is the DECnet nodename?
B. What is the DECnet address?
C. What is the name of the node that contains an updated copy of the
remote node database? See your instructor for this information.
3. Plan your node configuration. Keep the same DECnet nodename and address.
Do not change your name and/or address without checking with your
instructor first. Otherwise, you could end up breaking the Training
Center Network and/or your own node.
A. Plan your DECnet security. Will you allow a default DECNET account?
FAL$SERVER? etc.? Refer to the example NETCONFIG.COM session in your
student guide for further information.
B. Decide on your Executor TYPE (NONROUTING IV, ROUTING IV, Area) What
do you need to do to make your node an Area Router?
4. Configure your node. Log into the SYSTEM account. (See your instructor
for the password.)
$ @STAFF_DISK:[SWIERKOWSKIS]CLEAR_DECNET !Give your node amnesia
$ @SYS$MANAGER:NETCONFIG !Define your DECnet environment
5. Finish your configuration by copying the remote node database from the
system in question number 2.
6. Rename your remote node database and object database from the specific
root to the common directory.
7. Shut down and reboot to ensure a proper configuration.
8. Verify your configuration:
$ SHOW SYSTEM
$ SHOW NETWORK
$ SET HOST 0
$ DIR 0""::
.END LITERAL
|
| 98.22 | PS to previous reply | MELKOR::SWIERKOWSKIS | | Thu Apr 23 1992 15:29 | 11 |
| Oh yes, the CLEAR DECNET command procedure I use simply wipes out the
existing information in the DECnet d/b as NETCONFIG does, and also removes
the accounts from SYSUAF and deletes the directories for all the default
accounts. It resets the system so they have the illusion they are starting
from scratch. They can also do this over and over if they want to. I once
had a student spend a whole Friday afternoon doing this until she felt she
could do it in her sleep. Since she had to start configuring all her network
nodes the next Monday, this was an ideal opportunity for her to make mistakes
and learn from them.
Susan
|