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

Read the Supporting Documentation

Read the following documents to better prepare for this NNM iSPI Performance for Traffic installation:

• NNMi Ultimate Release Notes
  
• NNMi Ultimate Support Matrix
  

You must always use the following sequence while installing the NNM iSPI Performance for Traffic:

1. Install the NNMi Extension for iSPI Performance for Traffic. The NNMi Extension for iSPI Performance for Traffic adds the NNM iSPI Performance for Traffic-related links and views into the NNMi workspace. You must always install the NNMi Extension for iSPI Performance for Traffic on the NNMi management server.
2. Install the Master Collector: The Master Collector is the centralized processing component for a deployment; the Master Collector receives data from all Leaf Collectors. The Master Collector can also connect and receive data from other regional Master Collectors as well as Leaf Collectors configured in the Global Network Management (GNM) setup.
3. Install the Leaf Collector: The Leaf Collector receives the IP flow packets exported by routers, parses and filters the IP flow packets, and sends the aggregated flow records to the Master Collector.

Depending on the scale of your network, you can install a single Master Collector with a single Leaf Collectors or multiple instances of Leaf Collectors with a single instance of the Master Collector. The NNMi Extension for iSPI Performance for Traffic must always be installed on the NNMi management server.

The NNMi Extension for iSPI Performance for Traffic adds the NNM iSPI Performance for Traffic related links and views into the NNMi workspace.

You must always install the NNMi Extension for iSPI Performance for Traffic on the NNMi management server.

1. Log on to the NNMi management server with the administrative privileges. Make sure that the user with administrative privileges is part of Local administrator group.

   Log on to the NNMi management server with the root privileges.

2. Extract the contents of the NNM iSPI Performance for Traffic installation media (or mount the media).

3. When NNMi is on Windows. Go to the Traffic_NNM_Extension\WinNT folder on the installation media, and then double-click the setup.exe file.

   When NNMi is on Linux. Go to the Traffic_NNM_Extension/Linux directory on the installation media, and then run the setup.bin file.

   Go to the Traffic_NNM_Extension/Linux directory on the installation media, and then run the setup.bin file.

   The installer configures your system for the installation and initializes the installation process.

4. On the Introduction (Install) page, review the overview information, and then click Next. The License Agreement page opens.
5. Review the License Agreement, select I accept..., and then click Next. The Select Features page opens.
6. Click Next. The Install Checks page opens.
7. Click Next. The Pre-Install Summary page opens.
8. Click Install. The installation process begins.
9. During installation, the NNMi Extension for iSPI Performance for Traffic dialog box opens. In this dialog box, specify the following details:
   • NNMi User Password: Type the password of the NNMi system account.

     Note: The system account is a special administrator account that NNMi creates during installation (see the Installing NNMi section in the HPE Network Node Manager i Software Interactive Installation Guide).

   • Retype Password: Type the password again.
   • Traffic Master FQDN: Type the Fully Qualified Domain Name (FQDN) of the Master Collector system.

     Since you plan to install the Master Collector in a high availability (HA) cluster environment, you must specify the virtual IP address or virtual FQDN of the cluster.

   The following details are automatically detected by the installer:

   • NNMi User Name: The NNMi system user
   • NNMi FQDN: The Fully Qualified Domain Name of the NNMi management server
   • NNMi JNDI Port: The JNDI port number of the NNMi management server
   • Traffic Master HTTP Port: The HTTP port that is used for communication between the Master Collector and the NNMi management server

10. When the installer completes installing the NNMi Extension for iSPI Performance for Traffic, a pop-up window appears displaying the status of the installation. Click OK.
11. Click Done.
12. Restart the NNMi processes after installing the NNMi Extension for iSPI Performance for Traffic. Make sure that no traffic processes are running while performing this operation.

    Restart NNMi’s processes by running the following commands:

    ovstop -c ovjboss

    ovstart -c

    You can also select Start > All Programs > HP > Network Node Manager > ovstop / ovstart.

You can install the NNM iSPI Performance for TrafficMaster Collector on the NNMi management server or on a standalone, remote server.

You can install only one Master Collector in your environment. In a Global Network Management (GNM) environment, you must install one Master Collector for every region.

Preinstallation Tasks

Create a New User with the Web Service Client Role on the NNMi Management Server

Create a user from the NNMi console with the Web Service Client role. For more information on creating a new user with the Web Service Client role, see the Network Node Manager i Software Help for Administrators.

Note Down the Details of the NNMi Management Server

1. Navigate to the following directory:

   %NnmDataDir%\Conf\nnm\props

   /var/opt/OV/Conf/nnm/props

