If a node becomes unresponsive or inaccessible, use the following table to
diagnose the problem.
Table 14. System connectivity symptoms
| Symptom | Recovery |
|---|---|
| Using the SP Hardware Perspective, bringing up hostResponds in a
table view for nodes and multiple nodes shows: Node Not
Responding.
Using the SP Hardware Perspective, bringing up switchResponds in a table view for nodes and multiple nodes shows: Adapter Not Configured. The spmon -G -d command shows hostResponds as no. The spmon -G -d command shows switchResponds as no. | "Action 1 - Diagnose multiple nodes" |
|
Using the SP Hardware Perspective, either the table view or nodes status page
of the notebook shows: Node Not Responding for
hostResponds or Adapter Not Configured for
switchResponds.
The spmon -G -d command shows hostResponds as no The spmon -G -d command shows switchResponds as
no.
| "Action 2 - Diagnose individual nodes" |
| Cannot access the node using a remote command or: telnet, rlogin or ping. | "Action 3 - Diagnose a network problem" |
| Cannot access the node using the telnet or rlogin, commands, but can access the node using the ping command. | The is a probable software error. See Producing a system dump to initiate a dump, record all relevant information and contact the IBM Support Center. |
|
Can access the node using telnet or ping, but
hostResponds still shows: Node Not Responding.
| "Action 4 - Diagnose a Topology-related problem" |