STN-OSPF-TRAP-MIB: View SNMP OID List / Download MIB

VENDOR: SPRING TIDE NETWORKS


 Home MIB: STN-OSPF-TRAP-MIB
Download as:   
SNMPv2-CONF, OSPF-MIB, SNMPv2-SMI, STN-ROUTER-MIB, OSPF-TRAP-MIB, SPRING-TIDE-NETWORKS-SMI, SNMPv2-TC, STN-IPROUTING-MIB

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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
             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.
             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.
             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.
             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.
             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.
             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.
             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.
             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.
             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.
             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.
             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.
             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.
             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.
             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.
             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.
             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.