CISCO-ADSL-DMT-LINE-MIB

DmtOverheadFraming0 = structure01 = structure12 = structure23 = structure3There exist two types of ADSL framing: full overhead and reduced overhead. Furthermore, there exist two versions of full overhead and two versions of reduced overhead. The table below defines the four resulting framing structures: 'structure0' Full overhead framing with asynchronous bit-to-modem timing (enabled synchronization control mechanism). 'structure1' Full overhead framing with synchronous bit-to-modem timing (disabled synchronization control mechanism). 'structure2' Reduced overhead framing with separate fast and sync bytes in fast and interleaved latency buffers respectively (64 kbps framing overhead). 'structure3' Reduced overhead framing with merged fast and sync byte, using either the fast or interleaved latency buffer (32 kbps framing overhead). During the training sequence, the ATU-C shall indicate the highest framing structure number that it supports. It is implied that if the ATU-C indicates it supports framing structure k, it also supports all framing structures 0 to k-1. If during the training sequence the ATU-R indicates a lower framing structure than that specified by the ATU-C, the ATU-C shall fall back to the framing structure number indicated by the ATU-R. Management requirements drive the determination of overhead, full or reduced. Full overhead provides more bandwidth to the EOC channel, thereby enabling higher polling rates. However, reduced overhead provides enough bandwidth to satisfy typical applications. If an ADSL line is supporting an ATM link, then a structure must be chosen that disables synchronization control. If an ADSL line is supporting an STM link, and the ADSL line interface has a clock tightly coupled to the stratum clock, then synchronization control is not necessary. If an ADSL line is supporting an STM link, and the ADSL line interface is driven by a clock that has no relationship with the stratum clock, then a struture that enables synchronization control is necessary.Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. · Integer32

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object represents the negotiated overhead framing structure being used by the ATU-C and ATU-R.

INTEGER1 = standard2 = unknown3 = downloading4 = downloadFailed5 = testing · Integer32

Reference: ADSL Forum Technical Specification TR-014, DMT Line Code Specific MIB.

The value of this object specifies the enterprise-specific specific status of the ATU-C. If the value of adslAtucDMTState is not 'other', then the value of this object is 'standard'. If the value of adslAtucDMTState is 'other', and the ATU-C is in an unrecognized state, then the value of this object is 'unknown'. If the value of adslAtucDMTState is 'other', and the ATU-C is not in an unrecognized state, then the value of this object specifies the enterprise-specific state of the ATU-C.

DmtFecSizeOne of the three parameters that affects FEC operation; the number of FEC redundancy bytes per Reed-Solomon codeword. The codeword size also affects FEC operation. The interleave depth also affects FEC operation on an interleaved channel (see the ADSL-LINE-MIB, specifically adslAtucChanConfMaxInterleaveDelay and adslAturChanConfMaxInterleaveDelay).Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. draft-ietf-adslmib-adsllinemib-04, Definitions of Managed Objects for ADSL Lines. (0 | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16) · Integer32 · bytes

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the number of FEC redundancy bytes the ATU-C appends to downstream on the corresponding channel. The ATU-C can fallback from the initial value specified for the corresponding channel (i.e., cAdslAtucDmtConfFastFecSize or cAdslAtucInterleaveFecSize) based on the aggregate data rate rate achieved during training.

DmtCodewordSizeOne of the three parameters that affects FEC operation; the number of ADSL symbols per FEC codeword. The FEC size also affects FEC operation. The interleave depth also affects FEC operation on an interleaved channel (see the ADSL-LINE-MIB, specifically adslAtucChanConfMaxInterleaveDelay and adslAturChanConfMaxInterleaveDelay). The following constraints apply: - This value is always '1' when performing the FEC operation on a fast buffer. - When performing the FEC operation on an interleaved buffer, the specification does not require a codeword size greater than '1' when the interleave depth is set to '1'. - if DmtCodeWordSize is positive, it represents the actual number of symbols per codeword. If DmtCodeWordSize is negative, it represents the exponent value in a power of 2. For example, if DmtCodeWordSize is equal to -1, then the number of symbols per codeword would be equal to 2^^-1 = 1/2.Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. RFC 2662 - Definitions of Managed Objects for the ADSL Lines. G. Bathrick,. Ly. August 1999. (-1 | 1 | 2 | 4 | 8 | 16) · Integer32 · symbols

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the actual number of symbols per codeword being used by the ATU-C for downstream messages. The ATU-C and ATU-R negotiate this value during the training sequence. A value of 0 indicates the automatic mode.

