IBM System Cluster 1350, Установка и обслуживание

Страница: 83 / 170

If the above procedures do not correct the problem you may have a problem with
a port on the terminal server.
Try a different port and retest. Issue the CSM command lsnode —AI <nodename>
lgrep
and record the port information shown. 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 72 and check the service processor
log.
Hardware problem in service processor log: Go to “Node” on page 72 for node
problem determination.
Amber LED lit on node:
Service processor log may be full. The log is cleared by
connecting to the service processor via the Falcon card. Otherwise, go to “Node”
on page 72 for node problem determination.
rpower to node fails:
v
Check service processor connection.
v
Try the rpower -a on command again.
v
Go to “Checking service processor logs” on page 72 and check the service
processor log.
v
Use the web interface or telnet to each RSA adapter on the system and then
connect to the service processor on the Cluster Node individually through the
″
Remote ASM Access
″
menu.
v
If the Cluster Node is not in the list, use the node’s firmware diskette to
diagnose the problem.
Service processor network
Table 16. Troubleshooting the service processor network
Symptom Action
Chapter 10. Hardware/software problem determination
65