CISCO-WAN-BBIF-ATM-CONN-STAT-MIB

All MIBs › CISCO-WAN-BBIF-ATM-CONN-STAT-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2002-10-18

Category: ATM, Vendor: Cisco Devices

Description: Tracks throughput and error counters for ATM connections on Cisco WAN broadband interfaces.

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-WAN-BBIF-ATM-CONN-STAT-MIB?

CISCO-WAN-BBIF-ATM-CONN-STAT-MIB provides real-time ATM connection statistics for broadband interfaces (logical ports) on the PXM1 service module used in Cisco MGX82xx WAN switching products. It exposes per-channel cell counters covering received CLP0/CLP1 cells, cells discarded for non-conformance under GCRA policing (traffic-shaping algorithm checks against SCR/PCR/CDVT parameters), and transmitted cell counts. Its primary monitoring purpose is detecting traffic-contract violations and congestion at the cell level: a rising bbChanNonConformCellsAtGcra1Policer or bbChanDscdClp0Cells count reveals a logical channel exceeding its negotiated cell rate and having cells discarded, directly affecting the health of that broadband ATM connection. It is a hardware-specific companion MIB to CISCO-WAN-BBIF-ILMI-MIB, since both describe the same PXM1 broadband interface ports. It is used exclusively in legacy Cisco MGX82xx ATM WAN switch deployments. Engineers can download the CISCO-WAN-BBIF-ATM-CONN-STAT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-WAN-BBIF-ATM-CONN-STAT-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 MGX82xx PXM1 service module broadband ATM interfaces

Monitoring Examples

An operator polling bbChanCntGrpTable by bbChanCntNum would compare bbChanRcvClp0Cells to bbChanDscdClp0Cells to compute the discard ratio for a given logical channel, and check bbChanNonConformCellsAtGcra1Policer/Gcra2Policer to see which of the two GCRA policing stages is triggering discards. A high bbChanRcvEOFCells count alongside rising discards could indicate malformed or truncated ATM cell streams arriving on that broadband interface.

What Can Be Monitored

received/transmitted cell counts by CLP class
GCRA policer non-conformance
discarded cell counts
end-of-frame cell counts

Imported Objects

From BASIS-MIB

bbChanCntGrp

OBJECT-IDENTITY

From CISCOWAN-SMI

ciscoWan

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE

How to Use in IPNetwork Monitor

Example using bbChanRcvClp0Cells OID:

Select a Cisco MGX ATM service module 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 bbChanRcvClp0Cells 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 cLP_0 Cells Received from broadband 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 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

