Select the upgrade path

Check your selections

The following steps are customized according to your selections. Check that your selections are correct.

If any selections are not correct, click Change.

Prerequisites

XServer

You can upgrade NNMi from the console by using an XServer with the $DISPLAY variable set appropriately. Make sure that the XServer application is installed on the server and the $DISPLAY variable is correctly set.

/tmp directory

The /tmp directory must contain at least 1 GB free space.

(Optional) Proxy Server Timeout

If the network you plan to manage uses a proxy server to act as an intermediary for NNMi requests, ensure that its timeout value is at least five minutes.

Public Key

If you are upgrading NNMi on a Linux NNMi management server, you must import the Micro Focus public key into the Linux RPM database before installing NNMi.

To import the public keys:

Download the following file on the system where you plan to install the product:
https://softwaresupport.softwaregrp.com/documents/10180/0/MF_public_keys.tar.gz
Extract the contents of the MF_public_keys.tar.gz file into a local directory.
Go to the directory where the contents of the file are extracted, and then run the following commands:
"rpm --import public_key_Micro_Focus_ Group_Limited RSA-2048-2-RPM.asc"
rpm --import DB5BDEE7.pub
The commands import all the necessary key files.

Install Libraries

Before installingupgrading NNMi, make sure the following libraries are installed:

Linux Version	Package	Library
Red Hat Enterprise Linux 6.x Oracle Linux 6.x	glibc	/lib64/libc-2.12.so
	libaio	/lib64/libaio.so.1
	libXtst	/usr/lib64/libXtst.so.6
	libXi	/usr/lib64/libXi.so.6
	unzip
	liberation-fonts-common
	liberation-sans-fonts
Red Hat Enterprise Linux 7.x Oracle Linux 7.x	glibc	/lib64/libc-2.17.so
	libaio	/lib64/libaio.so.1
	libXtst	/usr/lib64/libXtst.so.6
	libXi	/usr/lib64/libXi.so.6
	unzip
	liberation-fonts-common
	liberation-sans-fonts
SUSE Linux Enterprise Server 11	glibc	/lib64/libc-2.11.3.so
	libaio	/lib64/libaio.so.1
	xorg-x11-libs	/usr/lib64/libXtst.so.6 /usr/lib64/libXi.so.6
	unzip
	liberation-fonts-common
	liberation-sans-fonts
SUSE Linux Enterprise Server 12	glibc	/lib64/libc-2.19.so
	libaio	/lib64/libaio.so.1
	libXtst6	/usr/lib64/libXtst.so.6
	libXi6	/usr/lib64/libXi.so.6
	unzip
	liberation-fonts-common
	liberation-sans-fonts

Disable Anti-Virus Software

To improve upgrade performance, turn off the anti-virus software on the target system by following these steps:

On the Windows desktop, click Start > Settings > Control Panel.
Double-click Administrative Tools.
Double-click Component Services.
Select Services.
Review the status of the anti-virus services.
For each anti-virus service, right-click the service; then click Stop.
After you complete the NNMi upgrade, restart each anti-virus service.

Windows Server 2012 R2

Before you upgrade NNMi 2019.05 on Windows Server 2012 R2, perform the following tasks:

Download the following update packages:
- Update for Windows Server 2012 R2 (KB2919442)
- Windows Server 2012 R2 Update (KB2919355)
Install the packages by following the instructions on the download pages.

NNMi 2019.05 does not support Windows Server 2008 and Windows Server 2008 R2. Before you upgrade to NNMi 2019.05, upgrade your operating system to the supported version.

Requirements for the GNM Environment

In a GNM environment, the global manager must be upgraded to NNMi 2019.05 while the regional managers can run any of the following versions of NNMi:

NNMi 2018.11
NNMi 2018.08
NNMi 10.30
NNMi 10.20
NNMi 10.10

If you want to upgrade regional managers, follow this sequence:

Upgrade the global manager.
Upgrade the regional managers.

It is recommended that you upgrade all the NNMi management servers to 2019.05 if you want to use all the new features across regional and global managers.

Upgrade NNMi

Prepare the NNMi management server for upgrade.

Task 1:

Prepare the NNMi management server

Task 2:

Prepare the Application Failover environment

Task 23:

Upgrade NNMi on the Standby Server

Task 4:

Upgrade NNMi on the Active Server

Task 5:

Adding the servers back to the cluster.

Back up the NNMi management server using the nnmbackup.ovpl script. Do this as a precaution, as you would only use this backup in the unlikely event of a failed upgrade. For more information, see the nnmbackup.ovpl reference page, or the Linux man page. Take backup on both the servers in the Application Failover cluster.

Have your Oracle database administrator back up the NNMi data. Have your Oracle database administrator set the FLASHBACK ANY TABLE permission, as this enables NNMi to create restore points during upgrade.

Use the nnmconfigexport.ovpl script to back up configuration information from the NNMi management server. Do this as a precaution, as you would only use this backup in the unlikely event of a failed upgrade. For more information, see the nnmconfigexport.ovpl reference pagess.

Prepare the Application Failover environment.

Task 1:

Prepare the NNMi management server

Task 2:

Prepare the Application Failover environment

Task 23:

Upgrade NNMi on the Standby Server

Task 4:

Upgrade NNMi on the Active Server

Task 5:

Adding the servers back to the cluster.

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

Follow these steps on the standby server:

Run the nnmcluster -shutdown command on the standby NNMi management server. This shuts down all nnmcluster processes on both the active and standby NNMi management server.
Open the following file:
%NNM_SHARED_CONF%\props\/var/opt/OV/shared/nnm/conf/props/nms-cluster.properties
Comment out the following lines:
Carefully note down these values. You will need to use this value again after upgrade is complete. You can also take a backup of this nms-cluster.properties file.
```
com.hp.ov.nms.cluster.name
```
```
com.hp.ov.nms.cluster.member.hostnames
```
Save the file.
Edit the following file on both NNMi management servers:
%NnmDataDir%\shared\nnm\databases\Postgres\postgresql.conf
/var/opt/OV/shared/nnm/databases/Postgres/postgresql.conf
Remove the following lines, which are automatically added by application failover. This is an example of what these lines could look like. These lines might look slightly different on your server:
```
# The following lines were added by the NNM cluster.
```
```
archive_command = ...
```
```
archive_timeout = 900
```
```
max_wal_senders = 4
```
```
archive_mode = 'on'
```
```
wal_level = 'hot_standby'
```
```
hot_standby = 'on'
```
```
wal_keep_segments = 500
```
```
listen_addresses = 'localhost,10.78.61.68'
```
Make sure to save your changes.
Delete the recovery.conf and recovery.done files from this location.
Create the following trigger file, which tells PostgreSQL to stop running in standby mode and to start fully running:
%NnmDataDir%\tmp\postgresTriggerFile
/var/opt/OV/tmp/postgresTriggerFile
Stop all NNMi processes by running ovstop -c command.

Follow these steps on the active server:

Run the nnmcluster -halt command on the active NNMi management server. This shuts down all nnmcluster processes on both the active and standby NNMi management server.
Open the following file:
%NNM_SHARED_CONF%\props\/var/opt/OV/shared/nnm/conf/props/nms-cluster.properties
Comment out the following lines:
Carefully note down these values. You will need to use this value again after upgrade is complete. You can also take a backup of this nms-cluster.properties file.
```
com.hp.ov.nms.cluster.name
```
```
com.hp.ov.nms.cluster.member.hostnames
```
Save the file.
Stop all NNMi processes by running ovstop -c command.

Upgrade NNMi to the version 2019.05 by running the installer program on the standby server

