HP Network Node Manager i Smart Plug-in Performance for Metrics Software
System and Device Support Matrix

Software Version: 9.20

Introduction
Hardware and Software Requirements
Same Server Install
Dedicated Server Install
Hardware
Operating System
Web Browser
Legal Notices

Introduction

This document describes system requirements for the HP Network Node Manager iSPI Performance for Metrics (iSPI Performance for Metrics) version 9.20 and Network Performance Server (NPS) version 9.20.

NPS stores, aggregates, and provides reports for collected performance data. It is the foundation for operational reports on NNMi. Other iSPIs rely on NPS for report presentation functionality. The iSPI Performance for Metrics adds the performance management capability to NNMi by analyzing, processing, and aggregating a range of standard metrics collected by NNMi from different network elements.

This document provides information about supported deployment configurations that is not found in the Release Notes or the Installation Guide. When you are ready to install the product, refer to the Installation Guide. The Installation Guide is provided in PDF format on the installation media. When you install NPS, the Installation Guide is copied to the Docs directory.

Hardware and Software Requirements

You can install NPS on a dedicated system, separate from NNMi, or you can install it on the same system as NNMi. Before installing NPS and your iSPIs, make sure that your system meets the following minimum requirements. Be aware of the following:

·         If you are upgrading from a version 9.00 or 9.10 installation of iSPI Performance for Metrics, check the hardware tables below for the latest requirements and see the Installation Guide for instructions and available upgrade paths.

·         The data directory (NNMDataDir) will contain the bulk of the collected and aggregated data and should be on the fastest and largest disk partition. For UNIX platforms, this will be /var/opt/OV.

·         By default, NPS stores daily aggregated data for 800 days, hourly aggregated data for 70 days, and very fine grain, as collected, data for 14 days. The retention periods for hourly and fine grain data can be increased to a maximum of 400 days. Most of the required disk space for the iSPI is consumed by this fine grain data storage. To change retention periods from the default, use the Configuration utility. You can modify the settings for each of the storage areas independently, but fine grain data cannot be stored for longer than hourly data, which in turn cannot be stored for longer than daily data. Care should be taken to monitor the disk space usage on the system after a change to these parameters. The tables below quote disk space requirements for an out-of-the-box system as well as one with retention at the maximum.

·         These hardware recommendations are a guideline only, based on the use of the iSPI Performance for Metrics package. They do not take account of additional factors that may affect the sizing of your application, such as the installation of the iSPI Performance for Traffic, or additional custom collection reporting that may be configured after installation. Every installed package using NPS for reporting, and every custom collection with reporting enabled, will require additional disk and processing capacity on the NPS system.

·         NPS 9.20 does not support the application failover feature. However, you can use NPS with an NNMi management server that has been configured for application failover. If the NNMi management server is configured for application failover, you must install NPS on a dedicated server (and not on the NNMi management server).

·         NNMi has the ability to discover topology elements such as nodes and interfaces, but not all discovered elements will have performance data collected and reported on. The numbers quoted below relate only to performance polled elements.

·         The figures in the tables below quote hardware requirements for an NPS running with a 5-minute polling frequency. The number of polled interfaces and components is stated for each scale. Example: 130k/130k means 130,000 interfaces and 130,000 component sensors simultaneously.

    Higher polling frequencies will result in more data. So 400K interfaces at 5 minutes results in the same number of collected data points as 80K interfaces at 1-minute polling frequency.

    Custom, user-defined collections will result in additional storage requirements.

    Adding other iSPIs to your platform, such as iSPI Performance for Quality Assurance, iSPI for IP Telephony, or iSPI for MPLS, will result in additional storage and processing requirements for NPS.

    Monitor disk usage and processing performance on the system on a daily basis after introducing a new custom collection or iSPI.

Same Server Install (NNMi and NPS on the Same System)

The following table outlines the requirements for CPU, RAM and disk space when NNMi and NPS are on the same system. The CPU, RAM, and Disk figures represent the total requirements for the system and include the combined capacity required for NNMi and NPS. You must make sure that this host also meets any additional criteria defined in the NNMi support matrix.

Be aware of the following:

·         When NPS is installed on a system that hosts NNMi, half of the system RAM will be consumed by NPS. The figures below for RAM resources take account of the combined needs of NNMi and NPS, and are especially important when running NPS with several iSPIs providing data.

·         Once NPS is installed, you can use the Managed Inventory report to see the variety of collected elements for each iSPI. For example, looking at the count of distinct Qualified Interface Names in the Interface Health Managed Inventory report will tell you how many unique interfaces have had performance data collected within the selected time period.

·         Although it is a supported option to have NNMi and NPS on the same system for "Large" scale environments, HP recommends that NPS be installed on a separate, standalone system.

·         HP does not support NPS's being installed on the same server as NNMi for "Very Large" scale environments.

Management Environment Size

 

NNMi + iSPI Minimum System Requirements

 

Approximate managed environment tier

Number of
performance polled
interfaces/components
at
5-minute
polling interval

Number of
concurrent users

CPU (64-bit)
x86-64
AMD64

RAM

Disk space
for
application installation (NNMInstallDir)

