Re: setting up a LAT service via a terminal server
From: Robert Deininger (rdeininger_at_mindspring.com)
Date: 08/23/03
- Next message: John Gemignani, Jr.: "Re: SFTP"
- Previous message: Mike Naime: "Re: setting up a LAT service via a terminal server"
- In reply to: Phillip Helbig---remove CLOTHES to reply: "setting up a LAT service via a terminal server"
- Next in thread: Phillip Helbig---remove CLOTHES to reply: "Re: setting up a LAT service via a terminal server"
- Reply: Phillip Helbig---remove CLOTHES to reply: "Re: setting up a LAT service via a terminal server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 23 Aug 2003 15:09:10 GMT
In article <bi7sj9$3la$1@online.de>, helbig@astro.multiCLOTHESvax.de
(Phillip Helbig---remove CLOTHES to reply) wrote:
>Apart from the consoles, I have a VT320 connected to a serial port of a
>node in my hobbyist cluster. If that node is down for some reason,
>however, then of course one can't log in via that terminal. (The
>terminal in question is in my son's bedroom. How many 9-year-olds do
>you know who know how to use EDT? One of my biggest triumphs was when I
>heard him say "Mama's PC doesn't have a PROPER keyboard"!) Thus, I
>would like to have the terminal connect to the CLUSTER instead of to a
>specific node.
>
>It seems the way to do this would be to connect via a terminal server.
>I have a DECserver 250 and a DECserver 200/MC. Presumably these will
>work fine for what I want to do. I also have the necessary cables etc.
>
>Unfortunately, this stuff is located 500 km from where I spend most of
>my time, so I don't have much time to experiment. What I need is a
>step-by-step guide to setting up what I need. Presumably, the LAT
>service has to be created somehow, perhaps the terminal server has to
>boot from somewhere etc.
I don't remeber the exact commands for the terminal servers. I'll try to
give some hints for teh 200/MC from memory.
I think the 200/MC needs a MOP server to load its software when it powers
on. I believe it is/was on the layered product CDs. I don't remember the
file name; if you configure your MOP server (via LANCP or either DECnet
flavor) and watch OPCOM, you'll see a MOP request when you power on the
server.
You should be able to connect a terminal to any serial port and talk to
the terminal server, though it is possible to configure a port so that it
only makes outgoing connections. You can also connect via the network
using the MOP protocol.
To connect via MOP, use LANCP. The command is something like this:
$ LANCP := $LANCP
$ LANCP
LANCP> CONNECT NODE/DEVICE=Exy0 <ethernet address>
Exy0 is the network device on the VMS system you will connect through, and
the ethernet address should be on a sticker on the terminal server.
IIRC, you will get a "#" prompt, and you need to type
access <cr> to get the username> prompt on the server. Enter anything you
want for the username.
The terminal server's user interface is vaguely DCL-like. There is a HELP
command.
Like DECnet phase 4, the terminal server has both volatile and permanent
configuration information. See SHOW, LIST, SET, and DEFINE in the help.
To configure the server, you'll need privilege. I think the command is
SET PRIV. The default password is SYSTEM. User name doesn't matter.
You'll need to configure each port, then define LAT services and enable
each service on the port(s) as needed. LAT can do load balancing if you
configure things right, and since multiple nodes can offer the same
service, you get "cluster alias" functionality as well.
>I have no experience with LAT other than using SET HOST/LAT to connect
>to other nodes (in the cluster) and no experience with terminal servers
>(except as an end-user).
The System Manager's Manual has lots of details.
>Ideally, switching on the VT and hitting RETURN would bring up the login
>sequence from some machine in the cluster.
That's possible with most terminal servers.
>At the moment, the cluster has a VAX at 7.3, a VAX at 7.2 and an ALPHA
>at 7.2-1. There is no DECnet running. LAT is configured so that one
>can SET HOST/LAT to and from any machine in the cluster. With TCPIP I
>have a cluster alias so that to the outside world, the cluster behaves
>as one machine. Ideally, I'd like the same functionality with LAT. (In
>fact, since the connection to the outside world is via a DSL
>switch/router which does PAT and forwards incoming connections to the
>cluster alias, not only is there just one address for INcoming
>connections, but just one address for OUTgoing connections as well, the
>external address of the router. (Normally, a cluster alias applies to
>just incoming connections, whereas each node will use its own address
>for outgoing connections.))
>
>Load-balancing would be nice just to get some experience with it, but
>for my purposes failover (like with the TCPIP cluster alias) would be
>enough.
>
>While I'm at it, I have an LNO3 sitting around. Can I connect that to
>the terminal server as well?
Yes, and LAT-based VMS queues should work too.
- Next message: John Gemignani, Jr.: "Re: SFTP"
- Previous message: Mike Naime: "Re: setting up a LAT service via a terminal server"
- In reply to: Phillip Helbig---remove CLOTHES to reply: "setting up a LAT service via a terminal server"
- Next in thread: Phillip Helbig---remove CLOTHES to reply: "Re: setting up a LAT service via a terminal server"
- Reply: Phillip Helbig---remove CLOTHES to reply: "Re: setting up a LAT service via a terminal server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
