CISCO-OSPF-TRAP-MIB

        This MIB module describes new/modified notification
objects/events, which are defined in the latest
version for OSPF MIB IETF draft
draftietf-ospf-mib-update-05.txt. Support for OSPF 
Sham link is also added
    
Source file
CISCO-OSPF-TRAP-MIB
Last revised
Identity
ciscoOspfTrapMIB
Base OID
1.3.6.1.4.1.9.10.101
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-OSPF-TRAP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-OSPF-TRAP-MIB::ciscoOspfTrapMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-OSPF-TRAP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-OSPF-TRAP-MIB::ciscoOspfTrapMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (11)
.1.3.6.1.4.1.9.10.101
.1.3.6.1.4.1.9.10.101.0
.1.3.6.1.4.1.9.10.101.1
.1.3.6.1.4.1.9.10.101.1.1
Bits
.1.3.6.1.4.1.9.10.101.1.1.1
Enumeration
.1.3.6.1.4.1.9.10.101.1.1.2
Enumeration
.1.3.6.1.4.1.9.10.101.1.1.3
.1.3.6.1.4.1.9.10.101.1.1.4
.1.3.6.1.4.1.9.10.101.2
.1.3.6.1.4.1.9.10.101.2.1
.1.3.6.1.4.1.9.10.101.2.2
Dependencies (10) 5 direct · 5 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Conformance Groups (3)
Compliance Statements (2)

OID .1.3.6.1.4.1.9.10.101.2.2.1
The compliance statements for the Cisco OSPF TRAP
MIB. These statements are deprecated by
ciscoOspfTrapMIBComplianceRev1.
Required groups
Object refinements
ObjectAccessSyntaxDescription
cospfConfigErrorType notifyonly
This object is inaccessible except through OSPF
notification messages.
cospfPacketType notifyonly
This object is inaccessible except through OSPF
notification messages.
cospfPacketSrc notifyonly
This object is inaccessible except through OSPF
notification messages.

OID .1.3.6.1.4.1.9.10.101.2.2.2
The compliance statements for the Cisco OSPF TRAP
MIB.
Required groups
Object refinements
ObjectAccessSyntaxDescription
cospfConfigErrorType notifyonly
This object is inaccessible except through OSPF
notification messages.
cospfPacketType notifyonly
This object is inaccessible except through OSPF
notification messages.
cospfPacketSrc notifyonly
This object is inaccessible except through OSPF
notification messages.
Notifications / Traps (14)
NameOIDDescription
.1.3.6.1.4.1.9.10.101.0.1
A cospfIfConfigError trap signifies that a
packet with mismatched parameter MTU has been
received on a non-virtual interface from a
router.
.1.3.6.1.4.1.9.10.101.0.10
A cospfShamLinkConfigError signifies that a packet
has been received on a sham link from a router whose
configuration parameters conflict with this router's
configuration parameters.
.1.3.6.1.4.1.9.10.101.0.11
A cospfShamLinkAuthFailure trap signifies that a
packet has been received on a sham link from a router
whose authentication key or authentication type conflicts
with this router's authentication key and authentication
type.
.1.3.6.1.4.1.9.10.101.0.12
A cospfShamLinkRxBadPacket trap signifies that an OSPF
packet has been received on a sham link that cannot be
parsed.
.1.3.6.1.4.1.9.10.101.0.13
A cospfShamLinkTxRetransmit trap signifies that an
OSPF packet has been retransmitted on a sham link. All
packets that may be retransmitted are associated with an
LSDB entry. The LS type, LS ID, and Router ID are used
identify the LSDB entry.
.1.3.6.1.4.1.9.10.101.0.14
A ospfShamLinkStateChange trap signifies that
there has been a change in the state of a Sham
Link OSPF interface. This trap should be generated
when the interface state regresses from Point-to-Point
to Down or progresses to Down to Point-to-Point.
.1.3.6.1.4.1.9.10.101.0.2
A cospfVirtIfConfigError trap signifies that a
packet with mismatched parameter MTU has been received
on a virtual interface from a router.
.1.3.6.1.4.1.9.10.101.0.3
A cospfTxRetransmit trap signifies than an
OSPF packet, which has been associated with
an Opaque LSA LSDB Entry, has been retransmitted
on a non-virtual interface.
.1.3.6.1.4.1.9.10.101.0.4
A cospfVirtTxRetransmit trap signifies than an
OSPF packet, which has been associated with
an Opaque LSA LSDB Entry, has been retransmitted
on a non-virtual interface.
.1.3.6.1.4.1.9.10.101.0.5
A cospfOriginateLsa trap signifies that a new
Opaque 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. Additionally,
this trap does not include LSAs that
are being flushed because they have reached
MaxAge.
.1.3.6.1.4.1.9.10.101.0.6
A cospfMaxAgeLsa trap signifies that one of
the Opaque LSAs in the router's link-state database
has aged to MaxAge.
.1.3.6.1.4.1.9.10.101.0.7
A cospfNssaTranslatorStatusChange trap indicates that there
has been a change in the router's ability to translate OSPF
type-7 LSAs into OSPF type-5 LSAs. This trap should be
generated when the Translator Status transitions from or to
any defined status on a per area basis.
.1.3.6.1.4.1.9.10.101.0.8
A ospfShamLinkStateChange trap signifies that
there has been a change in the state of a Sham
Link OSPF interface. This trap should be generated
when the interface state regresses from Point-to-Point
to Down or progresses to Down to Point-to-Point. This
trap has been deprecated by cospfShamLinksStateChange.
.1.3.6.1.4.1.9.10.101.0.9
A cospfShamLinkNbrStateChange trap signifies that
there has been a change in the state of a sham link
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., Full).