HP Network Node Manager iSPI for MPLS Software System and Device Support Matrix

Software Version: 9.20/ May 2012

This document provides an overview of the system requirements and supported devices for HP Network Node Manager i Software Smart Plug-in for MPLS version 9.20.

This document is intended to augment the Release Notes. You can find the Support Matrix (MPLS_supportmatrix_en.html) and the Release Notes (MPLS_relnotes_en.html) at the root directory of the installation media.

To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals.

Installation Guide
Hardware and Software Requirements
    Hardware
        CPU, RAM, and Disk Space Requirements / Maximum Supported Managed Environment
       Global Network Management Recommendations
    Operating System
        Windows
        HP-UX
        Linux
        Solaris
      Database
    High Availability
    Web Browser
         Internationalization and Localization Support
Supported Network Devices

Installation Guide

Pre-installation requirements, as well as instructions for installing the NNM iSPI for MPLS, are documented in the installation guide provided in Adobe Acrobat (.pdf) format. The document file is included on the product's installation media as: MPLS_install_guide_en.pdf.

Hardware and Software Requirements

Before installing NNM iSPi for MPLS, verify that your system meets the following minimum requirements:

Hardware

CPU, RAM, and Disk Space Requirements / Maximum Supported Managed Environment

Below are the three tiers of managed network environments and the hardware required by the NNM iSPI for MPLS for supporting these environments. Managed environment bigger than the large tier is not supported without additional hardware resources and HP approval. To tune Java heap size, see the Tuning the jboss Memory.

If you intend to run any of the other NNM iSPIs, please review each iSPI support matrix before determining the hardware you need. Each of the NNMi iSPIs may require additional hardware beyond what NNMi and NNM iSPI for MPLS require. If you are running additional applications, please increase resources appropriately.

Single System Managed Environment Size
(NNM iSPI for MPLS)

Recommended Hardware System Requirements

Approximate
managed
environment
tier

Number of
discovered
VRFs

Number of
discovered
TE Tunnels

Number of
discovered PseudoWire VC
s
Number of Monitored LSPs Preferred NNMi Scale 1 Additional CPUs Additional RAM Recommended Java heap size
(see Tuning the jboss Memory Size)
Database Additional Disk space for database and
data during execution
(<NnmDataDir>)2

Small

Up to 2K

Up to 500

Up to 500

Up to 50

Low

1 CPU core

4GB

Default value

Oracle or PostgreSQL

10 GB

Medium

Up to 8K

500-1000

500-1000

Up to 100

Low or Medium

1 CPU core

8 GB

4 GB

Oracle or PostgreSQL

20 GB

Large

8K-23K

Up to 2K

Up to 2K

Up to 200

Large

2 CPU cores

16 GB

 

8 GB

 

Oracle or PostgreSQL

20 GB

Note: Physical RAM should be twice that of the combined Xmx values of NNMi and the available NNM iSPIs on the management server.

1 For more information about NNMi Scale, see NNMi 9.20 Support Matrix.
2Windows 2008 (C:\ProgramData\HP\HP BTO Software\ by default), or on UNIX /var/opt/OV/.

To calculate the disk space information for MPLS reports, check the number of VRFs. Consider this count of VRFs as the polled objects. Use the number of polled objects sizing information from NPS and iSPI Performance for Metrics Support Matrix. Allocate the same disk space information for the number of MPLS objects (VRF) according to the disk space required for the number of polled objects. For more information about NPS and iSPI Performance for Metrics, see NPS and iSPI Performance for Metrics Support Matrix.

Global Network Management Recommendations

MPLS Global Network Management Environment Size

Recommended Hardware System Requirements for Global Systems

Approximate
managed
environment
tier
Number of
discovered VRFs1

Number of discovered TE Tunnels

Number of
PseudoWires VCs
Number of Monitored LSPs Number of regional managers Additional CPUs Additional RAM Recommended Java heap size (see Tuning the jboss Memory Size) Database Additional Disk space for database and data during execution
(<NnmDataDir>)

Medium Global Manager

Up to 36K

Up to 3K

Up to 3600

Up to 600

Up to 3

4 cores

12 GB

6 GB

Oracle or PostgreSQL

30 GB

Large Global Manager

Up to 96K

Up to 6K

Up to 7200

Up to 1200

Up to 6 8 cores

24 GB or more

8 GB

Oracle or PostgreSQL

40 GB

1 Total number of discovered VRFs in the GNM topology. The count of discovered VRFs include the number of VRFs from all the Regional Managers.


Tuning the jboss Memory

To change the jboss Maximum Java Heap Size (‑Xmx) or other Java Virtual Machine parameters, follow these steps:

1. Stop the NNM iSPI for MPLS process by the following command: ovstop –c mplsjboss

2. Edit the nms-mpls.jvm.properties file:

Windows: C:\ProgramData\All Users\Application Data\HP\HP BTO Software\shared\mpls\conf\nms-mpls.jvm.properties

UNIX: /var/opt/OV/shared/mpls/conf/nms-mpls.jvm.properties

3.Update the Maximum Java Heap Size to the required value. For example, a snippet of the nms-mpls.jvm.properties file appears as:

# JVM Memory parameters
#   ‑Xms: Initial Java Heap Size
#   ‑Xmx: Maximum Java Heap Size
#
‑Xmx2048m
‑Xms1024m

4. Start the NNM iSPI for MPLS processes by the following command: ovstart –c mplsjboss

For more information, see the NNMi Support Matrix, 9.20.

Operating System

Windows

Supported Versions

Notes

HP-UX

Supported Version

Linux

Supported Versions

Solaris

Supported Version

Note

 

Database

The NNM iSPI for MPLS can store its data in an embedded PostgreSQL database or in an external Oracle database. You must choose the database type at installation time.
NOTE: You cannot change the database type after installing the NNM iSPI for MPLS.

High Availability

The NNM iSPI for MPLS can run on certain high availability systems with additional configuration. See NNMi Deployment Reference and NNM iSPI for MPLS Deployment Guide for information on how to install and configure NNMi and NNM iSPI for MPLS in the High Availability environment. The following configurations are supported on NNMi Supported Operating Systems:

Web Browser

Internationalization and Localization Support

The NNM iSPI for MPLS is internationalized and can be used on operating systems configured for non-US-English locales that are supported by the operating systems. Those locales include variants of Japanese, Korean, Simplified Chinese, Traditional Chinese, Western and Central European locales, and Russian.

On Windows systems, NNMi does not support installation using directory paths with localized characters; path names for $NnmInstallDir and $NnmDataDir can contain English characters only.

The NNM iSPI for MPLS, 9.20 is not localized.

Supported Network Devices

The NNM iSPI for MPLS supports the following:

For the latest updates for the NNMi devices, see NNMi Support Matrix, 9.20.