HPE NetworkNodeManageri Software - Dimiter Todorov · HPE NetworkNodeManageri Software...

HPE Network Node Manager iSoftwareSoftware Version: 10.20for the Windows® and Linux® operating systems

Support Matrix

Document Release Date: July 2016Software Release Date: July 2016

Legal Notices

WarrantyThe only warranties for Hewlett Packard Enterprise products and services are set forth in the express warrantystatements accompanying such products and services. Nothing herein should be construed as constituting anadditional warranty. HPE 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 LegendConfidential computer software. Valid license from HPE required for possession, use or copying. Consistent withFAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Datafor Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

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 inthe applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal AcquisitionRegulations are 'restricted computer software' and use, duplication, and disclosure of the programs, includingdocumentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-RestrictedRights (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.

Copyright Notice© Copyright 2007 - 2016 Hewlett Packard Enterprise Development LP

Trademark NoticesAdobe® is a trademark of Adobe Systems Incorporated.

Apple is a trademark of Apple Computer, Inc., registered in the U.S. and other countries.

AMD is a trademark of Advanced Micro Devices, Inc.

Google™ is a registered trademark of Google Inc.

Intel®, Intel® Itanium®, Intel® Xeon®, and Itanium® are trademarks of Intel Corporation in the U.S. and othercountries.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

Internet Explorer, Lync, Microsoft, Windows, and Windows Server are either registered trademarks or trademarks ofMicrosoft Corporation in the United States and/or other countries.

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

Red Hat® Enterprise Linux Certified is a registered trademark of Red Hat, Inc. in the United States and othercountries.

sFlow is a registered trademark of InMon Corp.

UNIX® is a registered trademark of The Open Group.

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

This product includes software developed by the Visigoth Software Society (http://www.visigoths.org/).

Documentation UpdatesThe title page of this document contains the following identifying information:

Support Matrix

HPE Network NodeManager i Software (10.20) of 32

l Software Version number, which indicates the software version.l Document Release Date, which changes each time the document is updated.l Software Release Date, which indicates the release date of this version of the software.

To check for recent updates or to verify that you are using the most recent edition of a document, go to:https://softwaresupport.hpe.com/group/softwaresupport/search-result?keyword=.

This site requires an HP Passport account. If you do not have one, click the Create an account button on the HPPassport Sign in page.

SupportVisit the HPE Software Support web site at: https://softwaresupport.hpe.com

This web site provides contact information and details about the products, services, and support that HPE Softwareoffers.

HPE Software Support provides customer self-solve capabilities. It provides a fast and efficient way to accessinteractive technical support tools needed to manage your business. As a valued support customer, you can benefitby using the support web site to:

l Search for knowledge documents of interestl Submit and track support cases and enhancement requestsl Download software patchesl Manage support contractsl Look up HPE support contactsl Review information about available servicesl Enter into discussions with other software customersl Research and register for software training

Most of the support areas require that you register as an HP Passport user and sign in. Many also require a supportcontract. To register for an HP Passport ID, go to https://softwaresupport.hpe.com and click Register.

To find more information about access levels, go to:https://softwaresupport.hpe.com/web/softwaresupport/access-levels

Support Matrix


ContentsAbout this Document 6

How to Use this Document 6

Part I: Requirements and Compatibility 7Requirements 7

Installation Guide 7Hardware 7Virtualization Products 8Operating Systems 9

Linux OS Prerequisites 10Required Libraries 10Red Hat Enterprise Linux 6 Prerequisites 10Red Hat Enterprise Linux 7 Prerequisites 10SUSE Prerequisites 11

Linux Kernel Tuning 11Virtual Memory / Swap Space 12

High-Availability Products 13Databases 15Web Browsers and Plug-ins 15

General Web Browser Requirements 15SupportedWeb Browsers on a Remote Client System (for operational use) 16Adobe Flash Player Plug-in 17

Microsoft Visio (NNM iSPI NET only) 17Compatibility 18

Languages 18HPE Software Integrations 18

Integrations with NNMi 18Integrations with iSPIs 20

HPE Software Coexistence 20

Part II: Performance, Sizing, and Other Recommendations 22Recommendations for NNMi 22

Sizing Recommendations 22Hardware Requirements for Each Tier 23

Tuning the NNMi Memory Size 27NNMi Disk Space Considerations 28Maximum Limits for Correlation Rules and Causal Rules 29Global Network Management Recommendations 29Recommended Soft Limits for Trap Burst Throughput Rate 29Other Recommended Limits 30

Part III: Device Support for NNMi 31Supported Network Devices for NNMi 31

Support Matrix


Send Documentation Feedback 32

Support Matrix


About this DocumentNote: For the latest copy of this document, click here:

https://softwaresupport.hpe.com/km/KM02208847

This document provides an overview of the system requirements and supported devices for Network NodeManager i Software (NNMi ).

Part 1 of this document contains the system requirements of NNMi .

Part 2 of this document provides performance and sizing recommendation for NNMi .

Part 3 of this document provides a list of devices supported by NNMi.

How to Use this DocumentTo See Go Here

Hardware and software requirements for installing NNMi. "Requirements" on page 7

Compatibility of NNMi with other HPE Software products. "Compatibility" on page 18

Performance and sizing recommendation for NNMi. "Recommendations for NNMi" on page 22

Device support for NNMi. "Device Support for NNMi" on page 31

Support MatrixHow to Use this Document




Part I: Requirements and CompatibilityThis section of the document describes hardware and software prerequisites and compatibility information forNetwork NodeManager i Software.

RequirementsThis section provides information about the supported hardware and software that youmust have tosuccessfully install and run Network NodeManager i Software 10.20.

Installation GuideTo obtain an electronic copy of themost current version of the Network NodeManager i Software InstallationGuide, go to https://softwaresupport.hpe.com/km/KM02208862.

HardwareThis section describes hardware component requirements for Network NodeManager i Software.

NNMi 10.20 is supported on Intel 64-bit (x86-64) or AMD 64-bit (AMD64) processors.

For Intel 64-bit (x86-64), the following Xeon processor families are recommended:

l Penryn, Nehalem, Westmere, Sandy Bridge, Ivy Bridge, Haswell or later for up toMedium tierl Sandy Bridge, Ivy Bridge, Haswell or later for Large or Very Large tier andGNM global managerFor information on hardware sizing, see "Performance, Sizing, andOther Recommendations" on page 22.


Virtualization ProductsNNMi 10.20 can be used with the following virtualization products:

Note: Virtual environments must meet the hardware requirements.

Summary of the table below:

Virtualization Product

NNMiManagementServer Additional Information

VMware ESXi Server

VMware ESXi Server 5.x ü

VMware ESXi Server 6.x ü

Microsoft Hyper-V

Microsoft Hyper-V 2012 ü l Host OS: Windows Server 2012 or 2012 R2 (or laterservice pack)

l Guest OS: Any of theWindows operating systemslisted in "Operating Systems" on page 9.

Microsoft Hyper-V 2012 R2(or later service pack)

ü

Kernel-Based Virtual Machine (KVM)

KVM ü l Guest operating systemmust be included in"Operating Systems" on page 9.

l Supported only up to theMedium Tierl Supported only for NNMi Premium.

Oracle VM

Oracle VM 3.x (starting at3.2)

ü l Guest operating systemmust be included in"Operating Systems" on page 9.

l Supported only up to theMedium Tierl Supported only for NNMi Premium (however; iRA isnot supported).

Table: Virtualization Support

Support Matrix


Operating SystemsNetwork NodeManager i Software 10.20 will run on the following operating systems:

Operating System


Windows Server 2012

Windows Server 2012 DatacenterEdition (or later service pack)

ü

Windows Server 2012 StandardEdition (or later service pack)

ü

Windows Server 2012 R2Datacenter Edition (or laterservice pack)

ü

Windows Server 2012 R2Standard Edition (or later servicepack)

ü

Red Hat Enterprise Linux

RedHat Enterprise Linux Server6.x (starting with 6.4)

ü

RedHat Enterprise Linux Server7.x

ü

Oracle Linux NNMi running onOracle Linux in an HA cluster is notsupported.

Oracle Linux Red Hat CompatibleKernel 6.x (starting with 6.4)

ü For a list of dependent libraries for NNMi, see "RedHat Enterprise Linux 6 Prerequisites " on the nextpage.

Oracle Linux Red Hat CompatibleKernel 7.x

ü For a list of dependent libraries for NNMi, see "RedHat Enterprise Linux 7 Prerequisites " on the nextpage.

SUSE Enterprise Linux

SUSE Linux Enterprise Server 11SP3 (or later service pack)

ü For a list of dependent libraries for NNMi, see "SUSEPrerequisites" on page 11.

SUSE Linux Enterprise Server 12(or later service pack)

ü

Table: Operating Systems

Support Matrix


Linux OS PrerequisitesThis section describes the prerequisites for installing Network NodeManager i Software on supported Linuxoperating systems.

For the prerequisites to install iSPIs, see the iSPI installation guides.

Required LibrariesNNMi requires the following library versions. The RPM versions may vary depending on theminor release ofRed Hat Enterprise Linux. Before installing NNMi on a 64-bit Linux server, verify that the following library filesare installed:

Make sure your systemmeets the following requirements for installing Network NodeManager i Software onRedHat Enterprise Linux (as well as Oracle Linux).

Red Hat Enterprise Linux 6 Prerequisites

RPM Package Library

glibc /lib64/libc-2.12.so

libaio /lib64/libaio.so.1

libXtst /usr/lib64/libXtst.so.6

libXi /usr/lib64/libXi.so.6

Red Hat Enterprise Linux 7 Prerequisites

RPM Package Library



libXtst /usr/lib64/libXtst.so.6

libXi /usr/lib64/libXi.so.6

For example, to install the Red Hat Enterprise Linux package libXtst, you can obtain and install the packagein one of two ways:

l If you have subscribed to the Red Hat repository, run the command yum install libXtst. Thiscommand automatically locates the package in the repository, then downloads and installs the package onthe system.

l If you do not have access to any Red Hat repository, contact your Linux administrator to download thepackage.

Support Matrix


SUSE PrerequisitesMake sure your systemmeets the following requirements for installing Network NodeManager i Software onSUSE operating system.

l Required Libraries: NNMi requires the following exact library versions. The RPM versions may varydepending on theminor release of SUSE. Before installing NNMi on a 64-bit Linux server, verify that thefollowing library files are installed:

RPM Package Library

glibc /lib64/libc-2.11.3.so


xorg-x11-libs /usr/lib64/libXtst.so.6/usr/lib64/libXi.so.6

SUSE Linux Enterprise Server 11

RPM Package Library



libXtst6 /usr/lib64/libXtst.so.6

libXi6 /usr/lib64/libXi.so.6

SUSE Linux Enterprise Server 12

Linux Kernel TuningNNMi requires that the following kernel tunable options be changed from their default settings.

l SNMP utilizes UDP (User Datagram Protocol) for sending and receiving SNMP request and responseProtocol Data Units (PDUs). The operating system utilizes UDP buffering tomatch the arrival rate of UDPpackets with their consumption rate by NNMi. Tominimize the chances for lost SNMP request or responsepackets, a sufficient amount of memory is required for UDP buffering. NNMi requests 8MB for the UDPreceive buffer (for incoming responses) and 2MB for the UDP send buffer (for outgoing requests). Linuxsystems typically reserve only 128 KB for each of these buffers.Tomake this change permanent (after a reboot):a. Edit the /etc/sysctl.conf file and add the following entry:

# NNMi settings for UDP receive and send buffer sizes

net.core.rmem_max = 8388608

net.core.wmem_max = 2097152

b. Reboot the system. To immediately apply the changes without a reboot, you can also run thecommand /sbin/sysctl -p.If ovjboss is running, restart the process to benefit from these changes:ovstop ovjboss; ovstart ovjboss

Support Matrix


l The default size of kernel.shmmax on an upgraded operating systemmight be too small for theembedded database to operate after a reboot (as reported by ovstatus -c nmsdbmgr). Configure thisvalue before installing NNMi.To validate, run /sbin/sysctl -q kernel.shmmax.Depending on thememory tier for your installation, this valuemight need to be as large as 12GB. Inmostcases, it is best to reset this value to 64GB, which is the default value for new RedHat installations.Tomake this change permanent (after a reboot)a. Edit the /etc/sysctl.conf file to add the following entry:

# NNMi settings for embedded database

kernel.shmmax = 68719476736

b. Either reboot the system or run /sbin/sysctl -p to immediately apply the changes without requiringa reboot.

l The number of open files per process must be increased. To increase the number of files:a. Edit the /etc/security/limits.conf file to add (or update) if the existing value is less than 16384

the following lines.# Increase the default max open files for NNMi* soft nofile 16384* hard nofile 16384

b. Save your changes.c. Log off from the Linux system, and then log back on, as the change to the limits.conf file only applies to

new shells.d. When you start installing NNMi, the installer inherits the new file limits.

Note: If you have already installed NNMi, do the following to restart NNMi so it inherits the newfile limits:ovstop; ovstart

Virtual Memory / Swap Spacel Recommended size is at least one and a half times physical memory (i.e., 1.5 * RAM).l Verify and adjust the virtual memory:

l Windows: UseSystem Properties.

l Linux: To verify, use the cat /proc/meminfo | grep Swap command. To adjust, use theparted andmkswap commands.

Support Matrix


High-Availability Products

Note: Use of the NNM iSPI NET diagnostics server on systems that are integrated in an NNMi cluster isnot supported. The NNM iSPI NET diagnostics server must be installed on a system separate from theNNMi cluster systems.

NNMi can run on certain high availability (HA) systems with additional configuration. See theDeploymentReference for information on how to install and configure NNMi with high availability systems. When youinstall and configure NNMi with high availability systems, it is important to carefully follow the stepsdocumented in theDeployment Reference and Interactive Installation and UpgradeGuide to accuratelyconfigure NNMi for HA. Only HA configurations that follow these documented steps can be supported byHPE.

Note: NNMi supports only a 1+1 configurationmodel for high availability.

Summary of the table below:

HA Cluster


Windows Server 2012

Microsoft Failover ClusteringforWindows Server 2012

ü Before configuring HA onWindows Server, youmustinstall the FailoverCluster-CmdInterface componentusing either Server Manager orWindows PowerShellcmdlets.Microsoft Failover Clustering

forWindows Server 2012 R2ü

Red Hat Enterprise Linux

RedHat Enterprise Linux 6.xwith Veritas Cluster Server(VCS) version 6.x

ü l Some disk types require the use of Veritas StorageFoundation (VSF) version 6.0.

l VCS 6.x and VSF 6.x might require operating systempatches. For specific information, see the appropriateVeritas product documentation.

Red Hat Enterprise Linux 7.xwith Veritas Cluster Server(VCS) version 6.x with 6.2

ü

RedHat Enterprise Linux 6.xwith Red Hat Cluster Suite(RHCS) 6.x

ü This combination is not supported by any iSPIs.

SUSE Enterprise Linux

SUSE Linux EnterpriseServer 11 SP3with Veritas


Table: HA Products


HA Cluster


Cluster Server (VCS) version6.x

SUSE Linux EnterpriseServer 12 with VeritasCluster Server (VCS) version6.x


Table: HA Products, continued

Support Matrix


DatabasesNNMi can store its data in an embedded PostgreSQL database or in an external Oracle database. Youmustchoose the database type at installation time.

Note: You cannot change the database type after NNMi installation.

Database Version Notes

Embedded database on the NNMimanagement server

l NNMi automatically installs, initializes, andmaintainsthe embedded database.

l NNMi provides tools for re-initializing, backing up whileonline, and restoring the embedded database.

Oracle andOracle Real Application Clusters(RAC) 11g Release 2 (11.2.0.x starting with11.2.0.3) installed on a remote system

l It is recommended that the network connectionbetween the NNMi management server and thedatabase server be at least 1 Gbps.

l TheOracle database user must be created with anappropriate table space before NNMi installation (seetheNNMi Interactive Installation and UpgradeGuide).

l The Enterprise Edition of Oracle database is supportedfor all tiers

l The Standard Edition of Oracle database is supportedup to theMedium tier.

Oracle andOracle Real Application Clusters(RAC) 12c Release 1 (12.1.0.x) installed on aremote system

Web Browsers and Plug-insThis section contains web browser and Adobe Flash Player plug-in requirements to work with NNMi webconsole.

General Web Browser RequirementsMake sure the web browser meets the following requirements to access NNMi using the supported webbrowser.

l Enable popups for the browser (see instructions on the NNMi console sign-in page or in theNNMiInteractive Installation and UpgradeGuide).

l Enable cookies for the browser (see instructions on the NNMi console sign-in page or in theNNMiInteractive Installation and UpgradeGuide).

l Enable JavaScript for the browser.l Install Adobe Flash (for proper display of Real-Time Line Graphs).l The resolution of the client display should be at least 1024x768.

Caution: The following browsers are not supported:


l Microsoft Internet Explorer version 11 when running in Compatibility View mode or in Enterprisemode.Be sure to disable Compatibility View in Internet Explorer using Tools → Compatibility View Settings(clear all check boxes).

l Microsoft Internet Explorer prior to version 11l Apple Safari prior to version 9.xl Mozilla Firefox prior to version 45.x ESRl Mozilla Firefox non-ESR versionl Opera (all versions)

Supported Web Browsers on a Remote Client System (foroperational use)The following web browsers are supported on a remote client system.

l Microsoft Internet Explorer (32-bit and 64-bit) version 11 (not running in Compatibility View mode).l Mozilla Firefox version 45.x ESR on aWindows or Linux client.

l The Firefox ESR (Extended Support Release) browser is available athttp://www.mozilla.org/firefox/organizations/all.html.

l The Firefox browser works best when you open links as new windows rather than tabs. For information,see "Mozilla Firefox Known Problems" in the Release Notes.

l Apple Safari version 9.x on anOS X client.l Exception: The NPS console and all other windows that are launched from the NPS console are notsupported with Safari.

l Google ChromeTM

l Exceptions:o NPS Query Studio and BI Server Administration features are not supported with Chrome.

Compatibility Matrix of Different NPS Components with Supported Web Browsers

GoogleChrome

Apple Safari 9.x (Onlyon OS X)

Microsoft InternetExplorer 11

Mozilla Firefox45.x ESR

Dashboards ✓ ✓ ✓ ✓

PerformanceTroubleshooting

✓ ✓ ✓ ✓

NPS console andreports

✓ X ✓ ✓

Query Studio X X ✓ ✓

BI Server Portal ✓ X ✓ ✓

Support Matrix


http://www.mozilla.org/firefox/organizations/all.html

GoogleChrome

Apple Safari 9.x (Onlyon OS X)

Microsoft InternetExplorer 11

Mozilla Firefox45.x ESR

BI ServerAdministration

X X ✓ ✓

Adobe Flash Player Plug-inThe Real-time Line Graphs (Actions →Graphs) requires the Adobe Flash Player Plug-in version 11.2 or aboveon Linux and 21.0.0.242 or above inWindows. The Adobe Flash Player is available fromwww.adobe.com/go/getflash/.

Microsoft Visio (NNM iSPI NET only)The NNM iSPI NET feature to export map views to Visio (Tools →Visio Export) requires Microsoft Visio 2010or Microsoft Visio 2013.

Support Matrix


CompatibilityThis section provides information about software and configurations that are not required, but which arecompatible with Network NodeManager i Software 10.20.

LanguagesNNMi is localized (or translated) to the following languages:

l Frenchl Germanl Japanesel Koreanl Russianl Simplified Chinesel SpanishWhen those localized packages are installed, NNMi accepts non-English characters as input. With all otherlocales, English strings appear as output while NNMi accepts non-English characters as input.

OnWindows systems, NNMi does not support installation using directory paths with localized characters;path names for %NnmInstallDir% and %NnmDataDir% can contain English characters only.

HPE Software IntegrationsThe following products have additional functionality available through an NNMi 10.20 integration.

Themost current information about HPE software that integrates with NNMi 10.20 can be found at the HPESupport web site. See HPE Software Integrations Catalog.

For information on specific features, see the appropriate integrationmanual.

Integrations with NNMil HPE Advanced TeMIP NNM Integration (ATNI) version 6.0 with HPE TeMIP version 6.0, 6.2NNMi 10.20 on RedHat Enterprise Linux integrated with ATNI 6.0 on Red Hat Enterprise Linux withpatches TEMIPTNTLIN_00049 (runtime) and TEMIPTNTLIN_00050 (for Customization Toolkit) or anysuperseding patches. NNMi 10.20 onWindows integrated with remote ATNI 6.0 on HP-UX with patchesPHSS_ 44066 on HP-UX and TEMIPTNTWIN_00006 onWindows or any superseding patches.See the TeMIP NNMi Advanced Integration Overview and other ATNI documentation for more details onthe integration.

l HPE ArcSight Logger version 6.0, 6.1 and 6.2NNMi 10.20 supports all SmartConnectors supported by ArcSight Logger version 6.0, 6.1 and 6.2.

l HPE Asset Manager version 9.41 (with HPE Connect-It 9.53), 9.50 (with HPE Connect-It 9.60), and 9.60(with HPE Connect-It 9.60)


https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/KM01663677

l HPE Business ServiceManagement (BSM) Real User Monitor (RUM), Run-time ServiceModel (RTSM),Operations Management (OMi), My BSMwith BSM version 9.25, 9.26

Note: Integration with OMi for BSM 9.25 or 9.26 is supported only with BSM Connector 10.01. TheBSMConnector must be installed on the NNMi management server.

l HPE Operations Manager i (OMi) 10.00, 10.01, 10.10, 10.11

Note: If you are using OMi 10.00 onWindows, apply the hotfix QCCR8D38153 onOMi. Contact HPESupport to obtain the hotfix.

Integration with OMi 10.00, 10.01, or 10.10 is supported with BSM Connector 10.01. Integration withOMi 10.01, 10.10, or 10.11 is supported with HPE Operations Connector (Operations Connector)10.11. The BSMConnector or Operations Connector must be installed on the NNMi managementserver.

l HPE Intelligent Management Center (IMC) version 7.1, 7.2l HPE Network Automation (NA) version 10.20, 10.11

Note: For NNMi and NA to run correctly on the same computer, youmust install NNMi beforeinstalling NA. If you install NA before installing NNMi, the NNMi installation reports a port conflict withNA and does not complete.

l HPE Operations Analytics Premium and Ultimate 2.31l See the HPE Operations Analytics Configuration Guide for more details on the integration.

Note: HPE Operations Analytics Express is not supported.

l HPE Operations Manager (OM)l HPOM for Linux version 9.11, 9.20, 9.21

l HPOM for UNIX version 9.11, 9.20, 9.21

l HPOM forWindows version 9.00

Note: Integration with OM (agent implementation) is supported only with HPE Operations agent 12.00.The HPE Operations agent must be installed on the NNMi management server.

l HPE Operations Orchestration (HPE OO) version 10.x

Note: NNM iSPI NET provides a different integration with HPE OO. An embedded package of therequired HPE OO version is included with the NNM iSPI NETmedia. For specific information, see theNNM iSPI NET requirements.

l HPE Route Analytics Management Software (RAMS) version 9.21 (requires a Premium, Ultimate or NNMiAdvanced license)

l HPE SiteScope version 11.23, 11.30, 11.31, 11.33

Support MatrixCompatibility


l HPE Systems Insight Manager (SIM) version 7.4.x, 7.5.xl HPE Universal CMDB (UCMDB) version 10.10, 10.11, 10.21, 10.22

Note: The HPE NNMi–HPE BSM/UCMDB Topology integration, as described in the NNMi—Business ServiceManagement/Universal CMDB Topology Integration Guide, now supportsintegration with either HPE Business ServiceManagement (BSM) Topology or HPE UCMDB. NNMicannot simultaneously integrate directly with both HPE BSM Topology and HPE UCMDB. If you wantNNMi information in both databases, configure the HPE NNMi–HPE BSM/UCMDB Topologyintegration with either HPE BSM Topology or HPE UCDMB and then configure integration betweenHPE BSM Topology and HPE UCMDB as described in the UCMDB Data Flow Management Guide,which is included on the UCMDB product media

l IBM Tivoli Netcool/OMNIbus version 8.1l NetScout nGenius PerformanceManager 5.2.1l NNM iSPIs

l NNM iSPI NET 10.20

l NNM iSPI Performance for Metrics 10.20

l NNM iSPI Performance for QA 10.20

l NNM iSPI Performance for Traffic 10.20

l NNM iSPI for IP Multicast 10.20

l NNM iSPI for MPLS 10.20

l NNM iSPI for IP Telephony 10.20

Integrations with iSPIsl NNM iSPI Performance for Metrics with HPE Operations Bridge Reporter 10.00, 10.01l NNM iSPI for IP Telephony with HPE SiteScopeSupports integration with SiteScope 11.30

HPE Software CoexistenceThe following products can coexist on the same system as NNMi 10.20:

l HPE ArcSight Smart Connector: HPE Network NodeManager i SNMP version 7.1.6l HPE Network Automation (NA) version 10.11, 10.20l HPE Business ServiceManagement Connector version 10.01l HPE Operations Connector version 10.11l HPE Operations agent (64-bit only) version 12.00, 12.01

Note: See theNNMi Coexistence with HPE Operations Agent section in theDeployment Reference



for more information on the proper installation order when using HPE Operations agent.

If you plan to install an HPE Operations agent on the NNMi management server (for communicatingwith OM), install NNMi before installing the HPE Operations agent.If you are also installing the Network Performance Server (NPS), youmust install NPS after NNMi andbefore the HPE Operations agent.

l IBM Tivoli Netcool/OMNIbus SNMP Probe: The latest version that is compatible with IBM TivoliNetcool/OMNIbus version 8.1




Part II: Performance, Sizing, and OtherRecommendationsThis section of the document describes hardware sizing, performance, and other recommendations forNetwork NodeManager i Software.

Recommendations for NNMiThis section describes performance, sizing, and other recommendations for NNMi software.

Sizing RecommendationsThe recommendations listed in this section apply to NNMi running under the default settings.

NNM iSPIs might require additional hardware beyond what NNMi requires. If you intend to run any of the NNMiSPIs, review each NNM iSPIs support matrix before determining the total hardware requirements for yourenvironment.

The following tables describe tiers of managed network environments and the hardware requirements forsupporting these tiers. The values stated here are approximate and reflect levels tested by HPE. If you have aparticularly complex environment, poll objects at a higher frequency, or poll more objects than stated in agiven tier, youmight need to increase the Java heap size, provisionmore powerful hardware as indicated bythe next higher tier, or both. The number of discovered objects and polled object counts appear in the NNMiconsole Help→System Information window. All polled counts in the tables below reflect both performanceand fault polling.

Note: Performance polling requires an Ultimate or Premium license.

Hardware Requirements for Each TierManaged environments larger than these tiers are not supported without additional HPE approval.

Managedenvironmenttier1

Total number ofdiscoverednodes

Number ofHypervisors2

Numberof VMs3

Number ofdiscoveredinterfaces

Number ofpolledaddresses

Number ofpolledinterfaces

Number ofcustom polledobjects4

Number of pollednode and physicalsensors

Number ofconcurrentusers

Entry Up to 250 5 100 15k 500 2500 1200 500 5

Small 250 - 3k 10 200 120k 5k 10k 30k 40k 10

Medium 3k – 8k 75 1500 400k 10k 50k 50k 60k 25

Large 8k – 18k 200 4000 900k 30k 70k 75k 80k 40

Very Large 18k - 30k 200 4000 1mil 60k 200k 200k 120k 40

Tiers of Managed Network Environments

l1To view discovered object counts and polled object counts, see the Database, State Poller, and Custom Poller tabs in the Help→System Information window.

l2The number of hypervisors (for example, VMware ESXi hosts) managed through aWeb Agent. This number is included in the total number of discovered nodes.

l3The number of VMs managed through aWeb Agent. This number is included in the total number of discovered nodes.

l4 This applies to Custom Polled Instances for Custom Poller "Instance" collection. For Custom Poller "Bulk" collection limits, see "Other Recommended Limits" on page 30.

of 32HPE Network NodeManager i Software (10.20)

Managedenvironmenttier

CPU (64-bit) x86-64 or AMD641 RAM2

Recommended Java heap size (see "Tuningthe NNMi Memory Size" on page 27)3

Disk space for applicationinstallation ($NnmInstallDir)4

Disk space for database and dataduring execution ($NnmDataDir)5

Entry 2 CPU cores 4GB 2GB 3GB 10GB

Small 4 CPU cores 8GB 4GB 3GB 30GB

Medium 6 CPU cores 16GB 8GB 3GB 40GB

Large 8 CPU cores 24GB 12GB 3GB 60GB

Very Large 12 CPU cores 48GB 16GB 3GB 80GB

Recommended Hardware for Tiers

l1See "Hardware" on page 7 for processor recommendations.

l2If you are running additional applications, increase resources appropriately. (For example, when the Network Performance Server (NPS) component of the NNM Performance iSPIs is installed onthe same system as NNMi, the NPS uses half of the system RAM, and NNMi plus other products must fit into the other half, requiring at least double the amount of RAM stated here.) If you areplanning to use any of the NNM iSPI Performance products (NNM iSPI Performance for Metrics, NNM iSPI Performance for Traffic, or NNM iSPI Performance for QA) and aremanaging at the Largetier or above, it is recommended that the NPS component of the NNM Performance iSPIs be installed on a separate server from NNMi. You can install spread NPS processes across multiple serversby creating a distributed deployment of NPS. See theNNM iSPI Performance for Metrics Deployment Reference for more information about the distributed deployment of NPS.

l3These recommendations are based on the environment size and polled object counts stated in this table. Polling fewer of a given object typemight use less Java heap. Pollingmore of a givenobject typemight require increased Java heap size as well as HPE approval.

l4NnmInstallDir is configured during installation onWindows ( C:\Program Files (x86)\HP\HP BTO Software\ by default), or on Linux by creating a symlink to /opt/OV/.

l5NnmDataDir is configured during installation onWindows ( C:\ProgramData\HP\HP BTO Software\ by default), or on Linux by creating a symlink to /var/opt/OV/ . See "Hardware Requirementsfor Each Tier" on the previous page before proceeding.


The following tables describe hardware recommendations for global network management environment.

Approximate managedenvironment

Number of regionally managednodes2

Number ofHypervisors3

Number ofVMs4

Number of regionalmanagers

Number of concurrentusers

Medium Global Manager 25k - 40k 500 10000 Up to 30 20

Large Global Manager 40k - 80k 1000 20000 Up to 30 40

Global Network Management Environment1

l1See "Global Network Management Recommendations" on page 29.

l2To view discovered object counts and polled object counts, see the Database, State Poller, and Custom Poller tabs in the Help→System Information window.

l3The number of hypervisors (for example, VMware ESXi hosts) managed through aWeb Agent. This number is included in the total number of discovered nodes.

l4The number of VMs managed through aWeb Agent. This number is included in the total number of discovered nodes.


Approximatemanagedenvironment

CPU (64-bit)x86-64 or AMD641 RAM

Recommended Java heap size (see "Tuning theNNMi Memory Size" on the next page)

Disk space for applicationinstallation ($NnmInstallDir)2

Disk space for database and data duringexecution ($NnmDataDir)3

Medium GlobalManager4

8 CPU cores 24GB

12GB 3GB 60GB

Large GlobalManager

12 CPU cores 48GB

16GB 3GB 80GB

Recommended Hardware for Global Network Management Environment

l1 See "Hardware" on page 7 for processor recommendations.

l2NnmInstallDir is configured during installation onWindows R2 ( C:\Program Files (x86)\HP\HP BTO Software\ by default), or on Linux by creating a symlink to /opt/OV/

l3NnmDataDir is configured during installation onWindows ( C:\ProgramData\HP\HP BTO Software\ by default), or on Linux by creating a symlink to /var/opt/OV/ . See "Recommendations forNNMi" on page 22 before proceeding.

l4Most NNMi customers with fewer than 30k nodes tomanage realize the lowest Total Cost of Ownership with a single server solution. If redundancy is required for a single server solution, a HighAvailability or NNMi Application Failover solution can be deployed with a clustered primary and standby server. Customers with fewer than 30k nodes who are considering aGNM solution shouldcontact their HPE representative to discuss whether GNM is right for their environment.


Tuning the NNMi Memory SizeDuring installation, the recommended default maximummemory size of the NNMi application is configured inthe ovjboss.jvmargs file. NNMi configures the -Xmx value by examining the amount of physical RAM andselecting the value for the closest tier. Review this memory size value after installation tomake sure it isappropriate for the expected size of your environment. Youmay need to increase or decrease thememorysize value to reflect the recommendations documented inNNMi Performance, Sizing, andOtherRecommendations.

The current Maximum Attemptable Memory value (adjusted with –Xmx) and amemory region report areavailable in the NNMi console withHelp → System Information. This -Xmx valuemust not exceed theamount of unused physical RAM. If the NNMi JVM's entire virtual memory space does not fit in physicalmemory, the operating system thrashes as NNMi randomly accesses its memory. NNMi supports amaximum –Xmx memory value of 24 GB.

Note: Setting the heap too largemay cause long pauses which can affect the ability of NNMi tomonitorthe network. Large heap sizes require a fast CPU with highmemory bandwidth.

You can approximate the amount of unused physical RAM available to NNMi as follows: From the amount ofphysical memory, subtract the following amounts:

l Memory for the operating system: 1 - 2 GBl Memory for the nmsdbmgr process: 1 - 8 GBl Memory for any other applications, including NNM iSPIs, that are running on the serverNNMi continues tomonitor its memory regions during operation. If NNMi memory resources are getting low, amessage appears on the NNMi console sign-on page, at the bottom of the NNMi console, and at the top ofNNMi forms. When NNMi is running low onmemory, it spends more time performing garbage collection,reducing overall system performance. Some of the possible memory regionmessages and suggested fixesinclude:

l [Critical] The region 'PS Old Gen' is at 100.00% usage

This indicates the system is running low on heapmemory. Check that the NNMi maximum heap setting isconfigured for the size of themonitored environment as specified under Sizing Recommendations.If the system is correctly configured and yet the warning persists, consider increasing themaximum NNMiheap size to the next tier, or by a small amount if at themaximum of 16GB. Larger heap sizes are notalways better as setting the heap too largemay cause longer pauses if the hardware is not fast enough tohandle the larger size.Setting themaximum heap to values over 16GB should be done with caution as only high performancehardware is able to garbage collect such large heaps with acceptable pause times. Warnings aboutexcessive pause times indicate the heap is too large for the system.

l [Warning] The average garbage collection pause of 13.00 seconds for the 'PS MarkSweep'collector is above the recommended maximum of 10 seconds.

This warning indicates that the system is unable to garbage-collect the heap within a reasonable timeleading to large pauses. This can indicate either a performance problem on the system, either swapping orinsufficient CPU time if a VM, or it could indicate that the heap has been set too large for the performanceof the system.

To change the NNMi Maximum Java Heap Size (–Xmx) or other Java Virtual Machine parameters:


1. Run the command ovstop -c ovjboss.2. Edit the ovjboss.jvmargs file:

Windows Server: C:\ProgramData\HP\HP BTOSoftware\shared\nnm\conf\props\ovjboss.jvmargsLinux: /var/opt/OV/shared/nnm/conf/props/ovjboss.jvmargs

3. Change the Maximum Java Heap Size to the required amount. For example, a snippet ofthe ovjboss.jvmargs file looks like this:# JVM Memory parameters

# -Xms: Initial Java Heap Size

# -Xmx: Maximum Java Heap Size

# -Xss: Java stack size (default to OS-supplied value)

#

-Xms2048m

-Xmx12g

Note: Changing values in this file should be done with care as it may have adverse impacts on theperformance of NNMi. If in doubt, contact HPE Support.

4. Run the command ovstart -c ovjboss.

NNMi Disk Space ConsiderationsBefore allocating disk space for NNMi, consider the following:

l The recommendations in the tables above are the recommendedminimum disk space amounts based onHPE's average test environment. More complex environments might require more disk space.

l Disk performance is extremely important for high scale environments that areMedium tier or higher. HPEstrongly recommends RAID 1+0 (10) with battery-backed write cache on discs of 15,000 rpm or better.Disk configurations that do not meet this level of performance are not adequate.

l Increasing log file size from the default settings uses more disk space. Before increasing log file size,validate that you have adequate disk space.

l During high scale testing, HPE has not seen tablespace sizes larger than 16GB (Oracle or embeddedPostgreSQL) - either single system or global manager in a Global Network Management environment. Ifusing Oracle in a high scale environment, configure for incremental table space growth beyond this size.

l For Large and Very Large scale environments running NNMi application failover with PostgreSQL, theNNMi management server must have at least 40 GB more disk space than the recommended amount forapplication failover logs. For these scaled environments, it is recommended that you allocate disk spaceseparate from $NnmDataDir for the application failover logs. The location of the failover logs can beconfigured in the nms-cluster.properties file.

l For Global Network Management environments, the global manager running NNMi application failover withPostgreSQLmust have at least 140GB more disk space than the recommended amount for applicationfailover logs. For these scaled environments, it is recommended that you allocate disk space separate from$NnmDataDir for the application failover logs. The location of the failover logs can be configured in thenms-cluster.properties file.

Support MatrixRecommendations for NNMi


l (Linux) if you partition your disk, you should ensure that the file systems containing the directories listed inthe following table have at least the specified disk space available for NNMi. If you use all-in-rootpartitioning, you should ensure that the total required disk space is available. Also see "Virtual Memory /Swap Space" on page 12 for swap space requirements.

Partition Recommended Minimum Disk Space

/tmp 1GB

/opt/OV/ SeeRecommended Hardware System Requirements for $NnmInstallDir for yourmanaged environment tier in the above tables.

/var/opt/OV/ SeeRecommended Hardware System Requirements for $NnmDataDir for yourmanaged environment tier in the above tables.

Disk Space Recommendations

Maximum Limits for Correlation Rules and CausalRulesTo ensure adequate performance, NNMi supports the followingmaximums:

l 25 Correlation Rulesl 25 Causal Rulesl 5 Filter String entries for each of the following filters:

l Child Incident

l Parent Incident

l Source Object

l Source Node

Valid Filter String entries include logic operators (AND, OR) and comparison operations (Attribute, Operator,Expression). NNMi displays each entry on a separate line above the Filter String output.

Global Network Management RecommendationsEach regional manager can forward information to a supported limit of two global managers.

Recommended Soft Limits for Trap Burst ThroughputRateNNMi has been tested with the following incoming SNMP trap rates. These rates assume awell-configuredsystem and are supported independent of the hardware tier:

l 1,000 SNMP traps/second for up to 1minute.l 200 SNMP traps/second for up to 5minutes.



l A sustained average of 50 SNMP traps/second.l The database limit for storing traps is 95,000; when that limit is reached, new traps are no longer persistedin the NNMi database. See theArchive and Delete Incidents help topic inHelp for Administrators for moreinformation on the stored trap limit. See the NNMi Deployment Reference for enabling Auto-Trim forSNMP traps to avoid reaching the limit for stored traps. Traps can also be trimmed using thennmtrimincidents.ovpl command. Even when new traps are not persisted in the NNMi database due tothe database limit for storing traps, they are still stored in the binary trap store and can be viewed with thennmtrapdump.ovpl command.

Other Recommended Limitsl NNMi supports amaximum of 1500 configured Users, 40 simultaneous users, 2000 User Groups, and2000 Security Groups. Each user is limited to amaximum of 32 User Groups

l NodeGroupsl NNMi supports amaximum of 12,000 NodeGroups

l NNMi supports a hierarchy of 6 NodeGroups deep

l Use separate node groups for maps andmonitoring settings

l Best node group performance is obtained by using the following filtering styles:o Use “hostname like B038255*” style filteringo Avoid “hostname like *router” style filteringo Use “customAttributeName = tokyo1” style filteringo Avoid long filters that use mgmtIPAddress = a.b.c.d or mgmtIPAddress = e.f.g.h or

mgmtIPAddress = u.v.w.x or mgmtIPAddress = w.x.y.z style filtering

l NNMi supports amaximum of 100 Interface Groupsl NNMi supports amaximum of 20monitoring configuration groups

l A monitoring configuration group can be either a NodeGroup or an Interface Group

l Click the Interfaces Settings and Node Settings tabs of theMonitoring Configuration form to see thenumber of configured groups:o NNMi does not enforce any hard limits on the number of monitoring groups you configureo NNMi does not support configurations of more than 20monitoring groups due to the risk of a

degradation in NNMi performanceo If the NNMi management server is nearing the limits of maximum performance, do not configure

monitoring groups to use complex filters; doing so adds processing time and decreases NNMiperformance

l NNMi supports amaximum of 20million records daily for "Bulk" collection for Custom Poller for Very Largetier (where a record can contain values for multiple OIDs from a single SNMP table entry)

l Some commands support batching for updates. If the batch file is too large, transactions timeouts canoccur. If that happens, decrease the size of the batch file and try again. The following limits may be usefulguidelines:l 1000 lines in the batch file for the nnmcommunication.ovpl command

l 100 lines in the batch file for the nnmnodegroup.ovpl command




Part III: Device Support for NNMiThis section of the document provides a list of devices supported by NNMi.

Supported Network Devices for NNMiFor the list of supported network devices, see theNNMi Device Support Matrix athttps://softwaresupport.hpe.com/km/KM02208863.

This device support information is based on the latest information available to HPE at the time of publication.Note that device vendors can at any time alter a device's MIB usage (for example, in newer IOS or systemsoftware versions) and invalidate NNM's interpretation of that device's MIB data.

For additional device support, see the NNMi Device Content page on HPE Live Network.


https://hpln.hpe.com/contentoffering/nnmi-device-content-packs

Send Documentation FeedbackIf you have comments about this document, you can contact the documentation team by email. If an emailclient is configured on this system, click the link above and an email window opens with the followinginformation in the subject line:

Feedback on Support Matrix (Network Node Manager i Software 10.20)

Just add your feedback to the email and click send.

If no email client is available, copy the information above to a new message in a webmail client, and sendyour feedback to [email protected].

We appreciate your feedback!


mailto:[email protected]?subject=Feedback on Support Matrix (Network Node Manager i Software 10.20)

HPE NetworkNodeManageri Software - Dimiter Todorov · HPE NetworkNodeManageri Software...

Documents

Transcript of HPE NetworkNodeManageri Software - Dimiter Todorov · HPE NetworkNodeManageri Software...