NNMi Introduction Slide Informative
NNMi Introduction Slide Informative
NNMi Introduction Slide Informative
0) Basics
Introduction
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
Health Checks
P ossible Use Scenarios
3
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
Performance Monitoring
(iSPI Performance for Metrics iSPI Performance for Traffic iSPI Performance for QA)
Advanced Services
(iSPIs for IPT, MC, MPLS)
Automated Diagnostics
(iSPI NET)
Routing Analysis
(RAMS)
Foundation
CMDB Unified Operations Run-Book Automation (Operations Orchestration)
iSPI IP Telephony
NNMi
iSPI MPLS
iSPI IP Multicast
Maximize efficiency of your network operations Single administrative and operational console
- Rapid and continuous discovery - Unifies fault, availability, performance
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
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
Up to 10 weeks of history data stored; hourly summary with configurable period for full detail data
Path health shows component and interface performance along important routes
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 userdefined custom collections
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
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
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
For Cisco IPT, alert based on call quality metrics and state changes
L3 VPN maps visualize PE topology types and connecting CE devices LSR inventory, service details such as VRF and VPN inventory integrated with NNMi
Monitor MPLS core network (LSRs & TEs) and Services (L2 VPN VPWS & VPLS)
The Deployment Reference Guide is the source for detailed information on integrations
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)
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. P aths need to be converted for W indows.
25
26
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
27
is is is is is is is is
is is is is
Initial L ogin
L ogin with browser (no more java plugins required) http://m yserver.example.com/nnm
28
29
30
31
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
T ype in the User Name and P assword (well call ours admin and the password will be adminpw)
33
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.
34
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
35
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 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
37
38
Discovery Configuration
L ist based discovery (similar to loadhosts of legacy NNM)
More No
R equires good
By
default, NNMi only discovery switches and routers (this is easily expanded)
39
40
Select the Auto-Discovery R ules tab and click on the New icon.
41
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.
42
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.
43
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
44
P ing
Sweep if configured
Gateway Protocol Discovery Protocol
EIGRP - Cisco
Enhanced Interior Gateway Routing Protocol ENDP - Enterasys Discovery Protocol (also known as CDP - Cabletron Discovery Protocol)
FDP - Foundry OSPF - Open
Discovery Protocol
45
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:
46
nnmloadseeds.ovpl f <seedfile>
47
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
48
29
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
50
51
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)
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.
53
54
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
57
R esults of the membership test Watch out for any stale filters on this view that might be inadvertently applied
58
59
60
Select the Interface Group and enter in an Ordering value We want it to be higher than the other policies (lower number)
61
62
Validate the Interface Group policy that is applied Validate that the interface is being polled
63
64
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
65
MIB Browser
Do an SNMP query to get current values
66
67
68
69
70