CISCO-BGP4-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-BGP4-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2010-09-30

Category: Cisco Devices, IP and Core Protocols, Routing Protocols

Description: Provides Cisco-specific extensions for monitoring BGP routing protocol implementation, supporting both IPv4 and IPv6 address families.

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

What Is CISCO-BGP4-MIB?

CISCO-BGP4-MIB is a Cisco-specific extension to the IETF's standard BGP4 MIB (RFC 1657), in the routing protocol technology area, adding support for both IPv4 and IPv6 address families to BGP monitoring. It exposes configuration and operational data about BGP peers, local AS number, routing table entries learned via UPDATE messages, and AS path attributes. This makes it central to monitoring the software/protocol status of BGP routing on a device: administrators use it to check peer session state, verify which routes are present in the Adj-RIBs-In, inspect route origin and AS path attributes, and detect route flapping or unexpected route withdrawals that indicate routing instability. It explicitly extends and depends on the IETF BGP4-MIB (RFC 1657) for base object definitions. It is deployed on Cisco routers running BGP in enterprise or service-provider IP networks, particularly where dual-stack IPv4/IPv6 BGP peering is used, making cisco-bgp4-mib a key reference for administrators monitoring BGP session health across address families.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-BGP4-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 BGP

Monitoring Examples

An admin would poll cbgpRouteTable (via cbgpRouteEntry) to inspect a specific route's cbgpRouteAddrPrefix and cbgpRouteAddrPrefixLen alongside cbgpRouteOrigin and cbgpRouteASPathSegment to verify the AS path a prefix took to reach the router. Checking cbgpRoutePeer and cbgpRoutePeerType for a route reveals which peer advertised it, and comparing this against cbgpLocalAs helps validate correct AS numbering in a dual-stack (cbgpRouteAfi/cbgpRouteSafi) deployment. A sudden disappearance of expected routes in cbgpRouteTable for a given peer would flag a BGP session or route-advertisement problem, and cbgpNotifsEnable controls whether related traps are sent via ciscoBgp4MIBObjects.

What Can Be Monitored

  • BGP peer sessions and peer type
  • routes learned per peer (Adj-RIBs-In)
  • route origin and AS path
  • IPv4/IPv6 address family routes
  • local AS number
  • BGP notification/trap enablement
Imported Objects

From BGP4-MIB

bgpPeerEntryOBJECT-TYPE
bgpPeerLastErrorOBJECT-TYPE
bgpPeerRemoteAddrOBJECT-TYPE
bgpPeerStateOBJECT-TYPE

From CISCO-SMI

ciscoMgmtOBJECT-IDENTITY

From INET-ADDRESS-MIB

InetAddress
InetAddressType
InetAutonomousSystemNumber
InetPortNumber

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using cbgpPeerAcceptedPrefixes OID:

Select a Cisco routers running BGP 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 cbgpPeerAcceptedPrefixes 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. It reports the number of accepted route prefixes on this connection, which belong to an address family. 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 BGP4 MIB for border gateway protocol routing management and statistics.

Start monitoring Cisco routers running BGP 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-BGP4-MIB