Hitachi

JP1 Version 12 JP1/Network Node Manager i Setup Guide

24.4.1 Upgrading from NNMi 12-10 configured for application failover

To upgrade from NNMi 12-10 while running in an NNMi application failover configuration, follow the steps provided below.

Organization of this subsection

(1) Upgrading to NNMi 12-50 configured for application failover

To upgrade NNMi management servers configured for application failover, follow these steps:

  1. As a precaution, run the nnmconfigexport.ovpl script on both the active and the standby NNMi management servers before proceeding.

    For details, see 4.2 Best practice: Save the existing configuration.

  2. As a precaution, back up your NNMi data on both the active and standby NNMi management servers before proceeding.

    For details, see 20.2.2 Backup scope.

  3. Complete the steps provided below on the active NNMi management server.

    Note that NNMi must be running for the following nnmcluster steps to work. Completing these steps will reduce the time needed for startup of the standby NNMi management server shown in step 7.

    a. Run the nnmcluster command.

    b. When NNMi prompts you, type dbsync, then press Enter. Review the displayed information to make sure it includes the following messages:

    • ACTIVE_DB_BACKUP: Reports that the active NNMi management server is performing a new backup.

    • ACTIVE_NNM_RUNNING: Reports that the active NNMi management server has completed the backup reported in the previous message.

    • STANDBY_RECV_DBZIP: Reports that the standby NNMi management server is receiving a new backup from the active NNMi management server.

    • STANDBY_READY: Reports that the standby NNMi management server is ready to perform in the event of a failure of the active NNMi management server.

    c. Run exit or quit to stop the interactive nnmcluster process you started in step a.

  4. Run the nnmcluster -shutdown command on the standby NNMi management server.

    This stops all nnmcluster processes on the standby NNMi management server.

  5. To verify there are no nnmcluster nodes running on the standby NNMi management server, complete the following steps on the standby NNMi management server:

    a. Run the nnmcluster command.

    b. Verify that there are no local nnmcluster nodes present except the one marked (SELF). There might be one or more remote nodes present.

    c. Run exit or quit to stop the interactive nnmcluster process you started in step a.

  6. Complete the following steps on the standby NNMi management server to temporarily disable application failover:

    a. Edit the following file:

    • Windows: %NNM_SHARED_CONF%\props\nms-cluster.properties

    • Linux: $NNM_SHARED_CONF/props/nms-cluster.properties

    b. Comment out the com.hp.ov.nms.cluster.name parameter.

    c. Save your change.

    d. Edit the following file:

    • Windows: %NNM_DB%\Postgres\postgresql.conf

    • Linux: $NNM_DB/Postgres/postgresql.conf

    e. Delete the following application failover settings:

    • Line beginning with # The following lines were added by the NNM cluster.

    • Line beginning with archive_command =

    • Line beginning with archive_timeout =

    • Line beginning with max_wal_senders =

    • Line beginning with archive_mode =

    • Line beginning with wal_level =

    • Line beginning with hot_standby =

    • Line beginning with wal_keep_segments =

    • Line beginning with listen_addresses =

    f. Save your changes.

    g. Create the following null file:

    • Windows: %NNM_TMP%\postgresTriggerFile

    • Linux: $NNM_TMP/postgresTriggerFile

  7. Start and then stop processes on the standby NNMi management server.

    a. Run the ovstart command on the standby NNMi management server. Running the ovstart command causes the standby NNMi management server to import the transaction logs from the active NNMi management server.

    b. When the ovstart command has finished, run the ovstatus -v command. All NNMi services normally show the state RUNNING.

    c. Run the ovstop command on the standby NNMi management server.

  8. Upgrade the standby NNMi management server to NNMi 12-50 by following the instructions in 2. Installing and Uninstalling NNMi and the Release Notes.

    If the certificate repository is not already migrated to the PKCS#12 repository, after upgrade installation, please migrate to the PKCS #12 repository on the former standby NNMi management server by using the steps in 10.2 Configuring an Upgraded NNMi Environment to Use the New Keystore.

    You now have the former active NNMi management server running NNMi 12-10 or earlier and the former standby NNMi management server running NNMi 12-50. These NNMi management servers are now running independently with no database synchronization. This means that both NNMi management servers are monitoring the network in parallel.

    To complete the upgrade and remedy this situation, select a time to upgrade the former active node to NNMi 12-50. Have the operators temporarily use the former standby node to monitor the network while you complete the upgrade.

    The remainder of this procedure assumes you plan to retain the database information from the former active node and discard the database information from the former standby node.

  9. Run the nnmcluster -halt command on the former active NNMi management server.

  10. To verify that there are no nnmcluster nodes running on the former active NNMi management server, complete the following steps on the former active NNMi management server:

    a. Run the nnmcluster command.

    b. Verify that there are no local nnmcluster nodes present except the one marked (SELF). There might be one or more remote nodes present.

    c. Run exit or quit to stop the interactive nnmcluster process you started in step a.

  11. Complete the following steps on the former active NNMi management server to disable application failover temporarily:

    a. Edit the following file:

    • Windows: %NNM_SHARED_CONF%\props\nms-cluster.properties

    • Linux: $NNM_SHARED_CONF/props/nms-cluster.properties

    b. Comment out the com.hp.ov.nms.cluster.name parameter.

    c. Save your changes.

  12. Upgrade the former active NNMi management server to NNMi 12-50 by following the instructions in 2. Installing and Uninstalling NNMi.

    If the certificate repository is not already migrated to the PKCS#12 repository, after upgrade installation, please migrate to the PKCS #12 repository on the former active NNMi management server by using the steps in 10.2 Configuring an Upgraded NNMi Environment to Use the New Keystore.

    Now you have two servers running NNMi 12-50, but they are still independent because the databases are not synchronized.

  13. Complete the following steps on the former active NNMi management server:

    a. Run the ovstop command.

    b. Edit the following file:

    • Windows: %NNM_SHARED_CONF%\props\nms-cluster.properties

    • Linux: $NNM_SHARED_CONF/props/nms-cluster.properties

    c. If you have upgraded from version 11-50, type in the value of the com.hp.ov.nms.cluster.name parameter.

    If you have upgraded from version 11-50, the commented-out properties are not preserved, so you must retype the cluster name.

    d. Uncomment the com.hp.ov.nms.cluster.name parameter.

    e. Save your changes.

  14. Run either the ovstart command or the nnmcluster -daemon command on the former active NNMi management server. It is now the active cluster node.

  15. Instruct the operators to begin using the active cluster node to monitor the network.

    The former standby NNMi management server discards all database activity that occurred during the maintenance process, from step 9 through step 13.

  16. Complete the following steps on the former standby NNMi management server:

    a. Run the ovstop command.

    b. Edit the following file:

    Windows: %NNM_SHARED_CONF%\props\nms-cluster.properties

    Linux: $NNM_SHARED_CONF/props/nms-cluster.properties

    c. If you have upgraded from version 11-50, type in the value of the com.hp.ov.nms.cluster.name parameter.

    d. Comment out the com.hp.ov.nms.cluster.name parameter.

    e. Save your changes.

  17. Run either the ovstart command or the nnmcluster -daemon command on the former standby NNMi management server.

    This NNMi management server becomes the standby node and receives a copy of the database from the active cluster node.