Task 1:

Prepare the NNMi management server

Task 2:

Prepare the Application Failover environment

Task 23:

Upgrade NNMi on the Standby Server

Task 4:

Upgrade NNMi on the Active Server

Task 5:

Adding the servers back to the cluster.

Log on to the NNMi management server as an administrator.
Log on to the NNMi management server as root.
Extract the contents of the NNMi 2019.05 media (or mount the media).
Enter the following command:
./setup.bin
setup.exe
If you are performing these steps from a remote server by using an XServer, and if the DISPLAY variable is not set correctly, the following message may appear:
```
Choose locale....
```
```
------------------------
```
```
-
```
```
-
```
```
CHOOSE LOCALE BY NUMBER:
```
If you see this message, do not continue with the installation. Stop the installation by pressing Ctrl+C, make sure that the DISPLAY variable is set correctly, and then run the setup file again.
The upgrade process prompts you for the language you want to use, and allows you to pick from the languages you configured your system to support. Then the software checks to make sure you are ready to proceed with the upgrade.
On the Introduction page, review the overview information for the upgrade, then click Next.
On the Setup Type page, select Typical; then click Next.
The Choose Java JDK dialog box opens.
NNMi requires that Java Development Kit (JDK) 1.8 be available on the system. This version of the NNMi installer contains OpenJDK 1.8. You can select the Install NNMi-bundled OpenJDK option to install OpenJDK 1.8 that is embedded with the NNMi media.
Alternatively, if another version of JDK 1.8 is already available on the system, you can select the Use Already-Installed JDK option, and then click Browse to select the path to the JDK.
On Linux, it is recommended that you use the JDK 1.8.x provided by your operating system vendor (Red Hat or SUSE).
For example:
To install Red Hat OpenJDK 1.8.x on Red Hat Enterprise Linux, run the following command:
yum install java-1.8.0-openjdk-devel.x86_64
To install SUSE OpenJDK 1.8.x on SUSE Linux, run the following command:
zypper install java-1_8_0-openjdk
To find out the directory where OpenJDK is installed, run one of the following commands:
whereis java
which java
If you manually installed JDK 1.8, be sure to check that the JDK installation directory is accessible to all users. To grant all users access to the JDK installation directory, run the following command:
chmod -R 755 <JDK_path>
In this instance, <JDK_path> is the complete path to the JDK's bin directory.
On Windows, it is recommended that you install the Oracle JDK 1.8.x.
Tip: Click Validate to check that the specified path is valid.
If you proceed with the default selection, the upgrade process does not retain the JDK configuration that you may have set with NNMi (either while installing the last version or by using the nnmupdateJdk.ovpl script) and reconfigures NNMi to use the OpenJDK 1.8 that was embedded with the NNMi media.
After making a selection, click Continue.
If the Application requirement check warnings dialog box appears, click each warning to understand the nature of the warning and to determine what action you should take.
After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
If the Application requirement check warnings dialog box appears, click each warning to understand the nature of the warning and to determine what action you should take.
After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
NNMi is supported on a 64-bit Linux server, but not on a 32-bit Linux server.
The Install Checks page displays progress as the installation software checks for additional NNMi requirements. After the check completes, click Next.
On the Pre-Upgrade Summary page, review your upgrade choices, and then click Upgrade.
On the Pre-Upgrade Summary page, review your choices, and then click Upgrade.
In the successful migration dialog box, click Finish.
Click Done to complete the upgrade.

If you did not choose to instal the OpenJDK package embedded with the NNMi installer, make sure that the nmsdbmgr and nmsproc users can access the JDK home directory.

Upgrade all iSPIs (that are installed on the NNMi management server) on this (standby) server, and then run the ovstop -c command.

Tip: At this point, if required, you can upgrade the operating system of this server from Windows Server 2008 to Window Server 2012 or 2012 R2.

Upgrade NNMi to the version 2019.05 by running the installer program on the active server

Task 1:

Prepare the NNMi management server

Task 2:

Prepare the Application Failover environment

Task 23:

Upgrade NNMi on the Standby Server

Task 4:

Upgrade NNMi on the Active Server

Task 5:

Adding the servers back to the cluster.

Start the upgrade process. Follow the procedure above. Upgrade all iSPIs (that are installed on the NNMi management server) on this (active) server, and then run the ovstop -c command.

Adding the servers back to the cluster.

Task 1:

Prepare the NNMi management server

Task 2:

Prepare the Application Failover environment

Task 23:

Upgrade NNMi on the Standby Server

Task 4:

Upgrade NNMi on the Active Server

Task 5:

Adding the servers back to the cluster.

Previous steps in this procedure decoupled the servers from the Application Server cluster. Complete the following steps to add the servers back to the original Application Failover cluster:

On each NNMi management server, follow these steps:
1. Edit the following file: %NNM_SHARED_CONF%\props\/var/opt/OV/shared/nnm/conf/props/nms-cluster.properties
2. Add the following properties:
```
com.hp.ov.nms.cluster.name
```
```
com.hp.ov.nms.cluster.member.hostnames
```
  Note: The NNMi upgrade procedure does not preserve commented-out properties. Therefore, you must retype the values of these properties.
  Assign appropriate values to these properties by referring to the backed-up versions of the nms-cluster.properties file.
3. Save your changes.
Finally, run the ovstart or nnmcluster -daemon command on the former active NNMi management server.

Check for the existence of the%NnmDataDir%\shared\nnm\databases\Postgres.9.0/var/opt/OV/shared/nnm/databases/Postgres.9.0 directory on the NNMi management server. If the Postgres.9.0 directory exists on the NNMi management server, you can delete it to free up disk space.

Prepare the NNMi management server for upgrade.
- Back up the NNMi management server using the nnmbackup.ovpl script. Do this as a precaution, as you would only use this backup in the unlikely event of a failed upgrade. For more information, see the nnmbackup.ovpl reference page.
- Make sure to apply the latest NNMi patch.
- Have your Oracle database administrator back up the NNMi data. Have your Oracle database administrator set the FLASHBACK ANY TABLE permission, as this enables NNMi to create restore points during upgrade.
- Use the nnmconfigexport.ovpl script to back up configuration information from the NNMi management server. Do this as a precaution, as you would only use this backup in the unlikely event of a failed upgrade. For more information, see the nnmconfigexport.ovpl reference pagess.
Prepare the HA cluster environment.
NNMi must be taken out of operation for the duration of the upgrade process. NNMi will be unavailable for approximately 30 to 60 minutes during this upgrade procedure. The upgrade procedure involves upgrading NNMi on the active node first, and then upgrading NNMi on the passive node while the HA cluster is still in the maintenance mode.
As a precaution, run the nnmconfigexport.ovpl script on both the active and standby NNMi management servers before proceeding. For information, see Best Practice: Save the Existing Configuration in the NNMi Deployment Reference.
Follow these steps:
1. Ensure that the NNMi configuration is consistent across all HA nodes by forcing a failover, in turn, to each of the passive nodes.
2. Make sure that the latest NNMi patch is applied.
3. Check the ov.conf files on both systems to ensure that they have the correct values. The ov.conf file is available in the following location:
  %NnmDataDir%\shared\nnm\conf
  /var/opt/OV/shared/nnm/conf
4. Determine which node in the NNMi HA cluster is active:
  %NnmInstallDir%\misc\nnm\ha\nnmhaclusterinfo.ovpl -group <resource_group> -activeNode
  /opt/OV/misc/nnm/ha/nnmhaclusterinfo.ovpl -group <resource_group> -activeNode
  The remainder of this procedure refers to the currently active node as server X and the currently passive node as server Y.
