CISCO-BGP-POLICY-ACCOUNTING-MIB

All MIBs › CISCO-BGP-POLICY-ACCOUNTING-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2002-07-26

Category: Cisco Devices, Routing Protocols

Description: Tracks per-BGP-policy traffic accounting counters on Cisco routers.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is CISCO-BGP-POLICY-ACCOUNTING-MIB?

CISCO-BGP-POLICY-ACCOUNTING-MIB supports BGP policy-based accounting on Cisco routers, a feature that classifies IP traffic by BGP attributes (such as AS path or community) and tallies traffic volume per classification bucket. It exposes a table of per-interface, per-traffic-index packet and octet counters for both inbound and outbound directions. Its role is purely performance/traffic monitoring rather than hardware health: it is used to understand how much traffic is associated with particular BGP routing policies, which is valuable for peering capacity planning and billing verification. It depends conceptually on BGP4-MIB and IF-MIB, since traffic indices are tied to configured BGP policies and physical/logical interfaces. It is deployed on Internet-facing or peering-edge routers running Cisco IOS where BGP policy accounting has been enabled. Network engineers evaluating or troubleshooting this functionality can download the CISCO-BGP-POLICY-ACCOUNTING-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-BGP-POLICY-ACCOUNTING-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 router (BGP-speaking edge/peering router)

Monitoring Examples

An operator would poll cbpAcctTable, keyed by interface and cbpAcctTrafficIndex, reading cbpAcctInPacketCount, cbpAcctInOctetCount, cbpAcctOutPacketCount, and cbpAcctOutOctetCount to trend traffic volume for a specific BGP policy bucket over time. A sudden spike in cbpAcctOutOctetCount for one traffic index compared to a baseline could reveal an unexpected shift in outbound routing for that policy class, such as traffic rerouting after a peering change.

What Can Be Monitored

inbound packet count per BGP policy
inbound octet count per BGP policy
outbound packet count per BGP policy
outbound octet count per BGP policy
traffic index-to-policy mapping

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From IF-MIB

ifIndex

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter64
Integer32
MODULE-IDENTITY
OBJECT-TYPE

How to Use in IPNetwork Monitor

Example using cbpAcctInPacketCount OID:

Select a Cisco router (BGP-speaking edge/peering) 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 cbpAcctInPacketCount 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. The total number of packets received for a particular traffic-type on an interface. 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 Counter64-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

OID symbolic	OID numeric	Type	Access	Description
ciscoBgpPolAcctMIB	1.3.6.1.4.1.9.9.148			BGP policy based accounting information
ciscoBgpPolAcctMIBObjects	1.3.6.1.4.1.9.9.148.1
cbpAcctTable	1.3.6.1.4.1.9.9.148.1.1		not-accessible	The cbpAcctTable provides statistics about ingress and egress traffic on an interface. This data could be used for purposes like billing.
cbpAcctEntry	1.3.6.1.4.1.9.9.148.1.1.1		not-accessible	Each cbpAcctEntry provides statistics for traffic of interest on an ingress and/or egress interfaces. The traffic of interest may be used for purposes like billing, and is referred to from here on in the MIB by the term 'traffic-type', which corresponds to cbpAcctTrafficIndex. Traffic-types are configured by the user on a per interface basis. The statistics include ingress packet counts, ingress octet counts, egress packet counts and egress octet counts. Entries are created when traffic-type is configured on an interface. Entries are deleted automatically when the user removes the corresponding traffic-type configuration from an interface.
I32 cbpAcctTrafficIndex	1.3.6.1.4.1.9.9.148.1.1.1.1	Integer32	read-only	An integer value greater than 0, that uniquely identifies a traffic-type. The traffic-type has no intrinsic meaning. It just means the traffic coming into an interface can be differentiated into different types. It is up to the user to give meaning to and configure the various traffic-types on an interface.
C64 cbpAcctInPacketCountEx	1.3.6.1.4.1.9.9.148.1.1.1.2	Counter64	read-only	The total number of packets received for a particular traffic-type on an interface.
C64 cbpAcctInOctetCount	1.3.6.1.4.1.9.9.148.1.1.1.3	Counter64	read-only	The total number of octets received for a particular traffic-type on an interface.
C64 cbpAcctOutPacketCount	1.3.6.1.4.1.9.9.148.1.1.1.4	Counter64	read-only	The total number of packets transmitted for a particular traffic-type on an interface.
C64 cbpAcctOutOctetCount	1.3.6.1.4.1.9.9.148.1.1.1.5	Counter64	read-only	The total number of octets transmitted for a particular traffic-type on an interface.
ciscoBgpPolAcctMIBConformance	1.3.6.1.4.1.9.9.148.3
ciscoBgpPolAcctMIBCompliances	1.3.6.1.4.1.9.9.148.3.1
ciscoBgpPolAcctMIBCompliance	1.3.6.1.4.1.9.9.148.3.1.1			The compliance statement for entities which implement this Cisco BGP-Policy Traffic Accounting MIB.
ciscoBgpPolAcctMIBComplianceRev1	1.3.6.1.4.1.9.9.148.3.1.2			The compliance statement for entities which implement this Cisco BGP-Policy Traffic Accounting MIB.
ciscoBgpPolAcctMIBGroups	1.3.6.1.4.1.9.9.148.3.2
cbpAcctTableGroup	1.3.6.1.4.1.9.9.148.3.2.1			A collection of objects providing customer traffic related parameters.
cbpAcctTableGroupRev1	1.3.6.1.4.1.9.9.148.3.2.2			A collection of objects providing customer traffic related parameters.

RFC description

BGP policy-based accounting for traffic billing with ingress and egress packet and octet counters.

Start monitoring Cisco routers (BGP-speaking edge/peering) 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-BGP-POLICY-ACCOUNTING-MIB