Option 11 TTY ports
There are two ways to console into an Option 11:
- If networked, Telnet (SSH from Rel.6) into the SSC IP address on a Pseudo TTY with PuTTY.
- You can get a TTY login prompt from each of the systems serial ports by building TTYs on those ports.
Print ADAN in LD 22, and look at the output. Note the TTY, TTY_TYPE, CAB, CARD, and PORT entries.
TTY 0 is built in, and its baud rate is set by the SSC front panel DIP switch. Additional TTY's can be built in LD 17: CHG ADAN, NEW TTY. There are 3 ports on the main cabinet SSC, expansion cabinet fibre receiver cards also have a useable serial port.
ADAN prompts and responses are detailed in Software Input Output Reference - Administration, under LD 17.
An Option 11 ADAN may end up looking something like below, in this example the third port is set for Call Detail Records (CDR), but it could equally be used as a TTY if the USER is changed to MTC SCH BUG instead of CTY.
ADAN TTY 0 TTY_TYPE SDI CAB 00 CARD 00 PORT 0 DES LOCAL FLOW NO USER MTC SCH BUG TTYLOG 0 BANR YES ADAN TTY 1 TTY_TYPE SDI CAB 00 CARD 00 PORT 1 DES REMOTE BPS 9600 BITL 8 STOP 1 PARY NONE FLOW NO USER MTC SCH BUG TTYLOG 0 BANR YES ADAN TTY 2 TTY_TYPE SDI CAB 00 CARD 00 PORT 2 DES CDR BPS 1200 BITL 8 STOP 1 PARY NONE FLOW NO USER CTY
With serial data cables, generaly only pins 2, 3 and 5 (or 7 if 25 pin) are required. A null modem may be used to swap pins 2 and 3, transmit and receive data. When the cable is correct, hitting return on a TTY port should yield a logon prompt.
TTY 00 SCH MTC 0:38 OVL111 IDLE 0 >
A communications setting of 9600, 8 n 1, no handshaking is usually standard for console TTY's, otherwise, look at the BPS, BITL, STOP, PARY, and FLOW settings, and set the terminal program port settings to match. A disabled TTY will not respond.
Enable, disable, and check the status of TTY ports in LD 37.
(PTY's enable automatically when active, eg, someone connects.)
ld 37 IOD000 .stat TTY 0 : ENBL DES: LOCAL TTY 1 : DSBL DES: REMOTE TTY 2 : ENBL DES: CDR .enl tty 1 OK
You cannot disable the TTY you're currently connected with.
Port 0 is special: it's required for installing/upgrading software. It's the only port that's enabled at boot time, allowing you to either watch the boot process, or break out of it.
If you suspect a hardware error, you can test a TTY port in LD 37:
.tty 0 ABCDEFGHIJKLM NOPQRSTUVWXYZ 0123456789"#$ %*!&()<>=:,.? READY FOR INPUT qwerty end .
Entered characters are echoed until
end is received.
PTY's are not compatible with this test.
Multi-User Login enables up to five users to log in, load, and execute overlay programs simultaneously, but NOT concurrently in the same load - this is to prevent database corruption.
- Check that MULTI_USER is ON by printing OVLY (overlay) in LD 22, the default is OFF.
It is enabled in LD 17 - REQ: CHG, TYPE: OVLY. Enter down to MULTI_USER and type ON.
When Multi-User Login is ON, if you try to enter a load, but see:
OVL429-OVERLAY CONFLICT your choice is either to try later, or force a log off for the user blocking your access.
At the > prompt, type
WHO to find out who is logged on, and which load they're in.
>who PORT ID OVERLAY NAME SPRT MONITOR TTY 00 0 ADMIN2 TTY 01 135 ADMIN1
FORC XX to force a log off for TTY XX (you must be logged in with a level 2 pasword for this to work).
If you're feeling very conscientious, you can precede this with a
SEND XX message informing the TTY XX user of his/her impending fate.
At the " SEND MSG: " prompt, enter your message (up to 80 characters).
SEND ALL sends the message to all logged-in TTY's.
If you get a
FORC NOT ALLOWED-OVERLAY NOT ABORTED message, disable, and re-enable the offending TTY port:
LD 37: DIS / ENL / STAT TTY XX/blockquote>