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

for the Windows® and Linux Operating Systems

Software Version: 10.00/ July 2014

Publication Date: June 2015

For the latest additions to the system requirements and support matrix, see http://support.openview.hp.com/selfsolve/document/KM00940856/binary/nnm_ispi_Traffic_SupportMatrix_10.00.html.

This document provides an overview of the system requirements for the HP Network Node Manager iSPI Performance for Traffic Software (NNM iSPI Performance for Traffic) version 10.00.

This document is intended to augment the Release Notes. You can find both the Support Matrix and the Release Notes at the root directory of the installation media.

You can find information about the following in this document:

Installation Notes
Hardware and Software Requirements
   Hardware
      CPU, RAM, and Disk Space Requirements / Maximum Supported Managed Environment
   Operating System
Virtual Memory / Swap Space
Supported IP Flow Export Formats
High Availability
   Database
   Web Browser
   Internationalization and Localization Support
Legal Notices

Installation Notes

Installation requirements, as well as instructions for installing NNM iSPI Performance for Traffic, are documented in an interactive version of the NNM iSPI Performance for Traffic Interactive Installation Guide. The NNM iSPI Performance for Traffic Interactive Installation Guide is included on the NNM iSPI Performance for Traffic media as traffic_interactive_installation_en.zip file. For instructions explaining how to extract and view the NNM iSPI Performance for Traffic Interactive Installation Guide, see the traffic_interactive_installation_en_README.txt file located at the root of the NNM iSPI Performance for Traffic installation media.

Hardware and Software Requirements

Before installing the NNM iSPI Performance for Traffic, make sure that your system meets the following minimum requirements:

Hardware

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

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

Below are the different tiers of managed network environments and the hardware required by the NNM iSPI Performance for Traffic for supporting these environments. Managed environments bigger than the large tier are not supported without additional HP approval. You can also refer to NNMi Support Matrix.

Note:

If the NNM iSPI Performance for Traffic components are installed on (or share the disk space with) a system where NNMi or the NNM iSPI Performance for Metrics is installed, the system requirements provided in this Support matrix is in addition to the specified system requirements in the support matrices for NNMi and the NNM iSPI Performance for Metrics.

Table 1 lists the hardware resource requirements for the NNM iSPI Performance for Traffic Master Collector component. The key factor considered for sizing is the total number of flow records per minute in the entire managed environment, that is, the sum of the traffic flow records per minute and the total number of interfaces that are being used by all the routers in the environment to export flows.

Note: Disable the data generation for the Interface Traffic reports in medium and large tiers for optimum performance. For steps to disable the data generation for the Interface Traffic report, refer to Disabling Data Generation for the Interface Traffic Reports section in the NNM iSPI Performance for Traffic Deployment Reference document. Interface Traffic Data is supported for up to 480k unique flow records per minute (600k flow records per minute with 80% uniqueness distributed across two Leaf Collectors) at the Master Collector.

Managed Environment Size NNM iSPI Performance for Traffic Master Collector Minimum Hardware System Requirements
Approximate managed environment tier

Flow records per minute
(Maximum)

Number of Flow-Exporting Interfaces (Maximum) Recommended Number of Leaf Collector Systems CPU (64-bit) x86-64/AMD64 RAM -Xmx

Disk space for application installation (<Traffic InstallDir>)2

Disk space for data during execution
(<Traffic DataDir>)3

Entry1

60K 50 Master and Leaf Collectors are co-located on the same system 4 CPU cores
(2.5GHz)

6 GB

Leaf: 1.5 GB

Master: 3 GB

1.5 GB 8 GB

Small

250K 200 1 4 CPU cores
(2.5GHz)
8 GB 6 GB 1.5 GB 8 GB

Medium4

1.2M 1000 2 4 CPU cores
(2.5GHz)
16 GB 12 GB 1.5 GB 32 GB

Large4 a

8M 4000 8 8 CPU cores
(2.5GHz)
24 GB 16 GB 1.5 GB 64 GB

a For a flow rate of up to 5M flow records per minute, you can use 5 Leaf Collectors.

Table 2 lists the resource requirements for a single NNM iSPI Performance for Traffic Leaf Collector. The key factor considered for sizing is the total number of flow records per minute being processed by the individual Leaf Collector instance.

Managed Environment Size NNM iSPI Performance for Traffic Leaf Collector Minimum Hardware System Requirements
Approximate managed environment tier

Flow records per minute to the Leaf Collector
(Maximum)

Number of Flow-Exporting Interfaces (Maximum)

CPU (64-bit) x86-64 /AMD64 RAM -Xmx

Disk space for application installation (<Traffic InstallDir>)2

Disk space for data during execution (<Traffic DataDir>)3
Small 250k 200

4 CPU cores
(2.5GHz)

4 GB

(1066 MHz or higher)

3 GB 1.5 GB 8 GB
Medium4 600k 500

4 CPU cores
(2.5GHz)