2. Open the nms-local.properties file with a text editor.
3. Note down the following properties from the primary NNMi management server:
   • com.hp.ov.nms.fqdn: The FQDN of the NNMi management server.
   • nmsas.server.port.web.http: The HTTP port used by NNMi.
   • nmsas.server.port.web.https: The HTTPS port used by NNMi.
   • nmsas.server.port.naming.port: The JNDI port of NNMi. If this property is commented out (with the #! characters) in the file, NNMi uses the default JNDI port, 1099.

If NNMi is installed and configured in the application failover mode, you must also note down the above properties from the nms-local.properties file on the secondary NNMi management server.

Ensure the Availability of Necessary Ports

On the Master Collector system, make sure the following ports are available for use:

12043, 12080, 12083, 12084, 12085, 12086, 12087, 12092, 12099, 12458, 12500, 12501, 12712, 12713, 12714, and 12873

Ensure KornShell is Installed

On the Master Collector system, make sure KornShell is installed.

To check that KornShell is installed, open a command-line terminal and type the following command:

ksh

If KornShell is installed, the command prompt changes to ksh.

If KornShell is not installed, the following error message appears:

ksh is not found

If you do not have KornShell installed, you can download it from http://www.kornshell.com/software/ and install it.

Ensure the Availability of GID 26

Make sure that the Group ID (GID) 26 is not used by any existing user groups on the system.

Ensure the Availability of the Required Libraries
Make sure that both the 64-bit compat-libstdc++ and 32-bit compat-libstdc++ libraries are available before installing Master Collector. Master Collector requires the following exact library versions; however, the RPM versions may vary depending on the minor release of Linux.

Before installing Master Collector on a 64-bit Linux server, verify that the following library files are installed:

RPM: compat-libstdc++-33-3.2.3-69.el6.x86_64
/usr/lib64/libstdc++.so.5
/usr/lib64/libstdc++.so.5.0.7

RPM: compat-libstdc++-33-3.2.3-69.el6.i686
/usr/lib/libstdc++.so.5
/usr/lib/libstdc++.so.5.0.7

RPM: glibc-2.12-1.47.el6_2.5.x86_64
/lib64/libc-2.12.so

RPM: libaio-0.3.107-10.el6.x86_64
/lib64/libaio.so.1

RPM: libXtst-1.0.99.2-3.el6.x86_64
/usr/lib64/libXtst.so.6

RPM: libXext-1.1-3.el6.i686
/usr/lib/libXext.so.6

RPM: libXi-1.3-3.el6.x86_64
/usr/lib64/libXi.so.6

RPM: libXi-1.3-3.el6.i686
/usr/lib/libXi.so.6

RPM: nss-softokn-freebl-3.12.9-11.el6.i686
/lib/libfreebl3.so
/usr/lib/libfreebl3.so

RPM: libgcc-4.4.6-3.el6.i686
/lib/libgcc_s-4.4.6-20110824.so.1
/lib/libgcc_s.so.1

RPM: libXau-1.0.5-1.el6.i686
/usr/lib/libXau.so.6
/usr/lib/libXau.so.6.0.0

RPM: libxcb-1.5-1.el6.i686
/usr/lib/libxcb-composite.so.0
/usr/lib/libxcb-composite.so.0.0.0
/usr/lib/libxcb-damage.so.0
/usr/lib/libxcb-damage.so.0.0.0
/usr/lib/libxcb-dpms.so.0
/usr/lib/libxcb-dpms.so.0.0.0
/usr/lib/libxcb-dri2.so.0
/usr/lib/libxcb-dri2.so.0.0.0
/usr/lib/libxcb-glx.so.0
/usr/lib/libxcb-glx.so.0.0.0
/usr/lib/libxcb-randr.so.0
/usr/lib/libxcb-randr.so.0.1.0
/usr/lib/libxcb-record.so.0
/usr/lib/libxcb-record.so.0.0.0
/usr/lib/libxcb-render.so.0
/usr/lib/libxcb-render.so.0.0.0
/usr/lib/libxcb-res.so.0
/usr/lib/libxcb-res.so.0.0.0
/usr/lib/libxcb-screensaver.so.0
/usr/lib/libxcb-screensaver.so.0.0.0
/usr/lib/libxcb-shape.so.0
/usr/lib/libxcb-shape.so.0.0.0
/usr/lib/libxcb-shm.so.0
/usr/lib/libxcb-shm.so.0.0.0
/usr/lib/libxcb-sync.so.0
/usr/lib/libxcb-sync.so.0.0.0
/usr/lib/libxcb-xevie.so.0
/usr/lib/libxcb-xevie.so.0.0.0
/usr/lib/libxcb-xf86dri.so.0
/usr/lib/libxcb-xf86dri.so.0.0.0
/usr/lib/libxcb-xfixes.so.0
/usr/lib/libxcb-xfixes.so.0.0.0
/usr/lib/libxcb-xinerama.so.0
/usr/lib/libxcb-xinerama.so.0.0.0
/usr/lib/libxcb-xselinux.so.0
/usr/lib/libxcb-xselinux.so.0.0.0
/usr/lib/libxcb-xtest.so.0
/usr/lib/libxcb-xtest.so.0.0.0
/usr/lib/libxcb-xv.so.0
/usr/lib/libxcb-xv.so.0.0.0
/usr/lib/libxcb-xvmc.so.0
/usr/lib/libxcb-xvmc.so.0.0.0
/usr/lib/libxcb.so.1
/usr/lib/libxcb.so.1.1.0

RPM: libX11-1.3-2.el6.i686
/usr/lib/libX11-xcb.so.1
/usr/lib/libX11-xcb.so.1.0.0
/usr/lib/libX11.so.6
/usr/lib/libX11.so.6.3.0

RPM: libaio-0.3.107-10.el6.i686
/lib/libaio.so.1
/lib/libaio.so.1.0.0
/lib/libaio.so.1.0.1
/usr/share/doc/libaio-0.3.107/
/usr/share/doc/libaio-0.3.107/COPYING
/usr/share/doc/libaio-0.3.107/TODO

RPM: compat-libstdc++-296-2.96-144.el6.i686
/usr/lib/libstdc++-3-libc6.2-2-2.10.0.so
/usr/lib/libstdc++-libc6.2-2.so.3

https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPLinuxCodeSigning

To know more about prerequisite information, see NNMi Ultimate Support Matrix.

To install the Master Collector:

1. Log on to the system where you want to install the collector with the administrative privileges. Make sure that the user with administrative privileges is part of Local administrator group.
2. Log on to the system where you want to install the collector with the root privileges.
3. Import the HPE public key into the Linux RPM database before installing the NNM iSPI Performance for TrafficMaster Collector. To do this, point your browser to the following location and follow the instructions:

   https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPLinuxCodeSigning

4. Extract the contents of the installation media (or mount the media).

   Go to the Traffic_Master directory on the installation media and double-click the setup file. The installer configures your system for the installation and initializes the installation process.

5. Go to the Traffic_Master directory on the installation media and run the following command:

   ./setup

   The installation initialization process prompts you to choose the language you want to use. The installer configures your system for the installation and initializes the installation process.

6. On the Introduction (Install) page, review the overview information, and then click Next. The License Agreement page opens.
7. Review the End User License Agreement, select I accept.., and then click Next. The Select Features page opens.
8. Click Next.
9. If no other HPE Software products are installed on the system, the installer opens the Choose the Application and Data Folder page. Make your selection, and then click Next.
10. Select HP Software Embedded Database.
11. Select Oracle.
12. Click Next.
12. The Choose Database Initialization Preferences page opens. On this page, follow these steps:
    1. Do one of the following:
       • If you want to initialize an Oracle database using previously defined database accounts, select Primary Server Installation, and then click Next.
       • If you want to connect to an existing database that is already initialized by another primary installation and use this installation in an application failover or HA configuration, select Secondary Server, and then click Next.
    2. In the Enter Your Database Server Information page, specify the following details:

       • Host: The FQDN of the Oracle server

         If you are using Oracle RAC:

         • Enter the physical host name of one of the Oracle servers.
         • Oracle RAC also requires a secondary Oracle RAC server. However the secondary Oracle RAC server is unknown at this point in the collector installation. See the last installation step for more information.
       • Port: The port used by Oracle
       • Instance: The Oracle instance name that you created when installing the NNM iSPI Performance for Traffic for the first time.
    3. Click Next. The Enter the Database Account User page opens.
    4. Type the user name and password to access the Oracle instance, and then click Next.
13. The Install Checks page displays progress as the installation software checks for additional Master Collector requirements. Click Next. The Pre-Install Summary page opens.

14. On the Pre-Install Summary page, review your installation choices and click Install. The installation process begins.

    The Choose Java JDK dialog box opens.

    NNM iSPI Performance for Traffic requires that Java Development Kit (JDK) 1.8 be available on the system. This version of the NNM iSPI Performance for Traffic installer contains OpenJDK 1.8. You can select the Install bundled OpenJDK option to install OpenJDK 1.8 that is embedded with the NNM iSPI Performance for Traffic 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 JDK is installed, run one of the following commands:

    whereis java

    which java

    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.

15. During installation, the Configuring Master dialog box opens with the following sections:
    Primary NNMi Server Information Required by NNM iSPI Performance for Traffic

    Specify the following details:

    • Web Service Client User Name: The new user that you created with the Web Service Client Role on the NNMi Management Server when you installed the NNM iSPI Performance for Traffic for the first time.
    • Web Service Client Password: The password for the above-mentioned user
    • Retype Password: The above-mentioned password.
    • Is Secure? Select this option if you want the NNM iSPI Performance for Traffic to communicate with NNMi securely (using the HTTPS protocol).

      Make sure that you use the same mode of communication for NNM iSPI Performance for Traffic and NNMi. That is if you decide NNMi to use secure mode of communication, make sure that NNM iSPI Performance for Traffic also uses secure mode of communication.

      To enable the NNM iSPI Performance for Traffic to use HTTPS protocol, use NNMi’s out-of-the-box HTTPS configuration that uses a self-signed certificate created during installation. For more information about using a signed certificate from a Certificate Authority instead of the self-signed certificate, see the HPE Network Node Manager i Software Deployment Reference. When the Master Collector is not installed on the NNMi management system, see the Enabling Secure Communication between NNMi and the NNM iSPI Performance for Traffic section in the Network Node Manager iSPI Performance for Traffic Software Deployment Reference.

    • NNMi Failover Configured: Select this option if you configured NNMi to work in the application failover mode.

    The following details are automatically detected by the installer:

    • NNMi FQDN: FQDN of the NNMi management server
    • NNMi HTTP Port: The HTTP port used by the NNMi management server
    • NNMi HTTPS Port: The HTTPS port used by the NNMi management server
    • NNMi JNDI Port: The JNDI port used by the NNMi management server
    Secondary NNMi Server Information Required by NNM iSPI Performance for Traffic

    This section is enabled only if you select the NNMi Failover Configured option. Do not type anything in this section if NNMi is not configured to work in the application failover mode.

    Specify the following details:

    • NNMi FQDN: FQDN of the NNMi management server
    • NNMi HTTP Port: The HTTP port used by the NNMi management server
    • NNMi HTTPS Port: The HTTPS port used by the NNMi management server
    • NNMi JNDI Port: The JNDI port used by the NNMi management server
    • Web Service Client User Name:The new user that you created with the Web Service Client Role on the NNMi Management Server when you installed the NNM iSPI Performance for Traffic for the first time.
    • Web Service Client Password: The password for the above-mentioned user
    • Retype Password: The above-mentioned password
    • Is Secure? Select this option if you want the NNM iSPI Performance for Traffic to communicate with NNMi securely (using the HTTPS protocol).

      Make sure that you use the same mode of communication for NNM iSPI Performance for Traffic and NNMi. That is, if you decide NNMi to use secure mode of communication, make sure that NNM iSPI Performance for Traffic also uses secure mode of communication.

      To enable NNM iSPI Performance for Traffic to use HTTPS protocol, use NNMi’s out-of-the-box HTTPS configuration that uses a self-signed certificate created during installation. For more information about using a signed certificate from a Certificate Authority instead of the self-signed certificate, see the HPE Network Node Manager i Software Deployment Reference. When the Master Collector is not installed on the NNMi management system, see the Enabling Secure Communication between NNMi and the NNM iSPI Performance for Traffic section in the Network Node Manager iSPI Performance for Traffic Software Deployment Reference.

    Traffic iSPI Server: Information Required by NNMi

    Specify the following details:

    • Traffic Password: Type the password for the system user for the Master Collector.

      This user is not the NNMi system user that you used while installing the NNMi Extension for iSPI Performance for Traffic. After you specify the password for this user, the Master Collector installer creates this user. This is not an operating system user profile; this user is provisioned inside the Master Collector application.

      Note down this password. You require this password to log on to the NNM iSPI Performance for Traffic Configuration form when configuring the Leaf Collectors. HPE recommends you to provide the same password here that was specified for the NNMi system account.

    • Retype Password: Type the above password again.
    • Is Secure? Select this option if you want the NNM iSPI Performance for Traffic to communicate with NNMi securely (using the HTTPS protocol).

      Make sure that you use the same mode of communication for NNM iSPI Performance for Traffic and NNMi. That is, if you decide NNMi to use secure mode of communication, make sure that NNM iSPI Performance for Traffic also uses secure mode of communication.

    The following details are automatically detected by the installer:

    • HTTP Port: 12080
    • HTTPS Port: 12043
    • JNDI Port: 12099

    You cannot modify these ports.

16. Click Submit. The installation process continues and the Performance SPI Server Configuration dialog box opens.
17. In the Performance SPI Server Configuration dialog box, type the FQDN of the NPS server, and then click OK.

    Do not specify any other parameter.

    Note: If the NPS server is configured in a distributed deployment, you must type the FQDN of the Database Server (DB Server) in the Performance SPI Server Configuration dialog box.

    Once the installer completes installing the Master Collector, the Installation Complete page opens.

18. Click Done.
19. Mount the shared directory on the Master Collector system when the Master Collector is installed on a system other than the NNMi management server.
    To use the NFS protocol, follow these steps:

    1. Log on to the NNMi management server.
    2. Navigate to the /etc directory.
    3. Open the exports file with a text editor and add the following entry:

       /var/opt/OV/shared/perfSpi/datafiles <mastercollectorhostname>(rw,sync,no_root_squash)

       In this instance, <mastercollectorhostname> is the hostname of the Master Collector system.

    4. Save and close the file.
    5. Restart the NFS service on the NNMi management server using the following command:

       service nfs restart

    6. Log on to the Master Collector system.
    7. Stop the Master Collector processes using the following command:

       /opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl

    8. Navigate to the following directory:

       /var/opt/OV/nmsas/traffic-master/conf

    9. Open the nnm.extended.properties file with a text editor.
    10. Set the com.hp.ov.nms.spi.traffic-master.Nnm.perfspidatapath property to the

        complete path to the shared directory between NNMi management server and the NPS system.

        The default path to the shared directory is /net/<nnmihostname>/var/opt/OV/shared/perfSpi/datafiles. In this instance, <nnmihostname> is the hostname of the NNMi management server.

    11. Save and close the file.

    To use the CIFS protocol, rRun the nmstrafficmountnpsshare.ovpl script as follows:

    Note: The nmstrafficmountnpsshare.ovpl enables you to mount the shared directory created using the Common Internet File System (CIFS) only.

    Perform this task only when NPS is configured to use the CIFS share. To use the nmstrafficmountnpsshare.ovpl, make sure that the samba-utils and cifs-utils are installed on the Master Collector system.

    Run the following command to mount the shared directory on the Master Collector system:
    nmstrafficmountnpsshare.ovpl -n <nnmihostname> -u <username> -p <password>.
    In this instance, <username> is the name of the user account that was specified while running the nnmenableperspi.ovpl script.

    <password> is the password of the above user.

    Tip: You can find the details specified during the last run of the nnmenableperfspi.ovpl file in the following file on the NNMi management server:

    (The file does not store the password.)

    • On Linux:

      /var/opt/OV/log/nnmenableperfspi.txt

    • On Windows:

      %nnmdatadir%\log\nnmenableperfspi.txt

If you want to install multiple Leaf Collectors, you must install all instances of the Leaf Collector on systems where the Master Collector is not installed. The Master Collector and a Leaf Collector instance cannot coexist on the same system when multiple Leaf Collectors are installed on the network.

Preinstallation Tasks

Ensure the Availability of Necessary Ports

On the Leaf Collector systems, make sure the following ports are available for use:

11043, 11080, 11083, 11084, 11085, 11086, 11087, 11092, 11099, 11458, 11500, 11501, 11712, 11713, 11714, and 11813

Ensure KornShell is Installed

On the Leaf Collector system, make sure that KornShell is installed.

To check that KornShell is installed, open a command-line terminal, and then type the following command:

ksh

If KornShell is installed, the command prompt changes to ksh.

If KornShell is not installed, the following error message appears:

ksh is not found

If you do not have KornShell installed, you can download it from http://www.kornshell.com/software/ and install it.

Ensure the Availability of GID 26

Make sure that the Group ID (GID) 26 is not used by any existing user groups on the system.

Ensure the Availability of the Required Libraries

Make sure that both the 64-bit compat-libstdc++ and 32-bit compat-libstdc++ libraries are available before installing Leaf Collector. Leaf Collector requires the following exact library versions. The RPM versions may vary depending on the minor release of Linux.

Before installing Leaf Collector on a 64-bit Linux server, verify that the following library files are installed:

RPM: compat-libstdc++-33-3.2.3-69.el6.x86_64
/usr/lib64/libstdc++.so.5
/usr/lib64/libstdc++.so.5.0.7

RPM: compat-libstdc++-33-3.2.3-69.el6.i686
/usr/lib/libstdc++.so.5
/usr/lib/libstdc++.so.5.0.7

RPM: glibc-2.12-1.47.el6_2.5.x86_64
/lib64/libc-2.12.so

RPM: libaio-0.3.107-10.el6.x86_64
/lib64/libaio.so.1

RPM: libXtst-1.0.99.2-3.el6.x86_64
/usr/lib64/libXtst.so.6

RPM: libXext-1.1-3.el6.i686
/usr/lib/libXext.so.6

RPM: libXi-1.3-3.el6.x86_64
/usr/lib64/libXi.so.6

RPM: libXi-1.3-3.el6.i686
/usr/lib/libXi.so.6

RPM: nss-softokn-freebl-3.12.9-11.el6.i686
/lib/libfreebl3.so
/usr/lib/libfreebl3.so

RPM: libgcc-4.4.6-3.el6.i686
/lib/libgcc_s-4.4.6-20110824.so.1
/lib/libgcc_s.so.1

RPM: libXau-1.0.5-1.el6.i686
/usr/lib/libXau.so.6
/usr/lib/libXau.so.6.0.0

RPM: libxcb-1.5-1.el6.i686
/usr/lib/libxcb-composite.so.0
/usr/lib/libxcb-composite.so.0.0.0
/usr/lib/libxcb-damage.so.0
/usr/lib/libxcb-damage.so.0.0.0
/usr/lib/libxcb-dpms.so.0
/usr/lib/libxcb-dpms.so.0.0.0
/usr/lib/libxcb-dri2.so.0
/usr/lib/libxcb-dri2.so.0.0.0
/usr/lib/libxcb-glx.so.0
/usr/lib/libxcb-glx.so.0.0.0
/usr/lib/libxcb-randr.so.0
/usr/lib/libxcb-randr.so.0.1.0
/usr/lib/libxcb-record.so.0
/usr/lib/libxcb-record.so.0.0.0
/usr/lib/libxcb-render.so.0
/usr/lib/libxcb-render.so.0.0.0
/usr/lib/libxcb-res.so.0
/usr/lib/libxcb-res.so.0.0.0
/usr/lib/libxcb-screensaver.so.0
/usr/lib/libxcb-screensaver.so.0.0.0
/usr/lib/libxcb-shape.so.0
/usr/lib/libxcb-shape.so.0.0.0
/usr/lib/libxcb-shm.so.0
/usr/lib/libxcb-shm.so.0.0.0
/usr/lib/libxcb-sync.so.0
/usr/lib/libxcb-sync.so.0.0.0
/usr/lib/libxcb-xevie.so.0
/usr/lib/libxcb-xevie.so.0.0.0
/usr/lib/libxcb-xf86dri.so.0
/usr/lib/libxcb-xf86dri.so.0.0.0
/usr/lib/libxcb-xfixes.so.0
/usr/lib/libxcb-xfixes.so.0.0.0
/usr/lib/libxcb-xinerama.so.0
/usr/lib/libxcb-xinerama.so.0.0.0
/usr/lib/libxcb-xselinux.so.0
/usr/lib/libxcb-xselinux.so.0.0.0
/usr/lib/libxcb-xtest.so.0
/usr/lib/libxcb-xtest.so.0.0.0
/usr/lib/libxcb-xv.so.0
/usr/lib/libxcb-xv.so.0.0.0
/usr/lib/libxcb-xvmc.so.0
/usr/lib/libxcb-xvmc.so.0.0.0
/usr/lib/libxcb.so.1
/usr/lib/libxcb.so.1.1.0

RPM: libX11-1.3-2.el6.i686
/usr/lib/libX11-xcb.so.1
/usr/lib/libX11-xcb.so.1.0.0
/usr/lib/libX11.so.6
/usr/lib/libX11.so.6.3.0

RPM: libaio-0.3.107-10.el6.i686
/lib/libaio.so.1
/lib/libaio.so.1.0.0
/lib/libaio.so.1.0.1
/usr/share/doc/libaio-0.3.107/
/usr/share/doc/libaio-0.3.107/COPYING
/usr/share/doc/libaio-0.3.107/TODO

RPM: compat-libstdc++-296-2.96-144.el6.i686
/usr/lib/libstdc++-3-libc6.2-2-2.10.0.so
/usr/lib/libstdc++-libc6.2-2.so.3

HPE Public Key

You must import the HPE public key into the Linux RPM database before installation.

To import the HPE public key, follow the instructions available on the following web page:

https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPLinuxCodeSigning

To know more about pre-requisite information, see NNMi Ultimate Support Matrix.

The NNM iSPI Performance for Traffic interacts frequently with NNMi and NPS. After installing the NNM iSPI Performance for Traffic, you must make sure that the product is able to interact with both NNMi and NPS.

Configuring a User for the Master Collector System

If the Master Collector is installed on a system other than the NNMi management server, run the following command after installation to create a user that can start the Master Collector processes:

%TrafficInstallDir%\traffic-master\bin\nmstrafficmastersetuser.ovpl [--domain=<DomainName>] --username=<AdministratorUsername> --password=<AdministratorPassword>

In this Instance, <Domain Name> is the Fully Qualified Domain Name of the Master Collector. Note that Domain is a mandatory parameter if you are using a domain account.

If NPS is installed on a Windows system, you must specify the user name and password of the user that was created by the nnmenableperfspi.ovpl command (See the HPE Network Node Manager iSPI Performance for Metrics Interactive Installation Guide).

Make sure that the username that you specified for nmstrafficmastersetuser.ovpl is the same user that has the read/write access rights to the shared network directory.

If you are using a non-English system, make sure the user is a member of the Administrators group on the Master Collector system.

Synchronizing Time for All the Collectors

If the Master Collector and the Leaf Collector are not located on the same system, you must synchronize the time for the NNMi, NPS, Master Collector, and all Leaf Collectors using Network Time Protocol (NTP).

The NNM iSPI Performance for Traffic fails to create bridge between the Master Collector and the Leaf Collectors, if they are not synchronized using NTP.

Starting the Master Collector

Skip this step if the Master Collector is configured in an HA cluster.

Make sure that NNMi processes are started before starting the Master Collector.

To start the Master Collector, follow these steps:

1. Log on to the Master Collector system with administrator privileges. The user must be a member of the Administrators group.
2. Log on to the Master Collector system with root privileges.
3. Run the following command:

   %NnmInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl

   or

   %TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl

   /opt/OV/traffic-master/bin/nmstrafficmasterstart.ovpl

To check the status of the Master Collector installation, run the following command on the Master Collector system:

%NnmInstallDir%\traffic-master\bin\nmstrafficmasterstatus.ovpl

or

%TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstatus.ovpl

/opt/OV/traffic-master/bin/nmstrafficmasterstatus.ovpl

To stop the Master Collector, run the following command:

%NnmInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl

or

%TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl

/opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl

Starting the Leaf Collector

To start the Leaf Collector, follow these steps:

1. Log on to the Leaf Collector system with the administrator privileges. The user must be a member of the Administrators group.
2. Log on to the Leaf Collector system with the root privileges.
3. Run the following command:

   %NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl

   or

   %TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl

   /opt/OV/traffic-leaf/bin/nmstrafficleafstart.ovpl

To check the status of the Leaf Collector installation, run the following command on the Leaf Collector system:

%NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstatus.ovpl

or

%TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstatus.ovpl

/opt/OV/traffic-leaf/bin/nmstrafficleafstatus.ovpl

To stop the Leaf Collector, run the following command:

%NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl

or

%TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl

/opt/OV/traffic-leaf/bin/nmstrafficleafstop.ovpl

Validating Installation Configuration

Before you start working with NNM iSPI Performance for Traffic, follow these steps to validate the configuration settings you set up while installing NNM iSPI Performance for Traffic:

1. Launch the NNMi Console.

2. Log on to the NNMi Console with one of the Administrator user roles.

3. In the Configuration workspace, click NNM iSPI Performance for Traffic Configuration. The NNM iSPI Performance for Traffic Configuration form opens.

4. Log on to the NNM iSPI Performance for Traffic Configuration form with the credentials of the system user for the Master Collector that you created when installing the Master Collector.

5. Open Installation Verification form from the NNM iSPI Performance for Traffic Configuration form and validate the configuration settings you set up while installing NNM iSPI Performance for Traffic.

Managing Securities

You can configure the NNM iSPI Performance for Traffic to ensure security by enabling single sign-on, by configuring access with Public Key Infrastructure authentication, and by enabling security between NNMi management server, NPS, Master Collector, and Leaf Collector. For more information, see the Managing Securities section in the Network Node Manager iSPI Performance for Traffic Software Deployment Reference.

Pre-upgrade checks:

https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPLinuxCodeSigning

Perform these tasks to prepare for the upgrade:

Back Up the Master Collector 10.1010.20

Note: Do take the backup even if you are planning for an in-place upgrade. By taking a complete backup before upgrade, you can minimize the loss of data in the event of system failure during upgrade. However, skip the step if the Master Collector is installed on the NNMi management server.

Before backing up, put the Master Collector resource group to the HA maintenance mode by placing the maintenance file under the following directory on the active node:

%nnmdatadir\hacluster\<resource_group>

/var/opt/OV/hacluster/<resource_group>

1. Log on to the Master Collector system as rootadministrator.

2. Stop the Master Collector:

   <Install_Dir>\traffic-master\bin\nmstrafficmasterstop.ovpl

   /opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl

3. Run the following command to back up:

   <Install_Dir>\traffic-master\bin\nmstrafficmasterbackup.ovpl -target <Full path of the target archived file> -scope all

   /opt/OV/traffic-master/bin/nmstrafficmasterbackup.ovpl -target <Full path of the target archived file> -scope all

The backup script creates a tar file of the backup data.

Additionally, use the Oracle tools to back up the Master Collector database instance. See the Oracle documentation for more information.

Back Up the Leaf Collector 10.1010.20

Skip this procedure for the Leaf Collector instance that is installed on the management server. Backing up NNMi successfully backs up the Leaf Collector data.

Note: Do take the backup even if you are planning for an in-place upgrade. By taking a complete backup before upgrade, you can minimize the loss of data in the event of system failure during upgrade. However, skip the step if the Leaf Collector is installed on the NNMi management server.

1. Log on to the Leaf Collector system as rootadministrator.

2. Stop the Leaf Collector:

   <Install_Dir>\traffic-leaf\bin\nmstrafficleafstop.ovpl

   /opt/OV/traffic-leaf/bin/nmstrafficleafstop.ovpl

3. Run the following command to back up:

   <Install_Dir>\traffic-leaf\bin\nmstrafficleafbackup.ovpl -target <Full path of the target archived file> -scope all

   /opt/OV/traffic-leaf/bin/nmstrafficleafbackup.ovpl -target <Full path of the target archived file> -scope all

The backup script creates a tar file of the backup data.

Additionally, use the Oracle tools to back up the Leaf Collector database instance. See the Oracle documentation for more information.

(On the NPS system) Save the customConfig.cfg file as userConfig.cfg if you configured custom retention periods

Skip this step if you did not set custom retention periods for different NNM iSPI Performance for Traffic Extension Packs by modifying the customConfig.cfg files on the NPS system.

The NNM iSPI Performance for Traffic10.1010.20 enables you to configure a non-default data retention period for an NNM iSPI Performance for Traffic Extension Packs by modifying the customConfig.cfg file for the Extension Pack. Each NNM iSPI Performance for Traffic Extension Pack includes a copy of the customConfig.cfg file in the following location:

<Data_Dir>/NNMPerformanceSPI/rconfig/<Extension_Pack_Name>/customConfig.cfg

In this instance, <Data_Dir> is the data directory of NPS and <Extension_Pack_Name> is the name of the Extension Pack.

Run the about.ovpl command to see a list of Extension Packs installed on the system.

The upgrade process overwrites the existing customConfig.cfg. To retain the non-default retention settings after upgrade, follow these steps:

1. Create an empty userConfig.cfg file in the same directory.
2. Copy all parameters from the customConfig.cfg file and paste them in the userConfig.cfg file.
3. Save the userConfig.cfg file.

In addition, if you modified the customConfig.cfg file for the Interface Traffic_15_min Extension Pack, save a copy of the file at a secure location, which you will need to use after upgrade.

Operating System Requirement

Make sure the operating system of each collector system is at least Windows 2008 R2 SP1.

Upgrading the Master and Leaf Collectors involves installing the 10.1010.20 version of a collector on a new Linux system, restoring the data backed-up on the original collector system, and then upgrading the collector to the version 10.30. You must prepare new systems that are running on Red Hat Enterprise Linux 6.4.

Make sure the operating system is upgraded to at least Red Hat Enterprise Linux 6.4.

NNMi Backup

You must take a complete backup of NNMi as part of the procedure to upgrade NNMi 10.1010.20 to the version 10.30. See the NNMi 10.30 Interactive Installation and Upgrade Guide for more information about backing up NNMi.

Additionally, use the Oracle tools to back up the NNMi database instance. See the Oracle documentation for more information.

Upgrade Oracle

You must also upgrade the Oracle database to a supported version (see the NNMi Ultimate Support Matrix) and migrate the Oracle data. Set the FLASHBACK ANY TABLE permission.

Create New Oracle Instance

You must create a new instance of the Oracle database that will be used by the upgraded NNMi management server.

If a Leaf Collector exists on the NNMi management server, create another new Oracle instance for the collector.

For the Master Collector, create one more new Oracle instance.

Install NNMi 10.1010.20 on a new server that is running on Red Hat Enterprise Linux 6.4. While specifying the details of the Oracle database instance, make sure to type the details of the Oracle database instance that you newly created for NNMi (created here).

Follow the instructions in the NNMi 10.30 Interactive Installation and Upgrade Guide.

Install the Master Collector 10.1010.00 on a new serveron the new NNMi management server that is running on Red Hat Enterprise Linux 6.4.

Install each instance of the Leaf Collector 9.2010.00 on a new server that is running on Red Hat Enterprise Linux 6.4.

Follow the instructions in the NNM iSPI Performance for Traffic 9.2010.00 Installation Guide to install the collector.

Apply the 9.21 patch after installing NNM iSPI Performance for Traffic 9.20.

To upgrade the NNMi Extension for iSPI Performance for Traffic to 10.30 on this server, log on to the system as rootadministrator, and then follow these steps:

1. Go to the Traffic_NNM_Extension/Linux directory on the media. On the media, go to the Traffic_NNM_Extension/WinNT directory if NNMi is on Windows or go to the Traffic_NNM_Extension/Linux directory if NNMi is on Linux.

2. Run the following command:

   If NNMi is on Linux:

   ./setup.bin

   If NNMi is on Windows:

   setup.exe

   The installation wizard opens.

3. Click Next on the Installation (Upgrade) screen. The License Agreement screen appears.
4. Select I accept the terms.., and then click Next. The screen opens.
5. On the Product Customization screen, click Next. The Preinstall Summary screen appears.
6. On the Preinstall Summary screen, click Upgrade.
7. After the upgrade is complete, click Done.

Before upgrading the Master Collector:

On the active node, follow these steps:

1. If not already done, put the resource group to the HA maintenance mode by placing the maintenance file under the following directory:

   %TrafficDataDir%\nmsas\traffic-master\hacluster\<resource_group>

   /var/opt/OV/hacluster/<resource_group>

2. Stop the Master Collector by running the following command:

   nmstrafficmasterstop.ovpl --HA

3. Run the following command:

   encrypttrafficpasswd.ovpl --nnmEncrypt=<web_service_password>

   In this instance, <web_service_password> is the password of the web service user that you used while installing the HPE NNMi Extension for iSPI Performance for Traffic.

4. Open nnm.extended.properties file with a text editor from the following location:

   %NnmDataDir%\nmsas\traffic-master\conf

   /var/opt/OV/nmsas/traffic-master/conf

5. Copy the value of the property com.hp.ov.nms.spi.traffic-master.Nnm.password.

6. Paste this value against the property com.hp.ov.nms.spi.traffic-master.Nnm.password in the nnm.extended.properties file that is available in the following location:

   %HA_MOUNT_POINT%\TRAFFIC\dataDir\nmsas\traffic-master\conf

   $HA_MOUNT_POINT/TRAFFIC/dataDir/nmsas/traffic-master/conf

On the passive node, do this:

Put the Master Collector resource group to the HA maintenance mode by placing the maintenance file under the following directory:

%TrafficDataDir%\nmsas\traffic-master\hacluster\<resource_group>

/var/opt/OV/hacluster/<resource_group>

To upgrade the Master Collector to 10.30 on this server, log on to the system as rootadministrator, and then follow these steps:

1. Go to the Traffic_Master directory on the media.

2. Run the following command:

   ./setupsetup.bat

   The installation wizard opens.

3. Click Next on the Installation (Upgrade) screen. The License Agreement screen appears.
4. Select I accept the terms.., and then click Next. The screen opens.
5. On the Product Customization screen, click Next. The Preinstall Summary screen appears.

6. On the Preinstall Summary screen, click Upgrade.

   The Choose Java JDK dialog box opens.

   The NNM iSPI Performance for Traffic10.30 installer removes the JDK that was installed on the system by the previous version of the installer provides an option to install OpenJDK 1.8. You can select the Install bundled OpenJDK option to install OpenJDK 1.8 that is embedded with the NNM iSPI Performance for Traffic 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 JDK is installed, run one of the following commands:

   whereis java

   which java

   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.

7. After the upgrade is complete, click Done.

   Note: For Red Hat Enterprise Linux. After upgrading the Master Collector to the version 10.30, you can upgrade the operating system of this server to Red Hat Enterprise Linux 7.x.

To upgrade the Leaf Collector to 10.30 on this server, log on to the system as rootadministrator, and then follow these steps:

1. Go to the Traffic_Leaf directory on the media.

2. Run the following command:

   ./setupsetup.bat

   The installation wizard opens.

3. Click Next on the Installation (Upgrade) screen. The License Agreement screen appears.
4. Select I accept the terms.., and then click Next. The screen opens.
5. On the Product Customization screen, click Next. The Preinstall Summary screen appears.

6. On the Preinstall Summary screen, click Upgrade.

   The Choose Java JDK dialog box opens.

   Note: The dialog box does not appear when the Leaf Collector is installed on the NNMi management server. If the Leaf Collector is installed on the management server, skip to the next step.

   The NNM iSPI Performance for Traffic10.30 installer removes the JDK that was installed on the system by the previous version of the installer provides an option to install OpenJDK 1.8. You can select the Install bundled OpenJDK option to install OpenJDK 1.8 that is embedded with the NNM iSPI Performance for Traffic 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 JDK is installed, run one of the following commands:

   whereis java

   which java

   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.

7. After the upgrade is complete, click Done.

On the NNMi management server, run the nnmenableperfspi.ovpl script. While running the script, make sure the specified details match the details provided during the NPS upgrade.

You can find these details specified during the last run of the nnmenableperfspi.ovpl file in the following file on the NNMi management server:

%nnmdatadir%\log\nnmenableperfspi.txt

/var/opt/OV/log/nnmenableperfspi.txt

You can now start the ETL process on the NPS system by running the following command:

startETL.ovpl

Most of the installationupgrade errors that you encounter, relate to incorrect installation configuration settings. Before you start working with the NNM iSPI Performance for Traffic, open the Installation Verification form from the NNM iSPI Performance for Traffic Configuration form, and then validate the configuration settings you set up while installingupgrading the NNM iSPI Performance for Traffic.

For details on how to resolve the installationupgrade errors, see the following troubleshooting scenarios and tips to resolve these issues.

The dashboard panels and analysis panes of the NNM iSPI Performance for Traffic do not show any data

Solution:

This problem occurs when NPS is configured to use a non-default port.

To resolve this problem, follow these steps:

1. Log on to the Master Collector system.

2. Open the following file with a text editor:

   /var/opt/OV/nmsas/traffic-master/conf/nps.extended.properties

   %nnmdatadir%\nmsas\traffic-master\conf\nps.extended.properties

3. Set the com.hp.ov.nms.spi.traffic-master.nps.sdk.port property to the correct value (the current NPS port).

4. Restart the Master Collector by running the following commands:

   /opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl

   /opt/OV/traffic-master/bin/nmstrafficmasterstart.ovpl

   %nnminstalldir%\traffic-master\bin\nmstrafficmasterstop.ovpl

   %nnminstalldir%\traffic-master\bin\nmstrafficmasterstart.ovpl

An error occurs during the Leaf Collector installation

Cause: A failure in any or all of the NNM iSPI Performance for Traffic installer tasks can lead to unsuccessful installation:

• Encryption of user password
• Creating a postgres user
• Changing the permissions of the following directories:
  • %NnmInstallDir%\nonOV\Postgres\bin
  • %NnmDataDir%\shared\nnm\databases\postgres
  • /opt/OV/nonOV/Postgres/bin
  • /var/opt/OV/shared/nnm/databases/postgres

Solution:

Make sure that you are running the NNM iSPI Performance for Traffic installer with administrative privileges. The user with administrative privileges must be part of Local administrator group.

Make sure that you are running the NNM iSPI Performance for Traffic installer with root provileges.

Not able to start nmsdbmgr on the Windows Management Server

Solution:

This may happen occasionally if the Master Collector and Leaf Collector processes were running when ovstop -c was issued. Go to Task Manager, search for nmsdbmgr.exe, and then manually end the process. Make sure that the Master Collector and Leaf Collector processes are not running. Restart NNMi after this operation.

The NNM iSPI Performance for TrafficLeaf Collector does not start

Cause: Cause can be any one of the following:

• Starting the NNM iSPI Performance for TrafficLeaf Collector with user account that does not belong to Administrator group.
• The NNM iSPI Performance for TrafficLeaf Collector ports have already been used
• PostgreSQL is running

• Running instances of Network Performance Server on the Leaf Collector system

• The \etc\hosts file does not contain the physical IP address, FQDN, and hostname entries on the Leaf Collector system.
• The /etc/hosts file does not contain the physical IP address, FQDN, and hostname entries on the Leaf Collector system.

Solution:

• Start the Leaf Collector with user account that belongs to the Local administrator group.
• The default Leaf Collector ports are available in the server.properties file in the following directory:

  %NnmInstallDir%\traffic-leaf\server\

  or

  %TrafficInstallDir%\traffic-leaf\server\

  /opt/OV/traffic-leaf/server/

  Check the file and make sure that the default ports are available.

  Check the jbossServer.log file for the Leaf Collector available in the following directory to see if there was any problem in starting the Leaf Collector:

  %NnmDataDir%\log\traffic-leaf

  or

  %TrafficDataDir%\log\traffic-leaf

  /var/opt/OV/log/traffic-leaf

  You can also look for following message: Bind Exception: Port is in use in the log file to identify if the used port numbers are causing an issue.

  Check the Windows Task Manager and make sure that postgres.exe is running. If you do not find the running process of postgres.exe, you can start the NNM iSPI Performance for TrafficLeaf Collector again.

  Run the command ps -aef | grep postgres. If no postgres install is running, follow these steps:

  • Shutdown the Leaf Collector processes.
  • Start postgres manually by running the command: /etc/init.d/HPSwNnmiSPIPgSql start
  • Start the Leaf Collector processes.

  Check that the Oracle database instance that is configured for use by the Leaf Collector is available and the user configuration is correct.

• If NPS is installed on the same system where you have installed the Leaf Collector, stop any running instances of NPS. You can restart the NPS instance after starting the Leaf Collector.

  Running NPS instances on the same system where you installed the Leaf Collector may increase the load on the system. Therefore, you may require additional system resources, such as CPU, memory, and disk space.

• Log on to the Leaf Collector system and open the following file using a text editor:

  <drive>:\windows\System32\drivers\hosts\etc

  /etc/hosts

  Add the physical IP address, FQDN, and hostname entries to the hosts file using the following syntax:

  physical IP address                    FQDN                    hostname

  For example, the Leaf Collector system with physical IP address 192.168.0.1 and FQDN name trfleaf.mydomain.com should have the following entry in the hosts file:

  127.0.0.1               localhost.localdomain               localhost

  192.168.0.1             trfleaf.mydomain.com                trfleaf

  Make sure that the loopback IP address (For example, 127.0.0.1) is not mapped to the physical FQDN (For example, trfleaf.mydomain.com).

The NNM iSPI Performance for TrafficMaster Collector does not start

Cause: Cause can be any one of the following:

• Starting Master Collector with user account that does not belong to Local administrator group.
• The Master Collector ports have already been used
• Make sure that you have run nmstrafficmastersetuser.ovpl
• PostgreSQL is not running
• Running instances of Network Performance Server on the Master Collector system
• The C:\windows\System32\drivers\etc\hosts file does not contain the physical IP address, FQDN, and hostname entries on the Master Collector system.
• The /etc/hosts file does not contain the physical IP address, FQDN, and hostname entries on the Master Collector system.

Solution:

• Start the Master Collector with user account that belongs to the Local administrator group.
• The default Master Collector ports are available in the server.properties file in the following directory:

  %NnmInstallDir%\traffic-master\server\

  or

  %TrafficInstallDir%\traffic-master\server\

  /opt/OV/traffic-master/server/

  Check the file and make sure that the default ports are available.

  Check the jbossServer.log file for the Master Collector available in the following directory to see if there was any problem in starting the NNM iSPI Performance for TrafficMaster Collector:

  %NnmDataDir%\log\traffic-master

  or

  %TrafficDataDir%\log\traffic-master

  /var/opt/OV/log/traffic-master

  You can also look for following message: Bind Exception: Port is in use in the log file to identify if the used port numbers are causing an issue.

• If NNMi is not installed on the same system where the Master Collector is installed, check if postgres is running.

  Check the Windows Task Manager and make sure that postgres.exe is running. If you do not find the running process of postgres.exe, start the NNM iSPI Performance for TrafficLeaf Collector again.

  Run ps -aef | grep postgres. If no postgres install is running, follow these steps:

  • Shutdown Master Collector processes.
  • Start postgres manually by running the command: /etc/init.d/HPSwNnmiSPIPgSql start
  • Start Master Collector processes.
• If NPS is installed on the same system where you have installed the Master Collector, stop any running instances of NPS. You can restart the NPS instance after starting the Master Collector.

  Running NPS instances on the same system where you installed the Master Collector may increase the load on the system. Therefore, you may require additional system resources, such as CPU, memory, and disk space.

• Log on to the Master Collector system and open the following file using a text editor:

  C:\windows\System32\drivers\etc\hosts

  /etc/hosts

  Add the physical IP address, FQDN, and hostname entries to the hosts file using the following syntax:

  physical IP address                    FQDN                    hostname

  For example, the Master Collector system with physical IP address 192.168.0.1 and FQDN name trfleaf.mydomain.com should have the following entry in the hosts file:

  127.0.0.1               localhost.localdomain               localhost

  192.168.0.1             trfmaster.mydomain.com              trfmaster

  Make sure that the loopback IP address (For example, 127.0.0.1) is not mapped to the physical FQDN (For example, trfmaster.mydomain.com).

The NNM iSPI Performance for Traffic Configuration form link does not launch the form

Solution:

• Make sure that the NNMi processes are running.
• Restart NNMi’s processes by running the following commands:
  • ovstop -c ovjboss
  • ovstart -c

  You can also select Start > All Programs > HP > Network Node Manager > ovstop / ovstart.

• Check the status of the Master Collector by running the nmstrafficmasterstatus.ovpl command available in the following directory:

  %NnmInstallDir%\traffic-master\bin\

  or

  %TrafficInstallDir%\traffic-master\bin\

  /opt/OV/traffic-master/bin/

  Make sure that the status of the Master Collector is RUNNING.

• Check the URL used to launch the Configuration UI. This URL must point to the Fully qualified Domain name of the Master Collector.
• Log on to the NNMi console again with new browser session and launch the NNM iSPI Performance for Traffic Configuration Form URL.
• Check that NNMi was restarted after the installation of the NNMi Extension for iSPI Performance for Traffic.
• Check the log files for the Master Collector available at the following location to see if there were any problems in starting the Master Collector:

  %NnmDataDir%\log\traffic-master

  or

  %TrafficDataDir%\log\traffic-master

  /var/opt/OV/log/traffic-master

• Make sure that you are using the supported version of the Web browser application. For more information, see NNMi Ultimate Support Matrix.

The nmstrafficmasterstop.ovpl command cannot stop the Master Collector

Solution:

Follow these steps to stop the Master Collector:

1. Retrieve the PID from the ps listing using the following command:

   ps -aef | grep traffic-master

2. Stop the Master Collector using the following command:

   kill -9 <PID>

3. Run the services.msc command to open the Services window.
4. Select and open the NNM iSPI Performance for Traffic Master service.
5. Click Stop.

Most of the upgrade errors that you encounter, relate to incorrect installation configuration settings. Before you start working with the NNM iSPI Performance for Traffic, open Installation Verification form from the NNM iSPI Performance for Traffic Configuration form and validate the configuration settings you set up while installing the NNM iSPI Performance for Traffic.

While uninstalling NNM iSPI Performance for Traffic, you must uninstall each component of the software separately.

Uninstalling NNMi Extension for iSPI Performance for Traffic

To remove the NNMi Extension for iSPI Performance for Traffic, follow these steps:

1. On the NNMi management server, go to the following directory:

   %NnmInstallDir%\Uninstall\HPOvTENM

   /opt/OV/Uninstall/HPOvTENM

1. Double-click the setup file.
   The uninstallation initialization process prompts you to choose the language you want to use. The installer then initializes the uninstallation process. The Application Maintenance page opens.
2. Run the command ./setup.
   The installer starts uninstalling the NNMi Extension for iSPI Performance for Traffic.
3. Select Uninstall and then click Next. The Pre-Uninstall Summary page opens.
4. Click Uninstall. The installer starts uninstalling the NNMi Extension for iSPI Performance for Traffic.
5. During uninstallation, Deregistering the NNMi Extension for iSPI Performance for Traffic dialog box opens. In this dialog box, specify the following details, and then click OK:
   • NNMi User Password: Type the password of the NNMi system account.
   • Retype Password: Type the password again.
6. The following details are automatically detected by the installer:
   • NNMi User Name: The NNMi system user.
   • NNMi FQDN: The Fully Qualified Domain Name of the NNMi management server.
   • NNMi JNDI Port: The JNDI port of the NNMi management server.
7. After completing the uninstallation process, the installer opens the Uninstall Complete page. Click Done.

Uninstallation Log Files

Uninstalling the Master Collector

To remove the Master Collector, follow these steps:

1. On the Master Collector system, go to the following location:

   %NnmInstallDir%\traffic-master\Uninstall\HPOvTRMiSPI

   or

   %TrafficInstallDir%\traffic-master\Uninstall\HPOvTRMiSPI

   /opt/OV/traffic-master/Uninstall/HPOvTRMiSPI

2. Double-click the setup file.
3. Run the following command:

   ./setup

4. Follow the on-screen instructions.

After uninstalling the Master Collector, you must uninstall the NNM iSPI Performance for Traffic report extension packs manually.

To uninstall the NNM iSPI Performance for Traffic report extension packs manually, follow these steps:

1. Log on to the system where NPS is running.
2. Go to the following directory:

   <NPS_Install_Dir>\NNMPerformanceSPI\bin

   In this instance, <NPS_Install_Dir> is the installation directory of the NPS.

   /opt/OV/NNMPerformanceSPI/bin

3. Use the command statusALL.ovpl to make sure that all the processes are running.
4. Uninstall the NNM iSPI Performance for Traffic report extension packs by running the following commands:

   uninstallExtensionPack.ovpl -p Interface_Traffic

   uninstallExtensionPack.ovpl -p Interface_Traffic_Aggregated

   uninstallExtensionPack.ovpl -p Interface_Traffic_1_min

5. Remove the iSPI Traffic directory manually.
   To remove the iSPI Traffic directory, follow these steps:
   1. Log on to the NNMi Console.
   2. Click Actions-HPE NNM iSPI Performance-Reporting - Report Menu. The NPS home page opens.
   3. Click BI Server workspace and click Public Folders. The iSPI Traffic directory appears in the HPE NNM iSPI Performance BI Portal.

      Note: If the iSPI Traffic folder does not appear, log on as an Administrator and click My home under My Content area.

   4. Select iSPI Traffic.
   5. Click More Actions for iSPI Traffic in the Actions column. Perform an action - iSPI Traffic form opens.
   6. Click Delete.
6. Navigate to the following shared directory on the NNMi management server:

   %NnmDataDir%/shared/perfSpi/datafiles/extension/final

   /var/opt/OV/shared/perfSpi/datafiles/extension/final

7. Delete the following files manually from the shared directory on the NNMi management server:
   • Interface_Traffic_1_min.tar.gz
   • Interface_Traffic_1_min.tar.gz.processed
   • Interface_Traffic_Aggregated.tar.gz
   • Interface_Traffic_Aggregated.tar.gz.processed
   • Interface_Traffic.gz
   • Interface_Traffic.tar.gz.processed

     Note: The Interface_Traffic_1_min.tar.gz and Interface_Traffic_1_min.tar.gz.processed files are available only if the Interface Traffic_1_min reports are enabled.

Uninstalling the Leaf Collector

To remove the Leaf Collector, follow these steps:

1. On the Leaf Collector system, go to the following directory:

   %NnmInstallDir%\traffic-leaf\Uninstall\HPOvTRLiSPI

   or

   %TrafficInstallDir%\traffic-leaf\Uninstall\HPOvTRLiSPI

   /opt/OV/traffic-leaf/Uninstall/HPOvTRLiSPI

2. Double-click the setup file.
3. Run the command ./setup.
4. The uninstallation initialization process prompts you to choose the language you want to use. The installer then initializes the uninstallation process.
5. On the Application Maintenance page, select Uninstall and then click Next. The Pre-Uninstall Summary page opens.
6. Click Uninstall.
7. After completing the uninstallation process, the installer opens the Uninstall Complete page. Click Done.