STN-OSPF-TRAP-MIB
AI MIB Summary
The STN-OSPF-TRAP-MIB module defines SNMP trap definitions for monitoring OSPF Version 2 protocol state transitions and error conditions, specifically enabling network management systems to receive asynchronous notifications regarding neighbor state changes, adjacency failures, and interface status events on STN-managed routing devices.
This MIB module describes traps for the OSPF Version 2 Protocol.
Main OID:
stnOspfTrap.1.3.6.1.4.1.3551.2.12.4.8.1
20
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
20 total| Object Name |
|---|
stnOspfTrapThis MIB module describes traps for the OSPF
Version 2 Protocol. MODULE-IDENTITY .1.3.6.1.4.1.3551.2.12.4.8.1 |
stnOspfTrapVars OBJECT IDENTIFIER .1.3.6.1.4.1.3551.2.12.4.8.1.1 |
stnOspfNotificationPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.3551.2.12.4.8.1.2 |
stnOspfNotification OBJECT IDENTIFIER .1.3.6.1.4.1.3551.2.12.4.8.1.2.0 |
stnOspfVirtIfStateChangeA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.1 |
stnOspfNbrStateChangeA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.2 |
stnOspfVirtNbrStateChangeA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.3 |
stnOspfIfConfigErrorAn 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.4 |
stnOspfVirtIfConfigErrorA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.5 |
stnOspfIfAuthFailureA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.6 |
stnOspfVirtIfAuthFailureA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.7 |
stnOspfIfRxBadPacketA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.8 |
stnOspfVirtIfRxBadPacketAn 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.9 |
stnOspfTxRetransmitA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.10 |
stnOspfVirtIfTxRetransmitA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.11 |
stnOspfOriginateLsaA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.12 |
stnOspfMaxAgeLsaA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.13 |
stnOspfLsdbOverflowA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.14 |
stnOspfLsdbApproachingOverflowA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.15 |
stnOspfIfStateChangeA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3551.2.12.4.8.1.2.0.16 |
More MIBs from Spring Tide
Browse all Spring TideMIBs →STN-POLICY-MIB
The STN-POLICY-MIB module manages STN (Secure Transport Network) policy enforcement by exposing the stnPmClassTable to monitor and configure traffic classification and policy matching rules. This interface enables administrators to retrieve specific policy class attributes, including match criteria and associated actions, for granular control over network security and QoS enforcement.
251 objects→
STN-ATM-MIB
STN-ATM-MIB provides management and monitoring capabilities for ATM (Asynchronous Transfer Mode) network interfaces and virtual circuits on STN (Sangoma) hardware, tracking critical performance metrics such as cell loss, cell delay, and interface status.
238 objects→
IKE-MON-MIB
SNMP MIB module
182 objects→
STN-AAA-MIB
The STN-AAA-MIB module enables monitoring and management of Spring Tide Networks authentication, authorization, and accounting (AAA) events, specifically tracking user session states, access control decisions, and accounting records for network access servers.
171 objects→
STN-PPTP-MIB
SNMP MIB module
135 objects→
STN-CHASSIS-MIB
The STN-CHASSIS-MIB provides SNMP-managed objects for monitoring Spring Tide Networks chassis hardware status, including physical port states, power supply conditions, fan module health, and environmental sensor readings. This module enables centralized visibility into the physical layer integrity and operational state of the chassis infrastructure.
106 objects→