12 GB

(1066 MHz or higher)

8 GB 1.5 GB 32 GB
Large4 1M 800

8 CPU cores
(2.5GHz)

16 GB

(1066 MHz or higher)

12 GB 1.5 GB 64 GB

Notes:

1 The entry tier specifications assume that the Master and Leaf Collectors are co-located on a single system. The total number of CPUs (4) and memory requirements (6 GB) are the cumulative resource requirements for one Master and one Leaf Collector on the system.

2<TrafficInstallDir> is configured during installation of the NNM iSPI Performance for Traffic (Master Collector or Leaf Collector) on Windows (C:\Program Files (x86)\HP\HP BTO Software by default). You can refer to the NNM iSPI Performance for Traffic Interactive Installation Guide to configure these parameters.

3 <TrafficDataDir> is configured during installation of the NNM iSPI Performance for Traffic (Master Collector or Leaf Collector) on Windows (C:\ProgramData\HP\HP BTO Software by default).

4 In this scenario, disable report data generation for the Interface_Traffic extension pack. For more information, see the NNM iSPI Performance for Traffic Deployment Reference Guide.

Table 3 lists the feature configurations on various scenarios for different managed environment sizes.

Managed Environment Size Feature Configurations on Various Scenarios
Max Site Configurations Max TOS Group Configurations Max Threshold Configurations
Entry 10 5

5

Small 20 5 5
Medium 30 10 10
Large 40 20 20

Note:

Tuning Parameters

Table 4 lists tuning parameter recommendations for different managed environment sizes. See the NNM iSPI Performance for Traffic Deployment Reference Guide for details about how to configure these parameters. FlowRecord and TopN FlowRecord are applicable for the Leaf Collector and Master Queue Size is applicable for the Master Collector.

Note:

Increase in FlowRecord pool size and TopN FlowRecord pool size requires additional memory. For every 100K increase in pool sizes, you must provide additional 100 MB memory. For example, if you increase FlowRecord pool size by 200K and TopN FlowRecord pool size by 500K, you must add additional 700 MB to the Xmx value for Leaf Collector.

The number of flow exporting interfaces also impacts the TopN pool sizes. The following table indicates the object pool size required for the Leaf Collector system and provides general guidelines for an environment that has large number of flow exporting interfaces per tier:

Managed Environment Size Object Pool Size
FlowRecord TopN FlowRecord Master Queue Size
Small 600K 2M 600K
Medium 2M 5M 3M
Large 2.5M 6M 5M

Table 5 lists the resource requirements for the Network Performance Server (NPS) for different managed environment sizes. These requirements are in addition to the requirements for the NPS for the NNM iSPI Performance for Metrics or any other iSPI that is installed. This is significantly affected by the changes in the configured retention period for the data queried by different extension packs.

Managed Environment Size Network Performance Server Minimum Hardware System Requirements
Approximate managed environment tier Total flow record rate CPU (64-bit) x86-64/ AMD64 RAM Disk space for flow record data storage in the Sybase DB (the NPS database)
(<DataDir on the NPS system >)^^
Entry 60K 4 CPU cores
(2.5GHz)
16 GB 1 TB
Small 250K 8 CPU cores
(2.5GHz)
32 GB 2 TB
Medium 1.2M 16 CPU cores
(2.5GHz)
48 GB 5 TB
Large 5M 24 CPU cores
(2.5GHz)
64 GB 12 TB

^^ <NNM iSPI Performance for Metrics DataDir> is configured during installation of iSPI Performance for Metrics on Windows (C:\ProgramData\HP\HP BTO Software by default). To configure the data retention period of the NNM iSPI Performance for Traffic Extension Packs, see the NNM iSPI Performance for Traffic Deployment Reference. If the data archival period for the NNM iSPI Performance for Traffic Extension Packs is set to a high value, ensure that adequate free disk space is available on the system on which you have installed the NNM iSPI Performance for Metrics.

Table 6 lists the retention periods for NNM iSPI Performance for Traffic data for each extension pack:

Note: Changing the default retention periods have a significant impact on the database space usage and NPS performance.

Retention Period for NNM iSPI for Traffic extension packs
Parameter Interface_Traffic Interface_Traffic_1_Minute* Interface_Traffic_Aggregated
PRSPI_DataRetention_Raw 3 days 30 days 400 days

* Not collected by default in NNM iSPI Performance for Traffic 10.00. However, if you had this already enabled in the existing/previous version of NNM iSPI Performance, then it will continue to be collected after upgrading to the NNM iSPI Performance for Traffic 10.00.

Note:

Increasing the tuning parameters for ETL process of NPS to values listed in Table 7, Table 8, and Table 9 results in significant increase in CPU utilization. Make sure that there is sufficient CPU bandwidth available before increasing these parameters.

Table 7 lists the number of child processes for the ETL process of NPS for medium and large tiers of traffic data based on different extension packs.