DmtFecSizeOne of the three parameters that affects FEC operation; the number of FEC redundancy bytes per Reed-Solomon codeword. The codeword size also affects FEC operation. The interleave depth also affects FEC operation on an interleaved channel (see the ADSL-LINE-MIB, specifically adslAtucChanConfMaxInterleaveDelay and adslAturChanConfMaxInterleaveDelay).Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. draft-ietf-adslmib-adsllinemib-04, Definitions of Managed Objects for ADSL Lines. (0 | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16) · Integer32 · bytes

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the number of FEC redundancy bytes the ATU-R appends to upstream on the corresponding channel. The ATU-C can fallback from the initial value specified for the corresponding channel (i.e., cAdslAturDmtConfFastFecSize or cAdslAturInterleaveFecSize) based on the aggregate data rate achieved during training.

DmtCodewordSizeOne of the three parameters that affects FEC operation; the number of ADSL symbols per FEC codeword. The FEC size also affects FEC operation. The interleave depth also affects FEC operation on an interleaved channel (see the ADSL-LINE-MIB, specifically adslAtucChanConfMaxInterleaveDelay and adslAturChanConfMaxInterleaveDelay). The following constraints apply: - This value is always '1' when performing the FEC operation on a fast buffer. - When performing the FEC operation on an interleaved buffer, the specification does not require a codeword size greater than '1' when the interleave depth is set to '1'. - if DmtCodeWordSize is positive, it represents the actual number of symbols per codeword. If DmtCodeWordSize is negative, it represents the exponent value in a power of 2. For example, if DmtCodeWordSize is equal to -1, then the number of symbols per codeword would be equal to 2^^-1 = 1/2.Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. RFC 2662 - Definitions of Managed Objects for the ADSL Lines. G. Bathrick,. Ly. August 1999. (-1 | 1 | 2 | 4 | 8 | 16) · Integer32 · symbols

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the actual number of symbols per codeword being used by the ATU-R for upstream messages. The ATU-C and ATU-R negotiate this value during the training sequence.

INTEGER1 = automatic2 = splitterless3 = g992Dot14 = g992Dot25 = t1Dot413 · Integer32

Reference: ITU G.992.1, Asymmetric Digital Subscriber Line (ADSL) Transceiver. ITU G.992.2, Splitterless Asymmetric Digital Subscriber Line (ADSL) Transceiver. ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the line operating mode being employed by the ADSL line. An ADSL line uses of one of two operating modes: - Automatic An ATU-C that employs this operating mode automatically detects the capabilities of the ATU-R and utilizes either a startup sequence specified by G.992.1, G.992.2, or T1.413-1998. This line operating mode is the default for an ADSL line. - Splitterless This operating mode should no longer be used. It is equivalent to the G.992.2 selection. Selecting this mode will automatically map to the G992.2 mode. It is appropriate in this case that both the ATU-C and ATU-R support 'heavy' capability but the ATU-C side wishes to force 'lite' operation. Selecting this mode will automatically convert to the G992.2 mode. - G992.1 This operating mode forces the used of the G994.1 startup sequence and compliance to G992.1 operation. - G992.2 This operating mode forces the use of the G994.1 startup sequence and compliance to G992.2 operation. It is appropriate in this case that both the ATU-C and ATU-R support 'heavy' capability but the ATU-C side wishes to force 'lite' operation. - T1.413 This operating mode forces the ATU-R to use the T1.413-1998 startup sequence.

INTEGER1 = standard2 = fast · Integer32

