Isolating Network, Node, And Linux Problems - IBM eserver Cluster 1350 Installation And Service Manual

The output provides information about each node, such as, the node type, model
number, serial number, and host name. The tab file output also provides information
that corresponds each node to its terminal server network and service processor
network. For the terminal server network, the output includes the console server
host name and the console port number to which the node is connected. For the
service processor network, the output includes the host name of the Remote
Supervisor Adapter device to which the node is connected and the internal service
processor name for the node.
CSM distinguishes between a management node, a pre-managed node, and a
managed node. A pre-managed node is a node that has been added to the
configuration but is not yet ready to be managed, for example, because it has not
yet been installed. To display a list of pre-managed nodes on the management
server, at the console prompt, type
Isnode -P
To display a list of managed nodes on the management server, at the console
prompt, type
Isnode
To display the management server, at any node console prompt, type
mgmtsvr

Isolating network, node, and Linux problems

Cluster 1350 nodes are connected over a 10/100 Mb Ethernet cluster network. A
Cluster 1350 can also have a second network, either an additional Ethernet network
or a Myrinet 2000 network.
As a preliminary diagnostic step, ping all the nodes over all available networks.
Compare the error to possible symptoms in Table 12.
38 IBM Eserver Cluster 1350 Installation and Service Guide
Table 12. Troubleshooting the shared VLAN
Symptom
v Can ping the storage node
from the management node
but cannot ping the cluster
nodes.
v Can ping the cluster nodes
from the management node
but cannot ping the storage
nodes.
v Cannot ping either the
storage nodes or the cluster
nodes.
v Cannot ping the cluster
nodes in one of the
expansion cabinets.
Action
1. Make sure that the links between the management
node, storage nodes, Cisco 3550, 3500, and 400x
switches.
2. Restart the management node and press F1 to enter
the Setup utility. Make sure that the Ethernet devices
are turned on.
3. Make sure that the correct driver level is installed for
1Gb Fibre Channel Ethernet. To view the status, at the
console prompt, type, ifconfig.
4. Check the Cisco (3500, 4003, or 4006) switch for green
status LEDs or system and status LEDs. If the green
LEDs are lit, the switch is OK.
5. To make sure that the 1 Gb Fibre-Channel Ethernet
connections are good, swap a known good cable with a
suspect cable to isolate the failing device.
6. Replace the failing Fibre-Channel cable, GBIC, or
network interface card.