Number of Child Processes
Approximate managed environment tier Interface_Traffic Interface_Traffic_1_Minute Interface_Traffic_Aggregated
Medium 5 10 10
Large 10 50 20

Table 8 lists the maximum number of records per child process for the ETL process of NPS for medium and large tiers of traffic data based on different extension packs.

Number of Records per Child (max)
Approximate managed environment tier Interface_Traffic Interface_Traffic_1_Minute Interface_Traffic_Aggregated
Medium 100k 100k 100k
Large 100k 200k 200k

Table 9 lists the number of files per batch for the ETL process of NPS for medium and large tiers of traffic data based on different extension packs.

Number of Files per Batch
Approximate managed environment tier Interface_Traffic Interface_Traffic_1_Minute Interface_Traffic_Aggregated
Medium 20 25 20
Large 30 50 30

Operating System

Windows

Notes:

Linux

Linux Kernel Tuning

Flow exporting protocols utilize User Datagram Protocol (UDP) for sending FlowRecord Protocol Data Units (PDUs). The operating system utilizes UDP buffering to match the arrival rate of UDP packets with their consumption rate by the NNM iSPI Performance for Traffic Leaf Collector. To minimize the chances for lost packets, a sufficient amount of memory is required for UDP buffering. The NNM iSPI Performance for Traffic requests 8MB for the UDP receive buffer (for incoming responses). Linux systems typically reserve only 128 KB for this buffer.

To make this change permanent (after a reboot), edit the /etc/sysctl.conf file and add the following entry:

# NNM iSPI Performance for Traffic settings for UDP receive buffer size
net.core.rmem_max = 8388608

Then either reboot the system or run /sbin/sysctl -p to immediately apply the changes without requiring a reboot. If the Leaf Collector processes are running, restart the processes to benefit from these changes.

NNMi and Master/ Leaf Collector Combinations

This table illustrates the supported combinations of operating systems for the NNMi management server and Master/Leaf Collector system:

  Master/Leaf Collector
Windows Linux
NNMi* Windows Supported Not Supported
Linux Supported Supported

* The HP NNMi Extension for iSPI Performance for Traffic must always be installed on the NNMi management server.

Virtual Memory/Swap Space

Supported IP Flow Export Formats

High Availability

The NNM iSPI Performance for Traffic Master Collector alone supports running on a High Availability system. The other components of the NNM iSPI Performance for Traffic does not support running on a high availability system. It can operate in an environment where NNMi is running on high availability systems, as well as where both NNMi and the NNM iSPI Performance for Metrics are running on high availability systems.

See the NNMi Deployment Reference and the NNM iSPI Performance for Traffic Interactive Installation Guide on how to install and configure the NNM iSPI Performance for Traffic for operating with the NNMi iSPI Performance for Metrics in high availability systems. The following configurations are supported on Operating Systems

Database

The database(embedded or Oracle) selection for the NNM iSPI Performance for Traffic should be same as NNMi. The Oracle database instance must be different from NNMi database instance. See the NNM iSPI Performance for Traffic Interactive Installation Guide for more information.

Web Browser

General Web Browser Requirements

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

Supported Web Browser Running on the Local Management Server System (for initial installation and configuration use)

Web Browser Configuration

HP recommends that you do not configure your web browser to use a proxy server. If you configure the web browser to use a proxy server, you may not be able to launch the NNM iSPI Performance for Traffic Configuration form (by clicking the Configuration workspace), release notes (by clicking the Help menu), and the Reference Pages(by clicking the Help menu) from the NNMi console.

Internationalization and Localization Support

The NNM iSPI Performance for Traffic 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.

The NNM iSPI Performance for Traffic is localized (or translated) to French, German, Japanese, Korean, Russian, Simplified Chinese, and Spanish. When those localized packages are installed, French, German, Japanese, Korean, Russian, Simplified Chinese, Spanish are displayed as output. With all other locales, English strings appear as output.

Before using Internet Explorer to access an NNMi management server that is configured to support the Asian Languages, install the East Asian Language with the following procedure:

  1. In the Control Panel, select Regional and Language Options.
  2. On the Languages tab, select Install files for East Asian Languages, and then follow the instructions.

Legal Notices

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

Warranty

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.

Restricted Rights Legend

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.

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

Copyright Notices

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

Trademark Notices

Acrobat® is a trademark of Adobe Systems Incorporated.

Google™ is a trademark of Google Inc.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Java and Oracle are registered trademarks of Oracle Corporation and/or its affiliates.

Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.

sFlow is a registered trademark of InMon Corp.

Acknowledgements

This product includes software developed by the Apache Software Foundation. (http://www.apache.org)

This product includes software developed by the Indiana University Extreme! Lab. (http://www.extreme.indiana.edu)

Oracle Technology — Notice of Restricted Rights

Programs delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

For the full Oracle license text, see the license-agreements directory on the NNMi product DVD.