19.7.3 Unconfiguring NNMi on the active cluster node

1. On the active cluster node, stop the NNMi HA resource group and NnmTrapReceiver.

   • Windows

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

   net stop NnmTrapReceiver

   • Linux

   - For distributions that uses systemd to manage services

   $NnmInstallDir/misc/nnm/ha/nnmhastoprg.ovpl NNM resource-group

   /opt/OV/bin/nettrap stop

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

   - Other distributions

   $NnmInstallDir/misc/nnm/ha/nnmhastoprg.ovpl NNM resource-group

   /etc/init.d/nettrap stop

   Important

   In a VCS or SCS environment where NNMi is in an HA configuration and the physical host name has been changed, before a resource group is stopped, the physical host name must be reverted to the name that was used when HA was configured. To continue using the new host name even after switching to a single server configuration, cancel the HA configuration, and then configure the required settings as described in

   22.5 Changing the host name or domain name of an NNMi management server

   .

2. On the active cluster node, unconfigure NNMi from the HA cluster:

   • Windows

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

   • Linux

   $NnmInstallDir/misc/nnm/ha/nnmhaunconfigure.ovpl NNM resource-group

   This command removes the corresponding node from the list of failover targets in the HA resource group.

   This command removes access to the shared disk but does not unconfigure the disk group or the volume group.

   The following message might be displayed, but this is not a problem:

   • WSFC

     Warning: There is no value in the public entry PUBLIC.HA_MOUNT_POINT in the resource group xxxxx in the cluster registry.

   • VCS or SCS

     VCS WARNING V-16-1-10133 Group does not exist: resource-group

3. Change the FQDN setting for the NNMi node to the physical host name.

   a. Edit the nms-local.properties file.

   File path

   - Windows: %NnmDataDir%conf\nnm\props\nms-local.properties

   - Linux: /var/opt/OV/conf/nnm/props/nms-local.properties

   What to edit

   com.hp.ov.nms.fqdn = virtual-host-name

   Specify a virtual host name, not a physical host name.

   b. Execute the nnmsetofficialfqdn.ovpl command.

   For FQDN, specify the FQDN of the physical host name (host name displayed by the hostname command).

   • Windows

     %NnmInstallDir%bin\nnmsetofficialfqdn.ovpl -force FQDN

   • Linux

     /opt/OV/bin/nnmsetofficialfqdn.ovpl -force FQDN

   This command changes the FQDN setting that was changed to the virtual host name during HA configuration to the FQDN of the physical host name.

   The following messages might be displayed during command execution:

   • For single sign-on to function normally, you must generate a new certificate manfully

     Ignore this message because single sign-on is not supported.

   • A new certificate cannot be generated. The self-signed alias xxx.xxx.xxx already exists in the key store.

     If it is displayed, rename the keystore backup file from nnm-key.p12.xxxxxxxxxxxxxx to nnm-key.p12, and rename the truststore backup file from nnm-trust.p12.xxxxxxxxxxxxxx to nnm-trust.p12 in the following directory.

     • Windows

       %NnmDataDir%shared\nnm\certificates\

     • Linux

       /var/opt/OV/shared/nnm/certificates/

     If multiple backup files exist, rename the file whose file name ends in the largest 14-digit number.

   As a result, a self-signed certificate is used. If you want to use a different self-signed certificate or a Certificate Authority (CA)-signed certificate for NNMi communications, you must do some additional work.

   For details about the certificates, see 10. Working with Certificates for NNMi.

4. On the active cluster node, move the files that are specific to the NNMi HA resource group to a separate location for safekeeping.

   If you do not plan to reconfigure the NNMi HA resource group, you do not need to save a copy of these files, and you can delete them at this time.

   • Windows

     In Explorer, delete the %NnmDataDir%hacluster\resource-group\ folder.

   • Linux

     cd /var/opt/OV/hacluster

     rm -r resource-group

5. Delete the following file:

   File path

   - Windows

   In Explorer, delete %NnmDataDir%shared\nnm\databases\nnmdatareplicator\DataReplicator.db.

   - Linux

   rm /var/opt/OV/shared/nnm/databases/nnmdatareplicator/DataReplicator.db

6. Mount the shared disk.

   Use an OS or cluster operation to make the shared disk accessible.

   Example:

   In the Server Manager, please open the management screen of Storage Services > Disks, right-click on the disk where the shared disk has mounted and select Onine.

7. Copy the NNMi files from the shared disk to the previous active cluster node.

   Perform this procedure if either of the following is applicable:

   • You will be running NNMi with a database migrated from an HA configuration to a single-server configuration.

   • You used nnmchangeembdbpw.ovpl in the HA configuration to change the database password.

   Use the following command to copy the NNMi files from the shared disk to the local disk on the previous active cluster node:

   • Windows

     %NnmInstallDir%misc\nnm\ha\nnmhadisk.ovpl NNM -from HA-mount-point

   • Linux

     /opt/OV/misc/nnm/ha/nnmhadisk.ovpl NNM -from HA-mount-point

8. Delete the NNM folder or the NNM directory from the shared disk.

9. Unmount the shared disk.

   Example:

   In the Server Manager, please open the management screen of Storage Services > Disks, right-click on the disk where the shared disk is mounted and select Offine.

10. Enable the service automatic start feature.

    • Windows

      From the Start menu, select Administrative Tools > Services, and select NNM Trap Receiver and NNM Trap Receiver Manager, and then set Startup type to Automatic.

    • RHEL 6

      ln -s /etc/init.d/nettrap /etc/rc0.d/K01nettrap

      ln -s /etc/init.d/nettrap /etc/rc1.d/K01nettrap

      ln -s /etc/init.d/nettrap /etc/rc2.d/K01nettrap

      ln -s /etc/init.d/nettrap /etc/rc3.d/S98nettrap

      ln -s /etc/init.d/nettrap /etc/rc5.d/S98nettrap

      ln -s /etc/init.d/nettrap /etc/rc6.d/K01nettrap

    • Other Linux distributions

      systemctl enable netmgt.service

      systemctl enable nettrap.service

      systemctl start netmgt.service

      systemctl start nettrap.service

      The NNMi services are started when the systemctl start command is executed.

    Note

    If you will be running NNMi on the previous active cluster node, the preparations are now complete.

    Execute ovstart to start NNMi.

    The information provided below applies if either of the following is applicable:

    • You will be running NNMi on the previous passive cluster node using a database migrated from an HA configuration to a single-server configuration.

    • You used nnmchangeembdbpw.ovpl in the HA configuration to change the database password.

11. Use the command shown below to back up the NNMi configuration on the previous active cluster node.

    This provides a backup containing the data that was copied from the shared disk to a local disk in step 7.

    • Windows

      %NnmInstallDir%bin\nnmbackup.ovpl -type offline -scope all -target directory

    • Linux

      /opt/OV/bin/nnmbackup.ovpl -type offline -scope all -target directory

12. Restore the active cluster node backup data obtained in step 11 to the previous passive cluster node on which you want to run NNMi using the data that was used with the HA configuration.

    • Windows

      %NnmInstallDir%bin\nnmrestore.ovpl -force -source backup_data

    • Linux

      /opt/OV/bin/nnmrestore.ovpl -force -source backup_data

    For details about this command, see 20. NNMi Backup and Restore Tools.

To Page Top