5. On server X, disable HA resource group monitoring by creating the following maintenance file:
  %NnmDataDir%\hacluster\<resource_group>\maintenance
  Ensure that the maintenance file does not have a .txt extension, which can occur if the file has been edited with a text editor, such as Notepad.
  /var/opt/OV/hacluster/<resource_group>/maintenance
  The file can be empty.
6. For Red Hat Cluster Suite only. Freeze the resource group on server X by running the following command:
  /usr/sbin/clusvcadm –Z <resource_group>
7. On server Y, unconfigure the Network Performance Server (NPS) from the HA cluster by running the following command:
  %NNMInstallDir%\misc\nnm\ha\nnmhaunconfigure.ovpl NNM -addon PerfSPIHA
  /opt/OV/misc/nnm/ha/nnmhaunconfigure.ovpl NNM -addon PerfSPIHA
  Skip this step if NPS is not installed on the NNMi management server.
8. On server X, to stop NNMi processes, enter the following command:
  ovstop
9. On server X, upgrade NNMi:
  1. Run the NNMi installer by following these steps:
    1. Log on to the NNMi management server as an administrator.
    2. Log on to the NNMi management server as root.
    3. Extract the contents of the NNMi 2019.05 media (or mount the media).
    4. Enter the following command:
      ./setup.bin
      setup.exe
      If you are performing these steps from a remote server by using an XServer, and if the DISPLAY variable is not set correctly, the following message may appear:
      Choose locale....
      ------------------------
      -
      -
      CHOOSE LOCALE BY NUMBER:
      If you see this message, do not continue with the installation. Stop the installation by pressing Ctrl+C, make sure that the DISPLAY variable is set correctly, and then run the setup file again.
      The upgrade process prompts you for the language you want to use, and allows you to pick from the languages you configured your system to support. Then the software checks to make sure you are ready to proceed with the upgrade.
    5. On the Introduction page, review the overview information for the upgrade, then click Next.
    6. On the Setup Type page, select Typical; then click Next.
    7. The Choose Java JDK dialog box opens.
      NNMi requires that Java Development Kit (JDK) 1.8 be available on the system. This version of the NNMi installer contains OpenJDK 1.8. You can select the Install NNMi-bundled OpenJDK option to install OpenJDK 1.8 that is embedded with the NNMi media.
      Alternatively, if another version of JDK 1.8 is already available on the system, you can select the Use Already-Installed JDK option, and then click Browse to select the path to the JDK.
      On Linux, it is recommended that you use the JDK 1.8.x provided by your operating system vendor (Red Hat or SUSE).
      For example:
      To install Red Hat OpenJDK 1.8.x on Red Hat Enterprise Linux, run the following command:
      yum install java-1.8.0-openjdk-devel.x86_64
      To install SUSE OpenJDK 1.8.x on SUSE Linux, run the following command:
      zypper install java-1_8_0-openjdk
      To find out the directory where OpenJDK is installed, run one of the following commands:
      whereis java
      which java
      If you manually installed JDK 1.8, be sure to check that the JDK installation directory is accessible to all users. To grant all users access to the JDK installation directory, run the following command:
      chmod -R 755 <JDK_path>
      In this instance, <JDK_path> is the complete path to the JDK's bin directory.
      On Windows, it is recommended that you install the Oracle JDK 1.8.x.
      Tip: Click Validate to check that the specified path is valid.
      If you proceed with the default selection, the upgrade process does not retain the JDK configuration that you may have set with NNMi (either while installing the last version or by using the nnmupdateJdk.ovpl script) and reconfigures NNMi to use the OpenJDK 1.8 that was embedded with the NNMi media.
      After making a selection, click Continue.
    8. If the Application requirement check warnings dialog box appears, click each warning to understand the nature of the warning and to determine what action you should take.
      After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
    9. If the Application requirement check warnings dialog box appears, click each warning to understand the nature of the warning and to determine what action you should take.
      After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
      NNMi is supported on a 64-bit Linux server, but not on a 32-bit Linux server.
    10. The Install Checks page displays progress as the installation software checks for additional NNMi requirements. After the check completes, click Next.
    11. On the Pre-Upgrade Summary page, review your upgrade choices, and then click Upgrade.
    12. On the Pre-Upgrade Summary page, review your choices, and then click Upgrade.
    13. In the successful migration dialog box, click Finish.
    14. Click Done to complete the upgrade.
    If you did not choose to instal the OpenJDK package embedded with the NNMi installer, make sure that the nmsdbmgr and nmsproc users can access the JDK home directory.
  2. Run the following command:
    ovstart -c
  3. To verify that the upgrade completed correctly, run the following command:
    ovstatus
    All NNMi services should show the state RUNNING (states of iSPI processes will not appear as RUNNING as iSPIs are yet to be upgraded).
    If your environment includes NNM iSPI Performance for Metrics installed on a dedicated server, you must apply Patch 4 of NNM iSPI Performance for Metrics 10.10 apply Patch 4 of NNM iSPI Performance for Metrics 10.20 apply Patch 1 of NNM iSPI Performance for Metrics 10.30 upgrade to NNM iSPI Performance Metrics 2018.11 and, then apply the NNM iSPI Performance for Metrics 2018.11 hotfix apply NNM iSPI Performance for Metrics 2018.11 hotfix after you upgrade to NNMi 2019.05.
  4. Upgrade all add-on iSPIs to the version 2019.05.
    It is possible that NNM iSPI Performance for Traffic are installed on the same NNMi HA cluster. In that case, NNM iSPI Performance for Traffic is also considered to be add-on iSPIs and you must upgrade them to 2019.05 at this point.
    If your environment includes the NNM iSPI Performance for Traffic (Master and Leaf Collectors) installed on dedicated servers, you must also upgrade that product to version 2019.05 for correct functionality. You can complete those upgrades after completing this procedure.
    If you have upgraded iSPIs on this server, perform the following post-upgrade steps:
    - Steps for the NNM iSPI Performance for QA
      Make sure that the following files from the %NnmdataDir%\nmsas\qa\conf/var/opt/OV/nmsas/qa/conf contain the virtual FQDN for the corresponding parameters:
      File Name Variable Name
      nms-qa.jvm.properties -Dcom.hp.ov.nms.ssl.keystore.alias
      nnm.extended.properties com.hp.ov.nms.spi.qa.Nnm.hostname
      nnm.extended.properties com.hp.ov.nms.spi.qa.spi.hostname
      Make sure that the server.properties file from the %nnmdatadir%\nmsas\qa/var/opt/OV/nmsas/qa directory contains the virtual FQDN of the NNMi management server (for the java.rmi.server.hostname and nmsas.server.net.hostname.private parameters).
      Make sure that the login-config.xml file from the %nnminstalldir%\qa\server\conf/var/opt/OV/qa/server/conf directory contains the virtual FQDN of the NNMi management server (for the moduleoption element).
    - Steps for the NNM iSPI for MPLS
      Make sure that the following files from the %NnmdataDir%\nmsas\mpls\conf/var/opt/OV/nmsas/mpls/conf contain the virtual FQDN for the corresponding parameters:
      File Name Variable Name
      nms-mpls.jvm.properties -Dcom.hp.ov.nms.ssl.keystore.alias
      nnm.extended.properties com.hp.ov.nms.spi.mpls.Nnm.hostname
      nnm.extended.properties com.hp.ov.nms.spi.mpls.spi.hostname
      Make sure that the server.properties file from the %nnmdatadir%\nmsas\mpls/var/opt/OV/nmsas/mpls directory contains the virtual FQDN of the NNMi management server (for the java.rmi.server.hostname and nmsas.server.net.hostname.private parameters).
      Make sure that the login-config.xml file from the %nnminstalldir%\mpls\server\conf/var/opt/OV/mpls/server/conf directory contains the virtual FQDN of the NNMi management server (for the moduleoption element).
    - Steps for the NNM iSPI for IP Telephony
      Make sure that the following files from the %NnmdataDir%\shared\ipt\conf/var/opt/OV/shared/ipt/conf contain the virtual FQDN for the corresponding parameters:
      File Name Variable Name
      nnm.extended.properties com.hp.ov.nms.spi.ipt.Nnm.hostname
      nnm.extended.properties com.hp.ov.nms.spi.ipt.spi.hostname
      Make sure that the server.properties file from the %nnmdatadir%\nmsas\ipt/var/opt/OV/nmsas/ipt directory contains the virtual FQDN of the NNMi management server (for the java.rmi.server.hostname and nmsas.server.net.hostname.private parameters).
      Make sure that the login-config.xml file from the %nnminstalldir%\ipt\server\conf/var/opt/OV/ipt/server/conf directory contains the virtual FQDN of the NNMi management server (for the moduleoption element).
    - Steps for the NNM iSPI for IP Multicast
      Make sure that the following files from the %NnmdataDir%\nmsas\mcast\conf/var/opt/OV/nmsas/mcast/conf contain the virtual FQDN for the corresponding parameters:
      File Name Variable Name
      nms-mcast.jvm.properties -Dcom.hp.ov.nms.ssl.keystore.alias
      nnm.extended.properties com.hp.ov.nms.spi.mcast.Nnm.hostname
      nnm.extended.properties com.hp.ov.nms.spi.mcast.spi.hostname
      Make sure that the login-config.xml file from the %nnminstalldir%\mcast\server\conf/var/opt/OV/mcast/server/conf directory contains the virtual FQDN of the NNMi management server (for the moduleoption element).
