NNMi 8.1x Support Matrix Updates

Last Updated: 24 January, 2014

This document contains updates to the HP Network Node Manager i-series (NNMi) 8.1x support matrix. You may also check for online NNMi 8.1x release note updates or the device support matrix.

05/21/2010: Managed Environment Size and NNM Minimum Hardware System Requirements Update

The Table for the Managed Environment Size and NNM Minimum Hardware System Requirements has been updated as follows:

Single System Managed Environment Size Recommended Hardware System Requirements

Approximate
managed
environment
tier¹

Number of
discovered
nodes

Number of
discovered
interfaces
Number of
polled
addresses Number of
polled
interfaces Number of
custom polled
objects Number of
polled
node
components
Number of
concurrent
users
CPU (64-bit)
IPF
x86-64
AMD64
SPARC² RAM³ Recommended Java heap size
(see Tuning the jboss Memory Size)⁴ Disk space for
application installation
($NnmInstallDir)⁵ Disk space for database and
data during execution
($NnmDataDir)⁶

Entry

Up to 250

15k

500

2500

1200

500

5

2 CPU cores

4 GB

2 GB
(-Xmx2g)

3 GB

10 GB

Small

250 - 3k

120k

5k

10k

30k

40k

10

4 CPU cores

8 GB

4 GB
(-Xmx4g)

3 GB

30 GB

Medium

3k – 8k

400k

10k

50k

50k

60k

25

4 CPU cores

16 GB

7 GB
(-Xmx7g)

3 GB

40 GB

Large

8k – 18k

900k

20k

70k

75k

80k

40

8 CPU cores

24 GB

10 GB
(-Xmx10g)

3 GB

60 GB

¹ To view discovered object counts and polled object counts, see the Help → About window.
² Minimum of 2.5GHz for x64 and 1.4GHz for IPF or RISC.
³ If you are running additional applications or NNM iSPIs, increase resources appropriately. If you are planning to use any of the NNM iSPI Performance products and are managing at the Large tier, it is recommended that the NNM iSPI Performance products be installed on a separate server from NNMi.
⁴ 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.
⁵ $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/. Disk space estimates are when using embedded PostgreSQL. If using an external Oracle database, only 10-20 GB is required for NnmDataDir.

Single System Managed Environment Size	Recommended Hardware System Requirements
Approximate managed environment tier¹	Number of discovered nodes	Number of discovered interfaces	Number of polled addresses	Number of polled interfaces	Number of custom polled objects	Number of polled node components	Number of concurrent users	CPU (64-bit) IPF x86-64 AMD64 SPARC²	RAM³	Recommended Java heap size (see Tuning the jboss Memory Size)⁴	Disk space for application installation ($NnmInstallDir)⁵	Disk space for database and data during execution ($NnmDataDir)⁶
Entry	Up to 250	15k	500	2500	1200	500	5	2 CPU cores	4 GB	2 GB (-Xmx2g)	3 GB	10 GB
Small	250 - 3k	120k	5k	10k	30k	40k	10	4 CPU cores	8 GB	4 GB (-Xmx4g)	3 GB	30 GB
Medium	3k – 8k	400k	10k	50k	50k	60k	25	4 CPU cores	16 GB	7 GB (-Xmx7g)	3 GB	40 GB
Large	8k – 18k	900k	20k	70k	75k	80k	40	8 CPU cores	24 GB	10 GB (-Xmx10g)	3 GB	60 GB

03/25/2010: Firefox browser version 3.5 or higher is not supported with NNM 8.1x

NNM 8.1x does not support Mozilla Firefox browser version 3.5 or higher.

02/25/2010: NNM i-series Smart Plug-ins Supported Platforms

For complete information about the supported platforms for any NNM i-series Smart Plug-ins, see that product's support matrix.

02/01/2010: NNMi 8.1x Patch 7 now supports Windows Server 2008

Windows Server 2008 Service Pack 2 and Windows Server 2008 R2 are now supported by NNMi 8.1x Patch 7.

02/01/2010: NNMi 8.1x Patch 7 now supports High Availability on Linux with Veritas Cluster Server (VCS)

NNMi 8.1x Patch 7 now supports Linux systems with Veritas Cluster Server (VCS). For more information, see the Deployment Guide.

11/11/2009: NNMi 8.1x Patch 6 adds additional device support

Please see the Device Support Matrix for more details.
- HP ProCurve Component Health for Performance monitoring
- Juniper Component Health monitoring on EX, MX, SRX, E, M, J, T and NetScreen NS, SSG
- Foundry Component Health monitoring on FastIron switches
- for Nortel Alteon devices
- for Nortel Baystack Ethernet Routing Switches
- for Nortel Secure Routers