To Page Top

(2) Applying patches to NNMi 12-50 configured for application failover

Both NNMi management servers must be running the same NNMi version and patch level. To apply patches to the active and standby NNMi management servers, use either of the following procedures:

(a) Applying patches for application failover, shutting down both the active and standby servers

This procedure results in both NNMi management servers being inactive for some period of time during the patch installation process. To apply patches on the NNMi management servers configured for application failover, follow these steps:

  1. As a precaution, run the nnmconfigexport.ovpl script on both the active and the standby NNMi management servers before proceeding.

    For details, see 4.2 Best practice: Save the existing configuration.

  2. As a precaution, back up your NNMi data on both the active and the standby NNMi management servers before proceeding.

    For details, see 20.2.2 Backup scope.

  3. As a precaution, run the following procedure on the active NNMi management server:

    a. Run the nnmcluster command.

    b. When NNMi prompts you, type dbsync, then press Enter. Review the displayed information to make sure it includes the following messages:

    • ACTIVE_DB_BACKUP: Reports that the active NNMi management server is performing a new backup.

    • ACTIVE_NNM_RUNNING: Reports that the active NNMi management server has completed the backup reported in the previous message.

    • STANDBY_READY: Reports the previous status of the standby NNMi management server.

    • STANDBY_RECV_DBZIP: Reports that the standby NNMi management server is receiving a new backup from the active NNMi management server.

    • STANDBY_READY: Reports that the standby NNMi management server is ready to perform in the event of a failure of the active NNMi management server.

    c. Run exit or quit to stop the interactive nnmcluster process you started in step a.

  4. Run the nnmcluster -halt command on the active NNMi management server.

    This stops all nnmcluster processes on both the active and standby NNMi management servers.

  5. To verify there are no nnmcluster nodes running on both servers, complete the following steps on both the active and the standby NNMi management servers:

    a. Run the nnmcluster command.

    b. Verify that there are no nnmcluster nodes present except the one marked (SELF).

    c. Run exit or quit to stop the interactive nnmcluster process you started in step a.

  6. On the active NNMi management server, comment out the com.hp.ov.nms.cluster.name parameter in the nms-cluster.properties file:

    a. Edit the following file:

    • Windows: %NNM_SHARED_CONF%\props\nms-cluster.properties

    • Linux: $NNM_SHARED_CONF/props/nms-cluster.properties

    b. Comment out the com.hp.ov.nms.cluster.name parameter.

    c. Save your change.

  7. Apply the NNMi patches on the active NNMi management server using the instructions in RELEASE.TXT provided with the patches.

  8. On the active NNMi management server, uncomment the com.hp.ov.nms.cluster.name parameter in the nms-cluster.properties file:

    a. Edit the following file:

    • Windows: %NNM_SHARED_CONF%\props\nms-cluster.properties

    • Linux: $NNM_SHARED_CONF/props/nms-cluster.properties

    b. Uncomment the com.hp.ov.nms.cluster.name parameter.

    c. Save your change.

  9. Run the ovstart command on the active NNMi management server.

  10. Verify that the patches have been installed correctly on the active NNMi management server by viewing information on the Product tab of the Help > System Information window in the NNMi console.

  11. Run the nnmcluster -dbsync command to make a new backup.

  12. On the standby NNMi management server, comment out the com.hp.ov.nms.cluster.name parameter in the nms-cluster.properties file, as shown in a through c in step 6.

  13. Apply the NNMi patches on the standby NNMi management server.

  14. On the standby NNMi management server, uncomment the com.hp.ov.nms.cluster.name parameter in the nms-cluster.properties file, as shown in a through c in step 8.

  15. Run the ovstart command on the standby NNMi management server.

