OverviewPrimeAlert for Veritas Cluster Server (VCS) monitors the health and resources of VCS. Defined VCS entities such as resources, resource agents, and service groups are monitored. Other monitored VCS resources include shared storage areas, VCS heartbeat, processes, configuration files, and log files. Monitoring ModesPrimeAlert for VCS can operate in one of two modes: monitoring of both local and VCS cluster resources, or monitoring of local resources only. When both local and VCS cluster resources are monitored, the nodes monitoring VCS cluster resources become activated (see Figure 1).
Figure 1 - PrimeAlert for VCS (monitoring of VCS cluster resources and local system resources) When monitoring of VCS cluster resources is deactivated, only local system resources are monitored (see Figure 2). Note: when all Sun MC agents monitoring VCS reference the same Sun MC server layer, the nodes monitoring VCS cluster resources in PrimeAlert for VCS should be activated on only one Sun MC agent. Otherwise, duplicate alarms will be sent to the Sun MC server layer for each VCS cluster event. For example, consider a two node cluster. If the Sun MC agent on each node is loaded with PrimeAlert for VCS and is monitoring both VCS cluster resources and local resources, then any single VCS cluster event will raise an alarm in both Sun MC agents. Thus, duplicate alarms per single VCS cluster event will be raised. To avoid duplicate alarms, set the Cluster Health Monitoring Failover Order parameter to be the same for both Sun MC agents (see Module Loading Page for details).
Figure 2 - PrimeAlert for VCS (monitoring of local resources only) Required Steps to monitor your Veritas Cluster Server installationTo configure and enable monitoring of your Veritas Cluster Server, the following two steps must be completed: |
