Anda di halaman 1dari 71

HP Network Node Manager(NNMi (9.

0) Basics

Sample deployment on a small test lab All using NNMi 9.00 W ill not address NNM 6.x/ 7.x to NNMi upgrades. This will be a virgin installation of NNMi 9.00 Goal is to give you a feel for what is required and for you to see how straightforward the tasks are This is abbreviated but the steps are similar for even our largest deployments

HP has written various white papers on deploying NNMi 9:


Steps Well T ake

Initial L ogin and User Creation Apply license Configure Communication Configure Discovery Configure Monitoring

Configure Incidents, T raps and Automatic Actions

Configure the Graphical User Interface Maintenance

Health Checks
P ossible Use Scenarios

Unique Challenges for Network Management

Resources - High administrative overhead to manage networking; inefficient use of operations and administration staff; lack of management automation

Visibility - Missing connection to virtualized systems management and network device virtualization/redundancy; lacking insight into specialized network services such as IP Telephony or MPLS

Correlation - Management software issues with overhead and inaccuracy; too many uncorrelated events and lack of visibility into relationships among incidents, performance and topology

HP Network Management Center

BSM Dashboard HP Network Management Center

Change, Configuration & Compliance

(Network Automation)

Fault & Availability Monitoring

(NNMi or NNMi Advanced)

Performance Monitoring
(iSPI Performance for Metrics iSPI Performance for Traffic iSPI Performance for QA)

Advanced Services
(iSPIs for IPT, MC, MPLS)

Automated Diagnostics

Routing Analysis

Historical Data Warehouse & Reporting

(Performance Insight)

CMDB Unified Operations Run-Book Automation (Operations Orchestration)

NNMi The consolidation point for fault, availability,

performance and advanced services

iSPI Perf Metrics

iSPI IP Telephony


iSPI Perf Traffic



iSPI IP Multicast

Network Node Manager i (NNMi)

Maximize efficiency of your network operations Single administrative and operational console
- Rapid and continuous discovery - Unifies fault, availability, performance

- Seamless integration of plug-ins

Extremely low administrative overhead

- Quick deployment, easy upgrade - Simplified configuration and customization - Fast ROI, low TCO

Key Incidents aligned with your environment

- Unified Root Cause Analysis - Define your relevant, service impacting events

Discover and monitor virtualized environments

- Map ESX Servers and guests to the physical infrastructure - Correlate physical fault to virtual services or applications

Network Node Manager i software (NNMi)

Maximize efficiency of your network operations

Unified network fault, performance and services monitoring in a single operational console

Continuous spiral discovery, single poller, and common casual analysis for low administrative overhead

Customizable node groups for logical partitioning including custom attribute selection

Workflow-based navigation and filtering for incidents, nodes, components, paths and metrics

Single interface for administration of NNMi and all plug-in iSPIs

NNMi scales to meet your needs

Single-server scalability to 25,000 managed nodes, 1 million discovered interfaces

Value-based pricing model and several product bundles to choose from

Global Network Management (GNM) configuration, with NNMi Advanced, localized polling with consolidation of up to 65,000 nodes

NNMi Advanced GNM architecture enables consolidation with regional control and survivability

Flexibility meets the needs of small and large environments as well as distributed teams

Discover & monitor virtualized environments

Discover and map VMware hosts and guests *

with NNMi Advanced

Find Attached Switch Port for virtualized systems *

Supported to run on virtual server environments

* NNMi Advanced only

Discover and monitor network device redundancy configurations *

NNMi iSPI Performance for Metrics

Report on interfaces and node component statistics Performance status, thresholds & incidents integrated with fault and topology Polling and administration unified with NNMi and configurable per node group OOB reports at hourly, daily, weekly or monthly level

Up to 10 weeks of history data stored; hourly summary with configurable period for full detail data

iSPI Performance for Metrics (continued)

Flexibility in reporting specific to your environment

Path health shows component and interface performance along important routes

Top-N, heat chart, detail and summary reports highlight areas of concern

Interactive navigation select any criteria for filtering and grouping

Detect negative performance trends before they affect users

Same interface reports on additional optional iSPI data for Traffic and QA as well as userdefined custom collections

iSPI Performance for Traffic

Augment operational performance monitoring with network traffic flow detail Configuration and
tight integration with NNMi, including traffic maps launch Highly scalable distributed collection architecture low overhead Collection, analysis, and presentation of NetFlow and sFlow traffic information Application mapping to traffic flow, configurable by collection point Reports out-of-the-box or customizable, with flexible grouping

iSPI Performance for Quality Assurance

unifying network service quality management with network management

Site-specific threshold administration

Test and monitor connections beyond management domain (into WAN/cloud)

Common iSPI Performance user interface, low overhead Detect and pinpoint network service degradation early

Consolidate discovery of IP SLA network tests and associate them with NNMi topology

NNM iSPI Network Engineering Toolset (iSPI NET)

Automate common data collection tasks
Trap analytics enable tuning of SNMP trap sources and incident generation

Export NNMi discovered topology to Visio for offline use Save engineering effort logging into individual devices for information and diagnosis

Predefined Operations Orchestration flows capture diagnostic detail on-demand or in response to incidents

Compare changes against baseline data collected to isolate problems

iSPI for IP Telephony

comprehensive monitoring for Cisco, Nortel, or Avaya IPT infrastructure

Discover, map, report and threshold on IPT devices and phones

For Cisco IPT, alert based on call quality metrics and state changes

For Avaya IPT, alert based on performance and usage

Scale up to 50,000 phones and associated devices

Flexible reporting aligned with iSPI Performance


Automated discovery and monitoring for MPLS services

L3 VPN maps visualize PE topology types and connecting CE devices LSR inventory, service details such as VRF and VPN inventory integrated with NNMi

MTTR and MTBF reporting for VPN-VRF

Monitor MPLS core network (LSRs & TEs) and Services (L2 VPN VPWS & VPLS)

TE tunnel path and Pseudowire monitoring

NNMi 9.0 New Features

New Support for Windows 2008, RHEL 5.2+, Vmware ESX 4.0, IE 8.0, Firefox 3.6, Oracle 11g, Veritas Cluster Server for Linux, IPv6 Global Network Management (regional/Global Mgrs) Management of virtualized servers (NNMi Advanced) MPLS WAN Cloud/Connection discovery (NNMi Advanced; with RAMS) Discover Cards, Daughter Cards, Card Redundancy Groups for Cisco and ProCurve Incident Suppression, Enrichment, Dampening User Interface improvements (sortable tables, new menu items, custom attributes for nodes or interfaces, new device icons, improved filtering) Custom Correlations Configuration (similar to Correlation Composer) Northbound interface forwards incidents to MULTIPLE registered trap receivers Support for MIB Expressions for polls or graphs using MIB Expression Editor MIB Browser for loading and viewing supported MIBS per node Real Time SNMP Line Graphs Custom Poller uses MIB expressions and exports data to CSV State Poller Customizations (pinging mgmt address only, etc) SNMP improvements (improved performance, new configuration options, etc) NNMi Self-Monitoring

NNMi 9.0 Advanced Features

Global Network Management

NNMi 9 Integrations to HP Software

HP NNMi iSPIs need to be updated to 9.0 along with NNMi HP Network Automation (NA) 7.50.02 and 7.60.01 HP Performance Insight (OVPI) 5.31, 5.40 and 5.41 HP RAMS 9.0 (with NNMi Advanced) Event forwarding from HP NNM 6.x / 7.x SE & AE HP Operations Manger: OMU 8.30 & 9.00; OMW 8.10 & 8.16; OML 9.00 HP OMi 8.10 HP uCMDB 8.03 and 8.04 HP BACRUM and MyBSM 7.54, 8.03 and 8.04; BSM 9.0 HP Operations Orchestration 7.51 w/7.60.01 patch and 7.60 w/7.60.01

The Deployment Reference Guide is the source for detailed information on integrations

Other NNMi 9 Integrations

HP ProCurve Manager Plus (PCM+) 3.10 Systems Insight Manager (SIM) 5.30 HP AssetManager 5.20, 5.21 (with Connect-IT also 4.10, 4.11) AlarmPoint Express, Standard, Enterprise, Pro, and Mobile Gateway 4.00 NetScout nGenius Performance Manager 4.6 MR1, 4.7, 4.7 MR2, and 4.8 Clarus IPC+ 2.6.1 CiscoWorks LAN Mgmt Solution 3.1 and 3.2 IBM Tivoli Netcool/OMNIbus 7.21 (with license for NNMi Netcool IM)

Why Upgrade to NNMi?

Increase service levels and efficiency while reducing costs

Continuous Layer 2 discovery and mapping essential for physical and virtual environments Ease of maintenance and ease of configuration N-tier architecture; single database; application failover; LDAP Integrations: HP Network Automation; HP Business Availability Center; HP uCMDB; AlarmPoint; NetScout; IBM Netcool; SIM; HPOM Increased scalability Web-based GUI with user roles Unified fault and performance (iSPIs for Metrics, Traffic and QA) Automated diagnostics (iSPI for NET)

Easy upgrade from NNMi 9.x


Challenges to Maximizing NNMis Value

Initial server sizing Proper node discovery Map container setup and configuration Event and trap tuning to ensure proper prioritization

Integration with other Enterprise Management Systems

Polling and data collection strategies Knowledge transfer to NNMi operators Post implementation configuration updates and tuning Proper backup and recovery procedures

Other Steps We W ill Not Cover Include:

Machine sizing N N Mi support for HTTPS and LDAP Integration with other products such as HP NA, HP OM, HP UCMDB, and other 3rd party products Configuring HA or Application Failover Configuring an Oracle database Configuring Global Network Management (GNM) Configuring IPv6 iSPIs See the NNMi Deployment Guide for more information on these topics

Installation has already been done

Hints: Check all prerequisites especially kernel parameters, shared memory, semaphores, RAM, etc.

This example is done on a Unix machine. P aths need to be converted for W indows.


After the Install, Validate Processes Are R unning

At command line, run ovstatus c for a basic check. Most processes are now within the ovjboss so you must also run ovstatus v for the details of the jboss services.


jboss Processes
# ovstatus -v ovjboss object manager name: ovjboss
state: PID: last message: exit status: additional info: RUNNING 20413 Initialization complete. STATUS Service Service Service Service Service Service Service Service Service Service Service Service

SERVICE CPListener CommunicationModelService CommunicationParametersStatsService CustomPoller EventsCustomExportService ExtensionDeployer InstanceDiscoveryService IslandSpotterService KeyManager StagedSnmp StatePoller TrustManager

is is is is is is is is
is is is is

started started started started started started started started

started started started started

Initial L ogin
L ogin with browser (no more java plugins required) http://m


Initially log in with the system password created during installation


Create a new user

Its best to create an administrator account rather than using the system login


Click on the Configuration Workspace and select User Interface configuration


Click on the New Icon to launch the Account Mapping form

Select the pull down menu to the right of the Account entry and select New. (It is a common mistake to try to simply type in the Account rather than creating a New one.)


T ype in the User Name and P assword (well call ours admin and the password will be adminpw)

Select the role and hit save and close


We now have an admin account

Try logging out and back in with the new account. You can see the user presently logged in to this session in the upper right.


Apply a L icense
Product comes with a 250 node instant on license. You dont need to do anything to use this license. But once you hit 250 nodes, no other nodes will be discovered or monitored. You can also obtain a temporary license from HP for initial trial. You can apply the license via a GUI using
nnmlicense.ovpl N NM g

Or via the command line using

nnmlicense.ovpl NNM -f ./ mylicense.key


Configure Communication
Go to the Configuration Workspace and select Communication Configuration


Select the Default Community Strings tab and click on the New icon. Enter all of your SNMP R ead Community Strings here. Order does not matter. N N Mi attempts all Comm Strings simultaneously and chooses the first one that succeeds. You can also modify the default timeout and retry attempts here. After making changes, save and close the form. SNMP GetBulk by default recommended to be unchecked for end nodes


SNMP Management Address Discovery

L eave Enable SNMP Address Discovery unchecked if you want to keep the same loopback address as the only address that will ever be tried for SNMP communication.


Discovery Configuration
L ist based discovery (similar to loadhosts of legacy NNM)
More No

control level of knowledge of nodes

surprises name or IP is required. No subnet masks required data

R equires high Only Static

Auto-discovery (well use this for our example)

Always up

to date rules to control breadth of discovery

R equires good


default, NNMi only discovery switches and routers (this is easily expanded)


Go to the Configuration Workspace and select Discovery Configuration.


Select the Auto-Discovery R ules tab and click on the New icon.


Fill out the Basics section and click on the New icon for the IP Address R anges in this rule. The value for Ordering doesnt matter in this case since well only have one auto-discover rule.


T ype in a range. A rule can contain multiple ranges. Choose the R ange T ype (Inclusive for our example) Save and close the forms. We now have a discovery rule for the 15.2. *. * subnet.


Since we didnt enable ping sweep, we must provide a seed router to get the discovery started.

Add the name or IP address of a router in this subnet to begin the discovery


NNMi uses the following sources of "hints":

ARP cache DNS

P ing

Sweep if configured
Gateway Protocol Discovery Protocol

BGP - Border CDP - Cisco

EIGRP - Cisco

Enhanced Interior Gateway Routing Protocol ENDP - Enterasys Discovery Protocol (also known as CDP - Cabletron Discovery Protocol)
FDP - Foundry OSPF - Open

Discovery Protocol

Shortest P ath First


Youll now begin to see nodes get discovered. You can view the list of discovered nodes in many places in the GUI. T ry the Network Overview under the T opology Maps workspace.
Note that this is usually an abbreviation of the entire set of nodes. You can also see discovery progress using the following graphs:

T ools -> Self-Monitoring Graphs -> Discovery Progress

T ools- > Status Distribution Graphs -> Node Status


Manual Seed Discovery

R ecommended if you know your network well Create a seed file
L ist of management IP s for all the nodes to be managed One IP per line, comments followed by # Example: <IP address> # <DNS name> IP goes under Hostname/IP field and DNS goes to Notes section Notes can later be filtered for troubleshooting based on hostnames

nnmloadseeds.ovpl f <seedfile>


Manual Seed Discovery (cont.)

R ediscovery interval 24 hrs by default L oad the nodes across 24 hrs so that discovery goes across the cycle

example, for loading 3000 nodes manually using a seed file:

L oad 300 nodes at a time every 3 hrs overnight (evening to next day morning)

Ensures that CPU spikes for NNMi server are not occurring daily at the same time


Interface Discovery Filter

Now supports interface filters for discovery Based on the interface groups Interfaces passing this filter do not get added during discovery of new nodes For already existing nodes, next scheduled or manual config poll takes care of removing the filters from the topology


Monitoring Configuration
Default Behavior
N N Mi

monitors connected interfaces where connected means the interface has a discovered connection to another interface in N N Mi. Most access switch ports would not be considered connected if you dont discover end nodes. Instead typically the uplink would be monitored. does ICMP monitoring of management addresses may not need to make any additional changes

N N Mi You


Example of monitoring the uplink


Steps to Modify Monitoring

The basic steps to modify the monitoring in NNM include:

a node group and/or interface group Associate a monitoring setting (polling policy) with the group Prioritize the monitoring setting (nodes and interfaces can match multiple groups)

(by default connected interfaces and management addresses)


Suppose that we have some nodes with an IfAlias that begins with tunnel to.

We have been instructed that these interfaces need to be monitored if their speed is also 9 Kbs.
Well need to create a filter to identify any interfaces that match this criterion. Then well apply a polling policy to these interfaces.


Creating an Interface Group

Under the Configuration Workspace, select Interface Groups


Click on the New icon


Name the new Interface Group Create the filter expression using the logical operands Save the Interface Group Test the membership with Actions -> Show Members


New Filter Operators

N ot operator Exists and N ot Exists allow filters to be created with expected results when combining multiple custom attributes or capabilities

like router* OR EXISTS((customAttrName=edge AND customAttrValue=true)))


