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
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:
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 |
Number of |
Number of Sessions (Through Session Border Controllers)** |
Number of |
Number of |
Number of |
Number of |
|
RAM |
***Java heap size the NNM iSPI for IP Telephony
|
Java heap size for NNMi |
Disk space for |
Total Disk Space for Database
and Data During Execution |
Entry |
Up to 500 |
Up to 500 |
Up to 100 |
7K |
2500 |
5 |
2 CPU Cores |
9 GB
|
3 GB |
3 GB |
1 GB |
20 GB |
Small |
Up to 3K |
Up to 3K |
Up to 500 |
40K |
2500 |
10 |
4 CPU Cores |
10 GB
|
4 GB |
4 GB |
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 |
8 GB |
1 GB |
80 GB |
Large* |
Up to 30K |
Up to 30K |
Up to 3K |
250K |
50K |
30 |
8 CPU Cores |
28 GB
|
12 GB |
12 GB |
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 |
16 GB |
1 GB |
160 GB
|
Table 2: Standalone Instance of the NNM iSPI for
IP Telephony for Monitoring the Microsoft IP Telephony |
||||||||||||
Managed Environment Size |
IP Telephony Minimum Hardware
System Requirements |
|||||||||||
Approximate |
Number of |
Number of Sessions (Through Session Border Controllers)** |
Number of |
Number of |
Number of |
Number of |
CPU (64-bit) |
RAM |
***Java heap size for IP Telephony
|
Java heap size for NNMi |
Disk space for |
Total Disk Space for Database and Data During Execution |
Entry |
Up to 200 |
Up to 200 |
1 |
10 |
1 Central Site |
5 |
2 CPU Cores |
8 GB |
2 GB |
2 GB |
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 |
4 GB |
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 |
6 GB |
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 |
8 GB |
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 |
10 GB |
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 |
Number of regionally managed |
Number of Sessions (Through Session Border Controllers)** |
Number of |
Number of |
Number of |
|
RAM |
***Java heap size for the NNM iSPI for IP
Telephony
|
Java heap size for NNMi |
Disk space for |
Total Disk Space for Database
and Data During Execution |
Medium* |
Up to 150K |
Up to 150K |
Up to 15K |
Up to 30 |
20 |
4 CPU cores |
32 GB |
16 GB |
12 GB |
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 |
16 GB |
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 |
Number of |
Number of Sessions (Through Session Border Controllers)** |
Number of |
Number of |
Number of |
CPU (64-bit) |
RAM |
***Java heap size for the NNM iSPI for IP
Telephony
|
Java heap size for NNMi |
Disk space for |
Total Disk Space for Database
and Data During Execution |
Medium* |
Up to 150K |
Up to 150K |
Up to 3K |
Up to 30 |
20 |
8 CPU cores |
24 GB |
12 GB |
8 GB |
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 |
12 GB |
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.
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.
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 |
CPU (64-bit) |
RAM |
Disk space for IP Telephony historical
reporting |
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 |
CPU (64-bit) |
RAM |
Disk space for IP Telephony historical
reporting |
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:
To change the jboss Maximum Java Heap Size (‑Xmx) or other Java Virtual Machine parameters, follow these steps:
For more information about NNMi values, see the HP Network Node Manager i Software (NNMi) Device Support Matrix 10.00.
Supported Versions
- Windows Server 2008 R2 x64 Datacenter Edition with SP1 (or later service pack)
- Windows Server 2008 R2 x64 Enterprise Edition with SP1 (or later service pack)
- Windows Server 2008 R2 x64 Standard Edition with SP1 (or later service pack)
- Windows Server 2012 R2 and Windows Server 2012 Datacenter Edition (MS IPT Proxy is not supported; see a)
- Windows Server 2012 R2 and Windows Server 2012 Standard Edition (MS IPT Proxy is not supported; see a)
Notes
a The MS IPT Proxy component is not supported on Windows Server 2012 R2 and Windows Server 2012. You must install the component on a separate server running one of the following operating systems:
(You need to install MS IPT Proxy only if you want to manage a Lync environment.)
- Windows Server 2008 R2 x64 Datacenter Edition with SP1 (or later service pack)
- Windows Server 2008 R2 x64 Enterprise Edition with SP1 (or later service pack)
- Windows Server 2008 R2 x64 Standard Edition with SP1 (or later service pack)
- Windows operating systems on Itanium Processor Family (IPF) is not supported.
- Windows 32-bit operating systems are not supported.
- 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 2008 R2, C:\ProgramData\HP\HP BTO Software\shared\nnm\databases).
Supported Versions
- Red Hat
- Red Hat Enterprise Linux Server 6.4 (or later minor version)
- SUSE Linux Enterprise Server 11 SP3
- Oracle Linux 6.4 (Red Hat Compatible Kernel) or later minor version (High Availability is not supported)
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:
Veritas Cluster Server (VCS) version 6.0.
Notes
The corresponding version of Red Hat Cluster Suite (RHCS) for the supported versions of the Red Hat Enterprise Server operating system.
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.
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/.
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.
The following tables list the IP telephony devices supported by this version of the NNM iSPI for IP Telephony:
Devices/Entities |
Version/Model/Type/Supported Protocol |
Cisco Unified Communications Manager |
5.x,6.x,7.x, 8.x, and 9.x |
Voice Gateway |
All Cisco IOS-based gateways, Cisco VG224 Analog Gateways, and Cisco VG 248 Analog Gateways (supports Cisco Voice Gateways running MGCP and H.323 protocols; supports T1/E1 PRI, T1/E1 CAS, FXS, FXO, E&M voice interfaces). |
IP Phone |
Supports IP phones running on the SIP and SCCP (or Skinny) protocols. Supports Cisco IP Communicator Soft Phones. Also supports all other models of Cisco Unified IP Phone appliances. |
Gatekeeper |
All Cisco IOS routers that can run the Cisco H.323 Gatekeeper service. CISCO-GATEKEEPER-MIB must be accessible on the Cisco IOS-based device that runs the Cisco Gatekeeper Service. |
Unity |
|
Cisco Call Manager Express (CCME) |
All Cisco IOS routers that can run the CCME service. |
Survivable Remote Site Telephony (SRST) |
All Cisco IOS routers that can run the SRST service. |
Devices/Entities |
Version/Model/Type/Supported Protocol |
Communication Manager |
Supports Communication Manager software/Firmware version 4.x/ 5.x/6.x on the following servers :
Note:
|
Local Survivable Processor |
Supports Communication Manager software/Firmware version 4.x/5.x/6.x on the following servers :
|
H.248 Media Gateways |
Supports Communication Manager software/Firmware version 4.x/5.x/6.x on the following media gateways:
|
Port Network Media Gateway |
Supports Communication Manager software/Firmware version 4.x/5.x/6.x on the following port network media gateway:
|
IP Phones
|
Communication Manager software/Firmware 4.x/5.x/6.x compliant IP phones. The supported protocols include SIP and H.323. On the Avaya ONE –X soft phones, at the least, Avaya one-X Communicator Release 5.2 with Service Pack 4 (Product Version 5.2.0.23) or its equivalent Service Pack for Avaya one-X Communicator Release 6.x must be installed. The Service Pack level must include the fix for the issue with malformed CNAME in RTCP packets or the enhancement titled “Updated the CNAME in the RTCP packet for more accurate monitoring traceability.” |
Devices/Entities |
Version/Model/Type/Supported Protocol |
Call Server |
Models running the
software version 5.x |
Signaling Server |
Models running the
software version 5.x |
Media Gateway |
Media Gateway
Controller Card (MGC) with DSP daughter boards, Media Card (MC), Voice
Gateway Media Card (VGMC); MC 32 and MC 32S cards are supported in the MC or
VGMC category. |
IP Phone |
The following Nortel IP phone models are supported:
|
Devices/Entities |
Version/Model/Type/Supported Protocol |
Microsoft Lync Server 2010 Gateway |
|
Devices/Entities | Version/Model/Type/Supported Protocol |
Acme Packet Enterprise Session Border Controller |
3820, 4500 |
For the latest updates to the NNMi devices, see the HP Network Node Manager i Software (NNMi) Device Support Matrix 10.00.
The following Microsoft Lync versions are supported:
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.
HP Confidential ©Copyright 2008-2014 Hewlett-Packard Development
Company, L.P.
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.
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.
HP Confidential ©Copyright 2008-2014 Hewlett-Packard Development Company, L.P.
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.
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.
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.