10. On server X, run the following command: nnmhadisk.ovpl NNM -replicate <HA_mount_point>.
11. On server Y, disable HA resource group monitoring by creating the following maintenance file:
  %NnmDataDir%\hacluster\<resource_group>\maintenance
  Ensure that the maintenance file does not have a .txt extension, which can occur if the file has been edited with a text editor, such as Notepad.
  /var/opt/OV/hacluster/<resource_group>/maintenance
  The file can be empty.
12. On server Y, upgrade NNMi:
  1. Run the NNMi installer and follow these steps:
    1. Log on to the NNMi management server as an administrator.
    2. Log on to the NNMi management server as root.
    3. Extract the contents of the NNMi 2019.05 media (or mount the media).
    4. Enter the following command:
      ./setup.bin
      setup.exe
      If you are performing these steps from a remote server by using an XServer, and if the DISPLAY variable is not set correctly, the following message may appear:
      Choose locale....
      ------------------------
      -
      -
      CHOOSE LOCALE BY NUMBER:
      If you see this message, do not continue with the installation. Stop the installation by pressing Ctrl+C, make sure that the DISPLAY variable is set correctly, and then run the setup file again.
      The upgrade process prompts you for the language you want to use, and allows you to pick from the languages you configured your system to support. Then the software checks to make sure you are ready to proceed with the upgrade.
    5. On the Introduction page, review the overview information for the upgrade, then click Next.
    6. On the Setup Type page, select Typical; then click Next.
    7. The Choose Java JDK dialog box opens.
      NNMi requires that Java Development Kit (JDK) 1.8 be available on the system. This version of the NNMi installer contains OpenJDK 1.8. You can select the Install NNMi-bundled OpenJDK option to install OpenJDK 1.8 that is embedded with the NNMi media.
      Alternatively, if another version of JDK 1.8 is already available on the system, you can select the Use Already-Installed JDK option, and then click Browse to select the path to the JDK.
      On Linux, it is recommended that you use the JDK 1.8.x provided by your operating system vendor (Red Hat or SUSE).
      For example:
      To install Red Hat OpenJDK 1.8.x on Red Hat Enterprise Linux, run the following command:
      yum install java-1.8.0-openjdk-devel.x86_64
      To install SUSE OpenJDK 1.8.x on SUSE Linux, run the following command:
      zypper install java-1_8_0-openjdk
      To find out the directory where OpenJDK is installed, run one of the following commands:
      whereis java
      which java
      If you manually installed JDK 1.8, be sure to check that the JDK installation directory is accessible to all users. To grant all users access to the JDK installation directory, run the following command:
      chmod -R 755 <JDK_path>
      In this instance, <JDK_path> is the complete path to the JDK's bin directory.
      On Windows, it is recommended that you install the Oracle JDK 1.8.x.
      Tip: Click Validate to check that the specified path is valid.
      If you proceed with the default selection, the upgrade process does not retain the JDK configuration that you may have set with NNMi (either while installing the last version or by using the nnmupdateJdk.ovpl script) and reconfigures NNMi to use the OpenJDK 1.8 that was embedded with the NNMi media.
      After making a selection, click Continue.
    8. If the Application requirement check warnings dialog box appears, click each warning to understand the nature of the warning and to determine what action you should take.
      After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
    9. If the Application requirement check warnings dialog box appears, click each warning to understand the nature of the warning and to determine what action you should take.
      After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
      NNMi is supported on a 64-bit Linux server, but not on a 32-bit Linux server.
    10. The Install Checks page displays progress as the installation software checks for additional NNMi requirements. After the check completes, click Next.
    11. On the Pre-Upgrade Summary page, review your upgrade choices, and then click Upgrade.
    12. On the Pre-Upgrade Summary page, review your choices, and then click Upgrade.
    13. In the successful migration dialog box, click Finish.
    14. Click Done to complete the upgrade.
    If you did not choose to instal the OpenJDK package embedded with the NNMi installer, make sure that the nmsdbmgr and nmsproc users can access the JDK home directory.
  2. To verify that the upgrade completed correctly, enter the following command:
    ovstatus
    All NNMi services should show the state NOT-RUNNING.
  3. Upgrade all add-on iSPIs to version 2019.05.
    If you have upgraded iSPIs on this server, perform the following post-upgrade steps:
    - Steps for the NNM iSPI Performance for QA
      Make sure that the following files from the %NnmdataDir%\nmsas\qa\conf/var/opt/OV/nmsas/qa/conf contain the virtual FQDN for the corresponding parameters:
      File Name Variable Name
      nms-qa.jvm.properties -Dcom.hp.ov.nms.ssl.keystore.alias
      nnm.extended.properties com.hp.ov.nms.spi.qa.Nnm.hostname
      nnm.extended.properties com.hp.ov.nms.spi.qa.spi.hostname
      Make sure that the server.properties file from the %nnmdatadir%\nmsas\qa/var/opt/OV/nmsas/qa directory contains the virtual FQDN of the NNMi management server (for the java.rmi.server.hostname and nmsas.server.net.hostname.private parameters).
      Make sure that the login-config.xml file from the %nnminstalldir%\qa\server\conf/var/opt/OV/qa/server/conf directory contains the virtual FQDN of the NNMi management server (for the moduleoption element).
    - Steps for the NNM iSPI for MPLS
      Make sure that the following files from the %NnmdataDir%\nmsas\mpls\conf/var/opt/OV/nmsas/mpls/conf contain the virtual FQDN for the corresponding parameters:
      File Name Variable Name
      nms-mpls.jvm.properties -Dcom.hp.ov.nms.ssl.keystore.alias
      nnm.extended.properties com.hp.ov.nms.spi.mpls.Nnm.hostname
      nnm.extended.properties com.hp.ov.nms.spi.mpls.spi.hostname
      Make sure that the server.properties file from the %nnmdatadir%\nmsas\mpls/var/opt/OV/nmsas/mpls directory contains the virtual FQDN of the NNMi management server (for the java.rmi.server.hostname and nmsas.server.net.hostname.private parameters).
      Make sure that the login-config.xml file from the %nnminstalldir%\mpls\server\conf/var/opt/OV/mpls/server/conf directory contains the virtual FQDN of the NNMi management server (for the moduleoption element).
    - Steps for the NNM iSPI for IP Telephony
      Make sure that the following files from the %NnmdataDir%\shared\ipt\conf/var/opt/OV/shared/ipt/conf contain the virtual FQDN for the corresponding parameters:
      File Name Variable Name
      nnm.extended.properties com.hp.ov.nms.spi.ipt.Nnm.hostname
      nnm.extended.properties com.hp.ov.nms.spi.ipt.spi.hostname
      Make sure that the server.properties file from the %nnmdatadir%\nmsas\ipt/var/opt/OV/nmsas/ipt directory contains the virtual FQDN of the NNMi management server (for the java.rmi.server.hostname and nmsas.server.net.hostname.private parameters).
      Make sure that the login-config.xml file from the %nnminstalldir%\ipt\server\conf/var/opt/OV/ipt/server/conf directory contains the virtual FQDN of the NNMi management server (for the moduleoption element).
    - Steps for the NNM iSPI for IP Multicast
      Make sure that the following files from the %NnmdataDir%\nmsas\mcast\conf/var/opt/OV/nmsas/mcast/conf contain the virtual FQDN for the corresponding parameters:
      File Name Variable Name
      nms-mcast.jvm.properties -Dcom.hp.ov.nms.ssl.keystore.alias
      nnm.extended.properties com.hp.ov.nms.spi.mcast.Nnm.hostname
      nnm.extended.properties com.hp.ov.nms.spi.mcast.spi.hostname
      Make sure that the login-config.xml file from the %nnminstalldir%\mcast\server\conf/var/opt/OV/mcast/server/conf directory contains the virtual FQDN of the NNMi management server (for the moduleoption element).
