Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Consolidated Management 2/Network Node Manager i Setup Guide


17.7.2 Unconfiguring NNMi on the passive cluster node

If there are multiple passive cluster nodes, follow the steps below for each passive cluster node on which NNMi is to be unconfigured.

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

    • Windows

    %NnmInstallDir%misc\nnm\ha\nnmhaunconfigure.ovpl \

    NNM resource-group

    • UNIX

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

    • HP-UX HPSG

      Unable to perform the security token exchange with cmclconfd on node xxxxx

      Cannot connect to configuration daemon (cmclconfd) on node xxxxx

  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.

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

    • Windows

      %NnmInstallDir%bin\nnmsetofficialfqdn.ovpl -force FQDN

    • UNIX

      /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

      Edit the nms-local.properties file.

    File path

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

    [Figure] UNIX: /var/opt/OV/conf/nnm/props/nms-local.properties

    What to edit (if you use self-signed certificates)

    com.hp.ov.nms.ssl.KEY_ALIAS = FQDN.selfsigned

    For FQDN, specify (in lowercase) the FQDN specified in nnmsetofficialfqdn.ovpl.

    For details about the certificates, see Chapter 8. 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.

    • WSFC

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

    • HP Serviceguard

      cd /var/opt/OV/hacluster/

      rm -r resource-group

      cd /etc/cmcluster/

      rm -r resource-group

    • VCS or SCS

      cd /var/opt/OV/hacluster/

      rm -r resource-group

      When there are no more passive cluster nodes on which NNMi is to be unconfigured, the procedure is complete.

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