Disk hardware
required
for
NNMDataDir

Additional disk space
for
database and data
during execution (NNMDataDir)
14-day raw/detailed retention,
70-day hourly retention,
800-day daily retention

Additional disk space
for
database and data
during execution (NNMDataDir)
70-day raw/detailed retention,
70-day hourly retention,
800-day daily retention

Additional disk space
for
database and data
during execution (NNMDataDir)
70-day raw/detailed retention,
70-day hourly retention,
800-day daily retention

Entry

Up to 2500

5

8 CPU (2.5GHz for x64)

16 GB

15 GB

1 SCSI or SATA disk drive

200 GB

300 GB

300 GB

Small

Up to 10K/10K

10

8 CPU (2.5GHz for x64)

16 GB

15 GB

1 SCSI or SATA disk drive

300 GB

400 GB

1 TB

Medium

Up to 50K/50K

25

8 CPU (2.5GHz for x64)

32 GB

15 GB

RAID 1+0 or 5/6 with write cache recommended

800 GB

1.5 TB

4 TB

Large

Up to 130K/130K

40

16 CPU (2.5GHz for x64)

64 GB

15 GB

High performance SAN storage

2 TB

3 TB

10 TB

Very Large

Same server install
not supported
for this scale

--

--

--

 

--

--

 

 

Dedicated Server Install

If you plan on installing NPS on a separate machine from NNMi, make sure that the following criteria are met. Note that NPS sizing requirements are driven by the amount of data generated by the custom collections and iSPIs that will supply it. The references provided in this document for sizing and scalability are a guideline only and are based on the iSPI Performance for Metrics using the number of interfaces and node components that NNMi is polling for performance data. The total number of interfaces or components discovered by NNMi is not relevant for this system.

iSPI Minimum System Requirements

Management Environment Size

 

iSPI Minimum System Requirements

Approximate managed environment tier

Number of performance polled interfaces / components at 5 minute polling interval

Number of concurrent users

CPU (64-bit)
x86-64

AMD64

RAM

Disk space for
Application installation (NNMInstallDir)
 

Disk space for database and data during execution (NNMDataDir)

Disk space for database and data during execution (NNMDataDir)

14 day raw/detailed retention,

70 day hourly retention

800 day daily retention

 

Disk space for database and data during execution (NNMDataDir)

70 day raw/detailed retention

70 day hourly retention

800 day daily retention

Disk space for database and data during execution (NNMDataDir)

70 day raw/detailed retention

400 day hourly retention

800 day daily retention

Small

Up to 5K/5K

10

8 CPU (2.5GHz for x64)

16 GB

10 GB

1 SCSI or SATA disk drive

300 GB

400 GB

1 TB

Medium

Up to 60K/60K

25

8 CPU (2.5GHz for x64)

24 GB

10 GB

RAID 1+0 or 5/6 with write cache recommended

800 GB

1.5 TB

4 TB

Large

Up to 130K/130K

40

16 CPU (2.5GHz for x64)

48 GB

10 GB

RAID 1+0 or 5/6 with write cache recommended

2 TB

3 TB

10 TB

Very Large

Up to 400K/200K

40

16 CPU (2.5GHz for x64)

72 GB

10 GB

High performance SAN storage

4 TB

8 TB

20 TB

Virtualization

·         VMware ESX Server 4.0 or later minor version, ESXi 4.1 or later minor version, ESXi 5.0 or later minor version.

·  Only supported for the Windows or Linux operating systems.

·   Virtual environment must meet the x86-64 or AMD64 hardware requirements listed here.

Hardware

·         Intel 64-bit (x86-64) or AMD 64-bit (AMD64)

o    Only supported for the Windows or Linux operating systems.

o    For Intel 64-bit (x86-64), the following Xeon processor families are recommended: Penryn, Nehalem, Westmere, and Sandy Bridge.

o    For AMD 64-bit (AMD64), the following Opteron processor families are recommended: Istanbul, Lisbon, and Valencia.

o    Caution: Intel 32-bit (x86) hardware is not supported. Verify your computer architecture by looking at the %PROCESSOR_ARCHITECTURE% variable or System Properties.

·         Itanium Processor Family

o    Caution: IPF hardware running the Windows or Linux operating system is not supported

·         Virtual Memory/Swap Space

o    Recommend 2 times physical memory and at least 32 GB

o    Windows: Verify virtual memory via System Properties

o    Linux: To verify, use the cat /proc/meminfo | grep Swap command. To adjust, use the parted and mkswap commands.

Networking Configuration of the NPS Server

·         Pure IPv6 is not supported, but dual stack IPv6 and IPv4 combined is supported.

Operating Systems

Windows

Supported Versions

·         Windows Server 2008 x64 Datacenter Edition with Service Pack 2

·         Windows Server 2008 R2 x64 Datacenter Edition with Service Pack 1

·         Windows Server 2008 x64 Enterprise Edition with Service Pack 2

·         Windows Server 2008 R2 x64 Enterprise Edition with Service Pack 1

·         Windows Server 2008 x64 Standard Edition with Service Pack 2

·         Windows Server 2008 R2 x64 Standard Edition with Service Pack 1