11/11/2009: NNMi 8.1x Patch 6 now supports VMWare ESX 4.x

NNMi 8.1x Patch 6 now supports VMWare ESX Server 4.x. The virtual environment must meet the x86-64 or AMD64 hardware requirements listed in the HP Network Node Manager i-series Software System and Device Support Matrix available on the HP Manuals web site at support.openview.hp.com/selfsolve/manuals

11/11/2009: NNMi 8.1x Patch 6 now supports Linux Red Hat 5.3

NNMi 8.1x Patch 6 now supports Linux Red Hat 5.3. In order to properly install and configure NNM 8.1x Patch 6 on RH 5.3, please follow the installation and configuration steps for Linux Red Hat 5.2 (listed here.)

11/11/2009: NNMi 8.1x Patch 6 now supports Internet Explorer Version 8 in Compatibility View

NNMi 8.1x Patch 6 now supports Internet Explorer Version 8 in Compatibility View. Use the Compatibility View Settings dialog to add the NNMi server to the list in Compatibility View.

11/11/2009: Known Problem with Linux Systems: Out of Memory error with postgres process

Linux systems running NNMi 8.1x with a embedded database may encounter an out of memory error and the postgres process is killed due to overcommitted memory. On Linux 2.6 and later, modify the kernel's behavior so that it will not "overcommit" memory. This is done by selecting strict overcommit mode via sysctl:
sysctl -w vm.overcommit_memory=2
or placing an equivalent entry in /etc/sysctl.conf.

11/11/2009: Linux Systems need 127.0.0.1 localhost entry in /etc/hosts

On Linux 5.2 and 5.3 systems, NNMi processes may fail to start if the entry "127.0.0.1 localhost" is missing in /etc/hosts. If this entry does not exist, add this entry and reboot.

11/11/2009: HP PA-RISC architecture is not supported on NNM 8.1x

HP PA-RISC architecture is not supported on NNM 8.1x.

05/01/2009: NNMi 8.1x Patch 3 Now Supports Linux Red Hat 5.2

NNMi 8.1x Patch 3 supports Linux Red Hat 5.2 after the following configuration steps. The configuration includes steps before NNMi 8.10 product installation, after installation, and before patch installation. Firewall configuration might be required.

Do the following steps:

Verify the SELinux configuration:
- If SELinx is set to Permissive or Disabled, it can be left with its current value.
- If SELinux is set to Enforcing, change it to Permissive in one of the following ways:
  - Edit the /etc/sysconfig/selinux file.
  - Use the System → Administration → SELinux Management tool to change the value.
Install the NNMi 8.10 product.
After installation is complete, run the following command:
  chcon -t textrel_shlib_t /opt/OV/lib/*
Error messages from chcon command such as:
  chcon: /opt/OV/lib/libxaLan-c.so.18: No such file or directory
  chcon: /opt/OV/lib/libxaLanMsg.so.18: No such file or directory
  chcon: /opt/OV/lib/libxerces-c.so.25: No such file or directory
can safely be ignored.
If you changed the SELinux configuration in step 1, restore SELinux to the previous value.

A firewall may block access to the NNMi Console, NNMi SPIs, and Application Failover. If you have problems accessing these functions, the firewall might be active and blocking access. Ensure that the following ports are opened up to gain full access to NNMi and NNMi SPI functionality:

Port Name	Default Value	Comments
`jboss.http.port`	`80/tcp`	`If the port number is changed from 80, the port might be blocked by the firewall. NNMi Console will not work. If a different port number was specified during installation, that port needs to be opened up instead of 80.`
`jboss.ejb3.port`	`3873/tcp`	`If iSPIs are being used, this port must be made accessible to remote systems running iSPIs.`
`Application Failover Port`	`45588/udp`	`This port must be unblocked if Application Failover is used.`
`SNMP Ports`	`161/udp, 162/udp`	`These ports must be unblocked for NNMi to receive traps.`

Once the configuration steps are completed, then install NNMi Patch 3.

05/01/2009: Need to Increase Semaphores for Solaris Systems

For Solaris systems, NNMi 8.1x requires that the semaphore count be increased to 256 to avoid problems.
- To make this change, run the following commands as root;
  prctl -n project.max-sem-ids -v 256 -r -i project user.root
  projmod -a -K "project.max-sem-ids=(priv,256,deny)" user.root