Troubleshoot > NNMi Installation and Upgrade Issues

NNMi Installation and Upgrade Issues

The following sections describe some possible installation issues:

Inadequate Disk Space During Installation on Linux

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:

  1. Uninstall NNMi, if necessary.
  2. 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

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

To switch to the root user, type su.

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.

Failure to Open the NNMi Console After Upgrade

Verify that all NNMi services have been started after upgrade:
  1. 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


    pmd 3327 RUNNING Initialization Complete
    ovjboss 3292 RUNNING Initialization Complete
    nmsdbmgr 3263 RUNNING Database Available
  2. Stop or start NNMi services as needed. At the command prompt, type the appropriate command:

    ovstop -c <service name>

    ovstart -c <service name>