ServerNet Cluster 6780 Operations Guide (G06.24+, H06.03+)

Monitoring a ServerNet Cluster
ServerNet Cluster 6780 Operations Guide—525606-002
1-3
Using OSM to Monitor a ServerNet Cluster
•
With SCF, you can compare information by logging on to a remote TACL process
and then running SCF at the remote node or by entering \nodename.$ZZSMN at a
TACL prompt. Both methods require matching remote passwords.
Using OSM to Monitor a ServerNet Cluster
OSM monitoring tasks for a ServerNet cluster include:
•
Obtaining information about the cluster-related hardware resources such as
MSEBs, the local node, the remote nodes, the external X and Y fabrics, the cluster
switches, and the cluster switch subcomponents.
•
Obtaining information about the cluster-related processes such as the ServerNet
system area network manager (SANMAN), the ServerNet cluster monitor process
(SNETMON), and the Expand-over-ServerNet lines.
•
Checking for alarms on cluster resources. An alarm describes a detected fault or
abnormal conditions and recommended repair actions. For more information, see
Using OSM Alarms on page 3-11.
•
Generating and viewing statistical information for the cluster and the ServerNet
nodes within it.
The OSM Service Connection obtains information about the local node and the fabrics
from both SANMAN and SNETMON. Information about the remote nodes comes only
from SNETMON.
To see the ServerNet cluster resources in the tree pane, click the plus sign (+) next to
the ServerNet Cluster resource to expand it. You can expand other subordinate cluster
resources in the same manner. To select a resource in the tree pane, click the name of
the resource itself. The examples in this section use the tree pane to navigate to and
select cluster resources.
Starting an OSM Session
Using an HP NonStop System Console attached to any functioning node in the
ServerNet cluster, log on and start the OSM Service Connection.
After OSM discovers the system and cluster resources, the Management window
appears as shown in Figure 1-1
.