CISCO-OSPF-TRAP-MIB
The CISCO-OSPF-TRAP-MIB module defines SNMP notification objects for monitoring Cisco IOS OSPF protocol state transitions, specifically including Sham Link events, to enable real-time alerting on topology changes and neighbor adjacency failures.
Imported Objects
Objects
25 total| Object Name |
|---|
ciscoOspfTrapMIBThis 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 MODULE-IDENTITY .1.3.6.1.4.1.9.10.101 |
ciscoOspfTrapMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.101.0 |
cospfIfConfigErrorA cospfIfConfigError trap signifies that a
packet with mismatched parameter MTU has been
received on a non-virtual interface from a
router. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.1 |
cospfVirtIfConfigErrorA cospfVirtIfConfigError trap signifies that a
packet with mismatched parameter MTU has been received
on a virtual interface from a router. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.2 |
cospfTxRetransmitA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.3 |
cospfVirtIfTxRetransmitA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.4 |
cospfOriginateLsaA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.5 |
cospfMaxAgeLsaA cospfMaxAgeLsa trap signifies that one of
the Opaque LSAs in the router's link-state database
has aged to MaxAge. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.6 |
cospfNssaTranslatorStatusChangeA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.7 |
cospfShamLinkStateChangeA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.8 |
cospfShamLinkNbrStateChangeA 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). NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.9 |
cospfShamLinkConfigErrorA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.10 |
cospfShamLinkAuthFailureA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.11 |
cospfShamLinkRxBadPacketA cospfShamLinkRxBadPacket trap signifies that an OSPF
packet has been received on a sham link that cannot be
parsed. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.12 |
cospfShamLinkTxRetransmitA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.13 |
cospfShamLinksStateChangeA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.10.101.0.14 |
ciscoOspfTrapMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.101.1 |
cospfTrapControl OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.101.1.1 |
cospfSetTrapAn octet string serving as a bit map for
the trap events defined by the OSPF traps in
this MIB. This object is used to enable and
disable specific OSPF traps where a 1
in the corresponding bit field represents
enabled.rw Bits .1.3.6.1.4.1.9.10.101.1.1.1 |
cospfConfigErrorTypePotential types of configuration conflicts.
Used by the cospfConfigError and cospfConfigVirtError
traps. When the last value of a trap
using this object is needed, but no traps of
that type have been sent, this value pertaining
to this object should be returned as noError.ro Enumeration .1.3.6.1.4.1.9.10.101.1.1.2 |
cospfPacketTypeOSPF packet types. When the last value of a trap
using this object is needed, but no traps of
that type have been sent, this value pertaining
to this object should be returned as nullPacket.ro Enumeration .1.3.6.1.4.1.9.10.101.1.1.3 |
cospfPacketSrcThe IP address of an inbound packet that can-
not be identified by a neighbor instance. When
the last value of a trap using this object is
needed, but no traps of that type have been sent,
this value pertaining to this object should
be returned as 0.0.0.0.ro IpAddress .1.3.6.1.4.1.9.10.101.1.1.4 |
ciscoOspfTrapMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.101.2 |
ciscoOspfTrapMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.101.2.1 |
ciscoOspfTrapMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.101.2.2 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.