HP Network Node Manager(NNMi (9.0) Basics

Introduction

2

– Sample “deployment” on a small test lab

– All using NNMi 9.00

– Will not address NNM 6.x/ 7.x to NNMi upgrades. will be a virgin installation of NNMi 9.00

This

– Goal is to give you a feel for what is required and for you tosee 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:http://support.openview.hp.com/selfsolve/manuals

Steps We‟ll Take

3

– Initial Login and User Creation

– Apply license

– Configure Communication

– Configure Discovery

– Configure Monitoring

– Configure Incidents, Traps and Automatic Actions

– Configure the Graphical User Interface

– Maintenance

– Health Checks

– Possible 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

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

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

HP Network Management Center

Change, Configuration & Compliance(Network Automation)

Fault & Availability Monitoring

(NNMi or NNMi Advanced)

Performance Monitoring(iSPI Performance for MetricsiSPI Performance for Traffic

iSPI Performance for QA)

Advanced Services(iSPIs for IPT, MC, MPLS)

Foundation

HP Network Management Center

BSM Dashboard

Historical Data Warehouse &

Reporting(Performance Insight)

CMDB Run-Book Automation (Operations Orchestration)

Automated Diagnostics

(iSPI NET)

Routing Analysis(RAMS)

Unified Operations

NNMi – The consolidation point for fault, availability, performance and advanced services

iSPI IP Telephony

iSPI MPLSiSPI Perf Traffic

iSPI Perf QA

iSPI Perf Metrics

NNMi

iSPI NET

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

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

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

Customizable node groups for logical partitioning including custom attribute selection

NNMi scales to meet your needs

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

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

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

NNMi Advanced GNM architecture enables consolidation with regional control and survivability

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

Discover & monitor virtualized environments

with NNMi Advanced

Supported to run on virtual server environments

Discover and monitor network device redundancy configurations *

Discover and map VMware hosts and guests *

Find Attached Switch Port for virtualized systems *

* NNMi Advanced only

NNMi iSPI Performance for Metrics

Performance status, thresholds & incidents integrated with fault and topology

Polling and administration unified with NNMi and configurable per node group

Report on interfaces and node component statistics

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

OOB reports at hourly, daily, weekly or monthly level

iSPI Performance for Metrics (continued)

Flexibility in reporting specific to your environmentPath health shows component and interface performance along important routes

Detect negative performance trends before they affect users

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

on additional optional iSPI data for Traffic and QA as well as user-defined custom collections

Interactive navigation select any criteria for filtering and grouping

iSPI Performance for Traffic

Augment operational performance monitoring with network traffic flow detail

Collection, analysis, and presentation of NetFlow and sFlow traffic information

Configuration and tight integration with NNMi, including traffic maps launch

Application mapping to traffic flow, configurable by collection point

Reports out-of-the-box or customizable, with flexible grouping

Highly scalable distributed collection architecture – low overhead

iSPI Performance for Quality Assurance

unifying network service quality management with network management

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

Detect and pinpoint network service degradation early

Site-specific threshold administration

Common iSPI Performance user interface, low overhead

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

NNM iSPI Network Engineering Toolset (iSPI NET)

Automate common data collection tasks

Save engineering effort logging into individual devices for information and diagnosis

Export NNMi discovered topology to Visio for offline use

Trap analytics enable tuning of SNMP trap sources and incident generation

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 Telephonycomprehensive monitoring for Cisco, Nortel, or Avaya IPT infrastructure

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

Scale up to 50,000 phones and associated devices

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

For Avaya IPT, alert based on performance and usage

Flexible reporting aligned with iSPI Performance

iSPI for MPLSAutomated discovery and monitoring for MPLS services

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

MTTR and MTBF reporting for VPN-VRF

LSR inventory, service details such as VRF and VPN inventory integrated with NNMi

L3 VPN maps visualize PE topology types and connecting CE devices

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 BAC–RUM 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?

• 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

Increase service levels and efficiency while reducing costs

22

Challenges to Maximizing NNMi’s 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 Will Not Cover Include:

24

– Machine sizing

– NNMi 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 thesetopics

Assumptions

25

– Installation has already been done• Installation Hints: Check all prerequisites especially kernel parameters,shared memory, semaphores, RAM, etc.

– This example is done on a Unix machine. Paths need to beconverted for Windows.

After the Install, Validate Processes Are Running

26

– At command line, run “ovstatus –c” for a basic check.

– Most processes are now within the ovjboss so you must alsorun “ovstatus –v” for the details of the jboss

services.

jboss Processes# ovstatus -v ovjboss

27

object manager name: ovjboss

state: RUNNING

PID: 20413

last message: Initialization complete.

exit status: -additional info:

SERVICE STATUS

CPListener Service is started

CommunicationModelService Service is started

CommunicationParametersStatsService Service is started

CustomPoller Service is started

EventsCustomExportService Service is started

ExtensionDeployer Service is started

InstanceDiscoveryService Service is started

IslandSpotterService Service is started…

KeyManager Service is started

StagedSnmp Service is started

StatePoller Service is started

TrustManager Service is started

Initial Login

28

– Login with browser (no more java plugins required)

– http://myserver.example.com/nnm

– Initially log in with the system password created during installation

29

Create a new user

30

– It‟s best to create an administrator account rather than using

the system login

– Click on the Configuration Workspace and select User Interface configuration

31

– 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.)

