All MIBs › CISCO-BERT-MIB › cbLoopback
cbLoopback
Module: CISCO-BERT-MIB
OID (symbolic): CISCO-BERT-MIB::cbLoopback
OID (numeric): 1.3.6.1.4.1.9.9.185.1.1.1.1.5
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: This object specifies the type of loopback established. Possible values are:
farEndLineLoopback(1): This loopback occurs at the CPE upon receiving a special code from the device which initiates the loopback. Upon receiving the loop activation request code, the CPE enters a Line loop mode in which it returns the entire line back to the initiator. The CPE will continue to return the data back to the initiator until it receives loopback deactivation request code.
remoteLineLoopback(3): This loopback is established at the Near-end. In this loopback the entire line is looped back to the Far-end with a) bit-sequence integrity maintained, b) no change in framing, and c) no removal of bi- polar violations.
localLoopback(3): This is also known as metallic loopback. This loopback is used for checking the internal circuitry of the T3/E3, T1/E1 device. Only for physical lines.
farEndPayloadLoopback(4): This loopback occurs at the CPE upon receiving a special code from the device which initiates the loopback. Upon receiving the loop activation request code, CPE enters a Payload loop mode in which it returns the Payload of the received data back to the initiator. The CPE will continue to return the data back to the initiator until it receives loopback deactivation request code.
remotePayloadLoopback(5): This loopback is established at the Near-end. In this loopback the signal that is returned to the Far-end consists of the payload of the received signal (with bit sequence integrity retained) and newly generated framing information.
noLoopback(6): There is no loopback established on the device.
What is cbLoopback?
This read-only object reports the type of loopback currently established for a BERT test, such as a far-end line loopback initiated at the CPE via a special activation code.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.185.1.1.1.1.5 snmpwalk -v2c -c public <target> CISCO-BERT-MIB::cbLoopback
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.185.1.1.1.1.5.1 snmpget -v2c -c public <target> CISCO-BERT-MIB::cbLoopback.1
Start monitoring Cisco router/access server with T1/E1/T3 WAN interfaces with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-BERT-MIB::cbLoopback OID value, configure state conditions and alerts, and monitor any Cisco router/access server with T1/E1/T3 WAN interfaces from a single console.
OID Breakdown
Upper-level ancestors (8 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 |
| 1.3.6.1.4.1.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.9 | ciscoMgmt | CISCO-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.9.185 | ciscoBertMIB | CISCO-BERT-MIB |
| 1.3.6.1.4.1.9.9.185.1 | ciscoBertMIBObjects | CISCO-BERT-MIB |
| 1.3.6.1.4.1.9.9.185.1.1 | ciscoBertConfig | CISCO-BERT-MIB |
| 1.3.6.1.4.1.9.9.185.1.1.1 | cbConfTable | CISCO-BERT-MIB |
| 1.3.6.1.4.1.9.9.185.1.1.1.1 | cbConfEntry | CISCO-BERT-MIB |
| 1.3.6.1.4.1.9.9.185.1.1.1.1.5 | cbLoopback | CISCO-BERT-MIB |