Choose an installation method

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

Ports

Verify that all of the following ports are free before installing NNMi:

80
443
1098
1099
3873
4444 through 4446
4457 through 4460
5432
7800 through 7810
8083
8886
8887
8989
162

Make sure that none of the above ports are used by the HA software. If necessary, configure your HA software to free up all the ports listed above.

Before installing NNMi, make sure that the firewall on your NNMi management server and other antivirus software applications do not block any of the above ports.

FQDN Configuration

Before you install NNMi on the management server, complete the following actions:

Determine the official fully-qualified domain name (FQDN) of the NNMi management server. You will need this information during installation. The official FQDN must meet the following requirements:
- It must be DNS-resolvable to the NNMi management server.
- It must be available for accessing the NNMi management server from other computers on your network.
Check for the SNMP service; if installed, the SNMP trap service needs to be disabled on this server.
For Dynamic Host Configuration Protocol (DHCP) users. Make sure that the NNMi management server is consistently assigned the same IP address.

HA Cluster Requirements

Before installing NNMi in an HA cluster, you must make sure that the HA software is correctly installed on all the systems in the cluster. Also, see the Support Matrix to make sure NNMi supports the HA software that you are going to use.

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

XServer

You can install 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.

Asynchronous Input/Output

Make sure that Asynchronous Input/Output (AIO) is enabled on the system.

Public Key

You must import the necessary 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 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. See the Installation Troubleshooting section if you see any error messages.

Install Libraries

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

Linux Version	Package	Library
Red Hat Enterprise Linux .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
	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
	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
	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
	liberation-fonts-common
	liberation-sans-fonts

Configure Swap Space

Configure the swap space of the system to at least one and a half times physical memory.

Disk partition recommendation

If you partition your disk, you should ensure that the file systems containing the directories listed in the following table have at least the specified disk space available for NNMi. If you use all-in-root partitioning, you should ensure that the total required disk space is available.

It is recommended that you keep at least 1 GB free space in the /tmp directory.

Tune Linux Kernel

Tune the Linux kernel parameters listed in the table below.

Kernel Parameter	Description	Steps
UDP Receive Buffer	NNMi requires sufficient amount of memory for User Datagram Protocol (UDP) buffering. Set the UDP buffer properties to the following values: UDP receive buffer: 8 MB UDP send buffer: 2 MB	On the Linux system, edit the `/etc/sysctl.conf` file to add the following entries: net.core.rmem_max = 8388608 net.core.wmem_max = 2097152 Save the file. Restart the system.
UDP Send Buffer
Shared Memory	NNMi requires you to set the Shared Memory to at least 12 GB (recommended: 64 GB).	On the Linux system, edit the `/etc/sysctl.conf` file to add the following entries: kernel.shmmax = 68719476736 kernel.shmall = 68719476736 Save the file. Restart the system.
Number of open files per process	This parameter should be set to at least 16384.	On the Linux system, edit the `/etc/security/limits.conf` file to add the following entries: * soft nofile 16384 * hard nofile 16384 Save the file. Restart the system.

Disable Anti-Virus Software

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

On the Windows server, 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 installation, restart each anti-virus service.

Prerequisites for the Oracle Database

To improve performance and to avoid a port conflict with NNMi, Oracle must be installed on a separate server from the NNMi management server.

An Oracle database administrator creates the NNMi Oracle database. To install an Oracle database instance for NNMi, complete the following tasks:

