CPIWF-MIB :: aal2CpsInPkts

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCPIWF-MIBaal2CpsInPkts

aal2CpsInPkts

Module: CPIWF-MIB

OID (symbolic): CPIWF-MIB::aal2CpsInPkts

OID (numeric): 1.3.6.1.4.1.353.5.10.1.1.6.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of CPS packets received

What is aal2CpsInPkts?

This read-only Counter32 counts the total number of AAL2 CPS packets received on this connection. It gives an admin a baseline traffic volume figure to compare against error counters, helping determine whether an error rate is proportionally significant. If aal2CpsParityErrors is climbing rapidly while this received-packet count stays flat, the admin knows the error rate per packet is worsening rather than just tracking increased traffic volume.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.353.5.10.1.1.6.1
snmpwalk -v2c -c public <target> CPIWF-MIB::aal2CpsInPkts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.353.5.10.1.1.6.1.1
snmpget -v2c -c public <target> CPIWF-MIB::aal2CpsInPkts.1

Start monitoring ATM access/carrier equipment (Loop Emulation Service CP-IWF) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CPIWF-MIB::aal2CpsInPkts OID value, configure state conditions and alerts, and monitor any ATM access/carrier equipment (Loop Emulation Service CP-IWF) from a single console.

How to Use in IPNetwork Monitor

Select an ATM access/carrier equipment (Loop Emulation Service CP-IWF) 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 aal2CpsInPkts into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of CPS packets received. 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.353atmForumATM-FORUM-ILMI40-MIB
1.3.6.1.4.1.353.5atmForumNetworkManagementATM-FORUM-SNMP-M4-MIB
Numeric OIDNameModule
1.3.6.1.4.1.353.5.10atmfLoopEmulationServiceCPIWF-MIB
1.3.6.1.4.1.353.5.10.1cpIwfMIBCPIWF-MIB
1.3.6.1.4.1.353.5.10.1.1cpIwfMIBObjectsCPIWF-MIB
1.3.6.1.4.1.353.5.10.1.1.6cpIwfAal2StatsCPIWF-MIB
1.3.6.1.4.1.353.5.10.1.1.6.1aal2CpsInPktsCPIWF-MIB