Reference record for OID 1.3.6.1.4.1.485.5.2.4.18


parent
1.3.6.1.4.1.485.5.2.4 (tfrapCfgDteTable)
node code
18
node name
tfrapCfgDteDcdOutput
dot oid
1.3.6.1.4.1.485.5.2.4.18
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) sync(485) tfrap(5) tfrapConfiguration(2) tfrapCfgDteTable(4) tfrapCfgDteDcdOutput(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) syncResearch(485) tfrap(5) tfrapConfiguration(2) tfrapCfgDteTable(4) tfrapCfgDteDcdOutput(18)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) sync(485) tfrap(5) tfrapConfiguration(2) tfrapCfgDteTable(4) tfrapCfgDteDcdOutput(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) syncResearch(485) tfrap(5) tfrapConfiguration(2) tfrapCfgDteTable(4) tfrapCfgDteDcdOutput(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) sync(485) tfrap(5) tfrapConfiguration(2) tfrapCfgDteTable(4) tfrapCfgDteDcdOutput(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) syncResearch(485) tfrap(5) tfrapConfiguration(2) tfrapCfgDteTable(4) tfrapCfgDteDcdOutput(18)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) sync(485) tfrap(5) tfrapConfiguration(2) tfrapCfgDteTable(4) tfrapCfgDteDcdOutput(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) syncResearch(485) tfrap(5) tfrapConfiguration(2) tfrapCfgDteTable(4) tfrapCfgDteDcdOutput(18)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/sync/tfrap/tfrapConfiguration/tfrapCfgDteTable/tfrapCfgDteDcdOutput
  • /iso/identified-organization/dod/internet/private/enterprise/syncResearch/tfrap/tfrapConfiguration/tfrapCfgDteTable/tfrapCfgDteDcdOutput
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/sync/tfrap/tfrapConfiguration/tfrapCfgDteTable/tfrapCfgDteDcdOutput
  • /iso/org/dod/internet/private/enterprise/syncResearch/tfrap/tfrapConfiguration/tfrapCfgDteTable/tfrapCfgDteDcdOutput
  • /iso/org/dod/internet/private/enterprises/sync/tfrap/tfrapConfiguration/tfrapCfgDteTable/tfrapCfgDteDcdOutput
  • /iso/org/dod/internet/private/enterprises/syncResearch/tfrap/tfrapConfiguration/tfrapCfgDteTable/tfrapCfgDteDcdOutput
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/sync/tfrap/tfrapConfiguration/tfrapCfgDteTable/tfrapCfgDteDcdOutput
  • /iso/iso-identified-organization/dod/internet/private/enterprises/syncResearch/tfrap/tfrapConfiguration/tfrapCfgDteTable/tfrapCfgDteDcdOutput
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/485/5/2/4/18

    Description by mibdepot

    Specifies the behavior of the Data Carrier Detect (DCD)
    control signal generated by the unit towards the DTE.
    (1) inactive always: signal is permanently INACTIVE.
    (2) active always: signal is permanently ACTIVE.
    (3) reflect WAN carrier: signal echoes the received signal status
    from the WAN.
    (4) inactive with test mode: signal is ACTIVE during normal
    data transfer and INACTIVE during diagnostic conditions
    that interfere with data transfer from the DTE to the WAN.
    (5) follow RTS: signal echoes the status of RTS as processed
    from the DTE.
    (6) reflect carrier and RTS: signal is a logical AND between
    RTS processed from the DTE and the received signal status
    from the WAN. No signal received from the WAN or RTS INACTIVE
    will cause this control signal to be asserted INACTIVE.
    (7) reflect sync and RTS: signal is a logical AND between RTS
    processed from the DTE and the frame synchronization with the WAN.
    Red Alarm defines the threshold for declaring synchronization.
    (8) reflect LMI and carrier and RTS: signal is a logical AND
    between RTS processed from the DTE and the carrier signal
    status from the WAN and LMI. If the unit is in an LMI
    passthrough state then LMI is considered Active.
    LMI Inactivity timer must be non-zero for LMI to be declared
    Inactive. In non-Frame Relay applications (type = dedicated)
    LMI will be presumed ACTIVE so this will setting is equivalent
    to (6).
    Note that there is a separate parameter for how the unit processes
    RTS that is related to this function if options (4), (5), (6), or (7)
    is selected, see CfgDteRts.

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

    Description by circitor

    Specifies the behavior of the Data Carrier Detect (DCD)
    control signal generated by the unit towards the DTE.
    (1) inactive always: signal is permanently INACTIVE.
    (2) active always: signal is permanently ACTIVE.
    (3) reflect WAN carrier: signal echoes the received signal status
    from the WAN.
    (4) inactive with test mode: signal is ACTIVE during normal
    data transfer and INACTIVE during diagnostic conditions
    that interfere with data transfer from the DTE to the WAN.
    (5) follow RTS: signal echoes the status of RTS as processed
    from the DTE.
    (6) reflect carrier and RTS: signal is a logical AND between
    RTS processed from the DTE and the received signal status
    from the WAN. No signal received from the WAN or RTS INACTIVE
    will cause this control signal to be asserted INACTIVE.
    (7) reflect sync and RTS: signal is a logical AND between RTS
    processed from the DTE and the frame synchronization with the WAN.
    Red Alarm defines the threshold for declaring synchronization.
    (8) reflect LMI and carrier and RTS: signal is a logical AND
    between RTS processed from the DTE and the carrier signal
    status from the WAN and LMI. If the unit is in an LMI
    passthrough state then LMI is considered Active.
    LMI Inactivity timer must be non-zero for LMI to be declared
    Inactive. In non-Frame Relay applications (type = dedicated)
    LMI will be presumed ACTIVE so this will setting is equivalent
    to (6).
    Note that there is a separate parameter for how the unit processes
    RTS that is related to this function if options (4), (5), (6), or (7)
    is selected, see CfgDteRts.

    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

    tfrapCfgDteDcdOutput OBJECT-TYPE SYNTAX INTEGER { signal-off (1), signal-on (2), follow-carrier (3), follow-test (4), follow-rts (5), follow-carrier-rts (6), follow-sync-rts (7), follow-lmi-carr-rts (8) } ACCESS read-write STATUS mandatory DESCRIPTION "Specifies the behavior of the Data Carrier Detect (DCD) control signal generated by the unit towards the DTE. (1) inactive always: signal is permanently INACTIVE. (2) active always: signal is permanently ACTIVE. (3) reflect WAN carrier: signal echoes the received signal status from the WAN. (4) inactive with test mode: signal is ACTIVE during normal data transfer and INACTIVE during diagnostic conditions that interfere with data transfer from the DTE to the WAN. (5) follow RTS: signal echoes the status of RTS as processed from the DTE. (6) reflect carrier and RTS: signal is a logical AND between RTS processed from the DTE and the received signal status from the WAN. No signal received from the WAN or RTS INACTIVE will cause this control signal to be asserted INACTIVE. (7) reflect sync and RTS: signal is a logical AND between RTS processed from the DTE and the frame synchronization with the WAN. Red Alarm defines the threshold for declaring synchronization. (8) reflect LMI and carrier and RTS: signal is a logical AND between RTS processed from the DTE and the carrier signal status from the WAN and LMI. If the unit is in an LMI passthrough state then LMI is considered Active. LMI Inactivity timer must be non-zero for LMI to be declared Inactive. In non-Frame Relay applications (type = dedicated) LMI will be presumed ACTIVE so this will setting is equivalent to (6). Note that there is a separate parameter for how the unit processes RTS that is related to this function if options (4), (5), (6), or (7) is selected, see CfgDteRts." ::= { tfrapCfgDteTable 18 }

    Information by circitor

    tfrapCfgDteDcdOutput OBJECT-TYPE SYNTAX INTEGER { signal-off (1), signal-on (2), follow-carrier (3), follow-test (4), follow-rts (5), follow-carrier-rts (6), follow-sync-rts (7), follow-lmi-carr-rts (8) } ACCESS read-write STATUS mandatory DESCRIPTION "Specifies the behavior of the Data Carrier Detect (DCD) control signal generated by the unit towards the DTE. (1) inactive always: signal is permanently INACTIVE. (2) active always: signal is permanently ACTIVE. (3) reflect WAN carrier: signal echoes the received signal status from the WAN. (4) inactive with test mode: signal is ACTIVE during normal data transfer and INACTIVE during diagnostic conditions that interfere with data transfer from the DTE to the WAN. (5) follow RTS: signal echoes the status of RTS as processed from the DTE. (6) reflect carrier and RTS: signal is a logical AND between RTS processed from the DTE and the received signal status from the WAN. No signal received from the WAN or RTS INACTIVE will cause this control signal to be asserted INACTIVE. (7) reflect sync and RTS: signal is a logical AND between RTS processed from the DTE and the frame synchronization with the WAN. Red Alarm defines the threshold for declaring synchronization. (8) reflect LMI and carrier and RTS: signal is a logical AND between RTS processed from the DTE and the carrier signal status from the WAN and LMI. If the unit is in an LMI passthrough state then LMI is considered Active. LMI Inactivity timer must be non-zero for LMI to be declared Inactive. In non-Frame Relay applications (type = dedicated) LMI will be presumed ACTIVE so this will setting is equivalent to (6). Note that there is a separate parameter for how the unit processes RTS that is related to this function if options (4), (5), (6), or (7) is selected, see CfgDteRts." ::= { tfrapCfgDteTable 18 }

    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.2.4.18.0 tfrapCfgDteDcdOutput 0 0 None

    Brothers (18)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.485.5.2.4.1 tfrapCfgDteIntfType 1 1 tfrapCfgDteIntftype
    1.3.6.1.4.1.485.5.2.4.2 tfrapCfgDteDataMode 1 1 Inverts the DTE data for transfer across the WAN. Can make
    some applications, particularly HDLC-based protocols, meet
    density req…
    1.3.6.1.4.1.485.5.2.4.3 tfrapCfgDteClockMode 1 1 This selection controls how the unit internally latches
    the transmit data from the DTE. Normal will sample
    data with the rising e…
    1.3.6.1.4.1.485.5.2.4.4 tfrapCfgDteTiming 1 1 Serial DTE Transmit Timing mode. Loop-1 (1) uses the clock
    returned from the DTE (TT/TCE) to sample tx data, Loop-2 (2)
    uses the …
    1.3.6.1.4.1.485.5.2.4.5 tfrapCfgDteLineRate 1 1 Serial DTE Data Rate in bits per second. Valid
    rates depend upon channel density selection: nX56K for
    bit-7-stuffing, and nX64K f…
    1.3.6.1.4.1.485.5.2.4.6 tfrapCfgDteChannelDensity 1 1 Packing of serial data into T1 DS0's. Bit-7-stuff
    supports DTE rates of nX56Kb/s (from 56K to 1344K) and
    provides sufficient ones…
    1.3.6.1.4.1.485.5.2.4.7 tfrapCfgDteStartDs0 1 1 T1 WAN includes 24 DS0's available for user data. Each DS0
    carries either 56Kbit/sec (bit-7-stuffing) or 64KBit/sec
    (clear-channe…
    1.3.6.1.4.1.485.5.2.4.8 tfrapCfgDteConnStatus 1 1 The current status of the WAN to DTE mappings.
    (1) connections valid and DS0s allocated to DTE data.
    (4) no connections configure…
    1.3.6.1.4.1.485.5.2.4.9 tfrapCfgDteConnStartDs0 1 1 T1 WAN includes 24 DS0's available for user data. Each DS0
    carries either 56Kbit/sec (bit-7-stuffing) or 64KBit/sec
    (clear-channe…
    1.3.6.1.4.1.485.5.2.4.10 tfrapCfgDteConnRate 1 1 Serial DTE Data Rate in bits per second. Valid
    rates depend upon channel density selection: nX56K for
    bit-7-stuffing, and nX64K f…
    1.3.6.1.4.1.485.5.2.4.11 tfrapCfgDteConnDensity 1 1 Packing of serial data into T1 DS0's. Bit-7-stuff
    supports DTE rates of nX56Kb/s (from 56K to 1344K) and
    provides sufficient ones…
    1.3.6.1.4.1.485.5.2.4.12 tfrapCfgDteConnDs0Required 1 1 The number of DS0s required by the node's DTE port.
    This is based upon the DTE data rate and channel density
    selections.
    1.3.6.1.4.1.485.5.2.4.13 tfrapCfgDteConnAutoStatus 1 1 There's a tight correlation among DTE data rate, starting
    DS0, and channel density. This read-only parameter reports
    the status o…
    1.3.6.1.4.1.485.5.2.4.14 tfrapCfgDteConnAutoUpdate 1 1 Updates the connection-critical parameters: line rate,
    channel density and starting ds0; drops the current
    connection; and initia…
    1.3.6.1.4.1.485.5.2.4.15 tfrapCfgDteRts 1 1 Controls the reporting of the status of the DTE's Request
    to Send (RTS) control signal, specifically the generation
    of traps in r…
    1.3.6.1.4.1.485.5.2.4.16 tfrapCfgDteDtr 1 1 Controls the reporting of the status of the DTE's Data
    Terminal Ready (DTR) control signal, specifically the
    generation of traps …
    1.3.6.1.4.1.485.5.2.4.19 tfrapCfgDteDsrOutput 1 1 Specifies the behavior of the Data Set Ready (DSR)
    control signal generated by the unit towards the DTE.
    (1) inactive always: si…
    1.3.6.1.4.1.485.5.2.4.20 tfrapCfgDteCtsOutput 1 1 Specifies the behavior of the Clear to Send (CTS)
    control signal generated by the unit towards the DTE.
    (1) inactive always: sign…