Reference: ITU G.992.1, Asymmetric Digital Subscriber Line (ADSL) Transceiver. ITU G.992.2, Splitterless Asymmetric Digital Subscriber Line (ADSL) Transceiver. ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the mode employed by the ATU-C and ATU-R when training against each other. One of two training modes can be employed: - Standard An ATU-C initiates a training sequence using the method defined by G.992.1, G.992.2, or T1.413-1998. This training mode is the default for ADSL modems. - Fast An ATU-C initiates a vendor-specific training sequence that can possibly provide a shorter training sequence.

DmtFecSizeOne of the three parameters that affects FEC operation; the number of FEC redundancy bytes per Reed-Solomon codeword. The codeword size also affects FEC operation. The interleave depth also affects FEC operation on an interleaved channel (see the ADSL-LINE-MIB, specifically adslAtucChanConfMaxInterleaveDelay and adslAturChanConfMaxInterleaveDelay).Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. draft-ietf-adslmib-adsllinemib-04, Definitions of Managed Objects for ADSL Lines. (0 | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16) · Integer32 · bytes

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the initial number of FEC redundancy bytes the ATU-C appends to downstream frames transmitted over the fast channel during the training sequence. The ATU-C can fallback from this value depending on the aggregate data rate achieved during training. It is desirable to choose a large FEC size, thereby increasing the chance of being able to correct errors in the data delivered by a frame. However, additional FEC redundancy bytes increases frame overhead, and thus frame latency.

DmtFecSizeOne of the three parameters that affects FEC operation; the number of FEC redundancy bytes per Reed-Solomon codeword. The codeword size also affects FEC operation. The interleave depth also affects FEC operation on an interleaved channel (see the ADSL-LINE-MIB, specifically adslAtucChanConfMaxInterleaveDelay and adslAturChanConfMaxInterleaveDelay).Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. draft-ietf-adslmib-adsllinemib-04, Definitions of Managed Objects for ADSL Lines. (0 | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16) · Integer32 · bytes

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the initial number of FEC redundancy bytes the ATU-C appends to downstream frames transmitted over the interleaved channel during the training sequence. The ATU-C can fallback from this value depending on the aggregate data rate achieved during training. It is desirable to choose a large FEC size, thereby increasing the chance of being able to correct errors in the data delivered by a frame. However, additional FEC redundancy bytes increases frame overhead, and thus frame latency. The value of this object must be a integral multiple of the value of cAdslAtucDmtConfCodewordSize.

DmtCodewordSizeOne of the three parameters that affects FEC operation; the number of ADSL symbols per FEC codeword. The FEC size also affects FEC operation. The interleave depth also affects FEC operation on an interleaved channel (see the ADSL-LINE-MIB, specifically adslAtucChanConfMaxInterleaveDelay and adslAturChanConfMaxInterleaveDelay). The following constraints apply: - This value is always '1' when performing the FEC operation on a fast buffer. - When performing the FEC operation on an interleaved buffer, the specification does not require a codeword size greater than '1' when the interleave depth is set to '1'. - if DmtCodeWordSize is positive, it represents the actual number of symbols per codeword. If DmtCodeWordSize is negative, it represents the exponent value in a power of 2. For example, if DmtCodeWordSize is equal to -1, then the number of symbols per codeword would be equal to 2^^-1 = 1/2.Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. RFC 2662 - Definitions of Managed Objects for the ADSL Lines. G. Bathrick,. Ly. August 1999. (-1 | 1 | 2 | 4 | 8 | 16) · Integer32 · symbols

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the number of symbols per codeword being used by the ATU-C for downstream messages on an interleaved channel during the training sequence. The ATU-C can fallback from this value based on the aggregate data rate achieved during training. It is desirable to choose a large codeword size to minimize overhead. However, increasing the codeword size increases the possibility of not being able to correct errors in the data delivered by a frame.

