IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Create clusters with monitoring components in a System Automation for Multiplatforms environment > Prepare for the base Tivoli Monitoring cluster with Tivoli System Automation for Multiplatform
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Check the cluster nodes environment
Before you install the Base cluster, check the environment thoroughly:
- Ensure that the name resolution for all network interface cards works properly
- Ensure that all entries for host names in the local host table, /etc/hosts, are set in the same order on both computers. For example, if /etc/hosts on node1 contains:
10.0.0.1 host.domain.com host
/etc/hosts on node2 should also contain:
10.0.0.1 host.domain.com host
And not:
10.0.0.1 host host.domain.com
- Ensure that the host tables have no double entries for the localhost. Under SUSE SLES10, using two network interface cards, you might see the following two entries:
localhost localhost
Remove the second entry, otherwise, clustering fails.
Ensure that the name resolution works for the virtual IP address that will be used for the cluster (the provided scripts assume that the virtual IP address is on the same subnet as the IP addresses of the nodes).
Verify that the virtual IP address of the cluster is a valid address, to avoid conflicts.
Verify that this Virtual IP address is not defined (doesn’t show up in ifconfig – a) on any interface on any node in the cluster.
Ensure that this IP address is valid for the configured addresses on the public network interface cards of the cluster nodes.
Verify on both nodes that the shared disk will not be mounted automatically during startup.
Verify on both nodes that the shared disk file system is not checked on start up of the node (fsck is not run).
Parent topic:
Prepare for the base Tivoli Monitoring cluster with Tivoli System Automation for Multiplatform