CISCO-WAN-AXIPOP-MIB :: bertDeviceToLoopMask

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-WAN-AXIPOP-MIBbertDeviceToLoopMask

bertDeviceToLoopMask

Module: CISCO-WAN-AXIPOP-MIB

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

OID (numeric): 1.3.6.1.4.1.351.110.6.1.28.1.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Every class of devices to loop is represented by 6 bits 
of mask. Bits 0-29 are valid in this integer. The meaning 
of the mask can be understood from the example below:

   -----------------------------------------------------------
             |     |         |       Test Medium
   Class of  | SM  |   MODE  |________________________________
   devices   |supp | Loopback|Line |multiple T1 | 64k |  56k
             |     |         |     | time slots |     |
   -----------------------------------------------------------
   noLatch   |  1        0      0        0         0      1
   latch     |  1        1      0        0         1      1
   v54       |  1        1      0        1         1      1
   inband/esf|  1        1      1        0         0      0
   metallic  |  1        0      1        0         0      0
   -----------------------------------------------------------
   (Table contents applicable to FRSM-4T1)
   bertDeviceToLoopMask = 001110011000100110000111011111 binary

The column titles represent the variables bertDeviceToLoop  
depends on. The mask is represented in column major order.
Due to the limitation on the length of the mask, 'noDevice'
option is not represented in this mask. But, the mask for 
it, is assumed to be a row of ones except for a zero on 
'MODE Loopback' column.
             

What is bertDeviceToLoopMask?

This read-only object is a bitmask (bits 0-29 valid, 6 bits per class of device) indicating which classes of loopback devices are supported by the Service Module in this slot, cross-referenced against mode and test-medium combinations. An admin needing to configure bertDeviceToLoop for a specific card would decode this mask first to confirm the intended device/loopback class is actually supported in the desired mode and medium combination. This level of detail matters because support varies by card type and by the specific mode/medium being used.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.6.1.28.1.5
snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::bertDeviceToLoopMask

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.6.1.28.1.5.1
snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::bertDeviceToLoopMask.1

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::bertDeviceToLoopMask 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.28bertSupportedTestsTableCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.6.1.28.1bertSupportedTestsTableEntryCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.6.1.28.1.5bertDeviceToLoopMaskCISCO-WAN-AXIPOP-MIB