Configuring NNMi on the Primary Cluster Node

Complete the following procedure on the primary cluster node.

1. If you have not already done so, complete the procedure for Verifying the Prerequisites to Configuring NNMi for High Availability.
2. If you have not already done so, install NNMi (including the latest consolidated patch, if any), and then verify that NNMi is working correctly.
3. If you expect to run any NNM iSPIs on this NNMi management server, see Configure NNM iSPIs for High Availability before continuing with this procedure.

4. Use the nnmbackup.ovpl command, or another database command, to back up all NNMi data. For example:

   nnmbackup.ovpl -type offline -scope all -target nnmi_backups

5. Define the disk device group (and logical volume), consisting of at least one shared disk for the NNMi HA resource group. For example:

   • WSFC: Use Disk Management to configure the disk mount point and format the disk.

   • VCS:

     Use VSF commands such as vxdiskadm, vxassist, and mkfs to add and initialize the disk, allocate disks by space, and create the logical volume.

   • RHCS:

     Use LVM commands such as pvcreate, vgcreate, and lvcreate to initialize the disk, create the volume group, and create the logical volume.

   Note NNMi requires RHCS clusters be configured such that the cluster node names specified in the /etc/cluster/cluster.conf file must be fully qualified for NNMi to correctly start and stop.

   For Linux operating systems, a reference web site is:
   http://www.unixguide.net/unixguide.shtml

6. Create the directory mount point (for example, S:\ or /nnmmount), and then mount the shared disk:

   • Windows: Use the Windows Explorer and Disk Management tool to assign a drive letter.

     Caution Use the Disk Management tool make sure that the shared disk displays online. If it displays reserved, this indicates WSFC has control of the shared disk. Use the Delete action from the WSFC user interface to remove the shared disk from WSFC control. Also use the Disk Management tool to confirm that the reserve flag is changed to online.

   • Linux:

     • Use the mkdir and mount commands.

     • Verify that the shared disk directory mount point has been created with root as the user, sys as the group, and the permissions set to 755. For example:

       ls -l /nnmmount

       Caution After configuration, the HA product manages disk mounting. Do not update the files system table with this mount point.

7. Stop NNMi:

   ovstop -c

   Note If NNMi is already installed on a node that you will include in this HA resource group, also run ovstop -c on that node at this time.

8. Copy the NNMi database to the shared disk:

   • Windows:

     %NnmInstallDir%\misc\nnm\ha\nnmhadisk.ovpl NNM -to <HA_mount_point>

   • Linux:

     $NnmInstallDir/misc/nnm/ha/nnmhadisk.ovpl NNM -to <HA_mount_point>

   Note To prevent database corruption, run this command (with the -to option) only one time. For information about alternatives, see Re-Enable NNMi for High Availability after All Cluster Nodes are Unconfigured.

9. (Linux only) Unmount the shared disk and deactivate the disk group:

   umount <HA_mount_point>

   vgchange -a n <disk_group>

10. Verify that NNMi is not running:

    ovstop -c

11. (RHCS only) Perform the following to add the necessary NNMscript resource to the /usr/share/cluster/cluster.rng file:

    1. Save a copy of the cluster.rng file.
    2. Edit the /usr/share/cluster/cluster.rng file as follows:
       1. Find <define name=”CHILDREN”>.

       2. Embed the contents of the file /opt/OV/misc/nnm/ha/NNMscript.rng ahead of the statement found in the previous step.

          For example go one line above <define name=”CHILDREN”>, and type:

          :r /opt/OV/misc/nnm/ha/NNMscript.rng

       3. In the CHILDREN XML block, add the text that is bold in the following:

          <define name=”CHILDREN”>

           <zeroOrMore>

            <choice>

                 …

                 <ref name=”SCRIPT”/>                

                 <ref name=”NNMSCRIPT”/>

                 <ref name=”NETFS”/>

       4. Save the cluster.rng file.
    3. Copy the /opt/OV/misc/nnm/ha/NNMscript.sh file to /usr/share/cluster and ensure that it has 755 permissions with root:root ownership.
    4. Restart the ccsd service or reboot.

    5. If you rebooted the system in the previous step, before continuing with the cluster configuration, stopNNMi:

       ovstop -c

    6. Verify that NNMi is not running:

       ovstatus -c

12. Configure the NNMi HA resource group:

    • Windows:

      %NnmInstallDir%\misc\nnm\ha\nnmhaconfigure.ovpl NNM

    • Linux:

      $NnmInstallDir/misc/nnm/ha/nnmhaconfigure.ovpl NNM

13. (Linux only) By default, NNMi starts in the locale of the user who ran the nnmhaconfigure.ovpl command. To change the NNMi locale, run the following command:

    $NnmInstallDir/misc/nnm/ha/nnmhaclusterinfo.ovpl –config NNM –set HA_LOCALE <locale>

14. In step 12, determine the value you specified for the shared file system type:

    • For type disk, the nnmhaconfigure.ovpl command configured the shared disk. Continue with step 15.
    • For type none, prepare the shared disk as described in Prepare the Shared Disk Manually in High Availability Environments, and then continue with step 15.

15. 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>

    If NNMi does not start correctly, see Troubleshooting the HA Configuration.