13. On server X, delete the maintenance file:
  %NnmDataDir%\hacluster\<resource_group>\maintenance
  /var/opt/OV/hacluster/<resource_group>/maintenance
  Additional Task in Red Hat Cluster Suite
  Unfreeze the resource group on server X by running the following command:
  /usr/sbin/clusvcadm –U<resource_group>
14. On server Y, delete the maintenance file:
  %NnmDataDir%\hacluster\<resource_group>\maintenance
  /var/opt/OV/hacluster/<resource_group>/maintenance
  Additional Tasks in Red Hat Cluster Suite
  Follow these steps on server X:
  1. Take a backup of the /usr/share/cluster/cluster.rng file.
  2. Edit the /usr/share/cluster/cluster.rng file as follows:
    Find the element <define name=”NNMSCRIPT”>.
    Remove everything from the line above to the first instance of </define> encountered (that is, <define name=”NNMSCRIPT”>, the next instance of </define>, and everything in between).
    In the same place in this file, embed the content of the /opt/OV/misc/nnm/ha/NNMscript.rng file.
  3. Save the /usr/share/cluster/cluster.rng file.
  4. Copy the /opt/OV/misc/nnm/ha/NNMscript.sh file to /usr/share/cluster and ensure that it has 555 permissions with root:root ownership.
  5. Restart the system.
  Follow these steps on server Y:
  1. Take a backup of the /usr/share/cluster/cluster.rng file.
  2. Edit the /usr/share/cluster/cluster.rng file as follows:
    Find the element <define name=”NNMSCRIPT”>.
    Remove everything from the line above to the first instance of </define> encountered (that is, <define name=”NNMSCRIPT”>, the next instance of </define>, and everything in between).
    In the same place in this file, embed the content of the /opt/OV/misc/nnm/ha/NNMscript.rng file.
  3. Save the /usr/share/cluster/cluster.rng file.
  4. Copy the /opt/OV/misc/nnm/ha/NNMscript.sh file to /usr/share/cluster and ensure that it has 555 permissions with root:root ownership.
  5. Restart the system.
15. Perform the following post-installation steps:
  1. Verify that the following variables are set:
    NNM_INTERFACE
    HA_MOUNT_POINT
    NNM_ADD_ON_PRODUCTS
    HA_LOCALE (not required if running in C)
    These variables are defined in the following locations:
    Veritas:
    /opt/VRTSvcs/bin/hagrp -display | grep UserStrGlobal
    Windows: Using regedit, the values are in the following location:
    HKEY_LOCAL_MACHINE\Cluster\Groups\<group>\Parameters
  2. If the variables are not set, you can run the following commands for each missing value:
    /opt/OV/misc/nnm/ha/%nnminstalldir%\misc\nm\ha\nnmhaclusterinfo.ovpl -config NNM -set NNM_INTERFACE <value for NNM_INTERFACE>
    /opt/OV/misc/nnm/ha/%nnminstalldir%\misc\nm\ha\nnmhaclusterinfo.ovpl -config NNM -set HA_MOUNT_POINT <value for HA_MOUNT_POINT>
    /opt/OV/misc/nnm/ha/%nnminstalldir%\misc\nm\ha\nnmhaclusterinfo.ovpl -config NNM -set NNM_ADD_ON_PRODUCTS <value for NNM_ADD_ON_PRODUCTS>
    /opt/OV/misc/nnm/ha/%nnminstalldir%\misc\nm\ha\nnmhaclusterinfo.ovpl -config NNM -set HA_LOCALE <value for HA_LOCALE>
    HA_LOCALE is only needed if you are attempting to use a localized language.
16. For all Linux HA upgrades, run the following sets of commands, as applicable for your system:
  - Red Hat Enterprise Linux:
    rm /etc/rc.d/rc*.d/S98netmgt
    rm /etc/rc.d/rc*.d/K01netmgt
  - SUSE:
    rm /etc/init.d/rc*.d/S98netmgt
    rm /etc/init.d/rc*.d/K01netmgt

File Name	Variable Name
nms-qa.jvm.properties	-Dcom.hp.ov.nms.ssl.keystore.alias
nnm.extended.properties	com.hp.ov.nms.spi.qa.Nnm.hostname
nnm.extended.properties	com.hp.ov.nms.spi.qa.spi.hostname

File Name	Variable Name
nms-mpls.jvm.properties	-Dcom.hp.ov.nms.ssl.keystore.alias
nnm.extended.properties	com.hp.ov.nms.spi.mpls.Nnm.hostname
nnm.extended.properties	com.hp.ov.nms.spi.mpls.spi.hostname

File Name	Variable Name
nnm.extended.properties	com.hp.ov.nms.spi.ipt.Nnm.hostname
nnm.extended.properties	com.hp.ov.nms.spi.ipt.spi.hostname

File Name	Variable Name
nms-mcast.jvm.properties	-Dcom.hp.ov.nms.ssl.keystore.alias
nnm.extended.properties	com.hp.ov.nms.spi.mcast.Nnm.hostname
nnm.extended.properties	com.hp.ov.nms.spi.mcast.spi.hostname

File Name	Variable Name
nms-qa.jvm.properties	-Dcom.hp.ov.nms.ssl.keystore.alias
nnm.extended.properties	com.hp.ov.nms.spi.qa.Nnm.hostname
nnm.extended.properties	com.hp.ov.nms.spi.qa.spi.hostname

