All MIBs › ACMIB › atmPvcVccCnfrmTypeA2B
atmPvcVccCnfrmTypeA2B
Module: ACMIB
OID (symbolic): ACMIB::atmPvcVccCnfrmTypeA2B
OID (numeric): 1.3.6.1.4.1.1751.2.18.6.1.1.30
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: The following is the description of this field This will be used in conjunction with the service type field to get the correct traffic behaviour. In the conformances the the 0 or 0plus1 refers to the clp bit in the cells. If 0plus1 is the bucket reference then the clp bit is ignored. If 0 is specified for the bucket then check only clp=0 cells. 1: Best Effort will try to send all cellsin a best effort way. This will follow the Aqueman Algorithm 2: one_bucket_notag_0plus1 will use 1 bucket i.e is the PCR(0+1) bucket and drop all cells in excess. 3: two_bucket_notag_0plus1_0plus1 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0+1). All cells conforming to both buckets will be passed through. The rest will be dropped. 4: two_bucket_notag_0plus1_0 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0) or pcr(0). Cells which conform to both buckets are passed through. The rest are dropped. 5: two_bucket_tag_0plus1_0 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0) or pcr(0). Cells which do not conform to the first bucket are dropped. Cells which do not conform to the 2nd bucket are tagged. 6: best_effort_tag. Tag all cells and then do a best effort.
What is atmPvcVccCnfrmTypeA2B?
This OID specifies the traffic conformance algorithm and Cell Loss Priority (CLP) handling for ATM cells traveling from side A to side B. A network engineer configures this to define whether non-compliant cells are discarded or marked with low priority, working in conjunction with the service type. For example, selecting conformance with CLP=0 means cells exceeding the traffic contract are dropped entirely, while CLP=0+1 allows excess cells to be delivered with low priority if bandwidth is available.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.6.1.1.30 snmpwalk -v2c -c public <target> ACMIB::atmPvcVccCnfrmTypeA2B
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.6.1.1.30.1 snmpget -v2c -c public <target> ACMIB::atmPvcVccCnfrmTypeA2B.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.1751.2.18.6.1.1.30.1 i <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> atmPvcVccCnfrmTypeA2B.1
Start monitoring Lucent/Nortel Access Concentrator (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ACMIB::atmPvcVccCnfrmTypeA2B OID value, configure state conditions and alerts, and monitor any Lucent/Nortel Access Concentrator (legacy) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.1751 | lucent | ACMIB |
| 1.3.6.1.4.1.1751.2 | mibs | ACMIB |
| 1.3.6.1.4.1.1751.2.18 | acMIB | ACMIB |
| 1.3.6.1.4.1.1751.2.18.6 | connectionConfig | ACMIB |
| 1.3.6.1.4.1.1751.2.18.6.1 | atmPvcVccTable | ACMIB |
| 1.3.6.1.4.1.1751.2.18.6.1.1 | atmPvcVccEntry | ACMIB |
| 1.3.6.1.4.1.1751.2.18.6.1.1.30 | atmPvcVccCnfrmTypeA2B | ACMIB |