- Installing the Oracle Solaris OS on a Cluster Node
- Securing Your Solaris Operating System
- Solaris Cluster Software Installation
- Time Synchronization
- Cluster Management
- Cluster Monitoring
- Service-Level Management and Telemetry
- Patching and Upgrading Your Cluster
- Backing Up Your Cluster
- Creating New Resource Types
- Tuning and Troubleshooting
This chapter is from the book
This chapter is from the book
This chapter is from the book
Cluster Monitoring
Most data centers use an enterprise management tool such as HP OpenView, BMC Patrol, or IBM Tivoli to monitor and manage their environment. If the data center has a large base of Sun servers, then the list might also include the Sun Management Center software. The Solaris Cluster software integrates with these tools using the Simple Network Management Protocol (SNMP), enabling administrators to monitor both the cluster nodes and the resource groups and resources they contain.
Sun Management Center Integration
The Sun Management Center software enables you to manage and monitor all the Sun servers in your data center. The Sun Management Center software is implemented as a three-tier architecture: console, server, and agent. The agent is installed on the system you choose to monitor. It sends alerts to the server when certain events occur or when thresholds are exceeded. Each agent handles the monitoring of a specific function. For example, the Solaris Cluster agent monitors the cluster infrastructure and the resource groups and resources configured on your system. The Sun Management Center console aggregates the alarms and alerts pertaining to a specific node, marking the node with a symbol to denote the most serious condition that it is encountering. If there are no problems with the node, then no symbol is present. Figure 4.4 shows an example of a serious error with the cluster transports, but just a warning for the scalable resource group because it is offline.
)
Figure 4.4 Sun Management Center GUI
Solaris Cluster SNMP Management Information Base
The Solaris Cluster software provides two Simple Network Management Protocol (SNMP) management information bases (MIBs): one for cluster events, the other for cluster objects and their status.
SNMP MIB for Cluster Events
The Solaris Cluster SNMP event MIB can be enabled on any cluster node without relying on additional SNMP agent infrastructure. Because all cluster nodes receive the same cluster events, you need to enable the SNMP event MIB on only one cluster node.
The cluster events are graded in severity from low to high, as follows:
- INFO
- WARNING
- ERROR
- CRITICAL
- FATAL
When the SNMP event MIB is enabled on a node, the cluster event SNMP interface can do the following:
- Store up to 50 of the most recent WARNING or higher-severity cluster events in the MIB table.
- Send SNMP traps to one or more hosts when WARNING or higher-severity cluster events occur.
By default, the SNMP event module uses port number 11161, and traps use port number 11162. These port numbers can be changed by using the cacaoadm command, as shown in the following example.
The Solaris Cluster SNMP event MIB Object ID (OID) is 1.3.6.1.4.1.42.2.80.
Example 4.7. Changing the SNMP Adapter Trap Port
Use the cacaoadm command to determine and change the SNMP adapter trap port.
phys-grass2# cacaoadm get-param snmp-adaptor-trap-port snmp-adaptor-trap-port=11162 phys-grass2# cacaoadm stop phys-grass2# cacaoadm set-param snmp-adaptor-trap-port=12345 phys-grass2# cacaoadm start phys-grass2# cacaoadm get-param snmp-adaptor-trap-port snmp-adaptor-trap-port=12345
SNMP Interface for Cluster Objects
The SNMP interface for cluster objects such as nodes, resource groups, and quorum devices, along with their corresponding status, is provided through the Solaris Cluster software to the Sun Management Center integration module. The integration module is installed by default on all cluster nodes as part of the SUNWscsal and SUNWscsam packages.
To enable the integration module on a cluster node, the Sun Management Center agent infrastructure must be installed and running on that node. After the Sun Management Center agent starts on the node, the integration module can be loaded and enabled through the Sun Management Center console. The Sun Management Center server and console can be installed on one of the cluster nodes, but they are usually installed on another system.
Similar to the SNMP event MIB, the integration module needs to be enabled on only one cluster node to receive cluster SNMP MIB data and traps. The integration module MIB OID is 1.3.6.1.4.1.42.2.80.1.1.1.
The Sun Management Center agent running on a cluster node sends SNMP traps to the Sun Management Center server whenever the status of an object changes, such as a resource group going online or offline, or becoming managed or unmanaged. The SNMP traps also can be sent directly from the Sun Management Center agent to any other hosts by adding the secondary trap destination through the Sun Management Center es-trapdest command. The following example shows how to add myHost to the hosts that receive Sun Management Center SNMP traps from the agent on port 11162.
Example 4.8. Adding a Secondary Trap Destination to the Sun Management Center Agent
Add myHost as a secondary trap destination using the es-trapdest command.
# /opt/SUNWsymon/sbin/es-trapdest -c agent -a myHost 11162
The agent has to be restarted for the setting to take effect.