This type is not a standard SMI/SNMP base type and is not defined as a documented TEXTUAL-CONVENTION in this MIB.
It was extracted as raw syntax from the source MIB file and could not be resolved to a known type definition.
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.
This OID is also declared by other modules:
CISCO-BERT-MIB