• Authentication failure notifications
• Enterprise change notifications
• Intrusion alarm notifications
Event scenario matrix
Different event scenarios for which traps are generated:
Event Id Severity Action Message
68 Info Slot Insertion I 06/20/16 09:18:43 00068 chassis: AM1: Slot C Inserted
67 Info Slot Removal I 06/20/16 09:18:50 00067 chassis: AM1: Slot C Removed
405 Info Transceiver Insertion I 06/20/16 09:18:56 00405 ports: AM1: port A23 xcvr hot-
swap insert
406 Info Transceiver Removal I 06/20/16 09:19:04 00406 ports: AM1: port A23 xcvr hot-
swap remove
552 Warning Stacking module
Insertion
W 04/20/16 09:20:43 00552 chassis: ST1-CMDR: Stacking
Module insertion detected: Reboot required
552 Warning Stacking module
Removal
W 06/20/16 09:19:43 00552 chassis: ST1-CMDR: Stacking
Module removal detected: Reboot required
Enabling and disabling traps
Action Command
Disable both the log and
trap
setMib eventType.<event_Id> -i 1 – to disable both log & Trap
Enable log only
setMib eventType.<event_Id> -i 2 – to allow only log
Enable both the log and
trap (Default)
setMib eventType.<event_Id> -i 4 – to allow both log & Trap
Enable trap only
setMib eventType.<event_Id> -i 3 – to allow only trap
NOTE: If the event is configured to disable a trap, then the trap will not be sent for that particular
event. In all other scenarios, a trap is generated for the listed events.
SNMP trap captures examples
Inserting a slot module
Event Id: 68
208 Aruba 2930F / 2930M Management and Configuration Guide
for ArubaOS-Switch 16.08
To Next Page
Loading...
