OSPFv3-TRAP-MIB: View SNMP OID List / Download MIB

VENDOR: INTERNET-STANDARD


 Home MIB: OSPFv3-TRAP-MIB
Download as:   

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
 ospfv3Trap 1.3.6.1.2.1.191.1.13
The MIB module to describe traps for the OSPF Version-3 Protocol.
       ospfv3TrapControl 1.3.6.1.2.1.191.1.13.1
           ospfv3SetTrap 1.3.6.1.2.1.191.1.13.1.1 octet string read-write
A four-octet string serving as a bit map for the trap events defined by the OSPFv3 traps. This object is used to enable and disable specific OSPFv3 traps where a 1 in the bit field represents enabled. The right-most bit (least significant) represents trap 0.
           ospfv3ConfigErrorType 1.3.6.1.2.1.191.1.13.1.2 integer read-only
Potential types of configuration conflicts. Used by the ospfv3ConfigError and ospfv3ConfigVir- tError traps. Enumeration: 'unknownNbmaNbr': 3, 'deadIntervalMismatch': 6, 'badVersion': 1, 'unknownVirtualNbr': 4, 'optionMismatch': 7, 'helloIntervalMismatch': 5, 'areaMismatch': 2, 'instanceMismatch': 8.
           ospfv3PacketType 1.3.6.1.2.1.191.1.13.1.3 integer read-only
OSPFv3 packet types. Enumeration: 'dbDescript': 2, 'lsUpdate': 4, 'lsAck': 5, 'lsReq': 3, 'hello': 1.
           ospfv3PacketSrc 1.3.6.1.2.1.191.1.13.1.4 inetaddress read-only
The IPv6 address of an inbound packet that can- not be identified by a neighbor instance.
           ospfv3LsdbAreaId 1.3.6.1.2.1.191.1.13.1.5 ospfv3areaidtc no-access
The 32-bit identifier of the Area from which the LSA was received.
           ospfv3LsdbType 1.3.6.1.2.1.191.1.13.1.6 unsigned32 no-access
The type of the link state advertisement. Each link state type has a separate advertisement format. Area-Scope LSAs unrecognized by the router are also stored in this database.
           ospfv3LsdbRouterId 1.3.6.1.2.1.191.1.13.1.7 ospfv3routeridtc no-access
The 32-bit number that uniquely identifies the originating router in the Autonomous System.
           ospfv3LsdbLsid 1.3.6.1.2.1.191.1.13.1.8 unsigned32 no-access
The Link State ID is an LS Type Specific field containing a unique identifier; it identifies the piece of the routing domain that is being described by the advertisement. In contrast to OSPFv2, the LSID has no addressing semantics.
       ospfv3Traps 1.3.6.1.2.1.191.1.13.2
           ospfv3IfStateChange 1.3.6.1.2.1.191.1.13.2.1
An ospfv3IfStateChange 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).
           ospfv3VirtIfStateChange 1.3.6.1.2.1.191.1.13.2.2
An ospfv3IfStateChange trap signifies that there has been a change in the state of an OSPF virtual 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).
           ospfv3NbrStateChange 1.3.6.1.2.1.191.1.13.2.3
An ospfv3NbrStateChange 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 ospfv3IfStateChange.
           ospfv3VirtNbrStateChange 1.3.6.1.2.1.191.1.13.2.4
An ospfv3IfStateChange 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).
           ospfv3IfConfigError 1.3.6.1.2.1.191.1.13.2.5
An ospfv3IfConfigError 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.
           ospfv3VirtIfConfigError 1.3.6.1.2.1.191.1.13.2.6
An ospfv3VirtIfConfigError 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 ad- jacency from forming.
           ospfv3IfRxBadPacket 1.3.6.1.2.1.191.1.13.2.7
An ospfv3IfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.
           ospfv3VirtIfRxBadPacket 1.3.6.1.2.1.191.1.13.2.8
An ospfv3VirtIfRxBadPacket trap signifies that an OSPFv3 packet has been received on a virtual interface that cannot be parsed.
           ospfv3TxRetransmit 1.3.6.1.2.1.191.1.13.2.9
An ospfv3TxRetransmit 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.
           ospfv3VirtIfTxRetransmit 1.3.6.1.2.1.191.1.13.2.10
An ospfv3VirtIfTxRetransmit 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.
           ospfv3OriginateLsa 1.3.6.1.2.1.191.1.13.2.11
An ospfv3OriginateLsa 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.
           ospfv3MaxAgeLsa 1.3.6.1.2.1.191.1.13.2.12
An ospfv3MaxAgeLsa trap signifies that one of the LSA in the router's link-state database has aged to MaxAge.
           ospfv3UnknownLsa 1.3.6.1.2.1.191.1.13.2.13
An ospfv3UnknownLsa trap signifies that one of the Nbr has sent an UNknown LSA. Only DR generate this trap and If NBR state is less than Exchange need not originate this trap
           ospfv3LsdbOverflow 1.3.6.1.2.1.191.1.13.2.14
An ospfv3LsdbOverflow trap signifies that the number of LSAs in the router's link-state data- base has exceeded ospfv3ExtAreaLsdbLimit.
           ospfv3LsdbApproachingOverflow 1.3.6.1.2.1.191.1.13.2.15
An ospfv3LsdbApproachingOverflow trap signifies that the number of LSAs in the router's link- state database has exceeded ninety percent of ospfv3ExtAreaLsdbLimit.
           ospfv3AsbrStatusChange 1.3.6.1.2.1.191.1.13.2.16
An ospfv3AsbrStatusChange trap signifies that device's Asbr Status has changed.
           ospfv3AbrStatusChange 1.3.6.1.2.1.191.1.13.2.17
An ospfv3AbrStatusChange trap signifies that device's Abr Status has changed. There are two distinct definitions of ABR given by IBM & Cisco, Implementations are free to follow their own interpretation of ABR while originating this trap
       ospfv3TrapConformance 1.3.6.1.2.1.191.1.13.3
           ospfv3TrapGroups 1.3.6.1.2.1.191.1.13.3.1
               ospfv3TrapControlGroup 1.3.6.1.2.1.191.1.13.3.1.1
These objects are required to control traps from OSPF systems.
           ospfv3TrapCompliances 1.3.6.1.2.1.191.1.13.3.2
               ospfv3TrapCompliance 1.3.6.1.2.1.191.1.13.3.2.1
The compliance statement