[Info-vax] virtual consoles
Jan-Erik Söderholm
jan-erik.soderholm at telia.com
Mon Oct 19 04:09:58 EDT 2009
Phillip Helbig---remove CLOTHES to reply wrote:
> In article <4adada39$0$83248$e4fe514c at news.xs4all.nl>, Robin Schipper
> <"thespriteman <remove_this> writes:
>
>> we have several OpenVMS systems (and even Cisco switches) connected from
>> the Console to a few Terminal servers, and that terminal server is
>> trough LAT or TCPIP connected to our central management systems (witch
>> has PCM (polycentre Console Manager) running)
>> on our central management system we can watch events comming by from the
>> systems and we can log in to the console if we need to.
>
> Interesting. I have some terminal servers---8 serial connections and an
> ethernet connection, or whatever. Normally, to connect several serial
> lines to one or more systems over the network. But they can apparently
> be used in "reverse"?
What is connected in "reverse" ?
Terminal servers are connected to something having
a serial port. May it be a printer or a consol port, there
isn't that much of a difference and neither of them is
"in reverse".
The only thing that might be called "reverse" is how the
connection (session) to the port of the terminalserver
is *established*. Sometimes someone at the port doing a
"connect" to something with a telnet service (like someone
sitting at a VT220 connected to a terminal server doing a
"connect <some-VMS-box>") is regarded as "normal" and when
the VMS server is establishing the session with the port is
regarded as "in reverse". But there is nothing "reverse" with
how soeting is serialy connected with the port itself.
>
> I have really old terminal servers---20 years or so. Would they work?
>
Easy to test. Note that this (establishing sessions to ports
from the network) works equaly well over LAT.
More information about the Info-vax
mailing list