BladeCluster Solution Manual

7 Checking Operations
This chapter provides procedures to check the operations of the BladeCluster.
Checking the Operation of the BladeCluster
From each BladeSystem or NonStop NS16000 series node, check the operation of the BladeCluster
after these procedures:
• Installing or migrating a node
• Replacing a ServerNet switch or processor switch
Using OSM to Check Operations
You can use the OSM Service Connection and associated online help to quickly check the health
of each ServerNet switch or processor switch and node in the BladeCluster. If you find problems
with a node, resolve the problems before adding additional nodes to the BladeCluster.
Checking the External Fabric for All Nodes
Perform this procedure after installing or migrating a BladeSystem or NonStop NS16000 series
node.
NOTE: You must configure remote passwords before you can use the STATUS SUBNET $ZZSCL,
PROBLEMS command to gather information about remote nodes.
Use SCF to check if direct ServerNet communication is possible on both fabrics between all nodes
in the ServerNet cluster. This command queries the SNETMON processes in all nodes, and displays
whether the X and Y fabrics are up for each node. You do not have to issue separate commands
for each node.
1. Log on to any node and check for connectivity problems in the ServerNet cluster:
STATUS SUBNET $ZZSCL, PROBLEMS
2. For each node that should be active, verify that the display shows “No connectivity problems
detected.”
3. If the display shows a list of nodes next to a particular node, a problem has occurred with the
connection between that node and the nodes in the list.
Checking the Operation of Each Node
The topics in this section describe operation tasks before and after a BladeSystem node installation
or migration.
• “Checking That Automatic Line-Handler Generation is Enabled” (page 71)
• “Checking MSGMON, SANMAN, and SNETMON” (page 71)
• “Checking the ServerNet Cluster Subsystem” (page 72)
• “Checking the BladeCluster Configuration” (page 72)
• “Checking the Internal ServerNet X and Y Fabrics” (page 73)
• “Checking the Operation of the Expand Processes and Lines” (page 74)
• “Checking the Status of Expand-Over-ServerNet Line-Handler Processes” (page 74)
• “Checking the Status of An Expand-Over-ServerNet Line” (page 74)
70 Checking Operations