Checking The Terminal Server - IBM eserver Cluster 1350 Installation And Service Manual

v If the node does not respond, go to "Node checks" on page 42 and continue with

Checking the terminal server

Check the terminal server nodes using the telnet SSH command or ping the nodes
using the Ethernet:
v If node communication fails, go to "Node checks" on page 42 and continue with
v If following the steps in Table 19 do not correct the problem, continue with the
46 IBM Eserver Cluster 1350 Installation and Service Guide
Node checks.
Node checks.
steps shown in "Isolating network, node, and Linux problems" on page 38..
Table 19. Troubleshooting the terminal server network for the Remote Console
Symptom
Unable to run rconsole
commands to get an active
terminal session.
Action
1. Check connection of cables and connectors at the nodes
and the In-Reach terminal server.
2. Make sure that the In-Reach terminal server is turned on
and connected to the network by pinging the unit at
172.30.20.1.
3. Follow steps 1 through 9 of Chapter 11, "Configuring the
terminal server after device replacement," on page 59,
then at the *IN-Reach_Priv>* prompt, type, show port
<portnumber> to compare the settings of all suspect ports
against ports that work.
4. Make sure that the In-Reach terminal server is powered
up and functional by pinging the unit at 172.30.20.1
5. Make sure that the serial port (COM 1) is configured to
redirect the output to the terminal server:
v Restart the node and watch the monitor screen.
v When indicated, press F1.
v From the main menu, select Devices and I/O Ports,
then press Enter.
v Make sure that Serial Port A is set to Port 3F8, IRQ 4.
v Select Serial Port A.
v Select Remote Console Redirection.
v Check the following settings:
Remote Console Active [Enabled]
Remote Console Com Port [COM1]
Remote Console Baud Rate [9600]
Remote Console Data Bits [8]
Remote Console Parity [None]
Remote Console Stop Bits [1]
Remote Console Emulation [VT100]
Remote Console Active After Boot [Enabled]
v Save settings and exit.
6. Swap out cables and dongle with known good units.
7. Run diagnostics against the serial port to test the
connectivity.