Extreme Networks EPICenter Software Installation Manual page 513

Table 25: SNMP Trap Events (continued)
Event
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
OSPF Originate LSA
OSPF TX_Retransmit
OSPF Virtual Interface
Authentication Failure
OSPF Virtual Interface
Config Error
OSPF Virtual Interface
Receive Bad Packet
EPICenter Software Installation and User Guide
Definition
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. This trap 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.
An ospfOriginateLsa trap signifies that a new LSA has been originated
by this router. This trap should not be invoked for simple refreshes of
LSAs (which happens every 30 minutes), but instead will only be
invoked when an LSA is (re)originated due to a topology change.
Additionally, this trap does not include LSAs that are being flushed
because they have reached MaxAge.
An ospfTxRetransmit trap signifies than an OSPF packet has been
retransmitted on a non- virtual interface. All packets that may be
retransmitted are associated with an LSDB entry. The LS type, LS ID,
and Router ID are used to identify the LSDB entry.
An ospfVirtIfAuthFailure trap signifies that a packet has been received
on a virtual interface from a router whose authentication key or
authentication type conflicts with this router's authentication key or
authentication type.
An ospfVirtIfConfigError trap signifies that a packet has been received
on a 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 ospfVirtIfRxBadPacket trap signifies that an OSPF packet has
been received on a virtual interface that cannot be parsed.
SNMP Trap Events
ExtremeWare
Version
6.1.9 or later
6.1.9 or later
6.1.9 or later
6.1.9 or later
6.1.9 or later
6.1.9 or later
6.1.9 or later
6.1.9 or later
6.1.9 or later
6.1.9 or later
6.1.9 or later
6.1.9 or later
6.1.9 or later
513