STN-OSPF-TRAP-MIB
File:
STN-OSPF-TRAP-MIB.mib (15889 bytes)
Imported modules
Imported symbols
Defined Values
stnOspfTrap |
1.3.6.1.4.1.3551.2.12.4.8.1 |
This MIB module describes traps for the OSPF
Version 2 Protocol. |
MODULE-IDENTITY |
|
|
|
stnOspfVirtIfStateChange |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.1 |
A stnOspfVirtIfStateChange 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).
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfNbrStateChange |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.2 |
A stnOspfNbrStateChange 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 transitioning to Down will be noted by
ospfIfStateChange.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfVirtNbrStateChange |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.3 |
A stnOspfVirtNbrStateChange 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).
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfIfConfigError |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.4 |
An stnOspfIfConfigError 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.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfVirtIfConfigError |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.5 |
A stnOspfVirtIfConfigError 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.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfIfAuthFailure |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.6 |
A stnOspfIfAuthFailure 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.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfVirtIfAuthFailure |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.7 |
A stnOspfVirtIfAuthFailure 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.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfIfRxBadPacket |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.8 |
A stnOspfIfRxBadPacket trap signifies that an OSPF packet has
been received on a non-virtual interface that cannot be parsed.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfVirtIfRxBadPacket |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.9 |
An stnOspfVirtIfRxBadPacket trap signifies that an OSPF packet
has been received on a virtual interface that cannot be parsed.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfTxRetransmit |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.10 |
A stnOspfTxRetransmit 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.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfVirtIfTxRetransmit |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.11 |
A stnOspfVirtIfTxRetransmit trap signifies than an OSPF packet
has been retransmitted on a 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.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfOriginateLsa |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.12 |
A stnOspfOriginateLsa 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.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfMaxAgeLsa |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.13 |
A stnOspfMaxAgeLsa trap signifies that one of the LSA in the
router's link-state database has aged to MaxAge.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfLsdbOverflow |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.14 |
A stnOspfLsdbOverflow trap signifies that the number of LSAs in
the router's link-state database has exceeded ospfExtLsdbLimit.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfLsdbApproachingOverflow |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.15 |
A stnOspfLsdbApproachingOverflow trap signifies that the number
of LSAs in the router's link state database has exceeded ninety
percent of ospfExtLsdbLimit.
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
stnOspfIfStateChange |
1.3.6.1.4.1.3551.2.12.4.8.1.2.0.16 |
A stnOspfIfStateChange 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).
The generation of this trap can be controlled by the OSPFTraps
configuration object. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|