Status of Remote Loopbacks received from the T1 network port.
csu-lpbk-from-remote (1) indicates the node is in a Network Line
Loopback state due to the reception of the CSU Loop-up pattern
from the network.
dsu-lpbk-from-remote (2) indicates the node is in a Network Line
Loopback state due to the reception of the TyLink proprietary
Loop-up pattern a remote node.
pyl-lpbk-from-remote (3) indicates the node is in a Payload
Loopback state due to the reception of the Facility Data Link's
Loop-up pattern from the network (ESF only).
csu-lpbk-sent-to-remote (4) indicates the node sent a csu loop up
pattern to the remote. The node doesn't know if the loopback was
accepted by the remote unit.
dsu-lpbk-sent-to-remote (5) indicates the node sent a dsu loop up
pattern to the remote. The node doesn't know if the loopback was
accepted by the remote unit.
Parsed from file tylink-3250.mib.txt
Company: None
Module: TY3250I-MIB
Status of Remote Loopbacks received from the T1 network port.
csu-lpbk-from-remote (1) indicates the node is in a Network Line
Loopback state due to the reception of the CSU Loop-up pattern
from the network.
dsu-lpbk-from-remote (2) indicates the node is in a Network Line
Loopback state due to the reception of the TyLink proprietary
Loop-up pattern a remote node.
pyl-lpbk-from-remote (3) indicates the node is in a Payload
Loopback state due to the reception of the Facility Data Link's
Loop-up pattern from the network (ESF only).
csu-lpbk-sent-to-remote (4) indicates the node sent a csu loop up
pattern to the remote. The node doesn't know if the loopback was
accepted by the remote unit.
dsu-lpbk-sent-to-remote (5) indicates the node sent a dsu loop up
pattern to the remote. The node doesn't know if the loopback was
accepted by the remote unit.
Parsed from file TY3250I-MIB.mib
Module: TY3250I-MIB
Vendor: Tylink
Module: TY3250I-MIB
[Automatically extracted from oidview.com]
ty3250DiagT1RmtLpbkStatus OBJECT-TYPE SYNTAX INTEGER { no-remote-lpbks (1), csu-lpbk-from-remote (2), dsu-lpbk-from-remote (3), pyl-lpbk-from-remote (4), csu-lpbk-sent-to-remote (5), dsu-lpbk-sent-to-remote (6) } ACCESS read-only STATUS mandatory DESCRIPTION "Status of Remote Loopbacks received from the T1 network port. csu-lpbk-from-remote (1) indicates the node is in a Network Line Loopback state due to the reception of the CSU Loop-up pattern from the network. dsu-lpbk-from-remote (2) indicates the node is in a Network Line Loopback state due to the reception of the TyLink proprietary Loop-up pattern a remote node. pyl-lpbk-from-remote (3) indicates the node is in a Payload Loopback state due to the reception of the Facility Data Link's Loop-up pattern from the network (ESF only). csu-lpbk-sent-to-remote (4) indicates the node sent a csu loop up pattern to the remote. The node doesn't know if the loopback was accepted by the remote unit. dsu-lpbk-sent-to-remote (5) indicates the node sent a dsu loop up pattern to the remote. The node doesn't know if the loopback was accepted by the remote unit." ::= { ty3250DiagT1Table 4 }
ty3250DiagT1RmtLpbkStatus OBJECT-TYPE SYNTAX INTEGER { no-remote-lpbks (1), csu-lpbk-from-remote (2), dsu-lpbk-from-remote (3), pyl-lpbk-from-remote (4), csu-lpbk-sent-to-remote (5), dsu-lpbk-sent-to-remote (6) } ACCESS read-only STATUS mandatory DESCRIPTION "Status of Remote Loopbacks received from the T1 network port. csu-lpbk-from-remote (1) indicates the node is in a Network Line Loopback state due to the reception of the CSU Loop-up pattern from the network. dsu-lpbk-from-remote (2) indicates the node is in a Network Line Loopback state due to the reception of the TyLink proprietary Loop-up pattern a remote node. pyl-lpbk-from-remote (3) indicates the node is in a Payload Loopback state due to the reception of the Facility Data Link's Loop-up pattern from the network (ESF only). csu-lpbk-sent-to-remote (4) indicates the node sent a csu loop up pattern to the remote. The node doesn't know if the loopback was accepted by the remote unit. dsu-lpbk-sent-to-remote (5) indicates the node sent a dsu loop up pattern to the remote. The node doesn't know if the loopback was accepted by the remote unit." ::= { ty3250DiagT1Table 4 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.466.4.10.4.0 | ty3250DiagT1RmtLpbkStatus | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.466.4.10.1 | ty3250DiagT1LocLineLpbk | 1 | 1 | Local Line Loopback on the T1 network port. Data and framing received from the network is transmitted back to the network |
| 1.3.6.1.4.1.466.4.10.2 | ty3250DiagT1LocPylLpbk | 1 | 1 | Local Payload Loopback on the T1 network port. Data (NOT framing) received from the network is reframed and transmitted back to t… |
| 1.3.6.1.4.1.466.4.10.3 | ty3250DiagT1LocAggrLpbk | 1 | 1 | Local Aggregate Loopback on the T1 network port. Data from the DTE is framed for transmission and looped back through the network… |
| 1.3.6.1.4.1.466.4.10.5 | ty3250DiagT1RmtLpbkCmd | 1 | 1 | Remote loopbacks that can be transmitted out the T1 network port. rmt-csu-lpbk-loopup (1) sends standard CSU loop up code into th… |