CISCO-OSPF-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-OSPF-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2003-07-18

Category: Cisco Devices, Routing Protocols

Description: Manages Cisco-specific OSPF routing protocol implementation details including sham link support, extending the standard OSPF-MIB.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring CISCO-OSPF-MIB with a free 30-day trial of IPNetwork Monitor.

What Is CISCO-OSPF-MIB?

This is a Cisco enterprise MIB module that extends the standard OSPF-MIB (RFC 1850) to manage Cisco-specific implementation details of the OSPF routing protocol, including support for OSPF sham links used in MPLS VPN environments. Its object tree, as reflected in cospfGeneralGroup, is organized around Cisco's additions to standard OSPF configuration and state objects, complementing rather than replacing the base RFC OSPF-MIB tables for areas, interfaces, and neighbors. Rather than hardware sensors, this MIB is used to monitor the software/protocol-level health of OSPF routing—sham link status and general OSPF process parameters—helping detect routing adjacency or configuration problems on Cisco routers. It explicitly depends on and extends RFC 1850's OSPF-MIB and the OSPF MIB update draft, so it must be read alongside the standard OSPF-MIB rather than in isolation. It is deployed on Cisco routers running OSPF, particularly in MPLS VPN backbones where sham links are used to force intra-area paths across a VPN backbone. Network engineers searching for the cisco ospf mib specifically use it to audit OSPF area and interface configuration on Cisco routers via SNMP rather than the CLI.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-OSPF-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Cisco routers running OSPF

Monitoring Examples

This module is largely a conformance and extension module—its objects (cospfGeneralGroup, cospfConformance, cospfGroups, cospfCompliances) describe compliance groupings rather than exposing a rich set of independent runtime data tables, so there is limited standalone monitoring data beyond what the base OSPF-MIB already provides; an admin would use it mainly to confirm which Cisco OSPF extensions (like sham-link support) an agent implements.

What Can Be Monitored

  • Cisco OSPF conformance/compliance group support
  • OSPF sham-link extension support
Imported Objects

From CISCO-SMI

ciscoExperimentOBJECT-IDENTITY

From IF-MIB

InterfaceIndexOrZero

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From OSPF-MIB

AreaID
HelloRange
Metric
PositiveInteger
RouterID
UpToMaxAge
ospfAreaEntryOBJECT-TYPE
ospfIfEntry
ospfLsdbAreaId
ospfLsdbLsid
ospfLsdbRouterId
ospfVirtIfEntry

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

TruthValue

How to Use in IPNetwork Monitor

Example using cospfAreaNssaTranslatorEvents OID:

Select a Cisco routers running OSPF as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cospfAreaNssaTranslatorEvents into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. Indicates the number of Translator State changes that have occurred since the last boot-up. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Extension to RFC 1850 for managing OSPF implementation with support for OSPF areas, interfaces, neighbors, and sham links.

Start monitoring Cisco routers running OSPF with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-OSPF-MIB