Extreme Networks EPICenter Reference Manual page 530

Event Types for Alarms
Table 58: SNMP Trap Events (continued)
Event
MSM Failover Occurred
Main Power Usage Off
Main Power Usage On
Netlogin
Authentication Failure
Netlogin User Login
Netlogin User Logout
OSPF Interface
Authentication Failure
OSPF Interface Config
Error
OSPF Interface
Receive Bad Packet
OSPF Interface State
Change
OSPF LSDB
Approaching Overflow
OSPF LSDB Overflow
OSPF Max_Age LSA
OSPF Neighbor State
Change
530
Definition
Extreme Networks proprietary trap. An MSM Failover occurred.
Indicates the PSE Threshold usage indication off, the usage
power is below the threshold. At least 500 msec must elapse
between notifications being emitted by the same object
instance.
Indicates the PSE threshold usage indication is on, and the
usage power is above the threshold. At least 500 msec must
elapse between notifications being emitted by the same object
instance.
Extreme Networks proprietary trap. Generated upon
authentication failure for a netlogin supplicant.
Extreme Networks proprietary trap. Generated when a netlogin
supplicant passes authentication and logs in successfully into
the network.
Extreme Networks proprietary trap. Generated when an
authenticated and logged in netlogin supplicant logs out.
An ospfIfAuthFailure trap signifies that a packet has been
received on a non-virtual interface from a router whose
authentication key or authentication type conflicts with this
router's authentication key or authentication type.
An ospfIfConfigError trap signifies that a packet has been
received on a non-virtual interface from a router whose
configuration parameters conflict with this router's configuration
parameters. Note that the event optionMismatch should cause a
trap only if it prevents an adjacency from forming.
An ospfIfRxBadPacket trap signifies that an OSPF packet has
been received on a non-virtual interface that cannot be parsed.
An ospfIfStateChange trap signifies that there has been a
change in the state of a non-virtual OSPF interface. This trap
should be generated when the interface state regresses (e.g.,
goes from Dr to Down) or progresses to a terminal state (i.e.,
Point-to-Point, DR Other, Dr, or Backup).
An ospfLsdbApproachingOverflow trap signifies that the number
of LSAs in the router's link-state database has exceeded ninety
percent of ospfExtLsdbLimit.
An ospfLsdbOverflow trap signifies that the number of LSAs in
the router's link-state database has exceeded ospfExtLsdbLimit.
An ospfMaxAgeLsa trap signifies that one of the LSA in the
router's link-state database has aged to MaxAge.
An ospfNbrStateChange trap signifies that there has been a
change in the state of a non- virtual OSPF neighbor.
should be generated when the neighbor state regresses (e.g.,
goes from Attempt or Full to 1-Way or Down) or progresses to a
terminal state (e.g., 2-Way or Full). When an neighbor
transitions from or to Full on non-broadcast multi-access and
broadcast networks, the trap should be generated by the
designated router. A designated router transitioned to Down will
be noted by ospfIfStateChange.
ExtremeWare/
ExtremeXOS
Version
ExtremeXOS 10.1
ExtremeXOS 11.1
ExtremeXOS 11.1
Not supported in
ExtremeXOS
Not supported in
ExtremeXOS
Not supported in
ExtremeXOS
ExtremeWare 6.1.9
ExtremeXOS 10.1
ExtremeWare 6.1.9
ExtremeXOS 10.1
ExtremeWare 6.1.9
ExtremeXOS 10.1
ExtremeWare 6.1.9
ExtremeXOS 10.1
ExtremeWare 6.1.9
ExtremeXOS 10.1
ExtremeWare 6.1.9
ExtremeXOS 10.1
ExtremeWare 6.1.9
ExtremeXOS 10.1
ExtremeWare 6.1.9
This trap ExtremeXOS 10.1
EPICenter Reference Guide