File Name	Variable Name
nms-mpls.jvm.properties	-Dcom.hp.ov.nms.ssl.keystore.alias
nnm.extended.properties	com.hp.ov.nms.spi.mpls.Nnm.hostname
nnm.extended.properties	com.hp.ov.nms.spi.mpls.spi.hostname

File Name	Variable Name
nnm.extended.properties	com.hp.ov.nms.spi.ipt.Nnm.hostname
nnm.extended.properties	com.hp.ov.nms.spi.ipt.spi.hostname

File Name	Variable Name
nms-mcast.jvm.properties	-Dcom.hp.ov.nms.ssl.keystore.alias
nnm.extended.properties	com.hp.ov.nms.spi.mcast.Nnm.hostname
nnm.extended.properties	com.hp.ov.nms.spi.mcast.spi.hostname

Prepare the NNMi management server for upgrade.
- Back up the NNMi management server using the nnmbackup.ovpl script. Do this as a precaution, as you would only use this backup in the unlikely event of a failed upgrade. For more information, see the nnmbackup.ovpl reference page.
- Make sure to apply the latest NNMi patch.
- Have your Oracle database administrator back up the NNMi data. Have your Oracle database administrator set the FLASHBACK ANY TABLE permission, as this enables NNMi to create restore points during upgrade.
- Use the nnmconfigexport.ovpl script to back up configuration information from the NNMi management server. Do this as a precaution, as you would only use this backup in the unlikely event of a failed upgrade. For more information, see the nnmconfigexport.ovpl reference pagess.
Run the setup file from the NNMi media.
Follow these steps:
1. Log on to the NNMi management server as an administrator.
2. Log on to the NNMi management server as root.
3. Extract the contents of the NNMi 2019.05 media (or mount the media).
4. Enter the following command:
  ./setup.bin
  setup.exe
  If you are performing these steps from a remote server by using an XServer, and if the DISPLAY variable is not set correctly, the following message may appear:
  Choose locale....
  ------------------------
  -
  -
  CHOOSE LOCALE BY NUMBER:
  If you see this message, do not continue with the installation. Stop the installation by pressing Ctrl+C, make sure that the DISPLAY variable is set correctly, and then run the setup file again.
  The upgrade process prompts you for the language you want to use, and allows you to pick from the languages you configured your system to support. Then the software checks to make sure you are ready to proceed with the upgrade.
5. On the Introduction page, review the overview information for the upgrade, then click Next.
6. On the Setup Type page, select Typical; then click Next.
7. The Choose Java JDK dialog box opens.
  NNMi requires that Java Development Kit (JDK) 1.8 be available on the system. This version of the NNMi installer contains OpenJDK 1.8. You can select the Install NNMi-bundled OpenJDK option to install OpenJDK 1.8 that is embedded with the NNMi media.
  Alternatively, if another version of JDK 1.8 is already available on the system, you can select the Use Already-Installed JDK option, and then click Browse to select the path to the JDK.
  On Linux, it is recommended that you use the JDK 1.8.x provided by your operating system vendor (Red Hat or SUSE).
  For example:
  To install Red Hat OpenJDK 1.8.x on Red Hat Enterprise Linux, run the following command:
  yum install java-1.8.0-openjdk-devel.x86_64
  To install SUSE OpenJDK 1.8.x on SUSE Linux, run the following command:
  zypper install java-1_8_0-openjdk
  To find out the directory where OpenJDK is installed, run one of the following commands:
  whereis java
  which java
  If you manually installed JDK 1.8, be sure to check that the JDK installation directory is accessible to all users. To grant all users access to the JDK installation directory, run the following command:
  chmod -R 755 <JDK_path>
  In this instance, <JDK_path> is the complete path to the JDK's bin directory.
  On Windows, it is recommended that you install the Oracle JDK 1.8.x.
  Tip: Click Validate to check that the specified path is valid.
  If you proceed with the default selection, the upgrade process does not retain the JDK configuration that you may have set with NNMi (either while installing the last version or by using the nnmupdateJdk.ovpl script) and reconfigures NNMi to use the OpenJDK 1.8 that was embedded with the NNMi media.
  After making a selection, click Continue.
8. If the Application requirement check warnings dialog box appears, click each warning to understand the nature of the warning and to determine what action you should take.
  After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
9. If the Application requirement check warnings dialog box appears, click each warning to understand the nature of the warning and to determine what action you should take.
  After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
  NNMi is supported on a 64-bit Linux server, but not on a 32-bit Linux server.
10. The Install Checks page displays progress as the installation software checks for additional NNMi requirements. After the check completes, click Next.
11. On the Pre-Upgrade Summary page, review your upgrade choices, and then click Upgrade.
12. On the Pre-Upgrade Summary page, review your choices, and then click Upgrade.
13. In the successful migration dialog box, click Finish.
14. Click Done to complete the upgrade.
If you did not choose to instal the OpenJDK package embedded with the NNMi installer, make sure that the nmsdbmgr and nmsproc users can access the JDK home directory.
Upgrade iSPIs
Skip this step if you do not use NNMi Ultimate/Premium.
Use the following sequence to upgrade iSPIs.
1. If you use the NNM iSPI Performance for Metrics, you need not upgrade NPS. You can continue to use the existing version, but you must install the NPS decoupling bundle.
  Install the NPS decoupling bundle NPS10.10DecouplingBundle.tar.gzNPS10.20DecouplingBundle.tar.gzNPS10.30DecouplingBundle.tar.gzNPS2018.08DecouplingBundle.tar.gzNPS2018.11DecouplingBundle.tar.gz, which is available on the page from where you downloaded the NNMi media.
  The highest available version of NPS is 2018.11.
2. Upgrade all other iSPIs.

To upgrade NNMi to a different server (side-by-side migration), follow these steps:

Back up NNMi.
As a precaution, back up the existing (source) management server using the nnmbackup.ovpl script. Label this backup for NNMi. For more information, see the nnmbackup.ovpl reference page.
Upgrade to NNMi 2019.05 on the original (source) server.
1. Log on to the NNMi management server as an administrator.
2. Log on to the NNMi management server as root.
3. Extract the contents of the NNMi 2019.05 media (or mount the media).
4. Enter the following command:
  ./setup.bin
  setup.exe
  If you are performing these steps from a remote server by using an XServer, and if the DISPLAY variable is not set correctly, the following message may appear:
  Choose locale....
  ------------------------
  -
  -
  CHOOSE LOCALE BY NUMBER:
  If you see this message, do not continue with the installation. Stop the installation by pressing Ctrl+C, make sure that the DISPLAY variable is set correctly, and then run the setup file again.
  The upgrade process prompts you for the language you want to use, and allows you to pick from the languages you configured your system to support. Then the software checks to make sure you are ready to proceed with the upgrade.