(b) Applying patches for application failover, keeping one NNMi management server active

This procedure results in one NNMi management server always being active during the patch installation process.

Although this method preserves continuous monitoring of the network, NNMi loses the transaction logs that are generated during this patch installation process.

To apply NNMi patches on the NNMi management servers configured for application failover, follow these steps:

  1. As a precaution, run the nnmconfigexport.ovpl script on both the active and the standby NNMi management servers before proceeding.

    For details, see 4.2 Best practice: Save the existing configuration.

  2. As a precaution, back up your NNMi data on both the active and the standby NNMi management servers before proceeding.

    For details, see 20.2.2 Backup scope.

  3. Run the nnmcluster command on one of the nodes.

  4. Enter dbsync on the NNMi management server used in the previous step to synchronize the two databases.

    The dbsync option works on an NNMi management server using an embedded database.

  5. Wait until the active NNMi management server reverts to ACTIVE_NNM_RUNNING and the standby NNMi management server reverts to STANDBY_READY before continuing.

  6. Exit from or quit the nnmcluster command.

  7. Stop the cluster on the standby NNMi management server by running the following command on the standby NNMi management server:

    nnmcluster -shutdown

  8. Make sure the following processes and services have terminated before continuing:

    - postgres
- ovjboss

  9. Make sure the nnmcluster process has terminated before continuing.

    If the nnmcluster process will not terminate, manually kill the nnmcluster process only as a last resort.

  10. Edit the following file on the standby NNMi management server:

    • Windows: %nnmDataDir%shared\nnm\conf\props\nms-cluster.properties

    • Linux: $nnmDataDir/shared/nnm/conf/props/nms-cluster.properties

  11. Comment out the cluster name property by placing a hash mark (#) at the beginning of the line, then save your change:

    #com.hp.ov.nms.cluster.name = NNMicluster

  12. Apply the NNMi patches on the standby NNMi management server.

  13. At this point, the standby NNMi management server has been patched but is stopped, and the active NNMi management server has not been patched and is running.

    Stop the active NNMi management server and immediately bring the standby NNMi management server online to monitor your network.

  14. Shut down the cluster on the active NNMi management server by running the following command on the active NNMi management server:

    nnmcluster -halt

  15. Make sure the nnmcluster process has terminated.

    If it does not terminate within a few minutes, manually kill the nnmcluster process.

  16. On the standby NNMi management server, uncomment the cluster name from the nms-cluster.properties file.

  17. Start the cluster on the standby NNMi management server by running the following command on the standby NNMi management server:

    nnmcluster -daemon

  18. Install the NNMi patches on the active NNMi management server.

  19. At this point, the previous active NNMi management server has been patched but is offline.

    Bring it back into the cluster (as the standby NNMi management server) by performing the following:

    a. Uncomment the entry in the nms-cluster.properties file on the active NNMi management server.

    b. Start the active NNMi management server with the following command:

    nnmcluster -daemon

  20. To monitor the progress, run the following command on both the active and the standby NNMi management servers:

    nnmcluster

    Wait until the previous active NNMi management server finishes retrieving the database from the previous standby NNMi management server.

  21. After the previous active NNMi management server displays STANDBY_READY, run the following command on the previous active NNMi management server:

    nnmcluster -acquire

To Page Top

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

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

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