Deployment Guide
Figure 3:System > Alerts Page Illustration
Figure 4 below shows an email from the recipient’s perspective.
Figure 4:Email Recipient of an Alert
Below shows the actual alerts output as seen by the NMS server.
Client Count
10:32:52.964243 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto 17, length: 284)
tipi.corp.airwave.com.38979 > airwave-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.airwave.com/ap_monitoringid=11277: AP User Count >= 2 users for 15 minutes"
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)
tipi.corp.airwave.com.38934 > airwave-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.airwave.com/ap_monitoringid=1: Device Down " E:12028.4.104=10.51.3.46 } }
OID Breakdown
12028.4.15.1.102 contains Severity Code
l 1 = Normal
l 2 = Warning
l 3 = Minor
l 4 = Major
l 5 = Critical
4 Integrating W-AirWave with Centralized NMSEvent Correlation | Integration