5. On the Introduction page, review the overview information for the upgrade, then click Next.
6. On the Setup Type page, select Typical; then click Next.
7. The Choose Java JDK dialog box opens.
  NNMi requires that Java Development Kit (JDK) 1.8 be available on the system. This version of the NNMi installer contains OpenJDK 1.8. You can select the Install NNMi-bundled OpenJDK option to install OpenJDK 1.8 that is embedded with the NNMi media.
  Alternatively, if another version of JDK 1.8 is already available on the system, you can select the Use Already-Installed JDK option, and then click Browse to select the path to the JDK.
  On Linux, it is recommended that you use the JDK 1.8.x provided by your operating system vendor (Red Hat or SUSE).
  For example:
  To install Red Hat OpenJDK 1.8.x on Red Hat Enterprise Linux, run the following command:
  yum install java-1.8.0-openjdk-devel.x86_64
  To install SUSE OpenJDK 1.8.x on SUSE Linux, run the following command:
  zypper install java-1_8_0-openjdk
  To find out the directory where OpenJDK is installed, run one of the following commands:
  whereis java
  which java
  If you manually installed JDK 1.8, be sure to check that the JDK installation directory is accessible to all users. To grant all users access to the JDK installation directory, run the following command:
  chmod -R 755 <JDK_path>
  In this instance, <JDK_path> is the complete path to the JDK's bin directory.
  On Windows, it is recommended that you install the Oracle JDK 1.8.x.
  Tip: Click Validate to check that the specified path is valid.
  If you proceed with the default selection, the upgrade process does not retain the JDK configuration that you may have set with NNMi (either while installing the last version or by using the nnmupdateJdk.ovpl script) and reconfigures NNMi to use the OpenJDK 1.8 that was embedded with the NNMi media.
  After making a selection, click Continue.
8. If the Application requirement check warnings dialog box appears, click each warning to understand the nature of the warning and to determine what action you should take.
  After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
9. If the Application requirement check warnings dialog box appears, click each warning to understand the nature of the warning and to determine what action you should take.
  After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
  NNMi is supported on a 64-bit Linux server, but not on a 32-bit Linux server.
10. The Install Checks page displays progress as the installation software checks for additional NNMi requirements. After the check completes, click Next.
11. On the Pre-Upgrade Summary page, review your upgrade choices, and then click Upgrade.
12. On the Pre-Upgrade Summary page, review your choices, and then click Upgrade.
13. In the successful migration dialog box, click Finish.
14. Click Done to complete the upgrade.
If you did not choose to instal the OpenJDK package embedded with the NNMi installer, make sure that the nmsdbmgr and nmsproc users can access the JDK home directory.
Install NNMi 2019.05 on a new (target) server.
Install NNMi 2019.05 on a new server by following these steps. If the source server is on Red Hat Linux, you can choose a target server with the same version of Oracle Linux. Similarly, if the source server is on Oracle Linux, you can choose a target server with the same version of the Red Hat Linux.
1. Log on as a user with administrator privileges to the system where you plan to install NNMi.
  The user must belong to the local Administrators group.
2. Log on as a user with root privileges to the system where you plan to install NNMi.
3. Extract the contents of the NNMi media (or mount the media).
4. Double-click the setup.exe file from the media root. The installation process prompts you for the language you want to use, and allows you to pick from the languages you configured your system to support. Then the software checks to make sure you are ready to proceed with the installation.
5. Run the following command:
  ./setup.bin
  The installation process prompts you for the language you want to use, and allows you to pick from the languages you configured your system to support. Then the software checks to make sure you are ready to proceed with the installation.
  Note: If a dialog box appears during the NNMi installation stating that the code signing key could not be found, do the following:
  1. Leave the dialog box displayed.
  2. Download the following file on the system where you plan to install the product:
    https://softwaresupport.softwaregrp.com/documents/10180/0/MF_public_keys.tar.gz
  3. Extract the contents of the MF_public_keys.tar.gz file into a local directory.
  4. Go to the directory where the contents of the file are extracted, and then run the following command:
    rpm --import *.asc
    rpm --import *.pub
    The command imports all the key files that were present in the MF_public_keys.tar.gz file.
  5. Go back to the dialog box, and then click No to resume the NNMi installation.
  If you are performing these steps from a remote server by using an XServer, and if the DISPLAY variable is not set correctly, the following message may appear:
  Choose locale....
  ------------------------
  -
  -
  CHOOSE LOCALE BY NUMBER:
  If you see this message, do not continue with the installation. Stop the installation by pressing Ctrl+C, make sure that the DISPLAY variable is set correctly, and then run the setup file again.
6. If the Installer Configuration dialog box appears, choose whether to use saved values from a previous installation or to change installation options. If you want to use the saved values, click Yes. If you want to select the installation options yourself, click No.
7. On the Introduction page, review the overview information for the installation, and then click Next.
8. On the License Agreement page, review the NNMi license terms. If you agree with the terms of the license agreement, select I accept…; then click Next.
9. On the Setup Type page, select Typical; then click Next.
10. On the Choose the folders page, accept the default location for the application and data folders, or browse to a different location; then click Next.
  This dialog box does not appear if you have previously installed other Micro Focus Software applications on this server.
  Do not use any of the following locations for the data folder: C:\Window, C:\Program Files, or C:\Program Files(x86). Micro Focus recommends using the default data directory, C:\ProgramData. You can choose other locations, such as drive:\data or drive:\yourdirectorychoice\data.
  Because NNMi is a 64-bit application that also installs 32-bit binaries, you must install NNMi in any folder other than drive:\Program Files (the 64-bit folder). The recommended folder is: drive:\Program files(x86).
  Installing NNMi using Server Message Block (SMB)/Common Internet File System (CIFS) networking protocol (Samba) is not certified. Do not attempt to install NNMi onto a mapped network drive.
11. If the Application requirement check warnings dialog box opens, click each warning to understand the nature of the warning and to determine what action you should take.
  After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
12. If the Application requirement check warnings dialog box opens, click each warning to understand the nature of the warning and to determine what action you should take.
  After you respond to the warnings in the Application requirement check warnings dialog box, click Continue.
  NNMi is supported on a 64-bit Linux server, but not on a 32-bit Linux server.
13. You will now see the Server Configuration > Choose the database type page. On this page, select Micro Focus Software Embedded Database, click Next.
14. You will now see the Server Configuration > Choose the database type page. On this page, select Oracle.
15. On the Choose Database Initialization Preferences page, do one of the following:
  
  If you want to initialize an Oracle database using previously defined database accounts, select Primary Server Installation; then click Next.
  
  If you want to connect to an existing NNMi database that is already initialized by another primary installation and use this installation in a High Availability or application failover configuration, select Secondary Server Installation; then click Next.
16. On the Enter your database server information page:
  - Type the Host Name of the Oracle database system.
    If you are using Oracle RAC, type the physical host name of one of the Oracle servers.
  - Type the name of the NNMi database Instance.
  - Type the Database Service Name, and then click Next.
  Oracle provides the high-availability solution Oracle Real Application Cluster (RAC). The RAC solution uses two physical Oracle database servers. If the first server malfunctions or the administrator invokes a failover (for example, to complete maintenance on the first server), the second server automatically takes over, and NNMi begins using the second server. There is a short time window of data loss that might occur after the failover occurs. The amount of data loss increases with the size of the managed network and the rate of traps and incidents being evaluated. To configure RAC, work with your Oracle database administrator to install an Oracle database according to the instructions provided by Oracle.
17. On the Enter the database user account information page, enter the Username and Password for the Oracle database user.
18. The Product Requirements: Install Checks page displays progress as the installer checks for additional NNMi installation requirements. After the check completes, click Next.
19. On the installer page, click Install.
  The Choose Java JDK dialog box opens.
  NNMi requires that Java Development Kit (JDK) 1.8.x be available on the system. This version of the NNMi installer contains OpenJDK 1.8. You can select the Install NNMi-bundled OpenJDK option to install OpenJDK 1.8 that is embedded with the NNMi media.
  Alternatively, if another version of JDK 1.8.x is already available on the system, you can select the Use Already-Installed JDK option, and then click Browse to select the path to the JDK.
  On Linux, it is recommended that you use the JDK 1.8.x provided by your operating system vendor (Red Hat or SUSE).
  For example:
  To install Red Hat OpenJDK 1.8.x on Red Hat Enterprise Linux, run the following command:
  yum install java-1.8.0-openjdk-devel.x86_64
  To install SUSE OpenJDK 1.8.x on SUSE Linux, run the following command:
  zypper install java-1_8_0-openjdk
  To find out the directory where OpenJDK is installed, run one of the following commands:
  whereis java
  which java
  If you manually installed JDK 1.8, be sure to check that the JDK installation directory is accessible to all users. To grant all users access to the JDK installation directory, run the following command:
  chmod -R 755 <JDK_path>
  In this instance, <JDK_path> is the complete path to the JDK's bin directory.
  On Windows, it is recommended that you install the Oracle JDK 1.8.x.
  Tip: Click Validate to check that the specified path is valid.
  After making a selection, click Continue.
