Switching Lan Consoles - Fujitsu Siemens Computers PRIMESTATION Series Manual

PRIMESTATION as LAN Console
To ensure correct key binding, (see VirtualBindings(3X), xmbind(1X)), you should
carry out one of the following steps beforehand:
Ê Copy the file /usr/dt/lib/bindings/sun_at under the name .motifbind to the user's
home directory, or
Ê add an entry with the name of the maker of the X server to xmbind.alias. The
maker name can be ascertained with the xdpyinfo command. For XVision, the
entry would have to be:
"Visionware Limited."
Ê If you are using /usr/dt/lib/bindings/xmbind.alias, you must also set
XMBINDDIR=/usr/dt/lib/bindings
in the .profile file.
If you are using a private copy of xmbind.alias in the home directory, you must
also copy /usr/dt/lib/bindings/sun_at to the home directory.
5.6

Switching LAN Consoles

The LAN Console is switched when representation of consoles from RM or
PRIMEPOWER (MR) servers, i.e. console access to these systems, is to be
handled from another LAN Console in the future. The connection to the
respective RM and PRIMEPOWER (MR) systems involved must be established
via the same RCAs from both LAN Consoles.
The prerequisite for this is that another LAN Console supporting the same
console accesses has been configured. For access to an RM or PRIMEPOWER
(MR) system, at least the port number of the RCA and the password allocated
to this port if the connection is set up via an RCA3 must be identical.
5.6.1 Planned switches
In this scenario, the activities of a LAN Console are planned to be taken over by
another LAN Console for organizational reasons, i.e. the two underlying LAN
Consoles are fully functional.
So that console accesses to the same RM and PRIMEPOWER (MR) servers
can take place from the other LAN Console, all active connections involving the
current LAN Console have to be terminated. This can be done with the "~."
string.
U41270-J-Z916-2-76
Operating the LAN Console
sun_at
69