This attribute is only used when the actualLinkMode is dce. It is
used to determine the clock to be used to recover the receive data.
Note that a V.11 DTE interface uses the S clock (see X.21 standard)
for both receive data and transmit data timing. The DTE interface
always loops the received S clock back to the DCE as the X clock
(see X.21 standard).
If the value of the attribute is fromDce, the DCE V.11 interface uses
the internally generated transmit clock as the S clock and for both
receive and transmit data timing. The X clock is ignored.
If the value of the attribute is fromDte, the DCE still uses the
internally generated transmit clock as the S clock and for transmit
data timing, but the receive data timing is derived from the X clock.
The fromDte mode is recommended when the DTE is far away from
the DCE interface.
Parsed from file nortelPC-logicalProcessorV1.mib.txt
Company: None
Module: Nortel-MsCarrier-MscPassport-LogicalProcessorMIB
This attribute is only used when the actualLinkMode is dce. It is
used to determine the clock to be used to recover the receive data.
Note that a V.11 DTE interface uses the S clock (see X.21 standard)
for both receive data and transmit data timing. The DTE interface
always loops the received S clock back to the DCE as the X clock
(see X.21 standard).
If the value of the attribute is fromDce, the DCE V.11 interface uses
the internally generated transmit clock as the S clock and for both
receive and transmit data timing. The X clock is ignored.
If the value of the attribute is fromDte, the DCE still uses the
internally generated transmit clock as the S clock and for transmit
data timing, but the receive data timing is derived from the X clock.
The fromDte mode is recommended when the DTE is far away from
the DCE interface.
Parsed from file Nortel-MsCarrier-MscPassport-LogicalProcessorMIB.mib
Module: Nortel-MsCarrier-MscPassport-LogicalProcessorMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-MsCarrier-MscPassport-LogicalProcessorMIB
[Automatically extracted from oidview.com]
mscLpX21DteDataClockSource OBJECT-TYPE SYNTAX INTEGER { fromDce(0), fromDte(2) } ACCESS read-write STATUS mandatory DESCRIPTION "This attribute is only used when the actualLinkMode is dce. It is used to determine the clock to be used to recover the receive data. Note that a V.11 DTE interface uses the S clock (see X.21 standard) for both receive data and transmit data timing. The DTE interface always loops the received S clock back to the DCE as the X clock (see X.21 standard). If the value of the attribute is fromDce, the DCE V.11 interface uses the internally generated transmit clock as the S clock and for both receive and transmit data timing. The X clock is ignored. If the value of the attribute is fromDte, the DCE still uses the internally generated transmit clock as the S clock and for transmit data timing, but the receive data timing is derived from the X clock. The fromDte mode is recommended when the DTE is far away from the DCE interface." DEFVAL { fromDce } ::= { mscLpX21ProvEntry 7 }
mscLpX21DteDataClockSource OBJECT-TYPE SYNTAX INTEGER { fromDce(0), fromDte(2) } ACCESS read-write STATUS mandatory DESCRIPTION "This attribute is only used when the actualLinkMode is dce. It is used to determine the clock to be used to recover the receive data. Note that a V.11 DTE interface uses the S clock (see X.21 standard) for both receive data and transmit data timing. The DTE interface always loops the received S clock back to the DCE as the X clock (see X.21 standard). If the value of the attribute is fromDce, the DCE V.11 interface uses the internally generated transmit clock as the S clock and for both receive and transmit data timing. The X clock is ignored. If the value of the attribute is fromDte, the DCE still uses the internally generated transmit clock as the S clock and for transmit data timing, but the receive data timing is derived from the X clock. The fromDte mode is recommended when the DTE is far away from the DCE interface." DEFVAL { fromDce } ::= { mscLpX21ProvEntry 7 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.36.2.1.12.10.10.1.1 | mscLpX21LinkMode | 0 | 0 | This attribute defines the intended gender of the X21 component (V.11 interface). The actual gender of the interface is determin… |
| 1.3.6.1.4.1.562.36.2.1.12.10.10.1.2 | mscLpX21ReadyLineState | 0 | 0 | This attribute specifies the line signals originating from the V.11 interface that will always be turned on, provided the interf… |
| 1.3.6.1.4.1.562.36.2.1.12.10.10.1.3 | mscLpX21DataTransferLineState | 0 | 0 | The state of the line signals required to indicate that the external equipment is in a good state (that is, data transfer can pr… |
| 1.3.6.1.4.1.562.36.2.1.12.10.10.1.4 | mscLpX21LineStatusTimeOut | 0 | 0 | This attribute defines the time the line state must be stable (good or bad) before a state change is declared. |
| 1.3.6.1.4.1.562.36.2.1.12.10.10.1.5 | mscLpX21LineSpeed | 0 | 0 | This attribute defines the speed of the line for source clocking. This attribute is ignored if the interface is not providing a … |
| 1.3.6.1.4.1.562.36.2.1.12.10.10.1.6 | mscLpX21ClockingSource | 0 | 0 | This attribute defines the source of synchronization of the outgoing clocks. This attribute is only used when the actualLinkMode… |
| 1.3.6.1.4.1.562.36.2.1.12.10.10.1.8 | mscLpX21LineTerminationRequired | 0 | 0 | This attribute specifies whether termination is required for this interface. If the hardware setup does not match this attribute… |
| 1.3.6.1.4.1.562.36.2.1.12.10.10.1.9 | mscLpX21ApplicationFramerName | 0 | 0 | This attribute contains the component name of a Framer which is associated with the X21 component. |
| 1.3.6.1.4.1.562.36.2.1.12.10.10.1.10 | mscLpX21EnableDynamicSpeed | 0 | 0 | When set to yes, this attribute specifies that the transmit link speed should be set to the calculated receiver link speed. This… |