HP HA s Software manual Interpreting Node Status

Page 60

Monitoring Cluster Resources

Cluster Monitor Reference

Node Status

 

 

The node status is the current status of a node relative to a particular cluster.

 

 

The MIB variable hpmcClusterState, which is part of the hp-mcCluster MIB,

 

 

provides the node status information to the monitor.

 

 

The cmviewcl -vcommand displays detailed information about the current

 

 

status of the cluster and packages on the cluster.

Table 3-2

Interpreting Node Status

 

 

 

 

 

Resource Name

/cluster/localNode/status/clusterName

 

 

 

 

 

 

Condition

 

Value

Interpretation

 

 

 

 

 

 

RUNNING

 

1

Node is accessible and operating normally.

 

 

 

 

 

 

INITIALIZING

 

2

Node’s daemon has started, but is not ready to communicate with

 

 

 

 

other nodes’ daemons.

 

 

 

 

 

 

RECONFIGURING

 

3

Node is running protocols to make sure all other nodes agree to the

 

 

 

 

new membership in the cluster.

 

 

 

 

 

 

INVALID

 

4

The cluster status may be DOWN.

 

 

 

 

 

 

HALTED

 

5

Node has been removed from the cluster, with the cmhaltnode

 

 

 

 

command, for example.

 

 

 

 

 

 

FAILED

 

6

Node is no longer a member of an active cluster.

 

 

 

 

 

You might want to create a request that notifies you when the local node is not running. You can then verify that the node or MC/ServiceGuard was stopped intentionally.

The minimum polling interval for cluster status is 30 seconds. You may want a longer interval, especially if system performance is affected.

60

Chapter 3

Image 60
Contents Using EMS HA Monitors B5735-90001 AugustLegal Notices Contents Monitoring Cluster Resources Monitoring Network InterfacesTroubleshooting Monitoring System ResourcesGlossary Contents Printing History Printing Date Part Number EditionB5735-90001 Page Preface PublicationsPage Installing and Using EMS Event Monitoring Services High Availability Monitors What are EMS HA Monitors?Chapter Role of EMS HA Monitors in a High Availability Environment Installing and Removing EMS HA Monitors Installing EMS HA MonitorsRemoving EMS HA Monitors Using EMS HA Monitors Event Monitoring Service Resource Class HierarchyStatus AvailMB PvpvlinkEvent Monitoring Service Screen Selecting a Resource to Monitor ScreenUsing Wildcards Creating a Monitoring Request Monitoring Request ParametersHow Do I Tell EMS When to Send Events? What is a Polling Interval? Which Protocols Can I Use to Send Events?What is a Notification Comment? Copying Monitoring Requests Modifying Monitoring RequestsRemoving Monitoring Requests Configuring MC/ServiceGuard Package Dependencies Service EMSPackage Configuration Screen Package Resource Dependencies Screen Resource Parameters Screen Using EMS HA Monitors Monitoring Disk Resources Monitoring Disk Resources Disk Monitor Reference Disk Monitor Resource Class HierarchyPhysical Volume Summary Interpreting Physical Volume SummaryDisk Monitor Reference Physical Volume and Physical Volume Link Status Interpreting Physical Volume and Physical Volume Link StatusLogical Volume Summary Interpreting Logical Volume SummaryLogical Volume Status Interpreting Logical Volume StatusLogical volume is inactive Logical volume is DOWN, a complete copy of the data is notLogical Volume Number of Copies Interpreting Logical Volume CopiesRules for Using the EMS Disk Monitor with MC/ServiceGuard Rules for Using the EMS Disk Monitor with MC/ServiceGuard Rules for RAID Arrays Pvsummary Calculations Case Conclusion StateCreating Volume Groups on Disk Arrays Using PV Links Adding PVGs to Existing Volume Groups# mkdir /dev/vgdatabase Creating Logical Volumes Rules for Mirrored Individual Disks Creating Disk Monitoring Requests Disk Monitoring Request Suggestions Parameters When Disks Fail Resources to Monitor for RAID Arrays RAID Array ExamplePvgup Return Resources to Monitor for Mirrored Disks Mirrored Disks ExampleMonitoring Parameters Resource Notify Condition Option Resources to Monitor for Lock Disks Example for Interpreting the pvsummary for Mirrored DisksNumber Pvsummary Valid Meaning Value Devices Resource Monitoring Parameters Notify Condition OptionResources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Monitor Reference Cluster Monitor Resource Class HierarchyCluster Cluster Status Interpreting Custer StatusNode Status Interpreting Node StatusPackage Status Interpreting Package StatusCreating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Reference Network Monitor Resource Class HierarchyInterpreting LAN Interface Status Chapter Net/interfaces/lan/status/LANname When value is Configuring Network Monitoring Requests30 sec HourMonitoring System Resources System Monitor Reference System Resource Monitor Class HierarchyNumber of Users Interpreting Number of UsersResource Name Value Range Interpretation Job Queues Interpreting Job QueuesResource Name Value Interpretation Range Filesystem Available Space Filesystem Available SpaceResource Name Creating System Resource Monitoring Requests 6Troubleshooting EMS Directories and Files Etc/opt/resmon/log Logging and tracing EMS LoggingEMS Tracing System Performance Issues Network Performance IssuesPerformance Considerations Testing Monitor Requests Testing Disk Monitor RequestsTesting Cluster Monitor Requests Testing Network Monitor RequestsMaking Sure Monitors are Running Glossary Notification See alert Glossary Glossary Index Index Index