32

– Type in the User Name and Password (we‟ll call ours “admin” and the

password will be “adminpw”)

– Select the role and hit save and close

33

– We now have an admin account

– Try logging out and back in with the new account.

You can see the userpresently logged in to this session in the

upper right.

34

Apply a License

35

– Product comes with a 250 node instant on license.You don‟t 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 usingnnmlicense.ovpl NNM –g

– Or via the command line usingnnmlicense.ovpl NNM -f ./ mylicense.key

Configure Communication– Go to the Configuration Workspace and select

Communication Configuration

36

– Select the Default Community Strings tab and click on the New icon.Enter all of your SNMP Read Community Strings here.

– Order does not matter. NNMi 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

37

SNMP Management Address Discovery– Leave “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.

38

Discovery Configuration

39

– List based discovery (similar to loadhosts of legacy NNM)• More control

• No surprises

• Requires high level of knowledge of nodes

• Only name or IP is required. No subnet masks required

• Static data

– Auto-discovery (we‟ll use this for our example)• Always up to date

• Requires good “rules” to control breadth of discovery

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

– Go to the Configuration Workspace and select Discovery

Configuration.

40

– Select the Auto-Discovery Rules tab and click on the New icon.

41

– Fill out the Basics section and click on the New icon for the IP Address Ranges in this rule. The value for Ordering doesn‟t matter in this case since we‟ll only have one auto-discover rule.

42

– Type in a range. A rule can contain multiple ranges.

– Choose the Range Type (Inclusive for our example)

– Save and close the forms.

– We now have a discovery rule for the 15.2.*.* subnet.

43

– Since we didn‟t enable “ping sweep”, we must provide a seed router to get thediscovery started.

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

44

– NNMi uses the following sources of "hints":

45

• ARP cache• DNS• Ping Sweep if configured• BGP - Border Gateway Protocol• CDP - Cisco Discovery Protocol• EIGRP - Cisco Enhanced Interior Gateway Routing Protocol• ENDP - Enterasys Discovery Protocol (also known as CDP - Cabletron Discovery Protocol)

• FDP - Foundry Discovery Protocol• OSPF - Open Shortest Path First

– You‟ll now begin to see nodes get discovered. You can view the list of discovered nodes in many places in the GUI. Try the Network Overview under the Topology 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:• Tools -> Self-Monitoring Graphs -> Discovery Progress

• Tools- > Status Distribution Graphs -> Node Status

46

Manual Seed Discovery– Recommended if you know your

network well– Create a seed file

• List of management IPs 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>

47

Manual Seed Discovery (cont.)

48

– Rediscovery interval 24 hrs by default

– Load the nodes across 24 hrs so that discovery goes across the cycle• For example, for loading 3000 nodes manually using a seed file:

– Load 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

29

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 ofremoving the filters from the topology

Monitoring Configuration

50

–Default Behavior• NNMi monitors “connected” interfaces where connected means the interface has a discovered connection to another interface in NNMi. Most access switch ports would not be considered connected if you don‟t discover end nodes. Instead typically the uplink would be monitored.

• NNMi does ICMP monitoring of management addresses• You may not need to make any additional changes

– Example of monitoring the uplink

51

Steps to Modify Monitoring

– The basic steps to modify the monitoring in NNM include:• Create 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)

52

– 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.

– We‟ll need to create a filter to identify any interfaces that match this criterion.

– Then we‟ll apply a polling policy to these interfaces.

53

Creating an Interface Group– Under the Configuration Workspace, select Interface Groups

54

– Click on the New icon

55

– Name the new Interface Group

– Create the filter expression using the logical operands

– Save the Interface Group

– Test the membership with Actions -> Show Members

56

New Filter Operators

57

– “Not” operator

– “Exists” and “Not Exists” allow filters to be created with expected results when combining multiple custom attributes or capabilities• (hostname like router*.hp.com OR EXISTS((customAttrName=edgeAND customAttrValue=true)))

– Results of the membership test

– Watch out for any “stale” filters on this view that might be inadvertentlyapplied

58

Apply a Polling Policy 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

59

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

– Note the current “ordering” values

– Click New

60

– 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

61

Testing the Polling Policy

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

– Open one of the interfaces

– Select Actions -> Monitoring Settings

62

– Validate the Interface Group policy that is applied

– Validate that the interface is being polled

63

Making Exceptions to Polling

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

64

Custom Poller

65

– 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 Poll• Step 2: Ensure the MIB Includes Supported Types• Step 3: Load the Required MIB• Step 4: Use an SNMP Query to View Current MIB Variable Values

– Setting Up a Custom Poll• Step 1: Enable Custom Poller• Step 2: Create a Custom Poller Collection• Step 3: Create a Policy for a Custom Poller Collection

– Examine the Results of Your Custom Poll• Step 1: View the Custom Node Collections Associated with Custom Poller Policies

• Step 2: View Details of a Custom Node Collection• Step 3: View Details of a Polled Instance• Step 4: Evaluate the Results of the Custom Poll

MIB Browser– Do an SNMP query to get current values

66

Enable Custom Poller– Click on “Enable Custom Poller” to enable

67

Create a Custom Poller Collection

68

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

69

Select a MIB Variable

70

Thank you for your Attention