DmtOverheadFraming0 = structure01 = structure12 = structure23 = structure3There exist two types of ADSL framing: full overhead and reduced overhead. Furthermore, there exist two versions of full overhead and two versions of reduced overhead. The table below defines the four resulting framing structures: 'structure0' Full overhead framing with asynchronous bit-to-modem timing (enabled synchronization control mechanism). 'structure1' Full overhead framing with synchronous bit-to-modem timing (disabled synchronization control mechanism). 'structure2' Reduced overhead framing with separate fast and sync bytes in fast and interleaved latency buffers respectively (64 kbps framing overhead). 'structure3' Reduced overhead framing with merged fast and sync byte, using either the fast or interleaved latency buffer (32 kbps framing overhead). During the training sequence, the ATU-C shall indicate the highest framing structure number that it supports. It is implied that if the ATU-C indicates it supports framing structure k, it also supports all framing structures 0 to k-1. If during the training sequence the ATU-R indicates a lower framing structure than that specified by the ATU-C, the ATU-C shall fall back to the framing structure number indicated by the ATU-R. Management requirements drive the determination of overhead, full or reduced. Full overhead provides more bandwidth to the EOC channel, thereby enabling higher polling rates. However, reduced overhead provides enough bandwidth to satisfy typical applications. If an ADSL line is supporting an ATM link, then a structure must be chosen that disables synchronization control. If an ADSL line is supporting an STM link, and the ADSL line interface has a clock tightly coupled to the stratum clock, then synchronization control is not necessary. If an ADSL line is supporting an STM link, and the ADSL line interface is driven by a clock that has no relationship with the stratum clock, then a struture that enables synchronization control is necessary.Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. · Integer32

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the overhead framing structure which the ATU-C will request when establishing a link with the ATU-R. The value of 'structure0' is not valid.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. RFC 2662 - Definitions of Managed Objects for the ADSL Lines. G. Bathrick,. Ly. August 1999.

This object specifies whether the ATU-C performs bitswapping. Bitswapping attempts to maintain an acceptable margin for each bin; equalizing the margin across all bins through bit reallocation, thereby maximizing error performance. The ATU-C performs bitswapping by monitoring the margin measured for each bin by the transmitter: 1) If a bin's margin falls below 'target' and the difference, between the margin and 'target' exceeds 'thresh(f)', then the ATU-C marks the bin as a 'from' bin. 2) If a bin's margin exceeds 'target' and the difference between the margin and 'target' exceeds 'thresh(t)', then the ATU-C marks the bin as a 'to' bin. Where: 'target' = adslAtucConfTargetSnrMgn 'thresh(f)' = cAdslAtucDmtConfBitSwapFrom 'thresh(t)' = cAdslAtucDmtConfBitSwapTo The ATU-C attempts to equalize the margin across the bins by swapping bits out of bins marked 'from' into bins marked 'to'. When the ATU-C swaps a bit out of bin, it decreases its b(i). Thus, the bins constellation is smaller, which increases its margin. When the ATU-C swaps a bit into a bin, it increases its b(i). Thus, the bins constellation is larger, which decreases its margin. In addition, the ATU-R may optionally implement its own monitoring capability. The ATU-R uses this information to request the ATU-C to perform bitswapping. When this object is 'true', the ATU-C must be prepared to accept and properly handle bitswap requests from the ATU-R. While bitswapping has its obvious advantages, bitswapping can have undesirable side effects. It can introduce errors on lines prone to impulse noise. In this case, it may be desirable to disable bitswapping.

Integer32 (1..9) · dB

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. RFC 2662 - Definitions of Managed Objects for the ADSL Lines. G. Bathrick,. Ly. August 1999.

Bitswapping attempts to maintain an acceptable margin for each bin; equalizing the margin across all bins through bit reallocation, thereby maximizing error performance. The ATU-C performs bitswapping by monitoring the margin measured for each bin by the transmitter. If a bin's margin falls below adslAtucConfTargetSnrMgn and the difference between the margin and adslAtucConfTargetSnrMgn exceeds the value of this object, then the ATU-C marks a bin as a 'from' bin. The ATU-C attempts to equalize the margin across the bins by swapping bits out of bins marked 'from' into bins marked 'to'. When the ATU-C swaps a bit out of bin, it decreases its b(i). Thus, the bins constellation is smaller. which increases its margin. When the ATU-C swaps a bit into a bin, it increases its b(i). Thus, the bins constellation is larger, which decreases its margin. If this value is too small, then the ATU-C may frequently toggle the bit allocation on bins, and if impulse noise is present, this can cause errors. If this value is too large, then the ATU-C may not identify an adequate number of bins that it can swap bits 'from', thereby decreasing the chances for the ATU-C to equalize the margin across all the bins. Unequalized margin across all the bins translates into poor error performance.

