Changing NNMi Hostnames and IP Addresses in a Cluster Environment

A node in a cluster environment can have more than one IP address and hostname. If a node becomes a member of another subnet, you might need to change its IP addresses. As a result, the IP address or fully-qualified domain name might change.

For example, on Linux systems, the IP address and the related hostname are generally configured in one of the following:

• /etc/hosts
• Domain Name Service (DNS)
• Network Information Service (NIS)

NNMi also configures the hostname and IP address of the management server for the managed node in the NNMi database.

If you are moving from a non-name-server environment to a name-server environment (that is, DNS or BIND), make sure that the name server can resolve the new IP address.

Hostnames work within IP networks to identify a managed node. While a node might have many IP addresses, the hostname is used to pinpoint a specific node. The system hostname is the string returned when you use the hostname command.

When changing the virtual hostname or IP address of the NNMi HA resource group, you must update the licenses.txt file on the shared disk with the new information from the license file on the active node. Complete the following procedure to correctly update the HA configuration.

To change the virtual hostname or IP address of the NNMi HA resource group, perform these steps on the active NNMi cluster node:

If you have purchased NNMi Premium or NNMi Ultimate, you need to use the license keys you requested from the Password Delivery Center for use with application failover or high availability. Be sure to request the following:

• High Availability: Obtain a license key for the virtual IP address of the NNMi HA resource group. This license key is initially used on the primary server and then used on the secondary server when needed.
• Application Failover: Obtain two license keys; one for the physical IP address of the primary server and one for the physical IP address of the standby server.

1. Convert the license keys for the prior virtual IP address of the NNMi HA resource group to the new virtual IP address of the NNMi HA resource group.

   Caution Do not install the new license keys at this time.

2. Put the NNMi HA resource group into maintenance mode as described in Putting an HA Resource Group into Maintenance Mode.

3. Stop the NNMi HA resource group:

   • Windows:

     %NnmInstallDir%\misc\nnm\ha\nnmhastoprg.ovpl NNM <resource_group>

   • Linux:

     $NnmInstallDir/misc/nnm/ha/nnmhastoprg.ovpl NNM <resource_group>

4. Change the IP address or node name of the NNMi HA resource group:

   1. In the ov.conf file, edit the NNM_INTERFACE entry to be the new hostname or IP address.
   2. In the ovspmd.auth file, edit any lines containing the old hostname to contain the new hostname.

   The ov.conf and ovspmd.auth files are available in the following location:

   • Windows: %NnmDataDir%\shared\nnm\conf
   • Linux: $NnmDataDir/shared/nnm/conf

5. If you changed the node name of the NNMi HA resource group, set NNMi to use the new fully-qualified domain name of the NNMi HA resource group with the nnmsetofficialfqdn.ovpl command. For example:

   nnmsetofficialfqdn.ovpl newnnmi.servers.example.com

   For more information, see the nnmsetofficialfqdn.ovpl reference page, or the Linux manpage.

6. Change the cluster configuration to use the new IP address:

   • WSFC:

     In Failover Cluster Management, open <resource_group>.

     Double-click <resource_group>-ip, select Parameters, and the enter the new IP address.

   • VCS:

     $NnmInstallDir/misc/nnm/ha/nnmhargconfigure.ovpl NNM <resource_group> -set_value <resource_group>-ip 
     Address <new_IP_address>

   • RHCS:

     On the active HA cluster node, edit the /etc/cluster/cluster.conf file to replace ip address="<old_IP_address>" with ip address="<new_IP_address>". Then run ccs_tool update /etc/cluster/cluster.conf to update all other systems.

7. Install the license keys for the new virtual IP address of the NNMi HA resource group as described in Apply Licenses.

8. Update the licenses.txt file on the shared disk with the new information from the LicFile.txt file on the active node. Do one of the following:

   • If the licenses.txt file exists in the NNM directory on the shared disk, append the new license keys in LicFile.txt on the active node to licenses.txt on the shared disk.
   • If the licenses.txt file does not exist on the shared disk, copy LicFile.txt from the active node to licenses.txt in the NNM directory on the shared disk.

   On the active node, the LicFile.txt file is in the following location:

   • Windows: %NnmDataDir%\shared\nnm\conf\licensing\LicFile.txt
   • Linux: $NnmDataDir/shared/nnm/conf/licensing/LicFile.txt

   On the shared disk, example locations of the licenses.txt file are as follows:

   • Windows: S:\NNM\licenses.txt
   • Linux: /nnmount/NNM/licenses.txt

9. Start the NNMi HA resource group:

   • Windows:

     %NnmInstallDir%\misc\nnm\ha\nnmhastartrg.ovpl NNM <resource_group>

   • Linux:

     $NnmInstallDir/misc/nnm/ha/nnmhastartrg.ovpl NNM <resource_group>

10. Verify that NNMi started correctly:

    ovstatus -c

    All NNMi services should show the state RUNNING.

11. Take the NNMi HA resource group out of maintenance mode as described in Removing an HA Resource Group from Maintenance Mode.