FOUNDRY-SN-ROUTER-TRAP-MIB
File:
FOUNDRY-SN-ROUTER-TRAP-MIB.mib (15752 bytes)
Imported modules
Imported symbols
Defined Values
| snTrapOspfIfStateChange |
3 |
| 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). |
| TRAP-TYPE |
|
|
|
| snTrapOspfVirtIfStateChange |
4 |
| An ospfIfStateChange trap signifies that there
has been a change in the state of an OSPF vir-
tual interface.
This trap should be generated when the inter-
face state regresses (e.g., goes from Point-
to-Point to Down) or progresses to a terminal
state (i.e., Point-to-Point). |
| TRAP-TYPE |
|
|
|
| snOspfNbrStateChange |
5 |
| 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 gen-
erated by the designated router. A designated
router transitioning to Down will be noted by
ospfIfStateChange. |
| TRAP-TYPE |
|
|
|
| snOspfVirtNbrStateChange |
6 |
| An ospfIfStateChange trap signifies that there
has been a change in the state of an OSPF vir-
tual 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). |
| TRAP-TYPE |
|
|
|
| snOspfIfConfigError |
7 |
| An ospfIfConfigError trap signifies that a
packet has been received on a non-virtual in-
terface from a router whose configuration
parameters conflict with this router's confi-
guration parameters. Note that the event op-
tionMismatch should cause a trap only if it
prevents an adjacency from forming. |
| TRAP-TYPE |
|
|
|
| snOspfVirtIfConfigError |
8 |
| An ospfConfigError trap signifies that a pack-
et 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 ad-
jacency from forming. |
| TRAP-TYPE |
|
|
|
| snOspfIfAuthFailure |
9 |
| An ospfIfAuthFailure trap signifies that a
packet has been received on a non-virtual in-
terface from a router whose authentication key
or authentication type conflicts with this
router's authentication key or authentication
type. |
| TRAP-TYPE |
|
|
|
| snOspfVirtIfAuthFailure |
10 |
| An ospfVirtIfAuthFailure trap signifies that a
packet has been received on a virtual interface
from a router whose authentication key or au-
thentication type conflicts with this router's
authentication key or authentication type. |
| TRAP-TYPE |
|
|
|
| snOspfIfRxBadPacket |
11 |
| An ospfIfRxBadPacket trap signifies that an
OSPF packet has been received on a non-virtual
interface that cannot be parsed. |
| TRAP-TYPE |
|
|
|
| snOspfVirtIfRxBadPacket |
12 |
| An ospfRxBadPacket trap signifies that an OSPF
packet has been received on a virtual interface
that cannot be parsed. |
| TRAP-TYPE |
|
|
|
| snOspfTxRetransmit |
13 |
| An ospfTxRetransmit trap signifies than an
OSPF packet has been retransmitted on a non-
virtual interface. All packets that may be re-
transmitted are associated with an LSDB entry.
The LS type, LS ID, and Router ID are used to
identify the LSDB entry. |
| TRAP-TYPE |
|
|
|
| ospfVirtIfTxRetransmit |
14 |
| An ospfTxRetransmit trap signifies than an
OSPF packet has been retransmitted on a virtual
interface. All packets that may be retransmit-
ted are associated with an LSDB entry. The LS
type, LS ID, and Router ID are used to identify
the LSDB entry. |
| TRAP-TYPE |
|
|
|
| snOspfOriginateLsa |
15 |
| 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 happesn every 30 minutes), but
instead will only be invoked when an LSA is
(re)originated due to a topology change. Addi-
tionally, this trap does not include LSAs that
are being flushed because they have reached
MaxAge. |
| TRAP-TYPE |
|
|
|
| snOspfMaxAgeLsa |
16 |
| An ospfMaxAgeLsa trap signifies that one of
the LSA in the router's link-state database has
aged to MaxAge. |
| TRAP-TYPE |
|
|
|
| snOspfLsdbOverflow |
17 |
| An ospfLsdbOverflow trap signifies that the
number of LSAs in the router's link-state data-
base has exceeded ospfExtLsdbLimit. |
| TRAP-TYPE |
|
|
|
| snOspfLsdbApproachingOverflow |
18 |
| An ospfLsdbApproachingOverflow trap signifies
that the number of LSAs in the router's link-
state database has exceeded ninety percent of
ospfExtLsdbLimit. |
| TRAP-TYPE |
|
|
|