Terminal Server as Console on a Workstation/Server with graphic Screen

Terminal Server as Console on a Workstation/Server with graphic Screen

Post by Erhard Sani » Tue, 18 Sep 2001 06:19:41



Hello,

I have the problem to have to support a server and a workstation
(both under Solaris 8) which are far from the company in a remote
subsidiary. We have an Annex terminal server connected to the WAN
and to serial line (ttya) on both machines. When we want to run the
console over the terminal server, we have to disconnect the keyboard
- in this case console will run over the serial line.

Anyway, we want (and sometimes need) to use the graphics screen when
on the site of the machines. And it is quite inconvenient to plug/unplug
the keyboard and reboot any time we want to do so. I was told there is a
solution how to have both graphics terminal and console over serial line
running, yet our local Sun support guys couldn't tell us. Any hints?

regards, e. sanio

 
 
 

Terminal Server as Console on a Workstation/Server with graphic Screen

Post by Karel Adam » Tue, 18 Sep 2001 08:22:39



Quote:

> Hello,

> I have the problem to have to support a server and a workstation
> (both under Solaris 8) which are far from the company in a remote
> subsidiary. We have an Annex terminal server connected to the WAN
> and to serial line (ttya) on both machines. When we want to run the
> console over the terminal server, we have to disconnect the keyboard
> - in this case console will run over the serial line.

> Anyway, we want (and sometimes need) to use the graphics screen when
> on the site of the machines. And it is quite inconvenient to plug/unplug
> the keyboard and reboot any time we want to do so. I was told there is a
> solution how to have both graphics terminal and console over serial line
> running, yet our local Sun support guys couldn't tell us. Any hints?

There ought not to be a problem.
Leave the keyboards detached, you really do not need them.
To access the console (in text mode) for basic problems,
you have your annex; you can use that from a neighbor
machine as well as cross country.
From the $ prompt, do a

telnet annex port

and (after maybe the annex authenticating)
the login will be there.
'annex' needs to be in your /etc/hosts, of course,
and 'port' is 5000 + the number 1-8 of the serial port

For graphical access, you also use a neighbor machine,
after exporting it's IP:0.0 into $DISPLAY.
Or do this from your luggable computer, which must then
have its own X-server running.

Sample session:
(assuming you wish to access the server from a luggable under X)

connect luggable to local hub/switch
make sure IP's are setup correctly (test by pinging mm.nn.qq.rr all ways)
if you wish, all machines in all /etc/hosts (test by pinging machine names)
on your luggable, telnet into server, and authenticate
then at the $,

export DISPLAY=mm.nn.qq.rr:0.0 ; /mypath/myprogram &

the & is there to leave your text console available

KA

 
 
 

Terminal Server as Console on a Workstation/Server with graphic Screen

Post by d.. » Tue, 18 Sep 2001 10:55:12


: Anyway, we want (and sometimes need) to use the graphics screen when
: on the site of the machines. And it is quite inconvenient to plug/unplug
: the keyboard and reboot any time we want to do so. I was told there is a

We avoid that, and never use the Sun monitor.  We have a VNCserver running
on the Solaris workstation, and run VNCviewer on any available PC, or a Sun
box that does have a monitor, remote, or local.  Our technicians carry a
laptop which can run the graphics this way.   Free.  
http://www.uk.research.att.com/vnc/

--
---

                - San Jose & Pope Valley (Napa County) CA.

 
 
 

Terminal Server as Console on a Workstation/Server with graphic Screen

Post by Ken Hanse » Tue, 18 Sep 2001 21:44:52


Why not simply set the OpenBoot PROM to use the serial console for all
console input/output, and leave the framebuffer/keyboard/monitor attached
for local use, as needed. That way, all console I/O is routed to the
terminal server and the local user can take control of the GUI?

EEPROM settings input-device and output-device seem appropriate...

Ken


Quote:

> Hello,

> I have the problem to have to support a server and a workstation
> (both under Solaris 8) which are far from the company in a remote
> subsidiary. We have an Annex terminal server connected to the WAN
> and to serial line (ttya) on both machines. When we want to run the
> console over the terminal server, we have to disconnect the keyboard
> - in this case console will run over the serial line.

> Anyway, we want (and sometimes need) to use the graphics screen when
> on the site of the machines. And it is quite inconvenient to plug/unplug
> the keyboard and reboot any time we want to do so. I was told there is a
> solution how to have both graphics terminal and console over serial line
> running, yet our local Sun support guys couldn't tell us. Any hints?

> regards, e. sanio

 
 
 

