HP Network Node Manager i-series Smart Plug-in for Performance Software

Support Matrix

Software Version: 8.10 / 25 November 2008

Introduction
Hardware and Software Requirements
    Same Server Install
    Dedicated Server Install
    Hardware
    Operating System
    Web Browser
Coexistence and Integration with Other Products

Introduction

This document describes system requirements for the HP Network Node Manager Software i-series Smart Plug-in for Performance (iSPI) version 8.10. The information in this document is not duplicated elsewhere. To download the latest edition of this document, visit the HP Product Manuals web site at http://h20230.www2.hp.com/selfsolve/manuals.

When you are ready to install the Performance SPI, refer to the installation guide (.pdf) and to release notes (.html). The installation guide and release notes ship with the Performance SPI on the installation media. Both documents are copied from the DVD to your system during product installation. To download the latest edition of each document, visit the HP Product Manuals web site.

Hardware and Software Requirements

You can install the iSPI for Performance on a dedicated server, separate from NNM, or you can install the iSPI for Performance on the same server that is hosting NNM. The following factors determine whether installing the iSPI for Performance on the same server with NNM is feasible:

  • How your NNM management server is configured for CPU, RAM, and disk space

  • The number of network elements NNM is polling for performance data

  • The frequency that NNM is polling network elements

Before installing the iSPI for Performance, note the following points regarding disk size, partitioning, and your options regarding the number of days your installed system retains "detail" data:

  • The data directory (NnmDataDir) will contain the bulk of the collected and aggregated data and as such should be on the fastest and largest disk partition. For Unix platforms this will be /var/opt/OV

  • Approximately half the required disk space for the iSPI is consumed by "detail" data storage. The default retention period for this type of data is 14 days.

  • To change the default, use the configuration utility. The maximum retention period is 70 days.

How long you retain detail data has a direct impact on disk usage. If you increase the retention period, be sure to monitor disk space usage.

Same Server Install (NNM and iSPI on the same server)

The table below outlines the requirements for CPU, RAM and disk space when NNM and the iSPI for Performance are on the same server. Note that the CPU, RAM and Disk figures represent total requirements for the server and include the combined capacity required for NNM and the iSPI. You must ensure that this server meets any and all NNM requirements. For details about NNM requirements, see the NNM system support matrix.

Management Environment Size

NNM + iSPI Minimum System Requirements

Approximate managed environment tier

 Number of discovered nodes

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

CPU (64-bit)
IPF
x86-64
AMD64

RAM

Disk space for
Application installation(NnmInstallDir)
 

Disk space for database and data during execution (NnmDataDir)
 

Small

Up to 3K

Up to 5K/5K

8 CPU (2.5GHz for x64 or 1.8GH for RISC)

12 GB

10 GB

130 GB

1 SCSI or SATA disk drive

Medium

3K - 8K

Up to 10K/10K

8 CPU (2.5GHz for x64 or 1.8GH for RISC)

24 GB

10 GB

240 GB

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

Large

8K - 18K

Up to 60K/60K

16 CPU (2.5GHz for x64 or 1.8GH for RISC)

32 GB

10 GB

700 GB

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

Dedicated Server Install

If you are planning to install the iSPI on a separate machine, ensure that your servers meet the criteria in the following two tables. Note that iSPI sizing requirements are driven by the number of interfaces and node components that NNM is polling for performance data, not the number of interfaces or components that NNM has discovered. Note also that enabling performance polling on NNM will impact NNM, so ensure that the machine hosting NNM meets criteria in the table below as well as criteria documented in the NNM System Support Matrix.

Minimum System Requirements for the iSPI Server

Management Environment Size

Minimum System Requirements for iSPI

Approximate managed environment tier

 Number of
polled nodes

# perf polled interfaces / components at 1 minute polling interval

CPU (64-bit)
IPF

x86-64

AMD64

RAM

Disk space for
Application installation (NnmInstallDir)
 

Disk space for database and data during execution (NnmDataDir)

Small

Up to 600

Up to 5K/5K

4 CPU (2.5GHz for x64 or 1.8GH for RISC)

8 GB

5 GB

50 GB

1 SCSI or SATA disk drive

Medium

Up to 1000

Up to 10K/10K

4 CPU (2.5GHz for x64 or 1.8GH for RISC)

16 GB

5 GB

100 GB

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

Large

Up to 10,000

Up to 60K/60K

8 CPU (2.5GHz for x64 or 1.8GH for RISC)

16 GB

5 GB

400 GB

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

Minimum System Requirements for the NNM Server

Management Environment Size

Minimum System Requirements for NNM

Approximate managed environment tier

 Number of discovered nodes

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

CPU (64-bit)
IPF
x86-64
AMD64

RAM

Disk space for
Application installation(NnmInstallDir)
 

Disk space for database and data during execution (NnmDataDir)

Small

Up to 3K

Up to 5K/5K

8 CPU (2.5GHz for x64 or 1.8GH for RISC)

12 GB

5 GB

80 GB

1 SCSI or SATA disk drive

Medium

3K - 8K

Up to 10K/10K

8 CPU (2.5GHz for x64 or 1.8GH for RISC)

24 GB

5 GB

140 GB

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

Large

8K - 18K

Up to 60K/60K

16 CPU (2.5GHz for x64 or 1.8GH for RISC)

32 GB

5 GB

300 GB

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