R esults of the membership test Watch out for any stale filters on this view that might be inadvertently applied


Apply a P olling P olicy to the Interface Group

In order to poll the interfaces defined by this filter, we must apply a polling policy to this group. Open the Monitoring Configuration view


Since we defined an Interface Filter, select the Interface Settings tab

Note the current ordering values

Click New


Select the Interface Group and enter in an Ordering value We want it to be higher than the other policies (lower number)

Extend the polling beyond connected interfaces

Save and Close the form


T esting the P olling P olicy

Identify the selected interfaces (Well select Inventory->Interfaces and choose our filter in the pull-down menu.)

Open one of the interfaces Select Actions -> Monitoring Settings


Validate the Interface Group policy that is applied Validate that the interface is being polled


Making Exceptions to P olling

Most polled objects can be Unmanaged or set to Out of Service


Custom P oller
Can configure polling to monitor MIB information not monitored by default
Enhanced in 9.0 to support MIB Expressions Setting Up Your MIB

Step 1: Identify the MIB Variable You Want to P oll

Step 2: Ensure the MIB Includes Supported T ypes

Step 3: L oad the R equired MIB Step 4: Use an SNMP Query to View Current MIB Variable Values Step 1: Enable Custom P oller Step 2: Create a Custom P oller Collection Step 3: Create a P olicy for a Custom P oller Collection Step 1: View the Custom Node Collections Associated with Custom P oller P olicies

Setting Up a Custom P oll

Examine the R esults of Your Custom P oll


Step 2: View Details of a Custom Node Collection

Step 3: View Details of a P olled Instance Step 4: Evaluate the R esults of the Custom P oll

MIB Browser
Do an SNMP query to get current values


Enable Custom P oller

Click on Enable Custom P oller to enable


Create a Custom P oller Collection


Create a MIB Expression

See the animation in the online help for a demo on creating a MIB expression


Select a MIB Variable


Thank you for your Attention