CISCO-BGP4-MIB :: cbgpPeerAcceptedPrefixes

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-BGP4-MIBcbgpPeerAcceptedPrefixes

cbgpPeerAcceptedPrefixes

Module: CISCO-BGP4-MIB

OID (symbolic): CISCO-BGP4-MIB::cbgpPeerAcceptedPrefixes

OID (numeric): 1.3.6.1.4.1.9.9.187.1.2.4.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of accepted route prefixes on this connection, which belong to an address family.

What is cbgpPeerAcceptedPrefixes?

Counts the number of route prefixes for a given address family that have been accepted from this BGP peer connection.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.187.1.2.4.1.1
snmpwalk -v2c -c public <target> CISCO-BGP4-MIB::cbgpPeerAcceptedPrefixes

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.187.1.2.4.1.1.1
snmpget -v2c -c public <target> CISCO-BGP4-MIB::cbgpPeerAcceptedPrefixes.1

Start monitoring Cisco routers running BGP with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-BGP4-MIB::cbgpPeerAcceptedPrefixes OID value, configure state conditions and alerts, and monitor any Cisco routers running BGP from a single console.

How to Use in IPNetwork Monitor

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.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.187ciscoBgp4MIBCISCO-BGP4-MIB
1.3.6.1.4.1.9.9.187.1ciscoBgp4MIBObjectsCISCO-BGP4-MIB
1.3.6.1.4.1.9.9.187.1.2cbgpPeerCISCO-BGP4-MIB
1.3.6.1.4.1.9.9.187.1.2.4cbgpPeerAddrFamilyPrefixTableCISCO-BGP4-MIB
1.3.6.1.4.1.9.9.187.1.2.4.1cbgpPeerAddrFamilyPrefixEntryCISCO-BGP4-MIB
1.3.6.1.4.1.9.9.187.1.2.4.1.1cbgpPeerAcceptedPrefixesCISCO-BGP4-MIB