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

Software Version: 8.10

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

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
    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.
• Itanium Processor Family
  • Caution: IPF hardware running the Windows or Linux operating systems is not supported
• Sun UltraSPARC
  • UltraSPARC T1 or T2 is not a recommended hardware platform for Medium and Large tier environments. Small tier environments running on UltraSPARC T1 or T2 platforms may see a decreased performance in comparison to other supported platforms.
• VMWare ESX Server 3.x
• Virtual environment must meet the x86-64 or AMD64 hardware requirements listed here

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:.

• For large scale deployments, use Oracle database.
• Physical RAM should be twice that of the combined Xmx values of the iSPI for IP Telephony and NNMi.

Managed Environment Size							IP Telephony Minimum Hardware System Requirements
Approximate managed environment tier	Number of discovered Phones	Number of discovered non phones nodes	Number of discovered Interfaces*	Number of polled Interfaces*	Number of polled Node Components	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 application installation (<NnmInstallDir>)**	Disk space for database and data during execution (<NnmDataDir>)***
Small	Up to 10K	Up to 1K	Up to 150K	Up to 10K	Up to 15K	10	4 CPU (2.5GHz for x64 or 1.4GHz for RISC)	NNMi Small Scale value+6 GB	2GB (-Xmx2g)	NNMi Medium Scale value	500 MB	60 GB
Medium	Up to 30K	Up to 3K	Up to 490K	Up to 50K	Up to 40K	20	8 CPU core (2.5GHz for x64; 1.4GHz for IPF or RISC	NNMi Large Scale value	3GB (-Xmx3g)	NNMi Large Scale value	500 MB	140 GB RAID 1+0 or 5/6 with write cache recommended (4 disk)
Large	30K – 45K	Up to 3K	Up to 535K	Up to 50K	Up to 40K	20	8 CPU core (2.5GHz for x64; 1.4GHz for IPF or RISC)	NNMi Large Scale value+6 GB	4GB (-Xmx4g)	NNMi Large Scale value	500 MB	300 GB RAID 1+0 or 5/6 with write cache recommended (4 disk)

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-series" dialog.
** <NnmInstallDir> is configured during installation on Windows (C:\Program Files (x86)\HP\HP BTO Software\ by default).
*** <NnmDataDir> is configured during installation on Windows (C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software by default), Disk space estimates are when using embedded PostgreSQL. If using an external Oracle database, only 10-20 GB is required for NnmDataDir.

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
• Caution: Windows operating systems on Itanium Processor Family (IPF) are not supported
• Caution: Windows 32-bit operating systems are not supported
• Other Windows Software
  • Microsoft Simple Network Management Protocol must be installed.

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 below.
• 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 4.6 (or newer minor version)
• RedHat Enterprise Server ES 4.6 (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 physical memory
• Verify virtual memory via the swapinfo command on HP-UX, the swap command on Solaris, the cat /proc/meminfo | grep Swap command on Linux, or System Properties on Windows.
• Adjust virtual memory via the shm or swapon command on HP-UX, the swap command on Solaris, the parted and mkswap command on Linux, or System Properties on Windows.

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 Services 2003
• HP-UX: Service Guard - 11.18 and above
• Linux: Service Guard - 11.18 and above
• Solaris: Veritas 5.

Database

The database(embedded or Oracle)selection for the iSPI for IP Telephony should be 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) 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 install 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 should have a resolution of at least 1024x768
• Caution: The following browsers are not supported:
  • Microsoft Internet Explorer version 6 (browser causes layout problems)
  • Microsoft Internet Explorer version 8
  • Mozilla Firefox version 3 (browser has table scrolling 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 7.0.5730.11 or newer with October 2007 or later Cumulative Patch for Internet Explorer 7. This patch increases the number of Internet Explorer cookies from 20 to 50, allowing for saving of more NNM console table configurations.
  • Mozilla Firefox version 2.0.0.17 or newer minor version from a Windows or Linux client. The Firefox browser may be downloaded from www.mozilla.org/firefox. Mozilla Firefox version 3 is not supported.

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
• Mozilla Firefox version 2.0.0.4 or newer minor version for HP-UX 11.31 on IPF server. The Firefox browser may be downloaded from www.hp.com/go/firefox
• Mozilla Firefox version 2.0.0.9 or newer minor version for Solaris SPARC 10. The Firefox browser may be downloaded from releases.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.9/contrib/solaris_pkgadd .

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, 8.10.

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, 8.10.

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.