OID symbolic	OID numeric	Type	Access	Description
INT bbChanCntClrButton	1.3.6.1.4.1.351.110.5.2.7.3.1.1.14	INTEGER	read-write	Writing a value of 2 resets all the counters.
bbChanCntGrpEntry	1.3.6.1.4.1.351.110.5.2.7.3.1.1		not-accessible	An entry for statistics on logical channel. Each entry contains statistics for an ATM connection on broadband interface.
bbChanCntGrpTable	1.3.6.1.4.1.351.110.5.2.7.3.1		not-accessible	This is the broadband channel statistics table.
I32 bbChanCntNum	1.3.6.1.4.1.351.110.5.2.7.3.1.1.1	Integer32	read-only	This object identifies the logical channel number. The value for this object must be same as the value of 'bbChanCnfNum' from bbChanCnfGrpTable.
C32 bbChanDscdClp0Cells	1.3.6.1.4.1.351.110.5.2.7.3.1.1.7	Counter32	read-only	This object provides a count of the CLP equal to 0 that are received and then discarded.
C32 bbChanDscdClp1Cells	1.3.6.1.4.1.351.110.5.2.7.3.1.1.8	Counter32	read-only	This object provides a count of the CLP equal to 1 that are received and then discarded.
C32 bbChanDscdClpOneCellsToPort	1.3.6.1.4.1.351.110.5.2.7.3.1.1.13	Counter32	read-only	Number of CLP = 1 cells discarded before transmitted to broadband interface.
C32 bbChanDscdClpZeroCellsToPort	1.3.6.1.4.1.351.110.5.2.7.3.1.1.12	Counter32	read-only	Number of CLP = 0 cells discarded before transmitted to broadband interface.
C32 bbChanNonConformCellsAtGcra1Policer	1.3.6.1.4.1.351.110.5.2.7.3.1.1.4	Counter32	read-only	This object provides a count of the nonconforming cells that are received at the first policing point(GCRA1 policer).
C32 bbChanNonConformCellsAtGcra2Policer	1.3.6.1.4.1.351.110.5.2.7.3.1.1.5	Counter32	read-only	This object provides a count of the nonconforming cells that are received at the second policing point(GCRA2 policer).
C32 bbChanRcvCellsSent	1.3.6.1.4.1.351.110.5.2.7.3.1.1.9	Counter32	read-only	Number of cells received from broadband interface and sent out of the Queue Engine(QE device).
C32 bbChanRcvClp0CellsEx	1.3.6.1.4.1.351.110.5.2.7.3.1.1.2	Counter32	read-only	CLP_0 Cells Received from broadband interface.
C32 bbChanRcvClp1Cells	1.3.6.1.4.1.351.110.5.2.7.3.1.1.3	Counter32	read-only	CLP_1 Cells Received from broadband interface.
C32 bbChanRcvEOFCells	1.3.6.1.4.1.351.110.5.2.7.3.1.1.6	Counter32	read-only	This object provides count of End Of Frame(EOF) cells that are received.
C32 bbChanXmtClp0Cells	1.3.6.1.4.1.351.110.5.2.7.3.1.1.10	Counter32	read-only	This object provides count of Number of cells with EFCI=0 that are transmitted.
C32 bbChanXmtClp1Cells	1.3.6.1.4.1.351.110.5.2.7.3.1.1.11	Counter32	read-only	This object provides count of Number of cells with EFCI set that are transmitted.
ciscoWanBbifAtmConnStatMIB	1.3.6.1.4.1.351.150.36			This MIB module contains ATM Connection related real time statistical counter objects. The ATM connections are applicable to PXM1 service module. in MGX82xx products. Logical Channel refers to ATM Connection(or connection end point). Terminologies used: broadband interface - Logical port on PXM1. SCR - Sustained Cell Rate BT - Burst Tolerance PCR - Peak Cell Rate CDVT - Cell Delay Transfer Variance Tolerance GCRA - The Generic Cell Rate Algorithm(GCRA) is used to define comformance with repect to the traffic contract. For each cell arrival, the GCRA determines whether the cell conforms to the traffic contract of the connection. GCRA1 - GCRA Bucket 1. For CBR and UBR connections, only GCRA-1 is needed to check for PCR, CDVT Conformance. GCRA2 - GCRA Bucket 2. For VBR and ABR Connections, GCRA-1 is needed to check for PCR, CDVT conformance and GCRA-2 for SCR, BT Conformance. EFCI - Explicit Forward Congestion Indication. QE - Queue Engine(QE). This ASIC Provides the traffic management functions related to VC queues, QoS queues and interface queues. This management function is performed for both directions of traffic(ingress, egress). ingress - ingress traffic is defined as data flowing toward the switch fabric. Ingress data can come from either the Service Modules through the backplane or the PXM1 Uplink back card. egress - Egress traffic is defined as data flowing away from the switch fabric.
cwbAtmConnStatCompliance	1.3.6.1.4.1.351.150.36.2.2.1			The compliance statement for broadband interface Connection Statstics MIB.
cwbAtmConnStatMIBCompliances	1.3.6.1.4.1.351.150.36.2.2
cwbAtmConnStatMIBConformance	1.3.6.1.4.1.351.150.36.2
cwbAtmConnStatMIBGroups	1.3.6.1.4.1.351.150.36.2.1
cwbAtmConnStatsGroup	1.3.6.1.4.1.351.150.36.2.1.1			The objects related to broadband interface connection statistics.

RFC description

Monitors Cisco WAN broadband interface ATM connection statistics including throughput and error counters.

Start monitoring Cisco MGX ATM service modules 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-WAN-BBIF-ATM-CONN-STAT-MIB