Administer > Configure NNMi in a High Availability Cluster > Verifying the Prerequisites to Configuring NNMi for High Availability

Verifying the Prerequisites to Configuring NNMi for High Availability

Successful configuration of NNMi for High Availability (HA) depends on a number of factors:

  • Appropriate hardware
  • Understanding of the HA product
  • A methodical approach to configuration

Before you begin to configure NNMi for HA, complete the following preparation:

  1. Verify that NNMi supports your HA product by checking the information in the NNMi Support Matrix.
  2. Read the documentation for your HA product to familiarize yourself with the capabilities of that product and to make design decisions.

    Tip HA product documentation changes frequently. Be sure you have the most recent versions available.

  3. Verify that each system to be included as a node in an NNMi HA cluster meets the following requirements:

    • Meets all requirements described in the documentation for the HA product.
    • Includes at least two network interface cards (NIC cards).

      Note Review the HA product, operating system, and NIC card documentation to verify that these products can all work together.

    • Supports the use of a virtual IP address for the HA resource group. This IP address is the IP address used for the NNMi license.

      Note WSFC requires multiple virtual IP addresses, one for the HA cluster and one for each HA resource group. In this case, the virtual IP address of the NNMi HA resource group is the IP address used for the NNMi license.

    • Supports the use of a shared disk or disk array

      Note Review the HA product, operating system, and disk manufacturer documentation to verify that these products, including the related SCSI cards, can all work together.

    • Meets all requirements for NNMi as described in the NNMi Support Matrix.
  4. If you plan to run any NNM iSPIs in the NNMi HA cluster, read the appropriate NNM iSPI documentation for additional HA configuration prerequisites.
  5. Allocate the following virtual IP addresses and host names:

    • One virtual IP address for the HA cluster (WSFC only)
    • One virtual IP address for each HA resource group to be configured
  6. From any system, use the nslookup command to validate correct DNS response for all of the IP addresses and hostnames you allocated in step 5.
  7. Verify that operating system of each system is at the correct version and patch level for the HA product and NNMi.
  8. If necessary, install the HA product.

  9. Prepare the shared disk as described in Prepare the Shared Disk Manually in High Availability Environments.
  10. Use the commands for your HA product to configure (if necessary) and test an HA cluster.

    The HA cluster provides such functionality as checking the application heartbeat and initiating failover. The HA cluster configuration must, at a minimum, include the following items:

    • (Linux only) ssh, remsh, or both
    • (Windows only) Virtual IP address for the HA cluster that is DNS-resolvable
    • Virtual hostname for the HA cluster that is DNS-resolvable
    • A resource group that is unique and specific to NNMi.

      Note NNMi expects that the NNMi HA resource group includes all required resources. If this is not the case, use the HA product functionality to manage dependencies between the NNMi HA resource group and the other HA resource groups. For example, if Oracle is running in a separate HA resource group, configure the HA product to ensure that the Oracle HA resource group is fully started before the HA product starts the NNMi HA resource group.

    • WSFC: Use the create cluster wizard of Failover Cluster Management for Windows Server. Be sure to add computer objects to the domain controllers.
    • VCS: Not necessary. Product installation created an HA cluster.
    • RHCS: Add services (cman, rgmanager) as described in the RHCS documentation.

    For information about testing the resources that you will place into the NNMi HA resource group, see HA Resource Testing.

This text is used in the following locations:

IPv6 chapter in the Deployment Reference

UCMDB integration chapter in the Integration Reference