STN-OSPF-TRAP-MIB

All MIBs › STN-OSPF-TRAP-MIB

Organization: Spring Tide Networks, Inc.

Last Updated: 2000-02-16

Category: Routing, Spring Tide Networks, Traps / Notifications

Description: Defines OSPF event trap notifications for Spring Tide Networks broadband aggregation devices.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is STN-OSPF-TRAP-MIB?

STN-OSPF-TRAP-MIB is a vendor-specific MIB from Spring Tide Networks that defines SNMP trap notifications for OSPF Version 2 protocol events on its broadband aggregation platforms. As a notifications-focused module, it does not expose polled counters directly but instead defines the structure of the traps an agent sends when significant OSPF routing events occur, such as neighbor state changes or interface state changes. In a monitoring context these traps are used to alert operators in near-real-time to routing-software faults, such as an OSPF adjacency going down, which affects the device's ability to route traffic correctly. It explicitly depends on the standard OSPF-MIB/OSPF-TRAP conventions defined for OSPFv2, adapting them for Spring Tide's platform. It would be deployed on Spring Tide broadband aggregation routers running OSPF as their IGP, feeding alerts to a network management station. Engineers can download the STN-OSPF-TRAP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in STN-OSPF-TRAP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Spring Tide Networks broadband aggregation router

Monitoring Examples

Because this MIB defines only trap/notification structures rather than polled data objects, there is no concrete polling scenario to describe; an NMS would instead configure itself as a trap receiver and alert whenever the device emits an OSPF neighbor-down, interface state-change, or similar routing-fault notification.

Imported Objects

From OSPF-MIB

ospf	MODULE-IDENTITY
ospfAddressLessIf
ospfExtLsdbLimit	OBJECT-TYPE
ospfIfIpAddress
ospfIfState
ospfLsdbAreaId
ospfLsdbLsid
ospfLsdbRouterId
ospfLsdbType
ospfNbrAddressLessIndex
ospfNbrIpAddr
ospfNbrRtrId
ospfNbrState
ospfRouterId	OBJECT-TYPE
ospfVirtIfAreaId
ospfVirtIfNeighbor
ospfVirtIfState
ospfVirtNbrArea
ospfVirtNbrRtrId
ospfVirtNbrState

From OSPF-TRAP-MIB

ospfConfigErrorType	OBJECT-TYPE
ospfPacketSrc	OBJECT-TYPE
ospfPacketType	OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SPRING-TIDE-NETWORKS-SMI

stnNotification

OBJECT-IDENTITY

From STN-IPROUTING-MIB

stnOspfTraps

OBJECT-IDENTITY

From STN-ROUTER-MIB

stnRouterIndex

OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Description
stnOspfTrap	1.3.6.1.4.1.3551.2.12.4.8.1	This MIB module describes traps for the OSPF Version 2 Protocol.
stnOspfTrapVars	1.3.6.1.4.1.3551.2.12.4.8.1.1
stnOspfNotificationPrefix	1.3.6.1.4.1.3551.2.12.4.8.1.2
stnOspfNotification	1.3.6.1.4.1.3551.2.12.4.8.1.2.0
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.

RFC description

Defines traps and notifications for OSPF Version 2 protocol on Spring Tide routers.

Start monitoring Spring Tide Networks (Lucent) broadband aggregation router (OSPFv2 event traps) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download STN-OSPF-TRAP-MIB

What Is STN-OSPF-TRAP-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description