Integer32 (1..9) · dB

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. RFC 2662 - Definitions of Managed Objects for the ADSL Lines. G. Bathrick,. Ly. August 1999.

Bitswapping attempts to maintain an acceptable margin for each bin; equalizing the margin across all bins through bit reallocation, thereby maximizing error performance. The ATU-C performs bitswapping by monitoring the margin measured for each bin by the transmitter. If a bin's margin exceeds adslAtucConfTargetSnrMgn and the difference between the margin and adslAtucConfTargetSnrMgn exceeds the value of this object, then the ATU-C marks a bin as a 'to' bin. The ATU-C attempts to equalize the margin across the bins by swapping bits out of bins marked 'from' into bins marked 'to'. When the ATU-C swaps a bit out of bin, it decreases its b(i). Thus, the bins constellation is smaller. which increases its margin. When the ATU-C swaps a bit into a bin, it increases its b(i). Thus, the bins constellation is larger, which decreases its margin. If this value is too small, then the ATU-C may frequently toggle the bit allocation on bins, and if impulse noise is present, this can cause errors. If this value is too large, then the ATU-C may not identify an adequate number of bins that it can swap bits 'to', thereby decreasing the chances for the ATU-C to equalize the margin across all the bins. Unequalized margin across all the bins translates into poor error performance.

DmtFecSizeOne of the three parameters that affects FEC operation; the number of FEC redundancy bytes per Reed-Solomon codeword. The codeword size also affects FEC operation. The interleave depth also affects FEC operation on an interleaved channel (see the ADSL-LINE-MIB, specifically adslAtucChanConfMaxInterleaveDelay and adslAturChanConfMaxInterleaveDelay).Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. draft-ietf-adslmib-adsllinemib-04, Definitions of Managed Objects for ADSL Lines. (0 | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16) · Integer32 · bytes

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the initial number of FEC redundancy bytes the ATU-R appends to upstream frames transmitted over the fast channel during the training sequence. The ATU-C can force the ATU-R to fallback from this value depending on the aggregate data rate achieved during training. It is desirable to choose a large FEC size, thereby increasing the chance of being able to correct errors in the data delivered by a frame. However, additional FEC redundancy bytes increases frame overhead, and thus frame latency.

DmtFecSizeOne of the three parameters that affects FEC operation; the number of FEC redundancy bytes per Reed-Solomon codeword. The codeword size also affects FEC operation. The interleave depth also affects FEC operation on an interleaved channel (see the ADSL-LINE-MIB, specifically adslAtucChanConfMaxInterleaveDelay and adslAturChanConfMaxInterleaveDelay).Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. draft-ietf-adslmib-adsllinemib-04, Definitions of Managed Objects for ADSL Lines. (0 | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16) · Integer32 · bytes

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the initial number of FEC redundancy bytes the ATU-R appends to upstream frames transmitted over the interleaved channel during the training sequence. The ATU-C can force the ATU-R to fallback from this value depending on the aggregate data rate achieved during training. It is desirable to choose a large FEC size, thereby increasing the chance of being able to correct errors in the data delivered by a frame. However, additional FEC redundancy bytes increases frame overhead, and thus frame latency. The value of this object must be a integral multiple of the value of cAdslAturDmtConfCodewordSize.

