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

Software Version: 9.01

This document provides an overview of the system requirements and supported devices for HP Network Node Manager i Software
Smart Plug-in for IP Telephony (iSPI for IP Telephony) version 9.01.

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 (IPT_SupportMatrix_en.html) and the Release Notes (IPT_ReleaseNotes_en.html) at the root directory of the installation media.

Hardware and Software Requirements
    Hardware
       CPU, RAM, and Disk Space Requirements / Maximum Supported Managed Environment
       Disk Space Requirements on the iSPI Performence for Metrics/NPS System for Retention of Reporting Data Generated by the iSPI for IP Telephony
    Operating System
Virtual Memory/Swap Space
    Database
    Web Browser
    Internationalization and Localization Support
Supported Devices
Support
Legal Notices

Hardware and Software Requirements

Pre-installation requirements, as well as instructions for installing iSPI for IP Telephony, 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: IPT_InstallGuide_en.pdf.

Before installing the iSPI for IP Telephony, make sure that your system meets the following minimum requirements:

Hardware

• Intel 64-bit (x86-64) or AMD 64-bit (AMD64)
  • Caution: Intel 32-bit (x86) hardware is not supported. Verify your computer architecture by looking at the %PROCESSOR_ARCHITECTURE% variable or System Properties.
  • Only supported for the Windows or Linux operating systems.
• Itanium Processor Family
  • Caution: IPF hardware running the Windows or Linux operating systems is not supported
  • Only supported for the HP-UX operating system
• Sun SPARC
  • Only supported for the Solaris operating system.
  • Supported Solaris processors:
    • UltraSPARC IIIi, IV, IV+
    • SPARC64 V, V+
    • SPARC64 VI, VII (M-class)
  • No support for the following Solaris T series processors: UltraSPARC T1, T2, and T2+
• Hypervisor Virtualization
  •  VMware ESX Server 3.5 or 4.0
    • Only supported for the Windows or Linux operating systems.
    • Virtual environment must meet the x86-64 or AMD64 hardware requirements listed here.
    • Bridged network environment required. NAT'ed network environments are not supported.
  • HP Integrity Virtual Machines
    • Only supported for the HP-UX operating system

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 for IP Telephony for supporting these environments. Managed environments bigger than the Large tier are not supported without additional HP approval. Make sure to check the NNMi Support Matrix.

The iSPI for IP Telephony hardware requirements mentioned in the below table is in addition to NNMi hardware requirements mentioned in the NNMi Support Matrix.

Before installing the iSPI for IP Telephony, make sure that your system meets the following minimum requirements:.

• The RAM Requirement mentioned in the table below is an approximate number to help you get started with the sizing of the system. However, if you are planning to install the iSPI Performance for Metrics/NPS on the same system, you must ensure that the physical RAM is greater than two times that of the combined Xmx values of NNMi, the iSPI for IP Telephony, other content iSPI s (if installed on the system), the iSPI Performance for Traffic Master Collector (if installed on the system), the iSPI Performance for Traffic Leaf Collector (if installed on the system), and the iSPI Performance for Quality Assurance (if installed on the system). You must also consider the consumption of memory in segments apart from the memory consumption by various heap segments. In addition, you must also consider consumption of memory by the operating system, applications from HP which are not listed in this document, and applications from other vendors.

• If you are planning to install the iSPI Performance for Metrics/NPS on a separate system, you must ensure that the physical RAM is greater than that of the combined Xmx values of NNMi, the iSPI for IP Telephony, other content iSPI s (if installed on the system), the iSPI Performance for Traffic Master Collector (if installed on the system), the iSPI Performance for Traffic Leaf Collector (if installed on the system) and the iSPI Performance for Quality Assurance (if installed on the system). You must also consider the consumption of memory in segments instead of considering various heap segments. In addition, you must also consider consumption of memory by the operating system, applications from HP which are not listed in this document, and applications from other vendors.

• It is recommended that you provision 4 GB or more of RAM for the operating system and the other applications on the system.

Managed Environment Size						IP Telephony Minimum Hardware System Requirements
Approximate managed environment tier	Number of discovered IP Phones	Number of discovered nodes that are not IP Phones	Number of discovered Interfaces*	Number of polled Interfaces*	Number of concurrent users	CPU (64-bit) IPF x86-64 AMD64 SPARC****	RAM	Java heap size for IP Telephony	Java heap size for NNMi*****	Disk space for iSPI for IP Telephony installation with an Incremental Demand on (<NnmInstallDir>)**	Total Disk Space for Database and Data During Execution (<NnmDataDir>)*** Note: This does not include the disk space to retain the data for reporting.
Entry	Up to 500	Up to 100	7K	2500	5	2 CPU Cores	8 GB	2 GB (-Xmx2g)	2 GB (-Xmx2g)	500 MB	20 GB
Small	Up to 3K	Up to 500	40K	2500	10	4 CPU cores	12 GB	3 GB (-Xmx3g)	4 GB (-Xmx4g)	500 MB	60 GB
Medium	Up to 10K	Up to 1.5K	90K	5K	20	4 CPU cores	16 GB	4 GB (-Xmx4g)	7 GB (-Xmx7g)	500 MB	140 GB RAID 1+0 or 5/6 with write cache recommended
Large	Up to 30K	Up to 3K	250K	50K	30	8 CPU cores	24 GB	8 GB (-Xmx8g)	10 GB (-Xmx10g)	500 MB	300 GB RAID 1+0 or 5/6 with write cache recommended
Very Large	Up to 50K	Up to 4K	550K	70K	40	8 CPU cores	32 GB	8 GB (-Xmx8g)	16 GB (-Xmx16g)	500 MB	300 GB RAID 1+0 or 5/6 with write cache recommended