Working with your Oracle database administrator, install an Oracle database according to the instructions provided by Oracle.
Create a database instance for NNMi. Make sure you know the host name of the Oracle server and the database instance name; you will need this information during the NNMi installation.
Create a tablespace that will only be used by the NNMi user accessing the database.
Assign a tablespace size depending on the number of nodes in your installation. For example, for an 18,000 node network, set your beginning tablespace size for 12 gigabytes (GB). Set the option for unlimited tablespace extensions in increments of 12 GB.
The database requirement grows as NNMi discovers additional nodes, so watch this growth carefully and expand your configured tablespace size when necessary.
It is important to assign a large enough tablespace quota to a user. If the tablespace is not large enough, NNMi will be installed, but will be unable to create the tables. This causes problems after the installation. To prevent this, set the quota to unlimited, but no smaller than 1MB before installing NNMi.
Create an Oracle user and assign the user to the newly created tablespace. The user should have the following permissions:
- Create sequence (required for NNMi to connect to the database)
- Create session (required for creating or updating the database schema)
- Create table (required for creating or updating the database schema
- Create view (required for creating or updating the database schema
- FLASHBACK ANY TABLE (recommended)
  
  The FLASHBACK ANY TABLE permission enables NNMi to create restore points during upgrade. After the upgrade completes, you can remove the FLASHBACK ANY TABLE permission.
- SELECT ANY DICTIONARY
  You can opt to not grant the SELECT ANY DICTIONARY permission to the user. If you do not grant the SELECT ANY DICTIONARY permission, NNMi does not show any information in the Health tab (under the Help > System Information menu).
  For Oracle 12.1.0.1.0 only. The SELECT ANY DICTIONARY permission, however, is required for the NNMi installation if you use Oracle 12.1.0.1.0. You can revoke the SELECT ANY DICTIONARY permission after the installation is complete.
Make note of the Oracle user name and password; you will need this information during the NNMi installation.

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.

Preparation for Application Failover

To create an NNMi Application Failover cluster, you must identify two servers, install NNMi on each of them, and then configure one server to be the active server while the other server remains in the standby mode. Both the servers must have unrestricted network access to each other.

Install NNMi

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.
Log on as a user with root privileges to the system where you plan to install NNMi.
Extract the contents of the NNMi media (or mount the media).
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.
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. Follow the instructions shown at https://marketplace.microfocus.com/itom/content/code-signing-gpg-or-rpm-signature-verification
3. 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.
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.
On the Introduction page, review the overview information for the installation, and then click Next.
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.
On the Setup Type page, select Typical; then click Next.
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.
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.
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.
You will now see the Server Configuration > Choose the database type page. On this page, select Micro Focus Software Embedded Database, click Next.
You will now see the Server Configuration > Choose the database type page. On this page, select Oracle.
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.
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.
On the Enter the database user account information page, enter the Username and Password for the Oracle database user.
The Product Requirements: Install Checks page displays progress as the installer checks for additional NNMi installation requirements. After the check completes, click Next.
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.
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.
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.
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.
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.
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.
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.
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/.
The installation process completes the installation and configuration processes and starts the NNMi services. This process takes several minutes.
Click Finish. The installation process begins.
Click Done to complete the installation.

To use the silent installation method with the help of the sample properties file:

On the target server (where you plan to install NNMi), log on with root privileges.
On the target server (where you plan to install NNMi), log on as a user with administrator privileges.
Copy the ovinstallparams.ini file from the support directory of the NNMi installation media to the /tmp directory if you are using Linux NNMi management servers.
From Control Panel, open System, and then click Advanced system settings.
Click Environment Variables, and then note the value of the TEMP variable.
In Windows Explorer, go to the directory mentioned in the TEMP environment variable. Copy the ovinstallparams.ini file from the support directory of the NNMi installation media to this directory.
Modify the ovinstallparams.ini file as shown below:
The following entries set the silent installation script to use the embedded database. Configure these settings as shown below:
[obs.install]
db.embedded=Solid

The following entry sets the HTTP port number for accessing NNMi. A common approach is to use port 8004 (the existing port number) if you are installing NNMi on a Windows operating system:
[nonOV.jboss]
httpport=8004
Under the [installer.properties] section, add the following parameter to choose a non-default Java Development Kit (JDK) installation.
Note: NNMi 2018.11 installer, by default, installs OpenJDK 1.8. If you have already installed an instance of OpenJDK 1.8 or Oracle JDK 1.8 on the system, use this parameter to specify the home directory of the already installed JDK.
```
com.hp.ov.nms.jdk.dir=
```
Set the parameter to the home directory of a JDK 1.8 instance that has already been installed.
Do not add the parameter if you want to use the embedded OpenJDK 1.8.
Modify the ovinstallparams.ini file as shown below:
The following entries set the silent installation script to use the embedded database. Configure these settings as shown below:
[obs.install]
db.embedded=Solid The following entry sets the HTTP port number for accessing NNMi. A common approach is to modify the port to 80 if you are installing NNMi on a Linux operating system. [nonOV.jboss] httpport=80
Under the [installer.properties] section, add the following parameter to choose a non-default Java Development Kit (JDK) installation.
Note: NNMi 2018.11 installer, by default, installs OpenJDK 1.8. If you have already installed an instance of OpenJDK 1.8 or Oracle JDK 1.8 on the system, use this parameter to specify the home directory of the already installed 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.
```
com.hp.ov.nms.jdk.dir=
```
Set the parameter to the home directory of a JDK 1.8 instance that has already been installed.
Do not add the parameter if you want to use the embedded OpenJDK 1.8.
If you are using an Oracle database and are not using High Availability or application failover, you must use a unique value for the db.instance parameter.

If you are using an Oracle database, and are using High Availability or application failover, run the ovstop -c command on the source system before beginning a silent installation.
On the target server, place the NNMi installation media.
Use the cd command to change to the media root.
Enter the following command: ./setup.bin -i silent
The silent installation runs silently, and takes some time. A silent installation shows no progress indicator. After the silent installation completes, NNMi is installed and available for use on the target server.
At the command prompt, enter the following command:
<media_root>\setup.exe -i silent
The silent installation runs silently, and takes some time. A silent installation shows no progress indicator. . After the silent installation completes, NNMi is installed and available for use on the target server.
To make sure that the NNMi services are running, enter the following at the command line: ovstatus -c
Stop the NNMi processes using the ovstop -c command.
As root, run the nnmchangesyspw.ovpl script to set the system password. You will need this new system password to run the Quick Start Configuration Wizard.
As Administrator, run the nnmchangesyspw.ovpl script to set the system password. You will need this new system password to run the Quick Start Configuration Wizard.
Start the NNMi processes using the ovstart -c command.
Run the Quick Start Configuration Wizard.

While installing NNMi instances in a GNM environment, you can choose any combination of supported operating systems and databases.

For example, you can create a GNM environment with:

One regional manager with the embedded database on Linux
One regional manager with an Oracle database on Windows
One global manager with the embedded database on Windows

Verify the Installation with the Installation Log Files

NNMi logs information about the installation process. You can view this information at the following location: %NnmDataDir%\log\nnm\

NNMi logs information about the installation process. You can view this information at the following location: /var/opt/OV/log/nnm/

The most important log file is the following file:

nnm-install-config.log: Contains a record of the most recent installation, including the processes that have been initialized. The installation is successful if you see the following message in the nnm-install-config.log file:

Installation was successful.

Next Steps

Configure the nnm-server.properties file for Oracle RAC

Skip this section if you do not use Oracle RAC.

Oracle RAC requires a secondary Oracle RAC server. To configure that information, after NNMi installation, do the following:

Open the following file in a text editor:

%NnmDataDir%\shared\nnm\conf\props\nnm-server.properties

/var/opt/OV/shared/nnm/conf/props/nnm-server.properties

Locate the following line:

com.hp.ov.nms.oracle.otherHost=<SAME_AS_FIRST_HOST>

Change the value of <SAME_AS_FIRST_HOST> to be the host name or IP address of the secondary Oracle RAC server.
Run the following commands to restart NNMi:
1. ovstop
2. ovstart

Install iSPIs

If you want to use NNMi with iSPIs, follow this sequence of installation:

Make sure that NNMi is successfully installed.
Install the NNM iSPI Performance for Metrics with Network Performance Server (available with the NNM iSPI Performance for Metrics media).
See the NNM iSPI Performance for Metrics Interactive Installation Guide for more information.
Install all other iSPIs.

Configure the HA cluster

Complete the installation procedure on both the nodes in the HA cluster, and then follow the instructions in the Configure high availability cluster section in NNMi help center.

Configure the application failover cluster

Complete the installation procedure on both the nodes in the HA cluster, and then follow the instructions in the Configure application failover section in NNMi help center.

Perform initial configuration tasks

Micro Focus recommends that you use the Quick Start Configuration Wizard for initial setup.

If you plan to manage areas in your network that contain overlapping IP addresses resulting from using Network Address Translation (NAT), choose one address domain for the Quick Start Wizard to discover (no duplicate addresses). Then, see additional discovery information in Overlapping Addresses in NAT Environments in the NNMi help center.

After initial configuration, you can use the NNMi console for additional configuration tasks, such as adding nodes to the network topology and configuring monitoring.

To use the Quick Start Configuration Wizard:

Point your browser to the following URL: http://<fully_qualified_domain_name>:<port_number>/quickstart/

where <fully_qualified_domain_name> represents the fully-qualified domain name of the NNMi management server and <port_number> is the https port number you selected during installation.

If your NNMi management server has more than one domain name, NNMi chooses one during the installation process. To determine which fully-qualified domain name NNMi is using, run the nnmofficialfqdn.ovpl script. See the nnmofficialfqdn.ovpl reference page, or the Linux manpage, for more information.
Log on as follows:
User Name: system
Password: The password that you created at the end of the installation process or during silent installation.
On the Add Community Strings page, enter a community string for one of the nodes in the discovery range; then click Add. Repeat this step until the SNMP Community Strings list includes the community strings for all nodes in the discovery range; then click Next.

NNMi automatically tries to match community strings to known devices. You do not need to manually associate each community string with a specific device.
On the Configure Auto Discovery page, add the IP address range for the quickstart rule; then click Next.

Examples of valid IP address ranges include:

10.1.1.*
10.1.1.1-99
10.10.50-55.*
10.1-7.1-9.1-9

On the Add Discovery Seeds page, add discovery seed information for your network; then click Next.

Enter discovery seeds in the form of IP addresses or fully-qualified domain names. The network devices represented by these seeds help the NNMi spiral discovery process discover your network accurately. See Specify Discovery Seeds in the NNMi help.

You can use the nnmloadseeds.ovpl command to load seeds using a command line. See the nnmloadseeds.ovpl reference page, or the Linux manpage, for more information.
On the Test Seeds page, review the results of the communication tests. If any of the seed nodes cannot be reached with the community strings that you identified earlier, click Previous to navigate to the Configure Community Strings page. Correct the community strings; then click Next.

Repeat this step until all nodes can be reached; then click Next.
On the CreateAdministrator Account page, enter a User Name, set the Password for a new account for administering the NNMi software, then click Next.
On the Summary page, review the information that you specified; then do one of the following actions:
To change any of the settings, click Previous.
To use the current settings, click Commit.
The Wizard is complete page indicates that you have successfully configured NNMi to discover a portion of your network. Click Previous to make changes or click Launch UI.

After you click Launch UI, The NNMi console user interface opens.

You cannot use the Quick Start Configuration Wizard to complete SNMP Version 3 (SNMPv3) configuration. If you have devices that you prefer to monitor using SNMPv3, do the following:

Open the NNMi console.
Select Communication Configuration from the Configuration Workspace.
Complete the SNMPv3 configuration.

After installation, restart any anti-virus software.

In addition, follow these steps:

On the active node, copy the following file:
- Windows: %nnmdatadir%\nmsas\NNM\data\topo\keystore.jceks
- Linux: /var/opt/OV/nmsas/NNM/data/topo/keystore.jceks
On the standby node, place the file in the following directory (manually create the directory if it does not exist):
- Windows: %nnmdatadir%\nmsas\NNM\data\topo
- Linux: /var/opt/OV/nmsas/NNM/data/topo

Licensing NNMi

The NNMi installer includes a temporary Instant-On license key that is valid for 60 days after you install NNMi. This temporary Instant-On license key enables you to use NNMi Ultimate features. You should obtain and install a permanent license key as soon as possible.

Installation Troubleshooting

The following information discusses some possible installation problems and solutions:

Error Messages While Importing Public Keys

While you import public keys from the MF_public_keys.tar.gz file, the following error message may appear:

Not an armored public key

Ignore this error message.

Inadequate Disk Space During Installation on Linux

NNMi installs all application binaries in the /opt/OV directory and all data files in the /var/opt/OV directory.

See the Network Node Manager i Software Support Matrix for the disk space requirements for your server. If you do not have enough disk space in either /opt/OV or /var/opt/OV, use the following workaround to address the problem:

Uninstall NNMi, if necessary.
Create symbolic links from the install targets to larger partitions that have enough available disk space to install the binaries and store the data files. The syntax to create the symbolic links is as follows:
- ln -s <large disk> /opt/OV
- ln -s <large disk> /var/opt/OV
Install NNMi.

Failure to Open the Installation 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 installation 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.

Legal Notices and Support Information

Network Node Manager i

For the Windows® and Linux® operating systems

Software Version: 2018.11

NNMi Interactive Installation Guide

Legal Notices

Warranty

Restricted Rights Legend

Copyright Notice

Trademark Notices

Acknowledgements

Documentation Updates

Support

Support

NNMi Interactive Installation Guide