19.7.2 Unconfiguring NNMi on the passive cluster node

1. On the passive cluster node, unconfigure NNMi from the HA cluster:

   • Windows

   net stop NnmTrapReceiver

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

   • Linux

   - For distributions that uses systemd to manage services

   /opt/OV/bin/nettrap stop

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

   - Other distributions

   /etc/init.d/nettrap stop

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

   This command removes the corresponding node from the list of nodes in the HA resource group. It does not change the settings for running NNMi configured for HA or data on the shared disk of any other node.

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

   • Windows

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

   Important

   In a VCS or SCS environment where NNMi is in an HA configuration and the physical host name has been changed, before the HA configuration is canceled, 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. In VCS or SCS, apply the changes to the HA cluster.

   haconf -dump -makero

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 nmsetofficialfqdn.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. Move the NNMi HA resource group-specific files 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. 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.

   • RHEL6

     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.

   The procedure is complete.

   If you want to remove NNMi completely from the HA cluster, unconfigure NNMi on the passive cluster nodes, and then unconfigure NNMi on the active cluster node.

To Page Top