Home/Catalog/NETSCREEN-OSPF-TRAP-MIB

NETSCREEN-OSPF-TRAP-MIB

AI MIB Summary

The NETSCREEN-OSPF-TRAP-MIB module defines SNMP trap notifications for Juniper NetScreen devices running OSPF Version 2, specifically alerting on topology changes, neighbor state transitions (such as Up/Down events), and link-state database synchronization failures.

The MIB module to describe traps for the OSPF Version 2 Protocol.
Main OID:
nsOspfTrap.1.3.6.1.4.1.3224.18.2.16
23
Objects
Active
Status
4
Dependencies

Imported Objects

Objects

23 total
Object Name
nsOspfTrapThe MIB module to describe traps for the OSPF Version 2 Protocol.
MODULE-IDENTITY
.1.3.6.1.4.1.3224.18.2.16
nsOspfTrapControl
OBJECT IDENTIFIER
.1.3.6.1.4.1.3224.18.2.16.1
nsOspfSetTrapA four-octet string serving as a bit map for the trap events defined by the OSPF traps. This object is used to enable and disable specific OSPF traps where a 1 in the bit field represents enabled. The right-most bit (least significant) represents trap 0.ro
OCTET STRING
.1.3.6.1.4.1.3224.18.2.16.1.1
nsOspfConfigErrorTypePotential types of configuration conflicts. Used by the nsOspfConfigError and nsOspfConfigVir- tError traps.ro
Enumeration
.1.3.6.1.4.1.3224.18.2.16.1.2
nsOspfPacketTypeOSPF packet types.ro
Enumeration
.1.3.6.1.4.1.3224.18.2.16.1.3
nsOspfPacketSrcThe IP address of an inbound packet that can- not be identified by a neighbor instance.ro
IpAddress
.1.3.6.1.4.1.3224.18.2.16.1.4
nsOspfTraps
OBJECT IDENTIFIER
.1.3.6.1.4.1.3224.18.2.16.2
nsOspfVirtIfStateChangeAn nsOspfIfStateChange 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).
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.1
nsOspfNbrStateChangeAn nsOspfNbrStateChange 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 nsOspfIfStateChange.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.2
nsOspfVirtNbrStateChangeAn nsOspfIfStateChange 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).
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.3
nsOspfIfConfigErrorAn nsOspfIfConfigError 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.4
nsOspfVirtIfConfigErrorAn nsOspfConfigError 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.5
nsOspfIfAuthFailureAn nsOspfIfAuthFailure 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.6
nsOspfVirtIfAuthFailureAn nsOspfVirtIfAuthFailure 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.7
nsOspfIfRxBadPacketAn nsOspfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.8
nsOspfVirtIfRxBadPacketAn nsOspfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.9
nsOspfTxRetransmitAn nsOspfTxRetransmit 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.10
nsOspfVirtIfTxRetransmitAn nsOspfTxRetransmit 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.11
nsOspfOriginateLsaAn nsOspfOriginateLsa 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.12
nsOspfMaxAgeLsaAn nsOspfMaxAgeLsa trap signifies that one of the LSA in the router's link-state database has aged to MaxAge.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.13
nsOspfLsdbOverflowAn nsOspfLsdbOverflow trap signifies that the number of LSAs in the router's link-state data- base has exceeded nsOspfExtLsdbLimit.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.14
nsOspfLsdbApproachingOverflowAn nsOspfLsdbApproachingOverflow trap signifies that the number of LSAs in the router's link- state database has exceeded ninety percent of nsOspfExtLsdbLimit.
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.15
nsOspfIfStateChangeAn nsOspfIfStateChange 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).
NOTIFICATION-TYPE
.1.3.6.1.4.1.3224.18.2.16.2.16
NETSCREEN-OSPF-TRAP-MIB - SNMP MIB Reference | MIBs Explorer