This document provides an overview of the system requirements and supported devices for the HP Network Node Manager iSPI Performance for Traffic Software (NNM iSPI Performance for Traffic) version 9.20.
To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals
This document is intended to augment the Release Notes. You can find both the Support Matrix (Traffic_SupportMatrix_en.html) and the Release Notes (Release_Notes_Traffic_SPI.htm) 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
Support
Legal Notices
Pre-installation requirements, as well as instructions for installing NNM iSPI Performance for Traffic, are documented in the installation guide provided in Adobe Acrobat® (.pdf) format. The document file is included in the root directory on the product's installation media as: Traffic_spi_installation_en.pdf.
Before installing the NNM iSPI Performance for Traffic, make sure that your system meets the following minimum requirements:
Note: HP recommends that you install NNM iSPI Performance for Traffic Master Collector on physical system.
Note: The HP NNMi Extension for iSPI Performance for Traffic is supported on all platforms that are supported by NNMi other than SUSE Linux.
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.
The tables below list the hardware resource requirements for the NNM iSPI Performance for Traffic components.
Table 1 lists the resource requirements for the NNM iSPI Performance for Traffic Master Collector component. The key factor considered for sizing is the total number of flows per minute in the entire managed environment, that is, the sum of the traffic flows per minute and the total number of interfaces that are being used by all the routers in the environment to export flows.
| Managed Environment Size | NNM iSPI Performance for Traffic Master Collector Minimum Hardware System Requirements | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Approximate managed environment tier | Flow record rate / Minute (Maximum) |
Number of Flow Exporting Interfaces(Maximum) | Recommended Number of Leaf Collector Systems | Flush Record Limit | 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 |
|
60k | 250 | Master and Leaf Collectors are co-located on the same system | 50k | 4 CPU cores (2.5GHz) |
6 GB |
Leaf: 1.5 GB Master: 3 GB |
1.5 GB | 8 GB |
|
200k | 400 | 1 | 100k | 4 CPU cores (2.5GHz) |
8 GB | 6 GB | 1.5 GB | 8 GB |
|
600k | 1000 | 2 | 100k | 8 CPU cores (2.5GHz) |
16 GB | 12 GB | 1.5 GB | 32 GB |
|
2400k | 4000 | 5 | 200k | 16 CPU cores (2.5GHz) |
32 GB | 28 GB | 1.5 GB | 64 GB |
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 flows 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 record rate to the leaf / Minute (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 | 200k | 400 | 4 CPU cores |
4 GB | 3 GB | 1.5 GB | 8 GB |
| Medium | 300k | 500 | 4 CPU cores |
12 GB | 8 GB | 1.5 GB | 32 GB |
| Large4 | 480k | 800 | 8 CPU cores |
16 GB | 12 GB | 1.5 GB | 64 GB |
Note: The total number of leaf collectors in a deployment is dependent on the total number of flows per minute in the environment, Total number of Flow Exporting Interfaces, and the processing capability of each leaf collector system. Each Master Collector can support flow data from up to 5 distinct Leaf Collector systems in a single deployment. Also, note that it is assumed that about 50% of the flows are unique in a given period of time.
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 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 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 Configurations | Max Threshold Configurations | |
| Entry | 10 | 5 | 5 |
| Small | 20 | 5 | 5 |
| Medium | 30 | 10 | 10 |
| Large | 40 | 20 | 20 |
In addition to the application mappings available by default in the NNM iSPI Performance for Traffic, you can configure 400 extra destination port-based application mappings.
Note: Regular expression-based application mappings that involve pattern matching with wildcards can result in significant effect on the system performance. HP recommends that you do not configure more than 10 such regular expression-based application mappings.
Note: For more information about tuning parameters, see the NNM iSPI Performance for Traffic Deployment Guide.
Table 4 lists tuning parameter recommendations for different managed environment sizes. See the NNM iSPI Performance for Traffic Deployment Guide for details about how to configure these parameters. Datagram, 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 200 MB memory. For example, if you increase FlowRecord pool size by 200K and TopN FlowRecord pool size by 500K, you must add additional 1.4 GB to the Xmx value for Leaf Collector.
The number of flow exporting interfaces also impacts the TopN pool sizes. The following table provides general guidelines for an environment that has large number of flow exporting interfaces per tier.
| Managed Environment Size | Object Pool Size | |||
|---|---|---|---|---|
| Datagram | FlowRecord | TopN FlowRecord | Master Queue Size | |
| Entry | 50000 | 75000 | 200000 | 200000 |
| Small | 50000 | 150000 | 350000 | 400000 |
| Medium | 50000 | 300000 | 800000 | 600000 |
| Large | 50000 | 600000 | 1500000 | 1000000 |
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 RAID 1+0 or 5/6 with write cache recommended (4 disk) |
| Small | 200k | 8 CPU cores (2.5GHz) |
32 GB | 2 TB RAID 1+0 or 5/6 with write cache recommended (4 disk) |
| Medium | 600k | 16 CPU cores (2.5GHz) |
48 GB | 5 TB RAID 1+0 or 5/6 with write cache recommended (4 disk) |
| Large | 2400k | 24 CPU cores (2.5GHz) |
64 GB | 8 TB RAID 1+0 or 5/6 with write cache recommended (4 disk) |
^^
Note: Increasing the tuning parameters for ETL process of NPS to values listed in Table 6, Table 7, and Table 8 result in significant increase in CPU utilization. Make sure that there is sufficient CPU bandwidth available before increasing these parameters.
Table 6 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.
| Approximate managed environment tier | Interface_Traffic | Interface_Traffic_1_Minute | Interface_Traffic_15_Minute |
| Medium | 5 | 10 | 10 |
| Large | 10 | 50 | 20 |
Table 7 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.
| Approximate managed environment tier | Interface_Traffic | Interface_Traffic_1_Minute | Interface_Traffic_15_Minute |
| Medium | 100k | 100k | 100k |
| Large | 100k | 200k | 200k |
Table 8 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.
| Approximate managed environment tier | Interface_Traffic | Interface_Traffic_1_Minute | Interface_Traffic_15_Minute |
| Medium | 20 | 25 | 20 |
| Large | 30 | 50 | 30 |
Notes
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.)
Both the 64-bit compat-libstdc++ and 32-bit compat-libstdc++ libraries are required before installing Master Collector and Leaf Collector.
Required LibrariesMaster Collector and Leaf Collector require the following exact library versions. The RPM versions may vary depending on the minor release of RHEL. Before installing Master Collector and Leaf Collector on a 64-bit Linux server, verify that the following library files are installed:
To know more about pre-requisite information, see NNMi Support Matrix.
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 |
| HP-UX | Supported | Supported | |
Linux |
Supported. Note: SUSE Linux is not supported. |
Supported | |
| Solaris | Supported | Supported | |
* The HP NNMi Extension for iSPI Performance for Traffic must always be installed on the NNMi management server.
cat /proc/meminfo | grep
Swap command. To adjust, use the parted and mkswap commands.The NNM iSPI Performance for Traffic Master Collector alone supports running on a High Availability system. The other components of 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 NNM iSPI Performance for Metrics are running on high availability systems.
Please see the NNMi Deployment Reference and NNM iSPI Performance for Traffic Installation Guide on how to install and configure NNM iSPI Performance for Traffic for operating with NNMi iSPI Performance for Metrics in high availability systems. The following configurations are supported on Operating Systems
Notes
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 Installation Guide for more information.
The Real-time Line Graphs (Actions → Quality Assurance → Graphs) and the Performance Graphs require the Adobe Flash Player Plug-in version 10.2 or higher. The Adobe Flash Player is available from www.adobe.com/go/getflash/.
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 Japanese, Simplified Chinese, and Korean.
This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online
HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to: Search for knowledge documents of interest Submit and track progress on support cases Submit enhancement requests online Download software patches Manage a support contract Look up HP support contacts Review information about available services Enter discussions with other software customers Research and register for software training
To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.
Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.
To register for an HP Passport ID, go to: HP Passport Registration
©Copyright 2009 - 2013 Hewlett-Packard Development Company, L.P.
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.
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.
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.
UNIX® is a registered trademark of The Open Group.
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)
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.