Note: See the NNMi 9.00 Support Matrix for requirements in a Global Network Management (GNM) environment.

To tune Java heap size, see the Tuning the jboss Memory.
* Maximum number of discovered Interfaces does not affect performance, it only affects the size of the database. Monitoring performance is affected by the number of Interfaces and Node being polled by the State Poller. The Number of Polled Interfaces reflects the number of Interfaces polled in a 5 minute interval. To view the number of polled objects, examine the Monitored Objects count in the "Help → About HP Network Node Manager i Software " dialog.
** $NnmInstallDir is configured during installation on Windows (C:\Program Files (x86)\HP\HP BTO Software\ by default), or on UNIX by creating a symlink to /opt/OV/. NOTE to NNM 7.x customers: /etc/opt/OV/ is no longer used on UNIX except for one configuration file.
*** $NnmDataDir is configured during installation on Windows Server 2003 (C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\ by default), or Windows Server 2008 (C:\ProgramData\HP\HP BTO Software\ by default), or on UNIX by creating a symlink to /var/opt/OV/.

****Minimum of 2.5GHz for x64 and 1.4GHz for IPF or RISC.

*****These recommendations are based on the environment size and polled object counts stated in this table.  Polling fewer of a given object type might use less Java heap.  Polling more of a given object type might require increased Java heap size as well as HP approval.

Disk Space Requirements on the iSPI Performance for Metrics/NPS System for Retention of Reporting Data Generated by the iSPI for IP Telephony

If you decide to enable CDR reporting in iSPI for IP Telephony, you must provision for incremental disk space usage on the system for long term storage of the call metric information provided by the iSPI for IP Telephony to the iSPI Performance for Metrics/NPS. You must make such a provision for the following scenarios:

• The iSPI Performance for Metrics/NPS is installed on the same machine where NNMi and the iSPI for IP Telephony are installed
• The iSPI Performance for Metrics/NPS is installed on a separate system

See the iSPI Performance for Metrics/NPS Support Matrix document for more information about minimum system requirements (including those for disk space) for appropriately evaluating the disk space requirements.

As a sample estimate, it was noticed that if you configure the iSPI for IP Telephony to process and analyze Call Detail Records (CDR) for 50,000 call attempts every hour, continuously for a period of 15 days, the corresponding incremental disk space usage on the iSPI Performance for Metrics/NPS system at the end of 14 days was approximately 7 GB in size.

You can use this information along with iSPI Performance for Metrics/NPS Support Matrix document for appropriate sizing of the systems involved.

Tuning the jboss Memory

To change the jboss Maximum Java Heap Size (‑Xmx) or other Java Virtual Machine parameters, follow these steps:

1. Stop the IP Telephony process by the following command: ovstop –c iptjboss
2. Edit the nms-ipt.jvm.properties file:
   • For Windows: C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\shared\ipt\conf\nms-ipt.jvm.properties
   • For UNIX: /var/opt/OV/shared/ipt/conf/nms-ipt.jvm.properties
3. Update the Maximum Java Heap Size to the required value. For example, a snippet of the nms-ipt.jvm.properties file appears as:
   #
   # JVM Memory parameters
   #   ‑Xms: Initial Java Heap Size
   #   ‑Xmx: Maximum Java Heap Size
   #
   ‑Xms1024m
   ‑Xmx2048m
4. Start the IP Telephony process by the following command: ovstart –c iptjboss

For more information related to NNMi values, see the NNMi Support Matrix.

Operating System

Windows 

• Windows Server 2003 x64 with Service Pack 2
• Windows Server 2003 x64 R2 with Service Pack 2
• Windows Server 2008 x64 Datacenter Edition with Service Pack 2
• Windows Server 2008 R2 x64 Datacenter Edition
• Windows Server 2008 x64 Enterprise Edition with Service Pack 2
• Windows Server 2008 R2 x64 Enterprise Edition

  Notes

  • Windows operating systems on Itanium Processor Family (IPF) is not supported.
  • Windows 32-bit operating systems are not supported.
  • Management of IPv4 networks through IPv6 address management is not supported for Microsoft Windows operating systems.
  • Manages IPv4 networks when NNMi and the iSPI for IP Telephony are run on a dual stack environment that includes both IPv4 and IPv6 implementation.
  • Does not manage IPv6 networks
  • The Windows SNMP Trap service (or any other service that takes UDP Port 162) must be disabled.
  • Anti-virus and backup software can interfere with NNMi operation if this software locks files while NNMi is running. Any application that locks files should be configured to exclude the NNMi database directory (on Windows 2003, C:\Documents and Settings\All Users\Application Data\HP HP BTO Software\databases; or on Windows 2008, C:\ProgramData\HP\HP BTO Software\databases).

