Hitachi

JP1 Version 12 JP1/Network Node Manager i Setup Guide


27.1 Changing NNMi from HP-UX or Solaris to Linux

To complete the following steps, you must have NNMi latest patch of 10-50 running on an HP-UX or Solaris server.

Verify in the window at Help > About Network Node Manager i that the NNMi version is latest patch of 10-50. Do not proceed if the version is not latest patch of 10-50; in such a case, you must first upgrade to NNMi latest patch of 10-50.

The procedure below explains how to change an NNMi management server running NNMi latest patch of 10-50 from an HP-UX or Solaris operating system.

If you are running NNMi on Application Failover environment, see 27.2 Changing NNMi from HP-UX or Solaris to Linux on Application Failover environment.

If you are running NNMi on Global Network Management environment, see 27.3 Changing NNMi from HP-UX or Solaris to Linux on Application Failover environment on the global manager and regional managers.

If you are running NNMi on High-Availability environment, see 27.4 Changing NNMi from HP-UX or Solaris to Linux in a High Availability Cluster.

This procedure uses the following two servers:

Server B cannot employ the same hardware configuration as the current Server A.

To change the NNMi management server:

  1. On Server A, run backup processing.

    Make a full backup of NNMi using the following command:

    nnmbackup.ovpl -type online -scope all -target temporary_location

    You must use the online option. For details, see the nnmbackup.ovpl Reference Page.

  2. On Server B, install RHEL 6.

  3. On Server B, install NNMi.

    Install NNMi on Server B.

    You must install at the same patch level that was in effect on NNMi Server A at the time the backup was made in step 1.

    Important

    You cannot back up with one version of NNMi and restore to a different version of NNMi. Therefore, Server B must be the identical NNMi version, including patch level, as Server A.

    Note

    If you are using an Oracle database, select Secondary Server Installation during the installation process.

  4. Save the port settings.

    During the NNMi installation on Server B, the installation script might assign ports that differ from the port settings in the Server A configuration. This might create port conflicts on Server B when the configuration is restored.

    To remedy this, do the following:

    a. On Server B, navigate to the $NNM_CONF/nnm/props/ directory.

    b. On Server B, copy the nms-local.properties file to nms-local.properties.save in a temporary location.

  5. On Server B, restore the backup.

    Use the following procedure to restore to Server B the backup made in step 1:

    a. On Server A, copy the backup made in step 1 to a temporary location on Server B.

    b. On Server B, complete a full NNMi restore by running the following command:

    nnmrestore.ovpl -force -source temporary_location

    For details about the command options to be used, see 20. NNMi Backup and Restore Tools and the nnmrestore.ovpl Reference Page.

    Important

    Use the command options that match the backup you completed in step 1.

  6. Resolve any port conflicts.

    On Server B, compare the nms-local.properties.save file from the temporary location to the nms-local.properties file located in the $NNM_CONF/nnm/props/ directory.

    Resolve any port conflicts, making changes to the nms-local.properties file located in the directory noted above. Make sure to keep the values for jboss.http.port (NNMi Web server port) and jboss.https.port (NNMi HTTPS Web server port) that were set during NNMi installation on Server B.

  7. Restart the NNMi management server.

    Restart the NNMi management server by running the following commands on Server B:

    ovstop
    ovstart
  8. Apply license keys on Server B.

    If the IP address of Server B is different from the IP address of Server A, obtain and install new NNMi license keys. See 22.4 Changing the IP address of a stand-alone NNMi management server.

    If the IP address of Server B is the same as the IP address of Server A, apply to Server B the license keys that apply to Server A.

  9. On Server B, perform overwrite installation of NNMi 11-00.

    For details about how to perform overwrite installation of NNMi 11-00, see the Release Notes.

    Before you install NNMi 11-00, you must obtain 11-00 license keys. For details, see 2.3 Licensing NNMi.