CISCO-WAN-ATM-CONN-STAT-MIB :: cwacsIngRcvCLP0

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-WAN-ATM-CONN-STAT-MIBcwacsIngRcvCLP0

cwacsIngRcvCLP0

Module: CISCO-WAN-ATM-CONN-STAT-MIB

OID (symbolic): CISCO-WAN-ATM-CONN-STAT-MIB::cwacsIngRcvCLP0

OID (numeric): 1.3.6.1.4.1.351.150.2.1.1.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of valid CLP=0 ATM cells in the ingress direction of this Channel prior to the traffic management entity.

What is cwacsIngRcvCLP0?

This read-only counter, in cells, tracks the number of valid ATM cells with Cell Loss Priority (CLP) set to 0, the higher-priority marking, received in the ingress direction of this channel before they reach the traffic management entity. An admin monitors this as a baseline count of incoming high-priority traffic entering the switch on this connection, useful for comparing against post-policing counters to see how much of that traffic survives enforcement. For example, comparing this pre-policing CLP=0 ingress count against cwacsIngXmtCLP0 lets the admin see whether high-priority cells are being dropped by traffic management, which shouldn't normally happen for compliant CLP=0 traffic.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.150.2.1.1.1.1.1
snmpwalk -v2c -c public <target> CISCO-WAN-ATM-CONN-STAT-MIB::cwacsIngRcvCLP0

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.150.2.1.1.1.1.1.1
snmpget -v2c -c public <target> CISCO-WAN-ATM-CONN-STAT-MIB::cwacsIngRcvCLP0.1

Start monitoring Cisco MGX/BPX ATM switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WAN-ATM-CONN-STAT-MIB::cwacsIngRcvCLP0 OID value, configure state conditions and alerts, and monitor any Cisco MGX/BPX ATM switches from a single console.

How to Use in IPNetwork Monitor

Select a Cisco MGX/BPX ATM switch 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 cwacsIngRcvCLP0 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 number of valid CLP=0 ATM cells in the ingress direction of this Channel prior to the traffic management entity. 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 (in cells), 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.351stratacomCISCOWAN-SMI
1.3.6.1.4.1.351.150ciscoWanCISCOWAN-SMI
Numeric OIDNameModule
1.3.6.1.4.1.351.150.2ciscoWanAtmConnStatMIBCISCO-WAN-ATM-CONN-STAT-MIB
1.3.6.1.4.1.351.150.2.1ciscoWanAtmConnStatMIBObjectsCISCO-WAN-ATM-CONN-STAT-MIB
1.3.6.1.4.1.351.150.2.1.1cwacsCISCO-WAN-ATM-CONN-STAT-MIB
1.3.6.1.4.1.351.150.2.1.1.1cwacsTableCISCO-WAN-ATM-CONN-STAT-MIB
1.3.6.1.4.1.351.150.2.1.1.1.1cwacsEntryCISCO-WAN-ATM-CONN-STAT-MIB
1.3.6.1.4.1.351.150.2.1.1.1.1.1cwacsIngRcvCLP0CISCO-WAN-ATM-CONN-STAT-MIB