smslc00in the Self-managed server room (in conjunction with the
conserversoftware package and the School's LCFG infrastructure) to provide remote access to the console of a machine in that room.
|Note: The assumption is that the machine in question has been configured so that its console has been redirected to its serial port. This configuration must - of course - be done by the owner of the machine in question. The serial interface of the machine should be configured to run at 9600,8,n,1.|
|Note: All of the following configuration will be arranged by computing support, on request from the owner of the machine in question.|
smslc00using a standard TP cable. You must use the appropriate RJ45<->DB9F adaptor at the machine end to make this connection: the Lantronix part number for the required adaptor is 200.2070A. Such adaptors are available in the Forum server room: we have some 'official' Lantronix adaptors (coloured grey, and labelled '200.2070A'), and also some adaptors which have been made in-house by our technicians: these are coloured green. Note that, by default, all incoming serial connections on the SLC are expected to run at 9600,8,n,1. The use of different baud rates etc. is strongly discouraged, but, if necessary, can be accommodated by appropriate reconfiguration of the SLC's device port(s).
live/smconsole_server.hand add the target machine's name, and the UUN's of its authorised console user(s), to the appropriate resources. Example: The serial console of machine
myserverhas been cabled to device port 05 of the Lantronix SLC console server
smslc00, and is to have three authorised console users, each of whom will have full read/write access to the console. Their UUNs are
uun1(a member of staff),
uun3(two postgrads). Add the following to
conserver.users_staff uun1 conserver.users_postgrads uun2 uun3 ...[snip]... conserver.consolename_smslc00p05 myserver !conserver.crw_smslc00p05 mADD(uun1) !conserver.crw_smslc00p05 mADD(uun2) !conserver.crw_smslc00p05 mADD(uun3)
|Note: The console can be accessed as described below by all users nominated by the owner of the machine in question (all such users will have been appropriately configured as described in the preceding section), as well as by all School C(S)O's.|
ssh to the machine
Issue the command
console <target machine name>
and authenticate using your usual DICE password *.
(Note that the <target machine name> is the single word name of the machine, and not its fully-qualified domain name.)
Once authenticated, proceed as described in the man page '
man -s1 console'.
In particular, note that:
consolecommand has been configured as
Ctrl-] Ctrl-] l 0(that's lower-case L, followed by a zero).
Ctrl-] Ctrl-] l 0 b.
Ctrl-] Ctrl-] ?.
Ctrl-] Ctrl-] .(that's a 'dot').
consolecommand can be found in the man page
man -s1 console..