HP Network Node Manager iSPI Performance for Traffic Support Matrix

for the Windows® operating system

Software version: 8.13

Publication date: September 2009

This document provides an overview of the system requirements and supported devices for HP NNM iSPI Performance for Traffic for NNMi 8.13.

What's New in This Release?

This is the first release for iSPI Performance for Traffic. You can use the iSPI Performance for Traffic in conjunction with the iSPI Performance for Metrics to view reports that help you understand performance bottlenecks in you network more effectively. In addition, you can monitor network flow data and store the data for future analysis.

Supported Environments

The iSPI Performance for Traffic runs on the following Microsoft Windows operating system environments:

· Windows Server 2003 x64 with Service Pack 2.

· Windows Server 2003 x64 R2 with Service Pack 2.

· Note: Microsoft Windows operating systems on Itanium Processor Family (IPF) and Windows 32 bit operating systems are not supported.
.

Software and Hardware Requirements

Pre-installation requirements, as well as instructions for installing 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 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)

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

· Disk space

§ 10 GB

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 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 both NNMi or iSPI Performance for Metrics components are installed on the same system or shares the disk space of the system, the system requirements provided in the iSPI Performance for Traffic Support matrix is in addition to the specified system requirements in the support matrices for NNMi and iSPI Performance for Metrics.

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

Managed Environment Size					iSPI Performance for Traffic Minimum Hardware System Requirements
	Master collector configuration		Leaf collector configuration		Master collector		Leaf collector		Java heap size for Master collector (see Tuning the jboss Memory Size, below)	Java heap size for leaf collector (see Tuning the jboss Memory Size, below)	Disk space for application installation (<Traffic InstallDir>)**	Disk space for data during execution (<Traffic DataDir>)***	Disk space for flow record data during execution (<iSPI Performace for metrics DataDir>)^^
Approximate managed environment tier	Flow record rate to the leaf	<nms.traffic-master.maxflowrecord.inqueue>^	<flowrecord.pool.size>^	No. of leaf collectors	CPU (64-bit) x86-64 AMD64	RAM	CPU (64-bit) x86-64 AMD64	RAM
Medium	upto 15K per sec	1000000	500000	5	4 CPU cores (2.5GHz)	7GB	2 CPU cores (2.5GHz)	5GB	5GB (-Xmx5g)	3GB (-Xmx3g)	500MB	100MB	300 GB RAID 1+0 or 5/6 with write cache recommended (4 disk)
Large	15K- 30K per sec	5000000	1000000	5	8 CPU cores (2.5GHz)	9GB	4 CPU cores (2.5GHz)	6GB	7GB (-Xmx7g)	4GB (-Xmx4g)	500MB	100MB	900 GB RAID 1+0 or 5/6 with write cache recommended (4 disk)

**<TrafficInstallDir> is configured during installation of iSPI Performance for Traffic (Master Collector or Leaf Collector) on Windows (C:\Program Files (x86)\HP\HP BTO Software\ by default)
***<TrafficDataDir> is configured during installation of iSPI Performance for Traffic (Master Collector or Leaf Collector) on Windows (C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software by default). You can refer to the HP NNM iSPI Performance for Traffic Installation Guide to configure these parameters.

^ You can refer to HP NNM iSPI Performance for Traffic Installation Guide to configure these parameters.

^^<iSPI Performance for metrics DataDir> is configured during installation of iSPI Performance for Metrics on Windows (C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software by default). You can also set the data archival period in the Configuration utility of the system. If the data archival period for iSPI Performance for Metrics maintenance is set to a high value, ensure that adequate free disk space is available on the system on which you have installed iSPI Performance for Metrics. You can refer to HP NNM iSPI Performance for Metrics Installation Guide to configure these parameters.

Tuning the jboss Memory Size

To change the jboss maximum java heap size or other Java Virtual Machine parameters, follow these steps:

1. Stop iSPI Performance for Traffic Master Collector and similarly iSPI Performance for Traffic Leaf Collector.
2. Edit the nms-traffic-master.jvm.properties or nms-traffic-leaf.jvm.properties file:
* The default maximum memory size of the jboss application server is configured in: C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\shared\traffic-master\conf\nms-traffic-master.jvm.properties location.
3. Change the Maximum Java Heap Size to the required amount. For example, a snippet of the nms-traffic-master.jvm.properties file looks like this:
#
#
# JVM Memory parameters
# -Xms: Initial Java Heap Size
# -Xmx: Maximum Java Heap Size
# -Xss: Java stack size (default to OS-supplied value)
#
-Xmx2048m
-Xms1024m

4. Start iSPI Performance for Traffic Master Collector and similarly iSPI Performance for Traffic Leaf Collector.

Note: For a larger deployment environment, the jboss maximum java heap size can be increased to improve performance of CPU, RAM, and Disk Space requirements. Do not make the jboss maximum java heap size value too large, because the operating system may crash as jboss accesses memory.
For more information about tuning the jboss maximum java heap size, see http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html.

Web Browser

General Web Browser Requirements

Any Window Popup Blockers must be disabled for the browser (see instructions on the console sign-in page, NNMi Installation Guide).
Cookies must be enabled for the browser (see instructions on the console sign-in page,NNMi Installation Guide.
Client display should have a resolution of at least 1024x768
Note:The following browsers are not supported:
- Microsoft Internet Explorer version 6
- Microsoft Internet Explorer version 8
- Mozilla Firefox version 2
- Apple Safari (all versions)
- Opera (all versions)
- Google Chrome (all versions)

Supported Web Browser
- Microsoft Internet Explorer version 7.
- Mozilla Firefox version 3 or newer minor version from Windows. The Mozilla Firefox browser may be downloaded from www.mozilla.org/firefox.

Documentation Updates

The first page of this release notes document contains the following identifying information:

· Version number, which indicates the software version.

· Publish date, which changes each time the document is updated.

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

To retrieve a document, select the:

1. Product name.

2. Version list.

3. Operating System.

4. Preferred Language.

5. Document title.

6. Click Open or Download.

You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.

Legal Notices

Copyright Notices

This product includes ASM Bytecode Manipulation Framework software developed by Institute National de Recherche en Informatique et Automatique (INRIA). Copyright © 2000-2005 INRIA, France Telecom. All Rights Reserved.

Trademark Notices

Java™ is a US trademark of Sun Microsystems, Inc.

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