Notes:

·         Windows 32-bit operating systems are not supported

·         Windows operating systems on Itanium Processor Family (IPF) are not supported

Please be aware of the following:

·         Anti-virus and backup software can interfere with the operation of NPS if the software locks files while NPS is running. Any application that locks files should be configured to exclude the NPS install and data directories (C:\ProgramData\HP\HP BTO Software\NNMPerformanceSPI).

·         Windows 2008 includes the concept of User Access Control (UAC). Users who are part of the Administrator group may not have full Administrator privileges. All scripts and commands associated with NPS will detect and warn if the user is not elevated. They should be run with full Administrator access. To achieve this, right-click on the Command Tool icon and choose ‘Run as Administrator.’

Linux

·         Red Hat

§  Red Hat Enterprise Linux Server 6.0 (or later minor version through 6.2)

§  Red Hat Enterprise Linux Server 5.4 (or later minor version through 5.x)

§  NOTE: Red Hat 5.5 or later is required for CPU chips with more than 4 cores on a single chip. (Do not confuse this number with the total number of cores; this number is just the cores per chip.)

 NNMi and NPS Combinations

This table illustrates the combinations of operating systems that are supported with NPS in a distributed installation environment. Note that NPS version 9.20 should always be used at the same version level as NNMi.

 

NPS

Windows

Linux

NNMi

Windows

Yes No

Linux

Yes Yes

HPUX

Yes Yes

Solaris

Yes Yes

High Availability

NPS and the iSPI Performance for Metrics can run on the following high availability systems with additional configuration. See the Installation Guide for further details on how to configure NPS with high availability systems:

·         Microsoft:

o    Microsoft Failover Clustering for Windows Server 2008

·         Linux

o    Veritas Cluster Server (VCS) version 5.0 or 5.1

Notes

 Some disk types require the use of Veritas Storage Foundation (VSF) version 5.0 or 5.1.

 VCS 5.1 and VSF 5.1 require Linux 5.4 or later and might require operating system patches. For specific information, see the appropriate Veritas product documentation.

Web Browser

o    Disable all pop-up window blockers for the browser (see instructions on the NNMi console sign-in page or in the Installation Guide).

o    Enable cookies for the browser (see instructions on the NNMi console sign-in page or in the Installation Guide).

o    Enable JavaScript for the browser.

o    The resolution of the client display should be at least 1024x768.

§  Caution: The following browsers are not supported:

o    Microsoft Internet Explorer version 8 or version 9 when running in Compatibility View mode
Be sure to disable Compatibility View in Internet Explorer using
Tools → Compatibility View Settings (clear all check boxes).

o    Microsoft Internet Explorer version 7
Internet Explorer 7 (or Internet Explorer in Compatibility View mode) has many known issues, including many layout issues, no ability to close the
Help → System Information window, and inability to change selections for CSV export.

o    Microsoft Internet Explorer version 6

o    Mozilla Firefox 3.6.x through 9.x

o    Mozilla Firefox 11.0 and other non-ESR versions of Firefox.

o    Apple Safari (all versions)

o    Opera (all versions)

o    Google™ Chrome (all versions)

      Supported Web Browsers on a Remote Client System (for operational use)

§  Microsoft Internet Explorer (32-bit and 64-bit) version 8 (not running in Compatibility View mode).

§  Microsoft Internet Explorer (32-bit and 64-bit) version 9 (not running in Compatibility View mode).

§  Mozilla Firefox version 10.x ESR on a Windows or Linux client. The Firefox ESR (Extended Support Release) browser is available from http://www.mozilla.org/firefox/organizations/all.html. The Firefox browser works best if new windows are opened as separate windows, not tabs. For information, see Mozilla Firefox Known Problems in the NNMi Release Notes.

Integration and Coexistence with Other Products

The following products have been tested to coexist on the same system as NPS 9.20:

·         HP Network Node Manager i 9.20 Software

·         HP Network Node Manager i Advanced 9.20 Software

·         HP Network Node Manager iSPI Performance for Traffic 9.20 Software

·         HP Network Node Manager iSPI Performance for Quality Assurance 9.20 Software

·         HP Network Node Manager iSPI Performance for Metrics 9.20 Software

·         HP Network Node Manager iSPI for IP Multicast 9.20 Software

·         HP Network Node Manager iSPI for IP Telephony Software version 9.20

·         HP Network Node Manager iSPI for MPLS Software version 9.20

·         HP Operations Agent version 11.03 (Note: When upgrading systems running older versions of HP Operations / OM Agent, upgrade to HP Operations Agent 11.03 before upgrading to NPS 9.20.)

Integration with Performance Insight

Check with Support regarding the integration between Performance Insight and NPS version 9.20.

Legal Notices

©Copyright 2009-2012 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

For information about third-party license agreements, see the license-agreements directory on the product installation DVD-ROM.

To view open source code, see the license-agreements/source and license-agreements/CygwinSources directories on the product installation media.

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.
Java is a registered trademark of Oracle and/or its affiliates.
Microsoft®, Windows® and Windows® XP are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.

Acknowledgements

This product includes: