HP Network Node Manager iSPI for IP Telephony Software System and Device Support Matrix

for the Windows® and Linux Operating Systems

Software Version: 10.00/ July 2014

Publication Date: March 2015

This document provides an overview of the system requirements and supported devices for HP Network Node Manager iSPI for IP Telephony Software (NNM iSPI for IP Telephony) version 10.00.

To check for recent updates and to see the Release Notes and Support Matrix for the NNM iSPI for IP Telephony 10.00, 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
Memory, CPU Requirements on the NNM iSPI Performance for Metrics/NPS System for Processing of the Reporting Data Generated by the NNM iSPI for IP Telephony
System sizing NNM iSPI Performance for Metrics/NPS System for Processing of the Reporting Data Generated by the NNM iSPI for IP Telephony
Operating System
Virtual Memory/Swap Space
Database
Web Browser
Internationalization and Localization Support
Supported Devices
Supported Microsoft Lync Server Versions
Support
Legal Notices

Hardware and Software Requirements

Pre-installation requirements, as well as instructions for installing NNM 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 NNM iSPI for IP Telephony, make sure that your system meets the following minimum requirements:

Hardware

CPU, RAM, and Disk Space Requirements / Maximum Supported Managed Environment

Listed here are the three tiers of managed network environments and the hardware required by the NNM 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 HP Network Node Manager i Software (NNMi) Device Support Matrix 10.00.

The NNM iSPI for IP Telephony hardware requirements mentioned in the following tables are in addition to NNMi hardware requirements mentioned in the HP Network Node Manager i Software (NNMi) Device Support Matrix 10.00.

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

Table 1: Standalone Instance of the NNM iSPI for IP Telephony for Monitoring the Cisco, Avaya, or Nortel IP Telephony, or the Acme Session Border Controller

Managed Environment Size

IP Telephony Minimum Hardware System Requirements

Approximate
managed
environment
tier

Number of
Directory Numbers (DNs)

Number of Sessions (Through Session Border Controllers)**

Number of
discovered NNMi nodes that are not hosting IP Phones

Number of
discovered
NNMi Interface objects

Number of
polled
NNMi Interfaces

Number of
concurrent
NNMi users

CPU (64-bit)
x86-64
AMD641

RAM

***Java heap size the NNM iSPI for IP Telephony

Java heap size for NNMi

Disk space for
NNM 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 500

Up to 100

7K

2500

5

2 CPU Cores

9 GB

3 GB
(-Xmx3g)

3 GB
(-Xmx3g)

1 GB

20 GB

Small

Up to 3K

Up to 3K

Up to 500

40K

2500

10

4 CPU Cores

10 GB

4 GB
(-Xmx4g)

4 GB
(-Xmx4g)

1 GB

40 GB

Medium*

Up to 10K

Up to 10K

Up to 1.5K

90K

5K

20

4 CPU Cores

18 GB

8 GB
(-Xmx8g)

8 GB
(-Xmx8g)

1 GB

80 GB

Large*

Up to 30K

Up to 30K

Up to 3K

250K

50K

30

8 CPU Cores

28 GB

12 GB
(-Xmx12g)

12 GB
(-Xmx12g)

1 GB

120 GB

Very Large*

Up to 50K

Up to 50K

Up to 4K

550K

70K

40

8 CPU Cores

40 GB

16 GB
(-Xmx16g)

16 GB
(-Xmx16g)

1 GB

160 GB

 

Table 2: Standalone Instance of the NNM iSPI for IP Telephony for Monitoring the Microsoft IP Telephony or the Acme Session Border Controller

Managed Environment Size

IP Telephony Minimum Hardware System Requirements

Approximate
managed
environment
tier

Number of
discovered
Lync End Users

Number of Sessions (Through Session Border Controllers)**

Number of
discovered Gateways

Number of
discovered
Lync Servers

Number of
discovered
Lync Sites

Number of
concurrent
NNMi
users

CPU (64-bit)
x86-64
AMD641

RAM

***Java heap size for IP Telephony

Java heap size for NNMi

Disk space for
NNM 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 200

Up to 200

1

10

1 Central Site

5

2 CPU Cores

8 GB

2 GB
(-Xmx2g)

2 GB
(-Xmx2g)

1 GB

20 GB

Small

Up to 1K

Up to 1K

Up to 11

Up to 50

1 Central Site and 10 Branches

10

4 CPU cores

12 GB

3 GB
(-Xmx3g)

4 GB
(-Xmx4g)

1 GB

40 GB

Medium*

Up to 5K

Up to 5K

Up to 110

Up to 500

1 Central Site and 100 Branches

20

4 CPU cores

16 GB

4 GB
(-Xmx4g)

6 GB
(-Xmx6g)

1 GB

80 GB

Large*

Up to 10K

Up to 10K

Up to 550

Up to 1K

5 Central Sites and 500 Branches

30

8 CPU cores

24 GB

6 GB
(-Xmx6g)

8 GB
(-Xmx8g)

1 GB

120 GB

Very Large*

Up to 50K

Up to 50K

Up to 1100

Up to 3K

10 Central Sites and 1000 Branches

40

8 CPU cores

32 GB

8 GB
(-Xmx8g)

10 GB
(-Xmx10g)

1 GB

160 GB

*Note: Also assumes up to 30 K, 75K, and 100K CDRs per hour collected and processed by the NNM iSPI for IP Telephony for the medium tier, large tier, and very large tier respectively.

1See above for processor recommendations.

**Indicates the concurrent SIP sessions through an Acme Session Director.

***To tune Java heap size, see the Tuning the jboss Memory for the NNM iSPI for IP Telephony.

Note: If the deployment comprises Microsoft and Cisco/Avaya/Nortel IP telephony environments, use the sizing requirements that are listed in Table 1.

Table 3: Global Network Management: Global Manager Instance of the NNM iSPI for IP Telephony for Monitoring the Cisco, Avaya, or Nortel IP Telephony, or the Acme Session Border Controller

Managed Environment Size

IP Telephony Minimum Hardware System Requirements

Approximate
managed
environment
tier

Number of regionally managed
Directory Numbers (DNs)

Number of Sessions (Through Session Border Controllers)**

Number of
regionally managed nodes that are not hosting IP Phones

Number of
regional managers

Number of
concurrent
NNMi users

CPU (64-bit)
x86-64
AMD642

RAM

***Java heap size for the NNM iSPI for IP Telephony

Java heap size for NNMi

Disk space for
NNM 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.

Medium*

Up to 150K

Up to 150K

Up to 15K

Up to 30

20

4 CPU cores

32 GB

16 GB
(-Xmx16g)

12 GB
(-Xmx12g)

1 GB

160 GB

Large*

Up to 250K

Up to 250K

Up to 20K

Up to 30

40

8 CPU cores

48 GB

24 GB
(-Xmx24g)

16 GB
(-Xmx16g)

1 GB

320 GB

Table 4: Global Network Management: Global Manager Instance of the NNM iSPI for IP Telephony for Monitoring the Microsoft IP Telephony or the Acme Session Border Controller

Managed Environment Size

IP Telephony Minimum Hardware System Requirements

Approximate
managed
environment
tier

Number of
regionally managed Lync End Users

Number of Sessions (Through Session Border Controllers)**

Number of
regionally managed Servers and Gateways

Number of
regional managers

Number of
concurrent
NNMi users

CPU (64-bit)
x86-64
AMD642

RAM

***Java heap size for the NNM iSPI for IP Telephony

Java heap size for NNMi

Disk space for
NNM 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.

Medium*

Up to 150K

Up to 150K

Up to 3K

Up to 30

20

8 CPU cores

24 GB

12 GB
(-Xmx12g)

8 GB
(-Xmx8g)

1 GB

160 GB

Large*

Up to 250K

Up to 250K

Up to 5K

Up to 30

40

8 CPU cores

32 GB

16 GB
(-Xmx16g)

12 GB
(-Xmx12g)

1 GB

320 GB

*Note: Also assumes a total of 375K and 500K CDRs per hour collected across regional manager instances of the NNM iSPI for IP Telephony and forwarded to a single global manager instance of the NNM iSPI for IP Telephony for the medium tier and large tier respectively.

**Indicates the concurrent SIP sessions through an Acme Session Director.

2See above for processor recommendations.

Note: For information about the requirements in a Global Network Management (GNM) environment, see the HP Network Node Manager i Software (NNMi) Device Support Matrix 10.00

***To tune Java heap size, see the Tuning the jboss Memory for the NNM iSPI for IP Telephony.

Note: If the deployment comprises Microsoft and Cisco/Avaya/Nortel IP telephony environments, use the sizing requirements that are listed in Table 4.

Memory, CPU Requirements on the NNM iSPI Performance for Metrics/NPS System for Processing of the Reporting Data Generated by the NNM iSPI for IP Telephony

If you decide to enable various reporting options for the NNM iSPI for IP Telephony, you must provision for incremental memory and CPU usage on the system for the NNM iSPI Performance for Metrics/NPS, which is supplied with the reporting data created by the NNM iSPI for IP Telephony. You must make such a provision for the following scenarios:

See the NNM iSPI Performance for Metrics/NPS Support Matrix document for more information on minimum system requirements (including those for the CPU and memory) for appropriately evaluating the CPU and memory requirements and taking adequate measures before deploying the NNM iSPI Performance for Metrics/NPS.

Also, make sure that the various parameters related to the NPS database and BI server are appropriately tuned for your scale. Default settings created by the NPS installation for these parameters might not be appropriate for the scale of your deployment.

If you want to disable the IP Telephony reporting packages for a specific IP Telephony vendor (Avaya, Cisco, Microsoft, or Acme), you can accomplish this by uninstalling the NPS report extension pack containing the specific reporting packages from NNM iSPI for IP Telephony. See the iSPI for IP Telephony and NPS documentation for instructions on uninstalling a specific extension pack.

System sizing NNM iSPI Performance for Metrics/NPS System for Processing of the Reporting Data Generated by the NNM iSPI for IP Telephony

The following table helps you to identify NPS system resources required for the NNM iSPI for IP Telephony reports. These are incremental additional demands on CPU, memory, and disk space on the NPS system because of the IP Telephony report data load, summarization, and retrieval using IP Telephony reports.

Table 5: Standalone instance of the NNM iSPI for IP Telephony integrated with standalone Network Performance Server (NPS): NPS system Minimum Hardware System Requirements

Approximate managed
environment tier ^

CPU (64-bit)
x86-64 AMD64

RAM

Disk space for IP Telephony historical reporting
data storage in the Sybase DB (the NPS database)
(DataDir on the NPS system)^^

Small

4 CPU cores

8 GB

1 TB

Medium

8 CPU cores

16 GB

1 TB

Large

16 CPU cores

32 GB

4 TB

Very Large

16 CPU cores

32 GB

8 TB

^ Refer to tiers in Table 1 and Table 2 for standalone or regional manager instance of the NNM iSPI for IP Telephony deployment.

^^ Indicates that the NNM iSPI Performance for metrics DataDir is configured during installation of the NNM 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 the NNM iSPI Performance for Metrics is set to a high value, make sure that adequate free disk space is available on the system on which you have installed the NNM iSPI Performance for Metrics. You can refer to the NNM iSPI Performance for Metrics Installation Guide to configure these parameters.

The following table provides information on Global Manager instance of the NNM iSPI for IP Telephony integrated with a Global Manager NPS system in Global Network Management (GNM) deployment of the NNM iSPI for IP Telephony.

Table 6: Global Manager instance of the NNM iSPI for IP Telephony integrated with Global Manager instance of Network Performance Server (NPS): NPS system Minimum Hardware System Requirements

Approximate managed
environment tier ^

CPU (64-bit)
x86-64 AMD64

RAM

Disk space for IP Telephony historical reporting
data storage in the Sybase DB (the NPS database)
(DataDir on the NPS system)^^

Medium

24 CPU cores

64 GB

16 TB

Large

24 CPU cores

64 GB

24 TB

^ See the tiers in Table 3 and Table 4 for the Global Network Management (GNM): Global Manager instance of the NNM iSPI for IP Telephony deployment.

^^ Indicates that the NNM 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 the NNM iSPI Performance for Metrics is set to a high value, make sure that adequate free disk space is available on the system on which you have installed the NNM iSPI Performance for Metrics. You can refer to the NNM iSPI Performance for Metrics Installation Guide to configure these parameters.

Note: For information about the disk I/O recommendations, see the NNM iSPI Performance for Metrics Software Support Matrix 10.00.

Note: In Table 5 and Table 6, the disk space requirements of the NPS database are valid for the following data retention criteria:

Additional Information

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 NNM iSPI for IP Telephony process by the following command: ovstop –c iptjboss
  2. Edit the nms-ipt.jvm.properties file available in the following directory:
  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 NNM iSPI for IP Telephony process by the following command: ovstart –c iptjboss

For more information about NNMi values, see the HP Network Node Manager i Software (NNMi) Device Support Matrix 10.00.

Operating System

Windows

Supported Versions

Notes

Linux

Supported Versions

Virtual Memory / Swap Space

High Availability

The NNM iSPI for IP Telephony can run on certain high availability systems with additional configuration. For more information about the instructions to install and configure NNM iSPI for IP Telephony on high availability systems, see the NNMi Deployment Reference and HP Network Node Manager iSPI for IP Telephony Software Installation Guide 10.00. The following configurations are supported:

Database

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

Web Browser

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 11.2.202.285 or later on Linux or version 11.7.700.202 or later on Windows.  The Adobe Flash Player is available from www.adobe.com/go/getflash/.

Internationalization and Localization Support

NNM iSPI for IP Telephony 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.

On Windows systems, the NNM iSPI for IP Telephony does not support installation using directory paths with localized characters; path names for %NnmInstallDir% and %NnmDataDir% can contain English characters only. Similarly for CLI, complete localization takes place only when additional languages are installed. Changing only the display languages will result in a mix of localized and English messages.

The NNM iSPI for IP Telephony is localized (or translated) to German, French, Japanese, and Simplified Chinese. When those localized packages are installed, German, French, Japanese, or Simplified Chinese are displayed as output. With all other locales, English strings appear as output.

NOTE: Localization support only applies to the Localization release of NNM iSPI for IP Telephony 10.00, not to the initial English-only release.

Supported Devices

IP Telephony Devices

The following tables list the IP telephony devices supported by this version of the NNM iSPI for IP Telephony:

For the latest updates to the NNMi devices, see the HP Network Node Manager i Software (NNMi) Device Support Matrix 10.00.

Supported Microsoft Lync Server Versions

The following Microsoft Lync versions are supported:

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:

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.

Legal Notices

HP Confidential ©Copyright 2008-2014 Hewlett-Packard Development Company, L.P.

Warranty

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.

Restricted Rights Legend

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.

Copyright Notices

HP Confidential ©Copyright 2008-2014 Hewlett-Packard Development Company, L.P.

Trademark Notices

Adobe™ is a trademark of Adobe Systems Incorporated.

AMD is a trademark of Advanced Micro Devices, Inc.

Google™ is a trademark of Google Inc.

Intel® and Itanium® are trademarks of Intel Corporation in the U.S. and other countries.

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

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Acknowledgements

This product includes software developed by Apache Software Foundation. (http://www.apache.org)

This product includes software developed by Indiana University Extreme! Lab.

This product includes software developed by SSHTools (http://www.sshtools.com/).

For information about third-party license agreements, see the license-agreements directory on the product installation media.

Oracle Technology — Notice of Restricted Rights

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 America, Inc., 500 Oracle Parkway, Redwood City, CA 94065. For the full Oracle license text, see the license-agreements directory on the NNMi product DVD.