Download - Deploying NNMi 9.0
![Page 1: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/1.jpg)
1 ©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
Deploying NNMi 9.0
Larry Besaw
Chief Architect, NNMi
![Page 2: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/2.jpg)
2
Introduction
– Sample “deployment” on a small test lab
– All using NNMi 9.00
– Will 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:
http://support.openview.hp.com/selfsolve/manuals
![Page 3: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/3.jpg)
3
Steps We‟ll Take
– 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
![Page 4: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/4.jpg)
4
Other Steps We Will Not Cover Include:
– 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 these
topics
![Page 5: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/5.jpg)
5
Assumptions
– 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 be
converted for Windows.
![Page 6: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/6.jpg)
6
After the Install, Validate Processes Are Running
– 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.
![Page 7: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/7.jpg)
7
jboss Processes# ovstatus -v ovjboss
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
![Page 8: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/8.jpg)
8
Initial Login
– Login with browser (no more java plugins required)
– http://myserver.example.com/nnm
![Page 9: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/9.jpg)
9
– Initially log in with the system password created during installation
![Page 10: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/10.jpg)
10
Create a new user
– It‟s best to create an administrator account rather than using
the system login
![Page 11: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/11.jpg)
11
– Click on the Configuration Workspace and select User Interface configuration
![Page 12: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/12.jpg)
12
– 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.)
![Page 13: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/13.jpg)
13
– 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
![Page 14: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/14.jpg)
14
– 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.
![Page 15: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/15.jpg)
15
Apply a License
– 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 using
nnmlicense.ovpl NNM –g
– Or via the command line using
nnmlicense.ovpl NNM -f ./mylicense.key
![Page 16: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/16.jpg)
16
Configure Communication
– Go to the Configuration Workspace and select Communication Configuration
![Page 17: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/17.jpg)
17
– 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
![Page 18: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/18.jpg)
18
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.
![Page 19: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/19.jpg)
19
Discovery Configuration
– 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)
![Page 20: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/20.jpg)
20
– Go to the Configuration Workspace and select Discovery Configuration.
![Page 21: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/21.jpg)
21
– Select the Auto-Discovery Rules tab and click on the New icon.
![Page 22: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/22.jpg)
22
– 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.
![Page 23: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/23.jpg)
23
– 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.
![Page 24: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/24.jpg)
24
– Since we didn‟t 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
![Page 25: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/25.jpg)
25
–NNMi uses the following sources of "hints":• 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
![Page 26: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/26.jpg)
26
– 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
![Page 27: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/27.jpg)
27
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>
![Page 28: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/28.jpg)
28
Manual Seed Discovery (cont.)
– 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
![Page 29: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/29.jpg)
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 of removing the filters from the topology
![Page 30: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/30.jpg)
30
Monitoring Configuration
–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
![Page 31: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/31.jpg)
31
– Example of monitoring the uplink
![Page 32: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/32.jpg)
32
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)
![Page 33: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/33.jpg)
33
– 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.
![Page 34: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/34.jpg)
34
Creating an Interface Group
– Under the Configuration Workspace, select Interface Groups
![Page 35: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/35.jpg)
35
– Click on the New icon
![Page 36: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/36.jpg)
36
– Name the new Interface Group
– Create the filter expression using the logical operands
– Save the Interface Group
– Test the membership with Actions -> Show Members
![Page 37: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/37.jpg)
37
New Filter Operators
– “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=edge
AND customAttrValue=true)))
![Page 38: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/38.jpg)
38
– Results of the membership test
– Watch out for any “stale” filters on this view that might be inadvertently
applied
![Page 39: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/39.jpg)
39
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
![Page 40: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/40.jpg)
40
– Since we defined an Interface Filter, select the Interface Settings tab
– Note the current “ordering” values
– Click New
![Page 41: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/41.jpg)
41
– 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
![Page 42: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/42.jpg)
42
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
![Page 43: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/43.jpg)
43
– Validate the Interface Group policy that is applied
– Validate that the interface is being polled
![Page 44: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/44.jpg)
44
Making Exceptions to Polling
– Most polled objects can be Unmanaged or set to
Out of Service
![Page 45: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/45.jpg)
45
Custom Poller– 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
![Page 46: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/46.jpg)
46
MIB Browser– Do an SNMP query to get current values
![Page 47: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/47.jpg)
47
Enable Custom Poller– Click on “Enable Custom Poller” to enable
![Page 48: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/48.jpg)
48
Create a Custom Poller Collection
![Page 49: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/49.jpg)
49
Create a MIB Expression– See the animation in the online help for a demo on creating a MIB expression
![Page 50: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/50.jpg)
50
Select a MIB Variable
![Page 51: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/51.jpg)
51
Finish Creating the Custom Poller Collection– Can configure thresholds
– Can affect node status and generate an incident
– Can export custom poller data to Metrics SPI for reporting or to CSV files
![Page 52: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/52.jpg)
52
Create a Custom Poller Policy– Specify the Custom Poller Collection we just created, the node group,
any filter, and the polling interval
![Page 53: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/53.jpg)
53
Examine the Results of the Custom Poll– Custom Polled Instances also available on the Node form
![Page 54: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/54.jpg)
54
Incident Configuration
– With NNMi, you can change various aspects of an incident. Some examples include enabling an incident, formatting a message, enabling de-duplication and enabling rate correlation.
– Newly available features are Suppression, Dampening, and Enrichment• Each of these as global settings or per node group or interface group
– Any of these can be applied based on payload filtering of CIA name/value pairs• CIA = Custom Incident Attribute (or varbinds)
– Suppose we wish to enhance the Interface Down incident to include the Interface Alias in the message.
– Open the Incident Configuration view
![Page 55: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/55.jpg)
55
– Choose the Management Event Configuration tab and open the Interface Down incident
– Create filter on basis of any field, multiple filter selection in a single go
![Page 56: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/56.jpg)
56
– We add the argument $ifAlias to our message
– See “Valid Parameters for Configuring Incident Messages” in the help
![Page 57: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/57.jpg)
57
– Now new incidents that arrive in the browser will have the new message format
– If there is no Alias defined, it is shown as null
– Filter on „Last Occurrence time‟ – new filter capabilities
![Page 58: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/58.jpg)
58
Understanding Incident Configuration
Matches
Interface
Settings?
Trap Arrives Matches
Node
Settings?
Apply default
Suppression, Enrichment,
Dampening, Actions
Apply Suppression,
Enrichment, Dampening,
Actions specific to Node
Group
Apply Suppression,
Enrichment, Dampening,
Actions specific to
Interface Group
yes
yes
no no
![Page 59: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/59.jpg)
59
Enrichment– Enrichment allows you to process a node differently based on node or
interface group membership
![Page 60: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/60.jpg)
60
Enrichment (cont.)– For example, can set the Priority to “Top” and assign to a particular
operator
![Page 61: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/61.jpg)
61
Suppression– Suppression allows you to discard an incident
– For example, can suppress a trap if the payload indicates the status is normal
or warning
![Page 62: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/62.jpg)
62
Dampening– Dampening defines a hold period before an incident is released
– If Incident is Closed during this period, it is never released
![Page 63: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/63.jpg)
63
Dampening (cont.)
– Out of the box, APA root cause (down) management events
are dampened for a period of 6 minutes.
• Dampening can be configured to a maximum of one hour.
– If you wish to go back to the original undampened
behavior, you can uncheck the Enable box on each
individual incident. Or alternatively, there is a command
line tool called nnmsetdampenedinterval.ovpl that can be
used to set the dampening period for all incidents. You can
disable dampening “across the board” with the command:
• nnmsetdampenedinterval.ovpl -hours 0 -minutes 0 -seconds 0
![Page 64: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/64.jpg)
64
Custom Correlation• Create new incident correlations of multiple existing child incidents under an existing incident or into a new parent incident • Incident filtering and correlation logic can be based on custom attributes or attribute values of the source node or source object.• NNMi provides a sample Custom Correlation for correlating sub-interface down incidents under the main interface down incident (for Cisco devices)• Another scenario that could be provided here: Forward a „Connection Down‟ event to the NBI only when both Primary and Secondary links go down between two sites
![Page 65: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/65.jpg)
65
Trap Configuration
– Traps must be defined by a MIB
– Load MIBs into NNMi using the nnmincidentcfg.ovpl command• Use the –loadMib or –loadTraps option depending on requirements
– Can alternately use Tools->Load MIB… GUI to load incidents from trap
# nnmincidentcfg.ovpl -u admin -p adminpw -loadMib ./ruggedcom.mib
Mib file loaded: /var/tmp/mibs/./ruggedcom.mib.
# nnmincidentcfg.ovpl -u admin -p adminpw -loadMib ./rcsysinfo.mib
Mib file loaded: /var/tmp/mibs/./rcsysinfo.mib.
# nnmincidentcfg.ovpl -u admin -p adminpw -loadTraps ./ruggedcomtraps.mib
Mib file loaded: /var/tmp/mibs/./ruggedcomtraps.mib.
Number of traps: 4.
The following traps were added to incident configuration:
cfgChangeTrap - .1.3.6.1.4.1.15004.5.4
swUpgradeTrap - .1.3.6.1.4.1.15004.5.3
powerSupplyTrap - .1.3.6.1.4.1.15004.5.2
genericTrap - .1.3.6.1.4.1.15004.5.1
![Page 66: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/66.jpg)
66
– „Discard Unresolved traps‟ – a checkbox to discard traps from devices that are not loaded into NNMi topology
– Block unwanted traps using nnmtrapd.conf and nnmtrapconfig.ovpl• See reference pages for more details
![Page 67: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/67.jpg)
67
Action Configuration
– You can add automatic actions to incidents.
– Usually done on Management Events rather than SNMP Traps because it‟s hard to predict the rate and volume of traps.
– NNMi automatic actions can either be executable commands or command line scripts or Python Scripts.
– In NNMi, actions are based on Lifecycle State change for incidents.
– Suppose you want to take an action when an interface goes down and another action when the interface comes back up again.• Both actions should be placed on the InterfaceDown incident
• One should be associated with the Lifecycle State of “Registered” and the other should be associated with the Lifecycle State of “Closed”
• There will not be an associated “Up” incident.
![Page 68: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/68.jpg)
68
– Suppose we have a script called writelog.ovpl that we want
to run when a Node Down incident arrives
– As root, copy the writelog.ovpl script into the actions
directory
– Windows:
\Documents and Settings\All Users\Application Data\HP\HP BTO
Software\shared\nnm\actions
– UNIX:
/var/opt/OV/shared/nnm/actions
– Confirm that the command is executable
– There is a separate process called „nnmactions‟ now in 9.0
that runs actions
• ovstatus –c shows the status of this process
![Page 69: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/69.jpg)
69
– Open the Management Event Configuration tab from within the
Incident Configuration Form
– Open the Node Down incident
![Page 70: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/70.jpg)
70
– Select the Action Configuration tab and click on the New button
![Page 71: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/71.jpg)
71
– Select the appropriate Lifecycle state (Registered in our example), Command Type (ScriptOrExecutable in our example) and the name of the command (specify the full path).
– Define a payload filter on the basis of CIA names and values • Execute the action only of the source node name is like: *NYC*.usa.hp.com
– Save and Close the form
![Page 72: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/72.jpg)
72
– Last, we must enable the action by checking the Enable box.
– Save and Close the form
![Page 73: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/73.jpg)
73
– Now we should test the action. The easiest way to do this is to look for a previous occurrence of this incident and modify the lifecycle state
![Page 74: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/74.jpg)
74
– We can practice running this action by setting the Lifecycle State back to Registered. This will cause our action to execute after you save this form (thus saving the Lifecycle State change).
– After saving it, we verify that our action ran as expected. We can look at the log file that this sample action script writes to. We should then set the Lifecycle State back to Closed and save the incident to return it to its original state.
![Page 75: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/75.jpg)
75
GUI Configuration - Node Group Map Configuration (aka containers)
– Container maps can be created that will show nodes that are contained in a Node Group
– Let‟s suppose that we wish to create some logical containers for a few different subnets and also nodes based on names. • Subnet A = Management Address of 192.25.*.*• Data Center = nodes that have a system name beginning with “data_center”
– Let‟s suppose we wish to create the hierarchy of groups:
My Network My Important Subnets Subnet A
Data Center
![Page 76: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/76.jpg)
76
– Easiest to work from the leaf groups first
– We create a Node Group for Subnet A
– Test it as previously shown
![Page 77: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/77.jpg)
77
– Now create a node group for the Data Center
![Page 78: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/78.jpg)
78
– Next we must create a Node Group Map for each Node Group in the hierarchy
![Page 79: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/79.jpg)
79
– Save the Layout on each Node Group Map
![Page 80: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/80.jpg)
80
– For “branch” node group maps, no filter is necessary. Instead we only
need to specify the hierarchy by selecting the Child Node Groups.
– Again must create the map for the group.
– Optionally, can expand the child nodes in parent node Group‟s map
![Page 81: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/81.jpg)
81
– We now have a map hierarchy that we can drill down and back. In our
example, you can open the Node Group Map for the node group “My
Network”.
![Page 82: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/82.jpg)
82
– From this map, we can drill down (double click) and back with the
arrows
![Page 83: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/83.jpg)
83
– Background graphics can be easily added
– Change the connectivity type as well – Layer2/Layer3
– Node group connectivity
• Site to Site connections based on End-points
− Show only Gigabit connectivity between sites based on „Interface Groups‟
![Page 84: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/84.jpg)
84
– Sign out and Sign in shows the changes in Node Groups map settings
– We can also change the status propagation algorithms
![Page 85: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/85.jpg)
85
– Select the initial UI launch
– „Last Node group‟ and „First node group‟ in the list• Decided by the „Topology map ordering‟ field
![Page 86: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/86.jpg)
86
SNMP Line Graph Configuration– Can create custom SNMP Line graphs based on MIB expressions
![Page 87: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/87.jpg)
87
SNMP Line Graph Configuration– Can configure custom SNMP Line Graphs as menu items
![Page 88: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/88.jpg)
88
Maintenance
– Backup and Restore• Full backup
−nnmbackup.ovpl / nnmrestore.ovpl
• Embedded database backup−nnmbackupembdb.ovpl / nnmrestoreembdb.ovpl
– Configuration Export and Import • Allows for pinpoint configuration snapshots• Make a snapshot before making any config change
− nnmconfigexport.ovpl / nnmconfigimport.ovpl
![Page 89: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/89.jpg)
89
Maintenance of traps– Need to regularly clean traps from the NNMi database (not the trap
store)nnmtrimincidents.ovpl –u system –p mypassword -age 1
-incr weeks -origin SnmpTrap –trimOnly –quiet
Trap Store
incoming
traps
NNMi Database
Tra
p S
erv
ice
filt
erin
g
Incid
en
t C
on
fig
ura
tio
n
NNMi
Trap
Service
nnmtrapdump.ovpl
NNMi
User
Interface
(nnmtrapconfig.ovpl)
![Page 90: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/90.jpg)
90
Health Checks – Run ovstatus –v to make sure the jboss processes are running well
– Launch the Help->System Information menu item for a listing of some important data points like Database objects, NNMi system health, Statepoller detailed health
![Page 91: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/91.jpg)
91
NNMi Self-Monitoring
– Monitors itself and generated incident in case non-Normal health
![Page 92: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/92.jpg)
92
NNMi Status and Health Reports
– Tools NNMi Status and Status Health reports show details on NNMi
process and overall status
![Page 93: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/93.jpg)
93
Status Distribution Graphs
– Tools Status distribution graphs• Nodes, Interfaces and IP address Status graphs
![Page 94: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/94.jpg)
94
Self-monitoring Graphs
– Tools NNMi Self-Montioring • Discovery progress, Trap rate graphs, SNMP request stats etc
![Page 95: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/95.jpg)
95
– Load the MIBs from UI now
– Open the MIB Browser UI for more details on MIB tree
![Page 96: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/96.jpg)
96
Audit the Node for Supported MIBs
![Page 97: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/97.jpg)
97
Possible Usage Scenarios
– Management by Exception
![Page 98: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/98.jpg)
98
– Layer 2 map showing outage
![Page 99: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/99.jpg)
99
– Investigate conclusions, history of status, incidents
– Run actions like ping, trace route, etc.
![Page 100: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/100.jpg)
100
Map-based Management
![Page 101: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/101.jpg)
101
List-based Management
![Page 102: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/102.jpg)
102
Miscellaneous Tips
– Use the embedded database even for large scale.
– Use caution with SNMP timeout configuration. This timeout value is incremented with each timeout and can grow quickly beyond your original intention. Keep your ping timeout and your SNMP timeout fairly equal in time.
– Use the Conclusions tab in the Node Form to understand why the current status is set for the node.
– Reduce the number of connections between node groups via the End Points Filter in the Node Group Map settings form.
– Do not use a “@” in your SNMP strings. This is a reserved character for Cisco devices and causes NNMi grief if used.
![Page 103: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/103.jpg)
103
Outcomes
–NNMi 9 is quick and easy to
deploy
–More advanced customization is
available if needed
![Page 104: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/104.jpg)
104
Q&A
![Page 105: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/105.jpg)
105©2010 Hewlett-Packard Development Company, L.P.
To learn more on this topic, and to connect with your peers after
the conference, visit the HP Software Solutions Community:
www.hp.com/go/swcommunity
![Page 106: Deploying NNMi 9.0](https://reader033.vdocument.in/reader033/viewer/2022050709/5470659eb4af9fae0a8b46f0/html5/thumbnails/106.jpg)
106