| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 100.1 | Chapter 5 draft available for review | SUPER::WTHOMAS | | Tue Aug 13 1991 15:47 | 12 |
|
A draft of the fifth Sysnet III chapter entitled:
Managing Terminal Servers
is available for review in:
SUPER::ES$REVIEW:[SYSNET_III]SYSNETIII_CHAP5.PS
Wendy
|
| 100.2 | ex | UKEDU::HARMER | Geoff Harmer U.K. Edu (830) 6229 | Wed Sep 18 1991 13:12 | 25 |
| This module addresses the subject well.
There may be some issues around The Decserver 90L (DEChub) which doesn't
downline load its all in ROM. And its 1 session only per port.
Joop's comments in 98.* about new way LAT is started need applying here
as well.
p 5-25 SET SHOW AND CLEAR are not possible in TSC. Only DEFINE LIST
and PURGE ( in the DS500 manual I looked in...I have no hands
on experience)
p 5-26 I'd prefer to see DEFINE used as this is the only certain
way to ensure the changes are permanent. Although you'd have
to use TSC to do it on a DS500.
Also SESSION LIMIT is the total for the server so 4 is a
ridiculous value. 32 is better.
p 5-27 Put the Instructor notes 1-9 as a student page.
p 5-28 Better to use DEFINE and to add that LOGOUT PORT 8 should
be used afterwards.
You can't SET a port that you aren't logged into on a DS200.
Remove VERIF ENA it is of limited use.
|
| 100.3 | Review Cutoff Date | SUPER::MORGAN | | Thu Sep 19 1991 17:32 | 11 |
|
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
|
| 100.4 | Comments from The Netherlands | NWGEDU::RODENBURG | Ed. Services, The Netherlands | Fri Sep 20 1991 07:27 | 71 |
|
First question evaluating this chapter is:
What is needed for the student to do his job, to work with terminal
servers?
Now this chapter includes too much info about the product itself.
The student of this level will be confused at the end.
First we need to define the tasks he has to do?
He/she must be able to
- install a new terminal server
- monitor terminal server status
- configure a printerport on a terminal server
- set up a printqueue on a terminal server
Why are the objectives of this chapter in the current version defined
in a product-oriented way? In my opinion because it has been
copied without modification from the EY-A946E: DECnet Management course.
Let's first have a look at the objectives, listed in the module:
- Describe the terms and concepts associated with terminal servers
- Install terminal server software on the load host
- configure terminal server software characteristics
- configure a server port for a printer device
- set up a print queue for a served printer
My reaction:
No student will have the task to configure terminal server software
characteristics. Better to say: he will have the task to configure
terminal servers to enable users to communicate with a computer
system, and that in different scenarios, for instance: with fixed or
flexible terminalconnection.
This defines the way how the subjects must be presented. When we
talk about task-oriented courses it is rather discutable to include
simply complete chapters from a product-oriented course in a
task-oriented course.
In my opinion several item from the current chapter can be used, but
the chapter must be re-aranged and re-defined.
In my opinion the contents of this chapter, based on my objectives,
must be:
* LAT-software terms and concepts
- Service nodes
- Terminal servers
- LAT software on a VMS node
* Installing a terminal server
- Installation overview
- Pre-installation tasks
- Configure the Load Hosts database
- Downline loading the server
- Post-installation tasks on the server
- Post-installation tasks on the VMS-node
* Monitor terminal server status
- In local mode on a local port
Example: SHOW SERVER
SHOW SERVER COUNTERS
MONITOR SERVER STATUS
- Using the remote console port
Example: NCP CONNECT NODE SERV01
- Monitoring users
- Monitoring ports
- Initiating a downline load
* Configure a printerport on a terminal server
- Define the server- and portcharacteristics
- Create and test LTA-port
- Set up a printqueue on a terminal server
|
| 100.5 | Server labs for review | SUPER::MATTHEWS | | Sun Sep 29 1991 14:33 | 530 |
| Fair comments in .4, and I suspect we won't get a chance to address
them until after the pilot since they would require more rewriting than
we have time to do. In the meantime I'm updating this chapter for LAT
V5.4-1 and incorporating the comments in .2.
The DECnet course had no exercises on this chapter, so I've written
a few (below, for review). Ideally the exercises should test what we
think the real objectives are.
- If "configure a printer port" is an objective, then "set up a
service for interactive login" should be one too; the proposed labs
address both. Another lab deals with server status; there are a
few more commands to be added but it's a start.
- I don't think anyone will do a lab on installing the DECserver
software, so maybe we should keep that objective to "understand
the steps involved in..."
- There should also be some written exercises on terms & concepts; I
may not get to those until after the pilot.
Val
Laboratory Exercises for Managing Terminal Servers
Laboratory Exercise 5-1-Creating a Service
Perform the following exercise if you have access to
an interactive terminal connected to a terminal
server. It does not require privileged access to the
server.
1. Use LATCP to set up a service whose name is the
same as your user name. Set it up on at least two
nodes of the cluster.
2. On the terminal server, find out whether the
service you created is available to the server and
port you are using. (If not, find out why and
remedy the problem.)
3. Connect to the service and log in. Which node are
you connected to?
4. Without terminating your current session, return to
the server's local prompt and connect to another
node that offers the same service.
5. Delete the service you created (without disrupting
any other LAT services on the system).
Managing Terminal Servers 1
Solution to Exercise 5-1
TBS
2 Managing Terminal Servers
Laboratory Exercise 5-2-Setting Up a Printer
This exercise requires access to two terminals
connected to a terminal server (not necessarily the
same server.) If you do not have the use of two
terminals by yourself, do this exercise with a
partner. The exercise also requires privileged access
to a terminal server.
1. Choose one of the terminals to act as a printer.
(It does not need to be a hard-copy terminal.) Set
up a service on the terminal server called
username_PRINT, using your own user name. Assign
that service to the terminal port to which your
chosen terminal is connected. Also make sure the
port characteristics are properly set for printing.
2. On a VMS system, use LATCP to set up a port that
can be used to print to your chosen terminal.
3. On the same system, set up a print queue that
queues jobs to the port you created with LATCP.
Give the queue the same name as your user name.
4. Test your work by submitting a small text file to
the queue you created. It should appear on your
chosen terminal.
5. Delete the print queue and the LAT port on the VMS
system.
6. Delete the service you created on the terminal
server, and restore the terminal characteristics so
that it functions as an interactive terminal. Log
into the terminal to make sure it is usable.
Managing Terminal Servers 3
Solution to Exercise 5-2
TBS
4 Managing Terminal Servers
Laboratory Exercise 5-3-Other Server Management Tasks
Perform the following tasks at an interactive terminal
connected to a terminal server. You do not need
privileged access to the server.
1. Use server commands to answer the following
questions:
a. What service groups are accessible to the port
you are logged into? The server?
b. What services are available to the port you are
logged into?
c. What host nodes are reachable from this server?
d. What services (if any) are offered by this
server?
e. What is this server's name and Ethernet address?
f. What is the server's node limit and has it been
reached? What does this limit represent?
2. Use LATCP commands to answer the following
questions:
a. What is the name and identification string for
each service offered by this node?
b. What service groups does this node belong to?
3. On the VMS system:
a. Use the remote console facility (RCF) to connect
to the terminal server.
b. Log in and verify that you are connected to the
server you specified.
Managing Terminal Servers 5
c. Log out and disconnect the RCF session.
6 Managing Terminal Servers
Solution to Exercise 5-3
o
a.
Local> SHOW PORT
.
.
.
Authorized Groups: 48,100,123
(Current) Groups: 48,100,123
.
.
.
Local> SHOW SERVER
.
.
.
Service groups: 123, 127-129
.
.
.
b.
Local> SHOW SERVICES
Service Name Status Identification
ARTHUR Available ARTHUR -- King of the Britons
ASDSYS Available Advanced System Development Cluster
BARTOL Available Welcome to VAX/VMS V5.4-1
.
.
.
Managing Terminal Servers 7
c.
Local> SHOW NODES
Service Name Status Identification
ARTHUR Available ARTHUR -- King of the Britons
BARTOL Available Welcome to VAX/VMS V5.4-1
.
.
.
d.
Local> SHOW SERVICES LOCAL
Service Name Status Identification
LPRINT Available Letter-quality printer
e.
Local> SHOW SERVER
.
.
.
Address: 08-00-2B-12-61-D4 Name: S178 Number: 0
.
.
.
f.
Local> SHOW SERVER
.
.
.
Node Limit: 150
To find out whether this limit is reached, enter
SHOW NODES and count the nodes listed in the
output.
8 Managing Terminal Servers
This limit represents the number of nodes
accessible by the server. If you were to add a
new node to the Ethernet and start the LAT
software on it, it would not be accessible
through any server that has already reached its
node limit.
o
a.
$ RUN SYS$SYSTEM:LATCP
LATCP> SHOW SERVICES/LOCAL
Service Name Status Identification
---------------- ----------- -----------------------------------------------
ASDSYS Available Advanced System Development Cluster
BARTOL Available Welcome to VAX/VMS V5.4-1
b.
LATCP> SHOW NODE
.
.
.
Service Groups: 123
.
.
.
o
a. Substitute your server name for S178 in the
following examples.
$ RUN SYS$SYSTEM:NCP
NCP> CONNECT NODE S178
Console connected (press CTRL/D when finished)
<RETURN>
DECserver 500 Terminal Server V2.1.5 - LAT V5.1
West Building, first floor
Managing Terminal Servers 9
Please type HELP if you need assistance
Enter username> Stuart
Local>
b.
Local> SHOW SERVER
DECserver 500 V2.1.5 LAT V5.1 ROM V1.0.2 Uptime: 0 17:48:54
Address: 08-00-2B-12-61-D4 Name: S178 Number: 0
Identification: West Building, first floor
.
.
.
Local>
c. Log out and disconnect the RCF session.
d.
Local> LOGOUT
Local -020- logged out port 0 on server S178
DECserver 500 Terminal Server V2.1.5 - LAT V5.1
West Building, first floor
Please type HELP if you need assistance
Enter username> <CTRL/D>
NCP>
10 Managing Terminal Servers
|
| 100.6 | Comments about the terminal server chapter | NWGEDU::RODENBURG | Ed. Services, The Netherlands | Fri Nov 08 1991 10:18 | 79 |
| Val,
I must still go through the exercises of this chapter, so you will
receive my comments on it.
About the chapter I found in the latest preliminary material some
comments. I know, you are working on another update, maybe you can
already use it, otherwise I will have a look at the new material when
I receive it.
I will not go into details about dots and words for this chapter, but
point to larger points:
Set up of this chapter in general is not what I wanted to be (see note
.3) I will not repeat it.
I am still not positive about one of the objectives of this course:
- configure terminal server software characteristics
page 5-6:
why only talk about DS200 and DS500?
Better to talk about most common terminal servers. (DS200 and
DS300). Talk about the DS500 only in an appendix to this chapter.
Now it is too confusing.
page 5-14: why a separate example about INVOKING DSVCONFIG?
Better make one example about adding a Server using DSVCONFIG.
Then give on one page the lines of the current examples 5-5, 5-6,
5-8 and 5-7 (with the entry added in 5-8 entered into it).
This will give a better to read page.
page 5-16: completely skip it. It is too much. The will understand it
when he sees the menu items in the previous example.
page 5-17: I don't think it is usefull in this course to talk about the
restore item. Leave it away.
page 5-18/19:
- Change the items about how to start OPCOM. This is realy basic...
- people didn't hear about logging before, why include it here?
Leave it away. The default on a standard VMS system is already
that this logging events are already there.
page 5-23:
Skip the verifying the downline load, because I don't do this by
giving the command TEST PORT etc. Here are some items mixed up.
All important items about Downline loading are already listed on
page 5-22 in the example.
page 5-24: don't use a Decserver 500, but a Decserver 200. That is more
usual for the customers.
page 5-25:
Leave the TSC away. It is too confusing, only usefull for the
DECserver 500.
page 5-26:
Leave it away, not important.
page 5-27/30: Okee
page 5-30: leave it away, is DECserver 500.
page 5-32: Ok, but refer only to ONE example, now it is too much.
page 5-34/36:
Give only one example. In this chapter it is confusing to see three
examples how to set up a printer port. The two examples about a
setup in a cluster environment are not realy of added value.
page 5-37:
Update the table, by adding the SERVER NAME.
Thats it, folks,
Joop
|
| 100.7 | Not much to say except we need info on the DS90 | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Fri Feb 21 1992 23:52 | 31 |
| This is basically the DECserver module lifted right from the Net Mgt I
course. I've taught that course and chapter numerous times (including today!)
and I find found it rather easy to teach. The favorite topic of the students
is always how to set up the LAT printer queues. I get question on the 200,
300 and 500 series, so don't remove the references to the 500 too quickly.
If it goes to the Appendix, I won't complain, but we need the info at least
in the DECnet class.
My only real concern is that the new DECservers (Model 90) have been shipping
since about last June and they aren't mentioned. They are easy to use as
normal servers, but putting queues on them needs to be addressed in the
module.
5-21 --
Format problem near bullet #2
5-25a, 3rd bullet, 2nd line --
typo - "Read ATt Version..."
5-30 --
How about a short explanation of /LOGICAL either bulleted or on the
instructor's page?
5-31, last line --
Huh? This seems to be an item best intended for the instructors page.
What is the "PAUSE" problem anyways?!
5-34 --
According to the Customer Support Center all characteristics (such as
verification, autobaud, etc.) should be disabled except for INPUT FLOW
and OUTPUT FLOW.
|
| 100.8 | | SUPER::MATTHEWS | | Wed Feb 26 1992 10:02 | 12 |
| Again, useful comments, and we'll fix all those things in the next rev.
>5-31, last line --
> Huh? This seems to be an item best intended for the instructors page.
> What is the "PAUSE" problem anyways?!
I seem to remember getting a written review from someone asking for
this information to be added, but I forget who and why. Seems
reasonable to move it to the I-page if I don't find a better
explanation of it.
Val
|
| 100.9 | Lab only works on New LATCP... | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Sat Feb 29 1992 00:28 | 9 |
| Page 12-25, a & b --
These commands only work on LATmaster software (the optional stuff
since V5.4-x), so if you have the old software the commands that are
probably equivalent are:
a. SHOW SERVER LOCAL
b. SHOW CHAR
$
|
| 100.10 | Good comment Thanks | WHEEL::TARRY | | Tue Mar 03 1992 10:57 | 20 |
| >
>Page 12-25, a & b --
> These commands only work on LATmaster software (the optional stuff
> since V5.4-x), so if you have the old software the commands that are
> probably equivalent are:
>
> a. SHOW SERVER LOCAL
> b. SHOW CHAR
>
Thanks for the comment. I am writing the TBI chapter on Terminal Servers and
will check this out. This comment will also be saved for the next revision of
the L/L
Emmalee Tarry
> $
>
|