Terminal Server as Console on a Workstation/Server with graphic Screen

Post by Darren Dunha » Wed, 19 Sep 2001 01:08:40



> Why not simply set the OpenBoot PROM to use the serial console for all
> console input/output, and leave the framebuffer/keyboard/monitor attached
> for local use, as needed. That way, all console I/O is routed to the
> terminal server and the local user can take control of the GUI?
> EEPROM settings input-device and output-device seem appropriate...

Yes.  Set them properly.  

After you do that, edit the /etc/dt/config/Xservers file also (create
one by copying /usr/dt/config/Xservers first).

Near the top it gives an example line of what the server line should
look like if there is no character device associated with the display.
After you force the console to use ttya, that will be true.  

You can get a "normal" dtlogin on the kbd/monitor (just without the
"command line login" option), while having the console remain on the
Annex.  You can use the kbd/monitor, but you cannot stop-a and you
cannot see boot messages on the screen.

--

Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
          < How are you gentlemen!! Take off every '.SIG'!! >

 
 
 

Terminal Server as Console on a Workstation/Server with graphic Screen

Post by d.. » Wed, 19 Sep 2001 01:41:10



:> EEPROM settings input-device and output-device seem appropriate...

: Yes.  Set them properly.  

Could either of you give some detail?
Sun reps imply that it can't work.  We've given up the Sun Monitor, which
is actually a cost savings on many models, but some have built in graphics,
which we ignore because we need the remote console access.
If we could have local graphics and remote console, that would be ideal.

My determination has always been the presence or absence of a keyboard,
which unfortunately causes some people to try to hotplug the keyboard,
which results in a stop-a or its equivalent ;-(

--
---

                - San Jose & Pope Valley (Napa County) CA.

 
 
 

Terminal Server as Console on a Workstation/Server with graphic Screen

Post by Darren Dunha » Wed, 19 Sep 2001 05:17:31





> :> EEPROM settings input-device and output-device seem appropriate...
> : Yes.  Set them properly.  
> Could either of you give some detail?

I think I gave quite a bit of detail on setting up the Xservers file.

Just set input-device and output-device to whatever you want.  The
following would be appropriate for serial port a...

# eeprom input-device=ttya
# eeprom output-device=ttya

Quote:> Sun reps imply that it can't work.

Do you have access to sunsolve?  See infodoc 18318.

Quote:> We've given up the Sun Monitor, which
> is actually a cost savings on many models, but some have built in graphics,
> which we ignore because we need the remote console access.
> If we could have local graphics and remote console, that would be ideal.

That's exactly what you get.  Local graphics and remote console.

Quote:> My determination has always been the presence or absence of a keyboard,
> which unfortunately causes some people to try to hotplug the keyboard,
> which results in a stop-a or its equivalent ;-(

The keyboard presence will cause the console to move around if
input-device is keyboard and output-device is screen.  If they are set
to another port, then the keyboard presence or absence is ignored.

Plugging/unplugging/stop-a will have no effect on the machine because
the console is on ttya (or wherever).

--

Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
          < How are you gentlemen!! Take off every '.SIG'!! >

 
 
 

Terminal Server as Console on a Workstation/Server with graphic Screen

Post by martha starke » Wed, 19 Sep 2001 22:50:35





> :> EEPROM settings input-device and output-device seem appropriate...

> : Yes.  Set them properly.

> Could either of you give some detail?
> Sun reps imply that it can't work.  We've given up the Sun Monitor, which
> is actually a cost savings on many models, but some have built in graphics,
> which we ignore because we need the remote console access.
> If we could have local graphics and remote console, that would be ideal.

> My determination has always been the presence or absence of a keyboard,
> which unfortunately causes some people to try to hotplug the keyboard,
> which results in a stop-a or its equivalent ;-(

If you are talking to sales "reps" I could understand that they may not have
all the correct info.  If these are technical reps, then shame on them.  This
is a very common configuration and it easily setup via the eeprom changes and
/usr/dt changes.  It's a common question and most definately is possible:

change the input-device and output-device to the serial port you want to use
(usually port a)

make the changes outlined in this thread for the /usr/dt stuff:

Copy /usr/dt/config/Xservers to /etc/dt/config/Xservers and modify the
line.  The config directory under /etc/dt does not exist by default and must
be created.


to


and reboot.

That should do it.  If you don't see any output on your console (dumb
terminal, terminal server, whatever) but the machine does come up, it's
probably a cable problem (needs a null modem cable and you don't have one or
vice versa. depends on the equipment).

HTH!