Dell PowerConnect W-Airwave 7.4 Service Manual
Integrating Dell PowerConnect W-AirWave 7.4
AMP with Centralized NMS Event Correlation
Overview
This document describes AMP’s alert/trap workflow when integrating with a centralized NMS Event Correlation
System, using the following topics:
“Adding NMS Event Correlation Servers to AMP” on page1
“Configuring Alerts/Traps in AMP” on page1
“Viewing Alerts in Various Destinations” on page2
“Acknowledging Alerts” on page3
“Compiling AMP’s MIB on NMS” on page3
“Matching AMP’s Severity in the NMS Event Correlation Servers” on page3
“Enhanced Integration” on page4
“Actual MIB” on page4
Adding NMS Event Correlation Servers to AMP
1. Navigate to AMP Setup > NMS and click Add.
2. Configure server settings, as shown in Figure 1.
Figure 1 AMP Setup > NMS Page Illustration
Configuring Alerts/Traps in AMP
1. Navigate to Systems > Triggers, as shown in Figure 2.
2. Select one of the built-in Alerts/Traps.
0511042-01 | December 2011 1
3. Click Add.
Figure 2 Configuring a Device Count Trigger
Configure properties for the Alert/Trap
Thresholds for the alert (quantity and time)
Severity of alert
Distribution options
Notification Method
Sender
Recipient
NMS – sends SNMP traps
Alert Suppression
Viewing Alerts in Various Destinations
As seen on AMP’s console System > Alerts page
Figure 3 System > Alerts Page Illustration
As seen in email from the recipient’s perspective
Figure 4 Email recipient of an alert
2 Dell PowerConnect W-AirWave 7.4 | NMS Integration Guide
As seen by the NMS server via a tcpdump of the actual alert
Device User Count
10:32:52.964243 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto 17, length: 284) demo.amp.com.38979 > amp-openvie.snmptrap:
[bad udp cksum ebf4!] { SNMPv2c C=foo { V2Trap(242) R=47680 system.sysUpTime.0=10 S:1.1.4.1.0=E:12028.4.15.0.3
E:12028.4.15.1.101=2 E:12028.4.15.1.102=4 E:12028.4.15.1.103="Device: HQ-Engineering -
https://demo.amp.com/ap_monitoringid=11277: AP User Count >= 2 users for 60 seconds" E:12028.4.104=10.2.26.164 } }
Device Down
10:32:23.055999 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto 17, length: 261) demo.amp.com.38934 > amp-openvie.snmptrap:
[bad udp cksum e740!] { SNMPv2c C=foo { V2Trap(219) R=47676 system.sysUpTime.0=10 S:1.1.4.1.0=E:12028.4.15.0.13
E:12028.4.15.1.101=2 E:12028.4.15.1.102=4 E:12028.4.15.1.103="Device: Aruba-AP65-ap.2.2.3 - https://demo.amp.com/
ap_monitoringid=11797: Device Down " E:12028.4.104=10.51.3.46 } }
OID Breakdown
12028.4.15.1.102 contains Severity Code
2 = Normal
3 = Warning
4 = Minor
5 = Major
6 = Critical
12028.4.15.1.103 contains several fields separated by colons
Object Type {Client, AMP, Device/AP, Group)
Object Name and URL (the URL is optional, if it exist then it will be separated by a dash “-“}
Trap Description and Evaluation Elements
12028.4.15.1.104 contains device IP Address
Group Traps will contain AMP’s IP address.
Acknowledging Alerts
AMP alerts must be manually acknowledge from the System > Alert page. AMP does not currently provide an
external interface to acknowledge alerts from an NMS server.
Compiling AMP’s MIB on NMS
1. Navigate to AMP Setup > NMS.
2. Click on the Download link.
3. Transfer to NMS server.
4. Compile on NMS server.
Matching AMP’s Severity in the NMS Event Correlation Servers
Most NMS Event Correlation systems have the ability to color code and esclate based on information received in
the trap, as shown in Figure 5. The OID 12028.4.15.1.102 contians AMP’s severity code.
Dell PowerConnect W-AirWave 7.4 | NMS Integration Guide 3
Loading...