DmtCodewordSizeOne of the three parameters that affects FEC operation; the number of ADSL symbols per FEC codeword. The FEC size also affects FEC operation. The interleave depth also affects FEC operation on an interleaved channel (see the ADSL-LINE-MIB, specifically adslAtucChanConfMaxInterleaveDelay and adslAturChanConfMaxInterleaveDelay). The following constraints apply: - This value is always '1' when performing the FEC operation on a fast buffer. - When performing the FEC operation on an interleaved buffer, the specification does not require a codeword size greater than '1' when the interleave depth is set to '1'. - if DmtCodeWordSize is positive, it represents the actual number of symbols per codeword. If DmtCodeWordSize is negative, it represents the exponent value in a power of 2. For example, if DmtCodeWordSize is equal to -1, then the number of symbols per codeword would be equal to 2^^-1 = 1/2.Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces. RFC 2662 - Definitions of Managed Objects for the ADSL Lines. G. Bathrick,. Ly. August 1999. (-1 | 1 | 2 | 4 | 8 | 16) · Integer32 · symbols

Reference: ANSI T1.413-1998 Issue 2, Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interfaces.

This object specifies the number of symbols per codeword being used by the ATU-R for upstream messages on an interleaved channel during the training sequence. The ATU-C can force the ATU-R to fallback from this value based on the aggregate data rate achieved during training. It is desirable to choose a large codeword size to minimize overhead. However, increasing the codeword size increases the possibility of not being able to correct errors in the data delivered by a frame.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to implement min-rate blocking on DMT interfaces that support this option.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to implement dual bitmap tables for Annex C compliant DMT interfaces. The bin data for the DSL interface will appear in cAdslAturDmtBinTable and cAdslAtucDmtBinTable.

Integer32

Reference: RFC 2662 - Definitions of Managed Objects for the ADSL Lines. G. Bathrick,. Ly. August 1999.

This object specifies a bit rate threshold. When the following condition is met, the agent generates an adslAtucRateChangeTrap: ( I + F ) < cAdslAtucDmtThreshRateFallback where I = adslAtucChanCurrTxRate for ATU-C's interleave channel F = adslAtucChanCurrTxRate for ATU-C's fast channel Setting this value to '0' prevents the agent from generating an adslAtucRateChangeTrap due to rate fallback.

Integer32

Reference: RFC 2662 - Definitions of Managed Objects for the ADSL Lines. G. Bathrick,. Ly. August 1999.

This object specifies a bit rate threshold. When the following condition is met, the agent generate an adslAturRateChangeTrap: ( I + F ) < cAdslAturDmtThreshRatefallback where I = adslAturChanCurrTxRate for ATU-R's interleave channel F = adslAturChanCurrTxRate for ATU-R's fast channel Setting this value to '0' prevents the agent from generating an adslAtucRateChangeTrap due to rate fallback.

Unsigned32 (1..5)

This index is used to step through all of the bin tables on a DSL interface.

Unsigned32 (1..256)

A unique value, greater than zero, for each dmt bin on the interface specified in cAdslDmtBinIfNumber It is recommended that values be assigned contiguously starting from 1.

Unsigned32 (0..15) · bits/Hz

This stores the number of bits allotted per Hertz in this bin. For example, a value of 15 would indicate that this slot is tranmitting at a physical rate of 64kbits/sec.

Unsigned32 (0..400) · tenth dB

This field has the transmitter gain for this bin and is stored in 0.01 dB increments.

Unsigned32 (0..255)

This field indicates the 4.3125 kHz band of downstream DSL line spectrum occupied by a bin. For example, a value of 3 would indicate the band from 12.9375 to 17.25 kHz of the spectrum.

Unsigned32 (1..5)

This index is used to step through all of the bin tables on a DSL interface.

Unsigned32 (1..256)

A unique value, greater than zero, for each dmt bin on the interface specified in cAdslDmtBinIfNumber It is recommended that values be assigned contiguously starting from 1.

Unsigned32 (0..15) · bits/Hz

This stores the number of bits allotted per Hertz in this bin. For example, a value of 15 indicates that this slot is transmitting at a physical rate of 64 Kbits.

Unsigned32 (0..400) · hundredth dB

This field has the transmitter gain for this bin and is stored in 0.01 dB increments.

Unsigned32 (0..255)

This field indicates the 4.3125 kHz band of upstream DSL line spectrum occupied by a bin. For example, a value of 3 would indicate the band from 12.9375 to 17.25 kHz of the spectrum.