IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > The clustering of IBM Tivoli Monitoring components > What to expect from the IBM Tivoli Monitoring infrastructure in a clustered environment
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Clustered agentless monitoring
With the Agentless Monitoring Server now maintaining connections to hundreds of servers, it becomes a more critical component in the infrastructure than a single agent instance.
The following two options are available:
- Option 1: Run the Agentless Monitoring Server within an Operating System cluster. The cluster provides the desired HA functionality.
- Option 2: Develop a set of custom situations, take action commands, and scripts in IBM Tivoli Monitoring to natively monitor the Agentless Monitoring Server status.
- Two Agentless Monitoring Servers are configured, with environment files modified to register to IBM Tivoli Monitoring with the same system name. The primary Agentless Monitor is started, while the backup Agentless Monitor is offline.
- Periodic scripting is done to synchronize the configurations between the two Agentless Monitors.
- If the Primary Agentless Monitor goes offline, the self-monitoring situation triggers, forwarding information to the event console for problem determination.
- A Take Action command associated with the situation issues a start command to the backup Agentless Monitor.
When you use Agentless Monitoring, a percentage of preparation time needs to be devoted to verifying the native data emitter configurations. Complete the following preparation tasks:
- Ensure that the SNMP daemons are installed, configured, and started
- Verify the MIB branches in SNMP configuration files
- Verify all Windows passwords and user account rights for Windows API collection
- Verify that the following patch levels for endpoint systems are installed:
- AIX and SLES systems are most likely to require SNMP patches
- Solaris CIM-XML systems are most likely to require CIM patches
- RedHat, HP-UX, and Windows agents typically operate as delivered. If possible, use tools such as snmpwalk, WMIExplorer, and perfmon to verify the metrics are configured before configuring IBM Tivoli Monitoring to monitor the environments
Single-computer installations have no problems for small environments where you want to monitor less than 50 remote systems. For information on Agentless monitoring, see the IBM Tivoli Monitoring: Installation Guide.
Parent topic:
What to expect from the IBM Tivoli Monitoring infrastructure in a clustered environment