Specifies the behavior of this control signal generated by
the M-FRAP towards the DTE.
inactive-always (1) - signal is permanently INACTIVE.
active-always (2) - signal is permanently ACTIVE.
reflect-carrier (3) - signal echoes the carrier signal status
from the WAN.
inactive-with-test-mode (4) - signal is ACTIVE during normal
data transfer and INACTIVE during diagnostic conditions
that interfere with data transfer from the DTE to the WAN.
follow-RTS (5) - signal echoes the status of RTS as processed
from the DTE.
reflect-carrier-and-RTS (6) - signal is a logical AND between
RTS processed from the DTE and the carrier signal status
from the WAN. No signal from the WAN or RTS INACTIVE
will cause this control signal to be asserted INACTIVE.
reflect-sync-and-RTS (7) - 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.
reflect-LMI-and-carrier-and-RTS (8) - 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.
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 MFRAP.MIB.txt
Company: None
Module: MFRAP-MIB
Specifies the behavior of this control signal generated by
the M-FRAP towards the DTE.
inactive-always (1) - signal is permanently INACTIVE.
active-always (2) - signal is permanently ACTIVE.
reflect-carrier (3) - signal echoes the carrier signal status
from the WAN.
inactive-with-test-mode (4) - signal is ACTIVE during normal
data transfer and INACTIVE during diagnostic conditions
that interfere with data transfer from the DTE to the WAN.
follow-RTS (5) - signal echoes the status of RTS as processed
from the DTE.
reflect-carrier-and-RTS (6) - signal is a logical AND between
RTS processed from the DTE and the carrier signal status
from the WAN. No signal from the WAN or RTS INACTIVE
will cause this control signal to be asserted INACTIVE.
reflect-sync-and-RTS (7) - 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.
reflect-LMI-and-carrier-and-RTS (8) - 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.
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 MFRAP-MIB.mib
Module: MFRAP-MIB
Vendor: Sync Research, Inc.
Module: MFRAP-MIB
[Automatically extracted from oidview.com]
mfrapCfgDteCtsOutput 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 this control signal generated by the M-FRAP towards the DTE. inactive-always (1) - signal is permanently INACTIVE. active-always (2) - signal is permanently ACTIVE. reflect-carrier (3) - signal echoes the carrier signal status from the WAN. inactive-with-test-mode (4) - signal is ACTIVE during normal data transfer and INACTIVE during diagnostic conditions that interfere with data transfer from the DTE to the WAN. follow-RTS (5) - signal echoes the status of RTS as processed from the DTE. reflect-carrier-and-RTS (6) - signal is a logical AND between RTS processed from the DTE and the carrier signal status from the WAN. No signal from the WAN or RTS INACTIVE will cause this control signal to be asserted INACTIVE. reflect-sync-and-RTS (7) - 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. reflect-LMI-and-carrier-and-RTS (8) - 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. 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. " ::= { mfrapCfgDteTable 20 }
mfrapCfgDteCtsOutput 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 this control signal generated by the M-FRAP towards the DTE. inactive-always (1) - signal is permanently INACTIVE. active-always (2) - signal is permanently ACTIVE. reflect-carrier (3) - signal echoes the carrier signal status from the WAN. inactive-with-test-mode (4) - signal is ACTIVE during normal data transfer and INACTIVE during diagnostic conditions that interfere with data transfer from the DTE to the WAN. follow-RTS (5) - signal echoes the status of RTS as processed from the DTE. reflect-carrier-and-RTS (6) - signal is a logical AND between RTS processed from the DTE and the carrier signal status from the WAN. No signal from the WAN or RTS INACTIVE will cause this control signal to be asserted INACTIVE. reflect-sync-and-RTS (7) - 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. reflect-LMI-and-carrier-and-RTS (8) - 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. 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. " ::= { mfrapCfgDteTable 20 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.8.2.4.20.0 | mfrapCfgDteCtsOutput | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.8.2.4.1 | mfrapCfgDteIntfType | 1 | 1 | mfrapCfgDteIntftype |
| 1.3.6.1.4.1.485.8.2.4.2 | mfrapCfgDteDataMode | 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.8.2.4.3 | mfrapCfgDteClockMode | 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.8.2.4.4 | mfrapCfgDteTiming | 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.8.2.4.5 | mfrapCfgDteLineRate | 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.8.2.4.6 | mfrapCfgDteChannelDensity | 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.8.2.4.7 | mfrapCfgDteStartDs0 | 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.8.2.4.8 | mfrapCfgDteConnStatus | 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.8.2.4.9 | mfrapCfgDteConnStartDs0 | 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.8.2.4.10 | mfrapCfgDteConnRate | 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.8.2.4.11 | mfrapCfgDteConnDensity | 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.8.2.4.12 | mfrapCfgDteConnDs0Required | 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.8.2.4.13 | mfrapCfgDteConnAutoStatus | 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.8.2.4.14 | mfrapCfgDteConnAutoUpdate | 1 | 1 | Updates the connection-critical parameters: line rate, channel density and starting ds0; drops the currect connection; and initia… |
| 1.3.6.1.4.1.485.8.2.4.15 | mfrapCfgDteRts | 1 | 1 | Selects whether the RTS signal is external-from-dte (2) or internal-held-active (1). |
| 1.3.6.1.4.1.485.8.2.4.16 | mfrapCfgDteDtr | 1 | 1 | Selects whether the DTR signal is external-from-dte (2) or internal-held-active (1). |
| 1.3.6.1.4.1.485.8.2.4.18 | mfrapCfgDteDcdOutput | 1 | 1 | Specifies the behavior of this control signal generated by the M-FRAP towards the DTE. inactive-always (1) - signal is permanentl… |
| 1.3.6.1.4.1.485.8.2.4.19 | mfrapCfgDteDsrOutput | 1 | 1 | Specifies the behavior of this control signal generated by the M-FRAP towards the DTE. inactive-always (1) - signal is permanentl… |