Introduction
Hardware and Software
Requirements
Same Server Install
Dedicated Server Install
Hardware
Operating System
Web Browser
Legal Notices
This document describes system
requirements for the HP Network Node Manager i Software Smart Plug-in
Performance for Metrics (iSPI Performance for Metrics) and Network Performance
Server (NPS) version 9.10.
The NPS stores, aggregates, and provides reports for collected performance
data. It is the foundation for operational reports on NNMi. Other iSPIs rely
upon the NPS for report presentation functionality. The iSPI Performance for
Metrics adds the performance management capability to NNMi by analyzing,
processing, and aggregating a range of standard metrics collected by NNMi from
different network elements.
This document provides information about supported deployment configurations
that is not found in Release Notes or the NPS Installation Guide. When you are
ready to install the product, refer to the installation guide. The installation
guide is provided in Adobe Acrobat (.pdf) format on the product's installation
media. Installing the NPS copies the installation guide to the Docs directory.
You can install the NPS on a dedicated system,
separate from NNMi, or you can install it on the same system as NNMi. Before
installing the NPS and your iSPIs, make sure that your system meets the
following minimum requirements. Note the following points:
·
If you are upgrading
from the version 9.00 installation of iSPI Performance for Metrics, check the
hardware tables below for the latest requirements and see the HP Network Node
Manager i Software Smart Plug-in Performance for Metrics/ Network Performance
Server Installation Guide for instructions and
available upgrade paths.
·
The data directory
(NNMDataDir) will contain the bulk of the collected and aggregated data and as
such should be on the fastest and largest disk partition. For UNIX platforms,
this will be /var/opt/OV.
·
By default, the NPS
stores hourly aggregated data for 70 days. In addition, it stores very fine
grain, as collected, data in an archive table. The default retention period for
this type of fine grain data is 14 days. Most of the required disk space for
the iSPI is consumed by this detailed archive data storage. To change retention
periods from the default, use the configuration utility. The maximum
configurable retention period is 400 days. You can modify the settings for
hourly and archive table retention independently of each other, but the hourly
retention should always be equal to or greater than the detailed archive
retention period. Care should be taken to monitor the disk space usage on the
system after a change to this parameter. The tables below quote disk space
requirements for an out of the box system as well as one with retention at the
maximum.
·
These hardware
recommendations are a guideline only, based upon the use of the HP Network Node
Manager i Software Smart Plug-in Performance for Metrics (iSPI Performance for
Metrics) package. They do not take account of additional factors which may
affect the sizing of your application—such as the installation of the iSPI
Performance for Traffic, or additional custom collection reporting which may be
configured after installation. Every installed package using NPS for reporting,
and every custom collection with reporting enabled, will require additional
disk and processing capacity on the NPS system.
·
The NPS 9.10 does not
support the application failover feature. However, you can use the NPS with an
NNMi management server that has been configured for application failover. If
the NNMi management server is configured for application failover, you must
install the NPS on a dedicated server (and not on the NNMi management server).
·
NNMi has the ability to
discover topology elements such as nodes and interfaces, but not all discovered
elements will have performance data collected and reported upon. The numbers
quoted below relate only to performance polled elements.
·
The figures in the
tables below quote hardware requirements for an NPS running with a 5 minute
polling frequency. The number of polled interfaces and components is stated for
each scale. Example: 130k/130k means 130,000 interfaces and 130,000 component
sensors simultaneously.
o
Higher polling
frequencies will result in more data. So 400K interfaces at 5 minutes results
in the same number of collected data points as 80K interfaces at 1 minute
polling frequency.
o
Custom, user-defined
collections will result in additional storage requirements.
o
Adding other iSPIs to
your platform, such as iSPI Performance for Quality Assurance, iSPI for IP
Telephony, or iSPI for MPLS, will result in additional storage and processing
requirements for the NPS.
o
Monitor disk usage and
processing performance on the system on a daily basis after introducing a new
custom collection or iSPI.
The table below outlines the requirements for CPU, RAM
and disk space when NNMi and the NPS are on the same system. Note that the CPU,
RAM, and Disk figures represent the total requirements for the system and
include the combined capacity required for NNMi and the NPS. You must ensure
that this host also meets any additional criteria defined in the NNMi support
matrix.
NOTE:
·
When the NPS is
installed on a system that hosts NNMi, half of the system RAM will be consumed
by the NPS. The figures below for RAM resources take account of the combined
needs of NNMi and NPS and are especially important when running the NPS with
several iSPIs providing data.
·
Once installed, you can
use the Managed Inventory report to see the variety of collected elements for
each iSPI. For example : looking at the count of distinct Qualified
Interface Names in the Interface Health Managed Inventory
report will tell you how many unique interfaces have had performance data
collected within the selected time period.
·
While it is a supported option
to have NNMi and NPS on the same system for ‘Large’ scale environments, it is
recommended that the NPS is installed on a separate, standalone system.
·
HP does not support the
NPS being installed on the same server as NNMi for ‘Very Large’ scale environments.
|
Management
Environment Size |
|
NNMi +
iSPI Minimum System Requirements |
|
||||||
|
Approximate
managed environment tier |
Number
of |
CPU
(64-bit) |
RAM |
Disk
space for |
Disk
hardware required for NNMDataDir |
Additional
disk space for database and data during execution (NNMDataDir) 14 day
archive retention, 70 day
hourly retention |
Additional
disk space for database and data during execution (NNMDataDir) 70 Day
Archive Retention 70 day
hourly retention |
Additional
disk space for database and data during execution (NNMDataDir) 70 Day
Archive Retention 400 day
hourly retention |
|
|
Entry |
Up to 2500 |
8 CPU (2.5GHz for x64) |
16 GB |
10 GB |
1 SCSI or SATA disk drive |
200 GB |
300 GB |
300 GB |
|
|
Small |
Up to 10K/10K |
8 CPU (2.5GHz for x64) |
16 GB |
10 GB |
1 SCSI or SATA disk drive |
300 GB |
400 GB |
1 TB |
|
|
Medium |
Up to 50K/50K |
8 CPU (2.5GHz for x64) |
32 GB |
10 GB |
RAID 1+0 or 5/6 with write cache recommended |
800 GB |
1.5 TB |
4 TB |
|
|
Large |
Up to 130K/130K |
16 CPU (2.5GHz for x64) |
64 GB |
10 GB |
High performance SAN storage |
2 TB |
3 TB |
10 TB |
|
|
Very Large |
Same
server install not supported for this scale |
-- |
-- |
|
-- |
-- |
|
|
|
If you plan on installing the NPS on a separate
machine from NNMi then you should ensure the following criteria are met. Note
that NPS sizing requirements are driven by the amount of data generated by the
custom collections and iSPIs which will supply it. The references provided in
this document for sizing and scalability are a guideline only and are based
upon the Metrics SPI, using the number of interfaces and node components that
NNMi is polling for performance data. - the total number of interfaces or
components discovered by NNMi is not relevant for this system. Enabling
performance polling on NNMi will have an impact on the NNMi system itself so
ensure that your NNMi host meets the criteria described in the section below as
well as any criteria defined within the NNMi support matrix.
|
Management
Environment Size |
|
iSPI
Minimum System Requirements |
|||||||
|
Approximate
managed environment tier |
Number
of performance polled interfaces / components at 5 minute polling interval |
CPU (64-bit) AMD64 |
RAM |
Disk
space for |
Disk
space for database and data during execution (NNMDataDir) |
Disk
space for database and data during execution (NNMDataDir) 14 day
detail archive, 70 day
hourly retention |
Disk
space for database and data during execution (NNMDataDir) 70 day
detail archive, 70 day hourly retention |
Disk space
for database and data during execution (NNMDataDir) 70 day
detail archive, 400 day
hourly retention |
|
|
Small |
Up to 5K/5K |
8 CPU (2.5GHz for x64) |
16 GB |
5 GB |
1 SCSI or SATA disk drive |
300 GB |
400 GB |
1 TB |
|
|
Medium |
Up to 60K/60K |
8 CPU (2.5GHz for x64) |
24 GB |
5 GB |
RAID 1+0 or 5/6 with write cache recommended |
800 GB |
1.5 TB |
4 TB |
|
|
Large |
Up to 130K/130K |
16 CPU (2.5GHz for x64) |
48 GB |
5 GB |
RAID 1+0 or 5/6 with write cache recommended |
2 TB |
3 TB |
10 TB |
|
|
Very Large |
Up to 400K/200K |
16 CPU (2.5GHz for x64) |
72 GB |
5 GB |
High performance SAN storage |
4 TB |
8 TB |
20 TB |
|
·
VMware ESX Server 4.0 or 4.1
·
Virtual environment must
meet the x86-64 or AMD64 hardware requirements listed here.
·
Intel 64-bit (x86-64) or
AMD 64-bit (AMD64)
o
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
o
Caution: IPF hardware running the Windows or Linux operating system is not supported
·
Virtual Memory/Swap Space
o
Recommend 2 times
physical memory and at least 32 GB
o
Verify virtual memory
via System Properties on Windows
Supported Versions
·
Windows Server 2008 x64
Datacenter Edition with Service Pack 2
·
Windows Server 2008 R2
x64 Datacenter Edition
·
Windows Server 2008 x64
·
Windows Server 2008 R2
x64
·
Windows Server 2008 x64
Standard Edition with Service Pack 2
·
Windows Server 2008 R2
x64 Standard Edition
Notes
·
Windows 32-bit operating
systems are not supported
·
Windows operating
systems on Itanium Processor Family (IPF) are not supported
·
IPv6 is not supported on Windows operating
systems.
NOTE:
·
Anti-virus and backup software
can interfere with the operation of the NPS if the software locks files while
the NPS is running. Any application that locks files should be configured to
exclude the NPS install and data directories (on Windows 2003, C:\Documents and Settings\All Users\Application
Data\HP HP BTO Software\NNMPerformanceSPI;
or on Windows 2008, C:\ProgramData\HP\HP
BTO Software\NNMPerformanceSPI).
·
Windows 2008 includes
the concept of User Access Control (UAC). Users who are part of the
Administrator group may not have full Administrator privileges. All scripts and
commands associated with NPS will detect and warn if the user is not elevated –
they should be run with full Administrator access. To achieve this, right-click
on the Command Tool icon and choose ‘Run as Administrator.’
·
Red Hat Enterprise
Server AS 5.3 (or newer minor version)
·
Red Hat Enterprise
Server ES 5.3 (or newer minor version)
This table illustrates the combinations of operating
systems which are supported with the NPS in a distributed installation
environment. Note that NPS version 9.1 should always be used at the same
version level as NNMi.
|
|
NPS |
||
|
Windows |
Linux |
||
|
NNMi |
Windows |
þ |
|
|
Linux |
þ |
þ |
|
|
HPUX |
þ |
þ |
|
|
Solaris |
þ |
þ |
|
The NPS/iSPI Performance for Metrics can run on the
following high availability systems with additional configuration:
·
Microsoft:
o
Microsoft Cluster
Service for Windows Server 2008 or 2008 R2
·
Linux
o
Veritas Cluster Server
version 5.0 or 5.1
o
HP Serviceguard version
11.18
o
Disable all pop-up
window blockers for the browser (see instructions on the NNMi console sign-in
page or in the Installation Guide).
o
Enable cookies for the
browser (see instructions on the NNMi console sign-in page or in the Installation Guide).
o
Enable JavaScript for
the browser.
o
Enable VML for Internet
Explorer browsers (or Maps will not properly display).
Caution: The following browsers are not
supported:
o
Microsoft Internet
Explorer version 9
o
Microsoft Internet
Explorer version 8 when running in Compatibility View mode
o
Be sure to disable
Compatibility View in Internet Explorer 8 using Tools->Compatibility View
Settings (uncheck all options)
o
Microsoft Internet
Explorer version 7
o
Microsoft Internet
Explorer version 6
o
Apple Safari (all
versions)
o
Opera (all versions)
o
Google™ Chrome (all
versions)
o
Microsoft Internet
Explorer version 8 (not running in Compatibility View mode).
o
Mozilla Firefox version
3.6.13 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.
The following products have been tested to co-exist on
the same system as NPS 9.10:
·
HP Network Node Manager
i 9.10 Software
·
HP Network Node Manager
i Advanced 9.10 Software
·
HP Network Node Manager
iSPI Performance for Traffic 9.10 Software
·
HP Network Node Manager
iSPI Performance for Quality Assurance 9.10 Software
·
HP Network Node Manager
iSPI Performance for Metrics 9.10 Software
Check with Support regading the integration between Performance Insight and version 9.10 of NPS.
©Copyright 2009-2011 Hewlett-Packard Development
Company, L.P.
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.
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.
For information about third-party license agreements,
see the license-agreements directory on the product installation DVD-ROM.
To view open source code, see the license-agreements/source
and license-agreements/CygwinSources directories on the product installation media.
Adobe® is a trademark of Adobe Systems Incorporated.
Java is a registered trademark of Oracle and/or its affiliates.
Microsoft®, Windows® and Windows® XP are U.S. registered trademarks of Microsoft
Corporation.
UNIX® is a registered trademark of The Open Group.
This product includes libjpeg library. This software
is copyright (C) 1991-1998, Thomas G. Lane.
The Graphics Interchange Format(c) is the Copyright property of CompuServe
Incorporated. GIF(sm) is a Service Mark property of CompuServe Incorporated.
This product includes libxml2 library. Copyright (C) 1998-2003 Daniel Veillard.
All Rights Reserved.
This product includes libxp library. Copyright © 2001,2003 Keith Packard.