Avaya 8800 Traps Reference page 35

OID
1.3.6.1.2.1.14.1
6.2.1
1.3.6.1.2.1.14.1
6.2.2
1.3.6.1.2.1.14.1
6.2.3
1.3.6.1.2.1.14.1
6.2.4
Traps Reference
Notification type
ospfVirtIfStateCh ospfRouterId
ange ospfVirtIfAreaId
ospfVirtIfNeighbo
r ospfVirtIfState
ospfNbrStateCha ospfRouterId
nge ospfNbrIpAddr
ospfNbrAddressL
essIndex
ospfNbrRtrId
ospfNbrStat
ospfVirtNbrState ospfRouterId
Change ospfVirtNbrArea
ospfVirtNbrRtrId
ospfVirtNbrState
ospfIfConfigError ospfRouterId
ospfIfIpAddress
ospfAddressLessI
f ospfPacketSrc
ospfConfigErrorT
ype
ospfPacketType
Objects
An ospfIfStateChange trap
signifies that there has been a
change in the state of an OSPF
virtual interface. This trap
should be generated when the
interface state regresses (e.g.,
goes from Point-to-Point to
Down) or progresses to a
terminal state (i.e., Point-to-
Point).
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 a 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 transitioning to Down will
be noted by ospfIfStateChange
An ospfIfStateChange trap
signifies that there has been a
change in the state of an OSPF
virtual 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., Full).
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.
Standard traps
Description
January 2014 35