IBM eserver Cluster 1350 Installation And Service Manual page 59

If the procedures in Table 16 on page 42 do not correct the issue you may have a
problem with a port on the terminal server. Complete the following steps to test a
different port:
1. Issue the CSM command lsnode —AI <nodename> lgrep and record the port
information.
2. Move the cable to a new port and change the port number using the CSM
command chnode <nodename> ConsolePortNum=xx where xx is the new port
number.
If the symptom persists, go to "Checking service processor logs" on page 50 and
check the service processor log.
Hardware problem in service processor log
Go to "Node checks" on page 42 for node problem resolution.
Amber LED lit on node
The service processor log might be full. The log is cleared by connecting to the
service processor through the Remote Supervisor Adapter card. Otherwise, go to
"Node checks" on page 42 for node problem resolution.
rpower to node fails
Use the following information to resolve remote power failures:
v Check the service processor connection.
v At the console prompt, type rpower -a on.
v Go to "Checking service processor logs" on page 50 and check the service
processor log.
v Use the Web interface, telnet, or SSH to reach each Remote Supervisor Adapter
card on the cluster and then connect to the service processor on each cluster
node individually through the Remote ASM Access menu.
v If the cluster node is not in listed, insert the node firmware diskette and try to
diagnose the problem.
Chapter 8. Troubleshooting hardware and software problems
43