Hitachi

JP1 Version 12 JP1/Network Node Manager i Setup Guide

19.6.2 Maintaining NNMi in an HA cluster

Note

For HA Monitor, some of the procedures might differ. For the actual procedures, see the Release Notes.

Organization of this subsection

(1) Starting and stopping NNMi

While NNMi is running under HA, do not use the ovstart and ovstop commands unless instructed to do so for HA maintenance purposes. For normal operation, use the NNMi-provided HA commands (nnmhastartrg.ovpl and nnmhastoprg.ovpl) or the appropriate HA product commands for starting and stopping HA resource groups.

To Page Top

(2) Changing NNMi host names and IP addresses in a cluster environment

(a) Renaming virtual hosts

NNMi's virtual hosts cannot be renamed after NNMi has been configured for HA. To rename a virtual host, unconfigure NNMi for HA and then re-configure NNMi for HA under the new virtual host name.

(b) Changing virtual IP addresses

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

  1. Stop the NNMi HA resource group:

    • Windows

    %NnmInstallDir%misc\nnm\ha\nnmhastoprg.ovpl NNM resource-group

    net stop NnmTrapReceiver

    • Linux

    - For distributions that uses systemd to manage services

    /opt/OV/misc/nnm/ha/nnmhastoprg.ovpl NNM resource-group

    /opt/OV/bin/nettrap stop

    - Other distributions

    /opt/OV/misc/nnm/ha/nnmhastoprg.ovpl NNM resource-group

    /etc/init.d/nettrap stop

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

    • Windows

      In the cluster's management console, change the IP address resource configuration. Open the resource group, double-click resource-group-ip, select parameters, and then enter the new IP address.

    • Linux

      /opt/OV/misc/nnm/ha/nnmhargconfigure.ovpl NNM resource-group -set_value resource-group-ip Address new-IP-address

      Run haconf -dump -makero to apply the configuration change to the HA cluster.

  3. Start the NNMi HA resource group:

    • Windows

      %NnmInstallDir%misc\nnm\ha\nnmhastartrg.ovpl NNM resource-group

    • Linux

      /opt/OV/misc/nnm/ha/nnmhastartrg.ovpl NNM resource-group

  4. Verify that NNMi started correctly:

    • Windows

      %NnmInstallDir%bin\ovstatus -c

    • Linux

      /opt/OV/bin/ovstatus -c

(c) Renaming physical hosts

If you need to rename a physical host in the system in a cluster environment, do so after stopping NNMi. No NNMi settings are required. After the physical host has been renamed, start NNMi.

Note that physical host names (computer names) cannot be changed in Windows cluster environments.

(d) Changing physical IP addresses

For details about the procedure for changing a physical IP address, see 22.4 Changing the IP address of a stand-alone NNMi management server.

To Page Top

(3) Stopping NNMi without causing failover

To perform NNMi maintenance, you can stop NNMi on the active cluster node without causing failover to a currently passive cluster node. Follow these steps on the active cluster node:

  1. If there are related products that require NNMi, stop those products or place them into a mode equivalent to maintenance mode.

  2. Put the HA resource group in maintenance mode as described in (1) Placing NNMi in maintenance mode.

  3. Stop NNMi:

    ovstop -c

To Page Top

(4) Restarting NNMi after maintenance

If you have stopped NNMi in the manner that prevents failover, follow these steps to restart NNMi and HA monitoring:

  1. Start NNMi:

    ovstart -c

  2. Verify that NNMi started correctly:

    ovstatus -c

    All NNMi services must show the state RUNNING.

  3. Take the HA resource group out of maintenance mode as described in (2) Removing NNMi from maintenance mode.

  4. If you have stopped or placed NNMi-related products into maintenance mode, restore them to their initial state.

To Page Top

(5) Backing up NNMi configured for HA

(a) Online backup

If you use online backups, verify that the shared disk is accessible from the active cluster node, and then perform the normal backup procedure.

(b) Offline backup

To make an offline backup of NNMi configured for HA, perform the procedure described below. For details about the maintenance mode indicated in the procedure, see 19.6.1 Placing NNMi in maintenance mode.

  1. Determine which cluster node in the HA cluster is active:

    • Windows

    %NnmInstallDir%misc\nnm\ha\nnmhaclusterinfo.ovpl -group resource-group -activeNode

    • Linux

    /opt/OV/misc/nnm/ha/nnmhaclusterinfo.ovpl -group resource-group -activeNode

  2. Place the active cluster node in the maintenance mode.

  3. Stop NNMi:

    ovstop -c

  4. Verify that the shared disk is online by using an HA product operation. If the shared disk is offline, place it online.

  5. Verify that the shared disk is accessible, and then execute the nnmbackup.ovpl command to perform an offline backup and obtain backup data.

  6. Start NNMi:

    ovstart -c

    Wait until NNMi completes its startup.

  7. After NNMi services have started, release maintenance mode.

To Page Top

(6) Restoring NNMi configured for HA

To restore backup data, perform the procedure described below. For details about the maintenance mode indicated in the procedure, see 19.6.1 Placing NNMi in maintenance mode.

Important

Do not restore backup data obtained from an NNMi with a single configuration to an NNMi with a cluster configuration.

  1. Restore NNMi to a status in which NNMi runs successfully as a cluster and is configured for HA.

    For example, if part or all of the system has failed due to a hardware failure, restore the system so that NNMi runs with the HA configuration.

  2. Set the node used to perform restore processing as the active cluster node.

  3. Place the active cluster node in the maintenance mode.

  4. Perform restore processing.

    • For backup data obtained by using the nnmbackup.ovpl command

      Use the nnmrestore.ovpl command to restore the backup data.

    • For backup data obtained by using the nnmbackupembdb.ovpl command

      Use the nnmrestoreembdb.ovpl command to restore the backup data.

      Important

      If you use the nnmrestore.ovpl command to restore backup data obtained on another node, do not specify the lic option so that that node's license is not applied.

  5. Start NNMi:

    ovstart -c

  6. Release maintenance mode.

  7. Perform steps 2 through 6 on the remaining node.

    These steps are necessary in order to synchronize the configuration files on all nodes' local disks. Make sure that you restore the same backup data.

    If you use the nnmrestoreembdb.ovpl command, restore the backup data only on one node because this command restores a database on the shared disk.

To Page Top

(7) Initializing the database

  1. Determine which cluster node in the HA cluster is active:

    • Windows

    %NnmInstallDir%misc\nnm\ha\nnmhaclusterinfo.ovpl -group resource-group -activeNode

    • Linux

    /opt/OV/misc/nnm/ha/nnmhaclusterinfo.ovpl -group resource-group -activeNode

  2. Place the active cluster node in the maintenance mode.

  3. Verify that the shared disk is accessible.

  4. Initialize the database by executing the nnmresetembdb.ovpl command with no argument specified:

    • Windows

      %NnmInstallDir%bin\nnmresetembdb.ovpl

    • Linux

      /opt/OV/bin/nnmresetembdb.ovpl

  5. Execute ovstatus -c to verify that the NNMi services are running.

  6. Release the maintenance mode.

To Page Top

© Copyright 2009-2022 Micro Focus or one of its affiliates.

All Rights Reserved. Copyright (C) 2019, 2022, Hitachi, Ltd.

This software and documentation are based in part on software and documentation under license from Micro Focus or one of its affiliates.