Reference record for OID 1.3.6.1.4.1.485.5.3.2.4


parent
1.3.6.1.4.1.485.5.3.2 (tfrapDiagT1Table)
node code
4
node name
tfrapDiagT1RmtLpbkStatus
dot oid
1.3.6.1.4.1.485.5.3.2.4
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) sync(485) tfrap(5) tfrapt1netwcarrierloss(3) tfrapDiagT1Table(2) tfrapDiagT1RmtLpbkStatus(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) sync(485) tfrap(5) tfrapDiagnostics(3) tfrapDiagT1Table(2) tfrapDiagT1RmtLpbkStatus(4)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) syncResearch(485) tfrap(5) tfrapt1netwcarrierloss(3) tfrapDiagT1Table(2) tfrapDiagT1RmtLpbkStatus(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) syncResearch(485) tfrap(5) tfrapDiagnostics(3) tfrapDiagT1Table(2) tfrapDiagT1RmtLpbkStatus(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) sync(485) tfrap(5) tfrapt1netwcarrierloss(3) tfrapDiagT1Table(2) tfrapDiagT1RmtLpbkStatus(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) sync(485) tfrap(5) tfrapDiagnostics(3) tfrapDiagT1Table(2) tfrapDiagT1RmtLpbkStatus(4)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) syncResearch(485) tfrap(5) tfrapt1netwcarrierloss(3) tfrapDiagT1Table(2) tfrapDiagT1RmtLpbkStatus(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) syncResearch(485) tfrap(5) tfrapDiagnostics(3) tfrapDiagT1Table(2) tfrapDiagT1RmtLpbkStatus(4)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/sync/tfrap/tfrapt1netwcarrierloss/tfrapDiagT1Table/tfrapDiagT1RmtLpbkStatus
  • /iso/identified-organization/dod/internet/private/enterprise/sync/tfrap/tfrapDiagnostics/tfrapDiagT1Table/tfrapDiagT1RmtLpbkStatus
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/syncResearch/tfrap/tfrapt1netwcarrierloss/tfrapDiagT1Table/tfrapDiagT1RmtLpbkStatus
  • /iso/org/dod/internet/private/enterprise/syncResearch/tfrap/tfrapDiagnostics/tfrapDiagT1Table/tfrapDiagT1RmtLpbkStatus
  • /iso/org/dod/internet/private/enterprises/sync/tfrap/tfrapt1netwcarrierloss/tfrapDiagT1Table/tfrapDiagT1RmtLpbkStatus
  • /iso/org/dod/internet/private/enterprises/sync/tfrap/tfrapDiagnostics/tfrapDiagT1Table/tfrapDiagT1RmtLpbkStatus
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/syncResearch/tfrap/tfrapt1netwcarrierloss/tfrapDiagT1Table/tfrapDiagT1RmtLpbkStatus
  • /iso/iso-identified-organization/dod/internet/private/enterprises/syncResearch/tfrap/tfrapDiagnostics/tfrapDiagT1Table/tfrapDiagT1RmtLpbkStatus
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/485/5/3/2/4

    Description by mibdepot

    Status of Remote Loopback commands sent or received on the WAN.
    (1) csu loopback from remote - indicates the node is in a Network
    Line Loopback state due to the reception of the standard CSU
    Loop-up pattern from the WAN.
    (2) dsu loopback from remote - indicates the node is in a Network
    Line Loopback state due to the reception of the Sync Research
    proprietary Loop-up pattern from a remote node.
    (3) payload loopback from remote - indicates the node is in a
    Payload Loopback state due to the reception of the ESF Facility
    Data Link's Loop-up pattern from the network.
    (4) csu loopback sent to remote - indicates the node has sent a csu
    loop up pattern towards the WAN. A device terminating the WAN's
    physical link is expected to enter a Line Loopback. The initating
    unit doesn't know if the loopback was accepted by the remote unit.
    (5) dsu loopback sent to remote - indicates the node has sent a dsu
    loop up pattern to a remote Sync unit out the WAN. A compatible
    device detecting this pattern is expected to enter a Line Loopback.
    The initating unit doesn't know if the loopback was accepted by
    the remote unit.

    Parsed from file TFRAP.MIB.txt
    Company: None
    Module: TFRAP-MIB

    Description by circitor

    Status of Remote Loopback commands sent or received on the WAN.
    (1) csu loopback from remote - indicates the node is in a Network
    Line Loopback state due to the reception of the standard CSU
    Loop-up pattern from the WAN.
    (2) dsu loopback from remote - indicates the node is in a Network
    Line Loopback state due to the reception of the Sync Research
    proprietary Loop-up pattern from a remote node.
    (3) payload loopback from remote - indicates the node is in a
    Payload Loopback state due to the reception of the ESF Facility
    Data Link's Loop-up pattern from the network.
    (4) csu loopback sent to remote - indicates the node has sent a csu
    loop up pattern towards the WAN. A device terminating the WAN's
    physical link is expected to enter a Line Loopback. The initating
    unit doesn't know if the loopback was accepted by the remote unit.
    (5) dsu loopback sent to remote - indicates the node has sent a dsu
    loop up pattern to a remote Sync unit out the WAN. A compatible
    device detecting this pattern is expected to enter a Line Loopback.
    The initating unit doesn't know if the loopback was accepted by
    the remote unit.

    Parsed from file TFRAP-MIB.mib
    Module: TFRAP-MIB

    Information by oid_info

    Vendor: Sync Research, Inc.
    Module: TFRAP-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    tfrapDiagT1RmtLpbkStatus 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 Loopback commands sent or received on the WAN. (1) csu loopback from remote - indicates the node is in a Network Line Loopback state due to the reception of the standard CSU Loop-up pattern from the WAN. (2) dsu loopback from remote - indicates the node is in a Network Line Loopback state due to the reception of the Sync Research proprietary Loop-up pattern from a remote node. (3) payload loopback from remote - indicates the node is in a Payload Loopback state due to the reception of the ESF Facility Data Link's Loop-up pattern from the network. (4) csu loopback sent to remote - indicates the node has sent a csu loop up pattern towards the WAN. A device terminating the WAN's physical link is expected to enter a Line Loopback. The initating unit doesn't know if the loopback was accepted by the remote unit. (5) dsu loopback sent to remote - indicates the node has sent a dsu loop up pattern to a remote Sync unit out the WAN. A compatible device detecting this pattern is expected to enter a Line Loopback. The initating unit doesn't know if the loopback was accepted by the remote unit." ::= { tfrapDiagT1Table 4 }

    Information by circitor

    tfrapDiagT1RmtLpbkStatus 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 Loopback commands sent or received on the WAN. (1) csu loopback from remote - indicates the node is in a Network Line Loopback state due to the reception of the standard CSU Loop-up pattern from the WAN. (2) dsu loopback from remote - indicates the node is in a Network Line Loopback state due to the reception of the Sync Research proprietary Loop-up pattern from a remote node. (3) payload loopback from remote - indicates the node is in a Payload Loopback state due to the reception of the ESF Facility Data Link's Loop-up pattern from the network. (4) csu loopback sent to remote - indicates the node has sent a csu loop up pattern towards the WAN. A device terminating the WAN's physical link is expected to enter a Line Loopback. The initating unit doesn't know if the loopback was accepted by the remote unit. (5) dsu loopback sent to remote - indicates the node has sent a dsu loop up pattern to a remote Sync unit out the WAN. A compatible device detecting this pattern is expected to enter a Line Loopback. The initating unit doesn't know if the loopback was accepted by the remote unit." ::= { tfrapDiagT1Table 4 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.485)

    Bartky Alan

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.485.5.3.2.4.0 tfrapDiagT1RmtLpbkStatus 0 0 None

    Brothers (5)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.485.5.3.2.1 tfrapDiagT1LocLineLpbk 1 1 Controls local network loopback. All data (including
    framing and line errors) received from the WAN,
    regardless of format or cont…
    1.3.6.1.4.1.485.5.3.2.2 tfrapDiagT1LocPylLpbk 1 1 Controls network payload loopback. All data
    received from the WAN is terminated, reframed
    and sent back towards the WAN. Framing …
    1.3.6.1.4.1.485.5.3.2.3 tfrapDiagT1LocAggrLpbk 1 1 Controls Local Aggregate Loopback. All data
    received from the DTE is framed, formatted
    and transmit towards the WAN while being l…
    1.3.6.1.4.1.485.5.3.2.5 tfrapDiagT1RmtLpbkCmd 1 1 Remote loopback commands are intended to place compatible external
    equipment into a loopback state. The initiating unit will mai…
    1.3.6.1.4.1.485.5.3.2.6 tfrapDiagT1TimeRemaining 1 1 The remaining time on the active loopback before the loopback
    times out and automatically clears itself to restore the unit
    to no…