CISCO-WAN-AXIPOP-MIB :: bertDS0DPIterationCount

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-WAN-AXIPOP-MIBbertDS0DPIterationCount

bertDS0DPIterationCount

Module: CISCO-WAN-AXIPOP-MIB

OID (symbolic): CISCO-WAN-AXIPOP-MIB::bertDS0DPIterationCount

OID (numeric): 1.3.6.1.4.1.351.110.6.1.12

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The Iteration Register needs to be programmed in SRM when DSO drop loop option is selected in bertDeviceToLoop. The value to be programmed there is minus one of this object value, since the register is 0 based. DSP-OP devices can be cross connected in the centeral office. By this, the user has capablitiy to put any of the devices in the chain in loopback mode. This is done by repeating the latching activation code in a specific manner. The binary number in the iterataion register determines how many times the first portion of a latching loop activation code needs to be repeated as per user request and according to the Bellcore spec. A value of 0 results in no iteration and will cause the very first device in chain to go into loop back. A value of 1 will result into one iteration and will cause the second device to go into loopback and so on. The range of this count is 1 to 32, and it would translate to a range of 0 to 31 for the iteration register.

What is bertDS0DPIterationCount?

This read-write object programs the Iteration Register in the SRM (one less than this object's value, since the register is zero-based) when the DS0 drop loop option is selected in bertDeviceToLoop, letting a chain of cross-connected DSP-OP devices in the central office be looped one at a time by repeating the latching activation the configured number of times. It lets an admin target a specific device within a daisy-chained set for loopback testing. An admin trying to isolate which device in a chain of cross-connected central-office equipment is faulty would increment this iteration count to step the loopback point further down the chain.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.6.1.12
snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::bertDS0DPIterationCount

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.6.1.12.1
snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::bertDS0DPIterationCount.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.6.1.12.1 i <value>

Start monitoring Cisco MGX 8000-series ATM WAN switches (AXIPOP processor, legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WAN-AXIPOP-MIB::bertDS0DPIterationCount OID value, configure state conditions and alerts, and monitor any Cisco MGX 8000-series ATM WAN switches (AXIPOP processor, legacy) from a single console.

OID Breakdown

Upper-level ancestors (9 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.110basisBASIS-MIB
1.3.6.1.4.1.351.110.6axisDiagnosticsBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.6.1bertCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.6.1.12bertDS0DPIterationCountCISCO-WAN-AXIPOP-MIB