Hardware

  • 64 bit architecture
    • 64 bit hardware is required, regardless of the operating system used
  • Virtual Memory/Swap Space
    • Recommend 2 times physical memory and at least 12GB
    • Verify virtual memory via System Properties on Windows

Operating Systems

  • Windows

    • Windows Server 2003 Enterprise x64 with Service Pack 2

    • Windows Server 2003 Enterprise x64 R2 with Service Pack 2

    • Update for Windows Server 2003 x64 Edition (KB925336)

    The update is a hot-fix. Without this update, iSPI installation may fail during installation of the HpErsBiServer package. According to the install log, the failure is caused by a problem with software restriction policy processing and the following error message is logged:

    Error 1718. File <filename> was rejected by digital signature policy.

    Download the hot-fix from here: http://support.microsoft.com/kb/925336

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

    • Windows 32-bit operating systems are not supported

  • HP-UX

    • HP-UX 11iv3
    • Kernel configuration (verify with /usr/sbin/smh)
      • Verify kernel parameters in the "Kernel Configuration/Tunables" section.  Note that the maxdsiz value will typically be set to 1GB and must be increased to around 3GB in order to avoid memory allocation problems during report generation.
        • nproc: add 50
        • max_thread_proc = 2048
        • nkthreads = 10000
        • maxdsiz = 3221225472
    • System Configuration
      • Verify using swapinfo that the system has a sufficient amount of swap. The minimum requirement is 12 GB. This is the sum of the RAM and swap space available.
    • Operating System Kernel Patches

      The following HP-UX 11iv3 operating system patches are required (or newer if the patch has been superseded). You can verify patches on HP-UX by running
      /usr/sbin/swlist -l fileset -a patch_state *.*,c=patch | grep -v superseded

      This list does not include Java patches (see next bullet), but only the list of OS-level patches. The following patches are required:

      • PHKL_36054
      • PHKL_36261
      • PHKL_36872
      • PHKL_37184
    • Run HPjconfig HP-UX 11i system configuration tool to validate the system configuration. HPjconfig can be downloaded from www.hp.com/go/java.  To install:
      • On your HP-UX system, gunzip and untar the .tar.gz file as follows:
        gunzip HPjconfig-3.1.00.tar.gz
        tar -xvf HPjconfig-3.1.00.tar
      • To start HPJconfig:
        Change to the directory you installed the HPjconfig files.
        There are two ways you can run HPjconfig, GUI and non-GUI mode. Enter one of the following commands:
        java -jar ./HPjconfig.jar (The default HPjconfig GUI)
        java -jar ./HPjconfig.jar -nogui -help
        (The -help command lists options that you can use in non- GUI mode)
      • To list missing patches in non-GUI mode:
        java -jar ./HPjconfig.jar -nogui -patches -listmis
        This will validate kernel configuration and patch levels

    • Solaris

      • Sun Solaris 10 SPARC
      • Caution: Solaris on Intel Architecture is not supported
      • The shared memory must be updated. Using an editor, update the /etc/system entry, as follows: set shmsys:shminfo_shmmax=1073741824

    • Linux

      • RedHat Enterprise Server AS 4.6 - or newer minor version
      • RedHat Enterprise Server ES 4.6 - or newer minor version
      • 64-bit libstdc++ libraries (HP Software Installer includes an automatic check for these libraries)

     

    Supported Platform Combinations

    The Performance SPI supports the following operating system combinations:

    		 SPI

    Windows

    		 Linux HPUX Solaris
    NNM Windows X      
    Linux X X    
    HPUX X X X X
    Solaris X X X X

    High Availability

    With additional configuration, the Performance SPI can run on certain high availability systems. For details about configuring the Performance SPI for high availability, see the NNM Deployment Guide. The following configurations are supported on Performance SPI Supported Operating Systems:

    • Microsoft: Microsoft Cluster Services 2003
    • HP-UX: Service Guard - 11.18 and above
    • Linux: Service Guard - 11.18 and above
    • Solaris: Veritas 5.0

    Web Browser

    • General Web Browser Requirements

      • Any Window Popup Blockers must be disabled for the browser (see instructions on the console sign-in page or the Install Guide)
      • Cookies must be enabled for the browser (see instructions on the console sign-in page, or see the installation guide)
      • Client display should have a resolution of at least 1024x768

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

      • Any browser supported for operational use (see above) when running on the management server

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

      • Microsoft Internet Explorer version 7.0.5730.11 or newer with October 2007 or later Cumulative Patch for Internet Explorer 7.
      • Mozilla Firefox version 2.0.0.8 or newer from a Windows client (excluding version 3.x). The Firefox browser may be downloaded from www.mozilla.org/firefox
      • Microsoft Internet Explorer version 6 is not supported
      • Apple Safari is not supported

    Coexistence and Integration with Other Products

    Coexistence

    The following products have been tested and found to co-exist on the same system as the Performance SPI 8.10.

    • MC SPI 8.10 (Windows)
    • MPLS SPI 8.10 (Windows, Linux, HP-UX, Solaris)
    • IPT SPI 8.10 (Windows, Linux, HP-UX, Solaris)
    • OVPA 4.7 (Windows)
    • OMW Agent 8.52 (Windows)
    • OMU Agent 8.51 (Linux, HP-UX, Solaris)

    Integrations

    The following product has additional functionality available through an integration with the Performance SPI 8.10.

    • HP Performance Insight Version 5.31