20. On the Pre-Install Summary page, review your installation choices; then do one of the following actions:
  - To change any of the settings, click Previous.
  - To start the installation process, click Install.
  The installation process installs NNMi and performs some initial configuration; this process normally takes between ten and thirty minutes to complete.
  As part of the installation process, NNMi performs additional checks to ensure that all installation requirements are met. If you do not meet one or more installation requirements, NNMi displays the appropriate error, warning, or informational dialog boxes to assist you in rectifying the problem. Take each of the required actions so that the NNMi installation can continue.
21. On the Pre-Install Summary page, review your installation choices; then do one of the following actions:
  
  To change any of the settings, click Previous.
  To start the installation process, click Install.
  The installation process installs NNMi and performs some initial configuration; this process normally takes between ten and thirty minutes to complete.
  As part of the installation process, NNMi performs additional checks to ensure that all installation requirements are met. If you do not meet one or more installation requirements, NNMi displays the appropriate error, warning, or informational dialog boxes to assist you in rectifying the problem. Take each of the required actions so that the NNMi installation can continue.
22. The System Account Password dialog box opens. Follow the instructions on the screen to create a password for the system account; then click OK.
  
  The system account is a special administrator account that NNMi creates during installation. After installation, the system account is still valid; however, it should only be used for command-line security and for recovery purposes.
23. In the NNM Web Server Port dialog box, notice the port number; you will use this port to access NNMi. Click OK to accept the default port, or change the port number, then click OK.
24. In the NNMi Https Web Server Port dialog box, you can accept or change the port number that NNMi uses for the NNMi web server. Click OKto accept the default port or to accept the port change you made.
25. The installation process searches for an official fully-qualified domain name (FQDN) for the NNMi management server. If the dialog box contains an incomplete or unresolvable FQDN, modify the name; then click OK.
  This entry is used as the official FQDN to provide users with access to the NNMi management server. It is also used to enable Single Sign-On (SSO) for NNM iSPIs. For SSO to work, URL access to NNMi and NNM iSPIs must share a common domain. If you do not have a FQDN for the NNMi management server, you can substitute the NNMi management server’s IP address; however, this will make the single sign-on for NNM iSPIs unusable.
26. The installation process prompts you for the location of any NNMi patches you want to install before starting NNMi. Select Install Patches or Skip Patching to continue.
  
  Before installing patches, unzip any zipped patch files and place the unzipped files in a folder on the target server before completing this step.
  
  For support information, including information on how to obtain patches, visit the Micro Focus Software Support Online web site at: https://softwaresupport.softwaregrp.com/.
27. The installation process completes the installation and configuration processes and starts the NNMi services. This process takes several minutes.
28. Click Finish. The installation process begins.
29. Click Done to complete the installation.
Copy the backed-up data to the target server.
Run the nnmrestore.ovpl script on the target server.

Post-Upgrade Configuration

Create a new self-signed certificate.
1. List the content of NNMi's self-signed certificate by running the following command:
  %nnminstalldir%\nonOV\jdk\hpsw\bin\keytool -list –v –keystore /var/opt/OV/shared/nnm/certificates/nnm.keystore –storepass nnmkeypass
  /opt/OV/nonOV/jdk/hpsw/bin/keytool -list –v –keystore /var/opt/OV/shared/nnm/certificates/nnm.keystore –storepass nnmkeypass
2. Obtain the CN value for the self-signed certificate [FQDN].
3. Run the following command to create a new self-signed certificate:
  %nnminstalldir%\nonOV\jdk\hpsw\bin\keytool –genkey –alias<new alias name> -keyalg rsa –sigalg SHA256withRSA –keysize 2048 –dname cn=<CN value>-keypass nnmkeypass –validity 36500 –keystore /var/opt/OV/shared/nnm/certificates/nnm.keystore –storepass nnmkeypass –storepass nnmkeypass
  /opt/OV/nonOV/jdk/hpsw/bin/keytool –genkey –alias<new alias name>-keyalg rsa –sigalg SHA256withRSA –keysize 2048 –dname cn=<CN value>-keypass nnmkeypass –validity 36500 –keystore /var/opt/OV/shared/nnm/certificates/nnm.keystore –storepass nnmkeypass –storepass nnmkeypass
  In this instance, <CN value> is the CN value that you noted down; you must replace <new alias name> with an alias name of your choice.
Edit the nms-local.properties file.
1. Go to the following location:
```
%nnmdatadir%\conf\props
```
```
/var/opt/OV/conf/nnm/props
```
2. Open the nms-local.propertiesfile in a text editor.
3. Locate the KEY_ALIAS line.
4. Copy and paste the line to create two entries.
5. For the first instance, comment out by adding # to the beginning of the line.
6. For the newly created line, change the value to the alias specified to the new alias value.
Restart NNMi by running the following commands
%nnminstalldir%\bin\ovstop -c
%nnminstalldir%\bin\ovtsrat -c
/opt/OV/bin/ovstop -c
/opt/OV/bin/ovstart -c

Post-Upgrade Tasks in a GNM Environment

NNMi automatically resynchronizes topology, state, and status following an upgrade.

Avoid stopping NNMi during the resynchronization. To help ensure resynchronization has completed, NNMi should remain running for several hours following the upgrade. The actual time required depends on the number of nodes and the volume of state changes and trap data received while performing the resynchronization.

If NNMi must be stopped before the resynchronization is finished, the resynchronization should be run again and allowed to complete.

To perform a manual resynchronization of the entire management server, run:

nnmnoderediscover.ovpl –all –fullsync

Upgrade Problems and Solutions

Failure to Open the Upgrade Wizard on Linux

If the installation wizard fails to open and the No protocol specified message appears in the console, verify that you logged on to the system as root.

Inability to Locate MEDIA Images

When the upgrade wizard stops during initialization and shows the locate MEDIA images pane with a message to manually select the media, you can conclude the NNMi installation media is not correctly downloaded on the server.

To resolve this problem, download the media again and start the installation.

Failure to Open the NNMi Console After Upgrade

Verify that all NNMi services have been started after upgrade:
At a command prompt, run the following command:
ovstatus -c

If the command output looks similar to the following text, all services have been upgraded.

Name	 PID	 State 	Last Message

OVsPMD 3262 RUNNING	-

pmd	3327	RUNNING	Initialization Complete

ovjboss	3292	RUNNING	Initialization Complete

nmsdbmgr	3263	RUNNING	Database Available

Stop or start NNMi services as needed. At the command prompt, type the appropriate command:
- ovstop -c <service name>
- ovstart -c <service name>

Network Node Manager i

For the Windows® and Linux® operating systems

Software Version: 2019.05

NNMi Interactive Upgrade Guide

Legal Notices

Warranty

Restricted Rights Legend

Copyright Notice

Trademark Notices

Acknowledgements

Documentation Updates

Support

Support

NNMi Interactive Upgrade Guide