Event Types for Alarms
Table 58: SNMP Trap Events (continued)
Event
Wireless Port Boot
Failed
Wireless Port State
Changed
Wireless Probe Info
Added
Wireless Probe Info
Removed
lldp Remote Table
Changed
Configuring SNMP Trap Events
There are a number of SNMP events that require configuration on the switch before they can be used in
EPICenter alarm definitions. If the configuration is not done on the switch, no trap events are
generated, and no EPICenter alarms for those events can occur. The Ping and OSPF traps fall into this
category.
To configure the switch to send one of these traps, you must use a tool that allows you to set the value
of the appropriate SNMP variable. Tools such as SNMPc can be used to perform this function. The
following information assumes that you have a thorough understanding of SNMP and an appropriate
SNMP utility.
Refer to the appropriate MIBs for details of the variable settings:
Ping MIB: pingmib.mib (RFC 2925)
●
OSPF v2 MIB: RFC 1850 or RFC 1850t
●
Table 59: Trap Variable Configuration
Trap
Ping Probe Failed
Ping Test Failed
Ping Test Completed
534
Definition
Extreme Networks proprietary trap. Sent by the platform if a
wireless port fails to boot too many times.
Extreme Networks proprietary trap. Generated when a wireless
port moves into enabled, disabled, or online state.
Extreme Networks proprietary trap. Generated when a new
station is added to the probe info table. Generated only if the
value of extremeWirelessProbeInfoSendAddedTrap is true.
Extreme Networks proprietary trap. Generated when a station is
removed from the probe info table. Generated only if the value
of extremeWirelessProbeInfoSendRemovedTrap is true.
A lldpRemTablesChange notification is sent when the value of
lldpStatsRemTableLastChangeTime changes. It can be utilized
by an NMS to trigger LLDP remote systems table maintenance
polls.
Note that transmission of lldpRemTablesChange notifications
are throttled by the agent, as specified by the
'lldpNotificationInterval' object.
Variables
set pingCtlTrapGeneration bit 0 ON to enable trap.
set pingCtlTrapProbeFailureFilter to specify the number of
successive probe failures that must occur to generate a Probe
Failed trap.
set pingCtlTrapGeneration bit 1 ON to enable trap.
set pingCtlTrapTestFailureFilter to specify the number of
successive test failures that must occur to generate a Test Failed
trap.
set pingCtlTrapGeneration bit 2 ON to enable the trap.
ExtremeWare/
ExtremeXOS
Version
ExtremeWare 7.3
Not supported in
ExtremeXOS
ExtremeWare 7.3
Not supported in
ExtremeXOS
ExtremeWare 7.3
Not supported in
ExtremeXOS
ExtremeWare 7.3
Not supported in
ExtremeXOS
ExtremeXOS 11.4/
Supported by Avaya
devices
EPICenter Reference Guide
Need help?
Do you have a question about the EPICenter and is the answer not in the manual?