IBM System Cluster 1350, Installation And Service

Page: 82 / 170

Table 15. Troubleshooting the remote console network (continued)
1. Cannot execute any rconsole command
to any Cluster Node.
2. Cannot execute any rconsole commands
to get an active terminal session.
1. Verify the ethernet connections between
the terminal server and the CISCO switch
are OK. Also check the connections
between the CISCO switch and the
Management Node.
2. Check the cables, dongles, and connectors
at the node and the terminal server. Verify
that the serial port at the node is attached
to the correct port on the terminal server
by using the CSM command LSNODE-aI
<NodeName>
. Refer to the information
listed under the ConsolePortNum
category.
3. Follow steps 1 through 9 of
“Configuration and setup after device
replacement” on page 90, then at the
*IN-Reach_Priv>*
prompt type show port
<portnumber> to verify the settings of all
suspect ports against ports that are
working correctly.
4. Verify the InReach terminal server is
powered up and functional by pinging
the unit at 172.30.20.1
5.
Ensure the serial port (COM 1) is
configured to redirect output to the
terminal server. Take the following steps:
v
Restart the node and watch the monitor
screen.
v
When the message Press F1 for
Configuration/Setup
appears, press F1.
v
From the main menu, select Devices
and I/O Ports
then press Enter.
v
Verify that Serial Port A is set to Port
3F8, IRQ 4
.
v
Select Serial Port A.
v
Select Remote Console Redirection.
v
Verify 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. For the x335 and x345 only, run
diagnostics against the serial port to
certify function.
7. Swap out the cables and dongle with
cables and dongle known to be good.
64
Installation and Service