HP-UX

• HP-UX 11iv3
• Kernel configuration (verify with /usr/sbin/smh)
  • Verify kernel parameters in the "Kernel Configuration/Tunables" section:
    • nproc: add 50
    • max_thread_proc = 2048
    • nkthreads = 10000
• System Configuration
  • Verify using swapinfo that the system has a sufficient amount of swap as documented in Virtual Memory/Swap Space.
• 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. Update the /etc/system entry using an editor as follows:
  set shmsys:shminfo_shmmax=1073741824

Linux

• RedHat Enterprise Server AS 5.2 (or newer minor version)
• RedHat Enterprise Server ES 5.2 (or newer minor version)
• The default size of kernel.shmmax may be too small for the embedded database to operate after a reboot (as reported by ovstatus -c nmsdbmgr).  To validate, run /sbin/sysctl –a | /bin/grep kernel.shmmax.  If this is less than 300 MB (300000000), then it must be modified. To change the value, run:

  /sbin/sysctl –w kernel.shmmax=300000000
  To make this change permanent (after a reboot), edit the /etc/sysctl.conf file and add the following entry:

  kernel.shmmax = 300000000

• See the installation guide for the dependency on the 64-bit libstdc++ libraries.

Virtual Memory/Swap Space

• Recommended size is at least equal to the physical memory
• Verify and adjust the virtual memory:
  • Windows: Use System Properties.
  • HP-UX: To verify, use the swapinfo command. To adjust, use the shm or swapon command.
  • Linux: To verify, use the cat /proc/meminfo | grep Swap command. To adjust, use the parted and mkswap commands.
  • Solaris: Use the swap command.

High Availability

The iSPI for IP Telephony can run on certain high availability systems with additional configuration. Please see the NNMi Deployment Guide and iSPI for IP Telephony Installation Guide on how to install and configure iSPI for IP Telephony on high availability systems. The following configurations are supported on Operating Systems:

• Microsoft: Microsoft Cluster Service for Windows Server 2008 or 2003
• HP-UX: HP Serviceguard version 11.18
• Linux
  • Veritas Cluster Server version 5.0
  • HP Serviceguard version 11.18
• Solaris: Veritas Cluster Server version 5.0.

Database

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

• Embedded database on the management system
  • The embedded database is automatically installed, initialized and maintained by NNMi and iSPI for IP Telephony.
  • The embedded database comes with tools for re-initialization, online backup, and restore.
  • The embedded database performs well for most deployments.
• Oracle 10g Release 2 (10.2.0.x) or Oracle 11g Release 2 (11.2.0.x), installed on a remote system:
  • Recommend at least a 1GB network connection between the NNMi management server and the database server.
  • Database user must be created before installation with appropriate tablespace.

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 must be at a resolution of at least 1024x768
• Caution: The following browsers are not supported:
  • Microsoft Internet Explorer version 6 (browser causes layout problems)
  • Apple Safari (all versions)
  • Opera (all versions)
  • Google Chrome (all versions)

 

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

• Microsoft Internet Explorer version 8.
• Microsoft Internet Explorer version 7.0.5730.11 or higher with October 2007 or later Cumulative Patch for Internet Explorer 7.
  This patch increases the number of Internet Explorer cookies from 20 to 50, which is useful for saving more NNMi console table configurations.
• Mozilla Firefox version 3.6 or newer minor version on a Windows or Linux client. The Firefox browser is available from www.mozilla.org/firefox. The Firefox browser works best if new windows are opened as separate windows, not tabs. For information, see Mozilla Firefox Known Problems in the Release Notes.

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 NNMi management server.
• Mozilla Firefox version 3.0.10.00 or newer minor version for HP-UX 11.31 on IPF server. This Firefox browser is available from www.hp.com/go/firefox.
• Mozilla Firefox version 3.6 or newer minor version for Solaris SPARC 10. This Firefox browser is available from releases.mozilla.org/pub/mozilla.org/firefox/releases/3.6/contrib/solaris_pkgadd/.

Adobe Flash Player Plug-in

The Real-time Line Graphs (Actions → Graphs) and the SNMP MIB Browser (Tools → Browse MIBs) require the Adobe Flash Player Plug-in version 10.0.32.18 or higher. The Adobe Flash Player is available from www.adobe.com/go/getflash/.

Internationalization and Localization Support

The iSPI for IP Telephony can be installed on a system configured for non-English language. The iSPI for IP Telephony is not localized; therefore, iSPI for IP Telephony specific strings appear in English. However, the NNMi-specific views and strings appear in the non-English language. For the list of languages supported by NNMi, see NNMi Support Matrix, 9.00.

Supported Devices

IP Telephony Devices

The following table lists the IP telephony devices supported by this version of the iSPI for IP Telephony:

For the latest updates to the NNMi devices, see NNMi Support Matrix, 9.00.

HP Software Support

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.