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

VENDOR: NETSCREEN TECHNOLOGIES


 Home MIB: NETSCREEN-OSPF-TRAP-MIB
Download as:   
SNMPv2-CONF, SNMPv2-TC, SNMPv2-SMI, NETSCREEN-TRAP-MIB, NETSCREEN-OSPF-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
 nsOspfTrap 1.3.6.1.4.1.3224.18.2.16
The MIB module to describe traps for the OSPF Version 2 Protocol.
       nsOspfTrapControl 1.3.6.1.4.1.3224.18.2.16.1
           nsOspfSetTrap 1.3.6.1.4.1.3224.18.2.16.1.1 octet string read-only
A 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.
           nsOspfConfigErrorType 1.3.6.1.4.1.3224.18.2.16.1.2 integer read-only
Potential types of configuration conflicts. Used by the nsOspfConfigError and nsOspfConfigVir- tError traps. Enumeration: 'unknownNbmaNbr': 3, 'deadIntervalMismatch': 9, 'badVersion': 1, 'authFailure': 6, 'unknownVirtualNbr': 4, 'optionMismatch': 10, 'helloIntervalMismatch': 8, 'areaMismatch': 2, 'authTypeMismatch': 5, 'netMaskMismatch': 7.
           nsOspfPacketType 1.3.6.1.4.1.3224.18.2.16.1.3 integer read-only
OSPF packet types. Enumeration: 'lsAck': 5, 'lsReq': 3, 'lsUpdate': 4, 'dbDescript': 2, 'hello': 1.
           nsOspfPacketSrc 1.3.6.1.4.1.3224.18.2.16.1.4 ipaddress read-only
The IP address of an inbound packet that can- not be identified by a neighbor instance.
       nsOspfTraps 1.3.6.1.4.1.3224.18.2.16.2
           nsOspfVirtIfStateChange 1.3.6.1.4.1.3224.18.2.16.2.1
An 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).
           nsOspfNbrStateChange 1.3.6.1.4.1.3224.18.2.16.2.2
An 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.
           nsOspfVirtNbrStateChange 1.3.6.1.4.1.3224.18.2.16.2.3
An 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).
           nsOspfIfConfigError 1.3.6.1.4.1.3224.18.2.16.2.4
An 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.
           nsOspfVirtIfConfigError 1.3.6.1.4.1.3224.18.2.16.2.5
An 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.
           nsOspfIfAuthFailure 1.3.6.1.4.1.3224.18.2.16.2.6
An 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.
           nsOspfVirtIfAuthFailure 1.3.6.1.4.1.3224.18.2.16.2.7
An 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.
           nsOspfIfRxBadPacket 1.3.6.1.4.1.3224.18.2.16.2.8
An nsOspfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.
           nsOspfVirtIfRxBadPacket 1.3.6.1.4.1.3224.18.2.16.2.9
An nsOspfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.
           nsOspfTxRetransmit 1.3.6.1.4.1.3224.18.2.16.2.10
An 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.
           nsOspfVirtIfTxRetransmit 1.3.6.1.4.1.3224.18.2.16.2.11
An 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.
           nsOspfOriginateLsa 1.3.6.1.4.1.3224.18.2.16.2.12
An 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.
           nsOspfMaxAgeLsa 1.3.6.1.4.1.3224.18.2.16.2.13
An nsOspfMaxAgeLsa trap signifies that one of the LSA in the router's link-state database has aged to MaxAge.
           nsOspfLsdbOverflow 1.3.6.1.4.1.3224.18.2.16.2.14
An nsOspfLsdbOverflow trap signifies that the number of LSAs in the router's link-state data- base has exceeded nsOspfExtLsdbLimit.
           nsOspfLsdbApproachingOverflow 1.3.6.1.4.1.3224.18.2.16.2.15
An nsOspfLsdbApproachingOverflow trap signifies that the number of LSAs in the router's link- state database has exceeded ninety percent of nsOspfExtLsdbLimit.
           nsOspfIfStateChange 1.3.6.1.4.1.3224.18.2.16.2.16
An 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).