Re: setting up a LAT service via a terminal server
From: Mike Naime (mnaime_at_kc.rr.com)
Date: 08/23/03
- Next message: Robert Deininger: "Re: setting up a LAT service via a terminal server"
- Previous message: Phillip Helbig---remove CLOTHES to reply: "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"
- Reply: Bart Zorn: "Re: setting up a LAT service via a terminal server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 23 Aug 2003 15:04:22 GMT
Phillip Helbig---remove CLOTHES to reply <helbig@astro.multiCLOTHESvax.de>
wrote in message news:bi7sj9$3la$1@online.de...
> 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.
>
You can set up a terminal server to allow you access to all of the
"services"/nodes that are out there using the LAT protocal. You first
connect to the Terminal Server, and then issue the CONNECT
{nodename/service} command. You can also setup preferred service. This
first takes you to the preffered node, but you have the capability to switch
to another service if you so desire. On a Decserver700, you could connect
to as many as 8 nodes at the same time through the one terminal server port
with SESSION LIMIT set to 8. (Max Value) Or, you can setup the port for
dedicated service if you only want to connect to one service.
Currently, I setup Telnet Listener on my Terminal Servers, Plug the Serial
Console Ports of Servers/Storage into the Terminal Server, and then
ConsoleWorks connects to the IP& Port of the consoles to log, monitor, and
allow access to these ports.
The only way that I think that you could setup something like what you are
asking for, is if you could get the terminal server port that you have the
VT plugged into to attempt to connect to the cluster alias IP. I have never
attempted anything like that. Possibly someone else out there has done
something like this.
Potential Problems: DS700 only allows for one network connection. Cat-5 or
Thinnet. Does the 250 or 200 even have a CAT-5 port on them? If not, then
your only option may be LAT, and not TCPIP.
> 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 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).
>
> Ideally, switching on the VT and hitting RETURN would bring up the login
> sequence from some machine in the cluster.
>
> 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?
>
- Next message: Robert Deininger: "Re: setting up a LAT service via a terminal server"
- Previous message: Phillip Helbig---remove CLOTHES to reply: "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"
- Reply: Bart Zorn: "Re: setting up a LAT service via a terminal server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|