SHE-XDSL-MIB: View SNMP OID List / Download MIB

The MIB module defining objects for the management of a pair of xDSL transceivers at each end of the xDSL line. Each such line has an entry in an ifTable with ifType 97 (VDSL) or 230 (ADSL2) An agent may reside at either end of the xDSL line. However, the MIB is designed to require no management communication between them beyond that inherent in the low-level xDSL line protocol. The agent may monitor and control this protocol for its needs. xDSL lines may support optional more then one channel. Naming Conventions: Xtuc -- transceiver at near (Central) end of line Xtur -- transceiver at Remote end of line Xtu -- One of either Xtuc or Xtur Curr -- Current Prev -- Previous Atn -- Attenuation ES -- Errored Second. SES -- Severely Errored Second UAS -- Unavailable Second LCS -- Line Code Specific Lof -- Loss of Frame Lol -- Loss of Link Los -- Loss of Signal Lpr -- Loss of Power xxxs -- Sum of Seconds in which xxx has occured (e.g., xxx = Lof, Los, Lpr, Lol) Max -- Maximum Mgn -- Margin Min -- Minimum Psd -- Power Spectral Density Snr -- Signal to Noise Ratio Tx -- Transmit Blks -- Blocks

This table includes common attributes describing both ends of the line. It is required for all XDSL physical interfaces. XDSL physical interfaces are those ifEntries where ifType is equal to xdsl(97).

An entry in the xdslLineTable.

This object indicates parameter that allows actions on a per line basis. These actions include abort, startup, and tests. Valid values: startup(0) -> normal operation (default) spectrumReverb(5) -> Testmode spectrumMedley(26) -> Testmode showTimeLock(39) -> Testmode - This feature can be used for measurement of the PSD. returnLoss(40) -> Testmode.

The value of this object identifies the row in the XDSL Line Configuration Profile Table, xdslLineConfProfileTable, which applies for this XDSL line, and channels if applicable. This object MUST be maintained in a persistent manner.

The value of this object identifies the row in the XDSL Line Alarm Configuration Profile Table, xdslLineAlarmConfProfileTable, which applies to this XDSL line, and channels if applicable. This object MUST be maintained in a persistent manner.

The capability of co-side. Be aware that multiple bits could be set! Each bit set to 1 means, that the corresponding standard is supported.

The capability of remote-side. Only available if line has trained - otherwise 0. Be aware that multiple bits could be set! Each bit set to 1 means, that the corresponding standart is supported.

The current used capability of the line. Only available if line has trained - otherwise 0. Only one bit could be set and means that the corresponding standard is supported.

Loop diagnostics mode forced (LDSF). Defines whether the line should be forced into the loop diagnostics mode by the near-end xTU on this line or only be responsive to loop diagnostics initiated by the far-end xTU.

The status of the recent occasion the Loop diagnostics mode forced (LDSF) was issued for the associated line. Possible values are: none (1) - The default value in case LDSF was never requested for the associated line. success (2) - The recent command completed successfully. inProgress (3) - The Loop Diagnostics process is in progress. unsupported (4) - The NE or the line card doesn't support LDSF. cannotRun (5) - The NE cannot initiate the command, due to a non specific reason. aborted (6) - The Loop Diagnostics process aborted. failed (7) - The Loop Diagnostics process failed. illegalMode (8) - The NE cannot initiate the command, due to the specific mode of the relevant line. adminUp (9) - The NE cannot initiate the command, as the relevant line is administratively 'Up'. noResources (11)- The NE cannot initiate the command, due to lack of internal memory resources.

Specifies the name of the used custom psd mask profile from sheXdslPsdMaskProfileTable for DOWNSTREAM direction. If not used the value is a empty string(default). The management system should also set a empty string if no profile is used and all existing profiles should be deleted.Only profiles with profile usage set to downstream could be configured here. IMPORTANT NOTE: SHE release since R1.42 will only support psdmask profile, notch profile and rfi-band configuration directly via linetable. The NE will support a automatic convertion of R1.41 databases. This convertion will perform the following steps: 1. Copy psdmask, rfi-band and notchprofile configuration for all used lineprofiles to all corresponding linetableentrys (only if usedflag's for psdmask or notch profile are set in lineprofile). 2. Reset usedflags and profilenames (empty string) in all lineprofiles to default value! If usedflag's or psdmask or notchprofile parameter will be set by TMN during extention profile modification, the NE will ignore these settings and return always the default values. No reject message will be send!

Specifies the name of the used custom psd mask profile from sheXdslPsdMaskProfileTable for UPSTREAM direction. If not used the value is a empty string(default). The management system should also set a empty string if no profile is used and all existing profiles should be deleted.Only profiles with profile usage set to upstream could be configured here. IMPORTANT NOTE: SHE release since R1.42 will only support psdmask profile, notch profile and rfi-band configuration directly via linetable. The NE will support a automatic convertion of R1.41 databases. This convertion will perform the following steps: 1. Copy psdmask, rfi-band and notchprofile configuration for all used lineprofiles to all corresponding linetableentrys (only if usedflag's for psdmask or notch profile are set in lineprofile). 2. Reset usedflags and profilenames (empty string) in all lineprofiles to default value! If usedflag's or psdmask or notchprofile parameter will be set by TMN during extention profile modification, the NE will ignore these settings and return always the default values. No reject message will be send!

Specifies the name of the used custom notch profile from sheXdslCustomNotchProfileTable if usage of custom notch is enabled. If not used or no NotchProfile exist in NE the value is a empty string(default). The management system should also set a empty string if no profile is used and all existing profiles should be deleted. Be aware, that the NE can handle only 16 notches per line at time. If all free defined notches in a customNotchProfile should be used, it is not allowed to enable additional predefined notches from the RFIBandMask for this line!! If such notches are already activ, it is not possible to assign a notchprofile to such a line if the total amount of notches (RFIBand's + UsedNotches in profile) is greater then 16. IMPORTANT NOTE: SHE release since R1.42 NE will only support psdmask profile, notch profile and rfi-band configuration directly via linetable. The NE will support a automatic convertion of R1.41 databases. This convertion will perform the following steps: 1. Copy psdmask, rfi-band and notchprofile configuration for all used lineprofiles to all corresponding linetableentrys (only if usedflag's for psdmask or notch profile are set in lineprofile). 2. Reset usedflags and profilenames (empty string) in all lineprofiles to default value! If usedflag's or psdmask or notchprofile parameter will be set by TMN during extention profile modification, the NE will ignore these settings and return always the default values. No reject message will be send!

The transmit power spectral density mask code, used to avoid interference with HAM (Handheld Amateur Radio) radio bands by introducing power control (notching) in one or more of these bands. Amateur radio band notching is defined in the DSL spectrum as follows: Start Frequency Stop Frequency ---------------- ------------------------------ 1. 1800 kHz 2000 kHz 2. 3500 kHz 3800 kHz 3. 7000 kHz 7200 kHz 4. 10100 kHz 10150 kHz 5. 14000 kHz 14350 kHz GMDSS - Frequency's: 6. 2173 kHz 2191 kHz 7. 4200 kHz 4215 kHz 8. 6300 kHz 6320 kHz This standard notches representing the following subcarrier-indices if a spacing of 4.3125 kHz is used (VDSL2 profiles 8A .. 17A or ADSL): Start-Carrier Stop-Carrier ------------ ----------------- 1. 417 464 2. 811 881 3. 1623 1670 4. 2342 2354 5. 3246 3328 6. 504 508 7. 974 977 8. 1461 1466 VDSL2 Profile 30A use a different spacing of 8.625 kHz: Start-Carrier Stop-Carrier ------------- ----------------- 1. 209 232 2. 406 441 3. 812 835 4. 1171 1177 5. 1623 1664 6. 252 254 7. 487 489 8. 730 733 Notching for each standard band can be enabled or disabled via the bit mask. Be aware, that the NE can handle only 16 notches per line at time. If all free defined notches in a customNotchProfile should be used, it is not allowed to enable additional predefined notches from the RFIBandMask!! If such notches are already activ, it is not possible to assign a notchprofile to such a line if the total amount of notches (RFIBand's + UsedNotches) is greater then 16.

Shows the preferred used standard compliance. see g.997.1 clause 7.3.1.1.1 (ATSE). The following bits are possible: g9921AdslPotsNonOverlapped(2), g9921AdslIsdnNonOverlapped(4), g9923Adsl2PotsNonOverlapped(18), g9923Adsl2IsdnNonOverlapped(20), g9923ADMAdsl2NonOverlappedAnnexJ(30), g9923ReachExtAdsl2PotsNonOverlappedM1(34), g9923ReachExtAdsl2PotsNonOverlappedM2(35), g9923ExtUpAdsl2PotsNonOverlapped(38), g9925Adsl2PlusPotsNonOverlapped(40), g9925Adsl2PlusIsdnNonOverlapped(42), g9925ADMAdsl2PlusNonOverlappedAnnexJ(48), g9925ExtUpAdsl2PlusPotsNonOverlapped(50), g9932Vdsl2NonOverlappedRegionB(57), The configuration is done via LineProfile.

Estimated Upstream Power Backoff Electrical Loop Length (UPBOKLE). This parameter contains the estimated electrical loop length expressed in dB at 1MHz, kle. This is the final electrical loop length that should be sent from the xTU-C to xTU-R if the loop length is not forced by the CO-MIB (see 12.2.4.2.1.2/G.993.2). The value shall be coded in the range 0 (coded as 0) to 128 dB (coded as 1280) in steps of 0.1 dB. The corresponding values line length to the damping in dB is about 10 dB per 500 m. A value of 0x8000 (32768) means that the current value is not available.

This object indicates the action that forces a change in the line state of power management. (Not available for ADSL, G992.1) The following changes are valid: pmsfL0ToL2StateForce(1) -> Force the line to transition from L0 full power to L2 low power state. This transition requires the entry into L2 mode. This is an out-of-service test value for triggering the L2 mode. Only valid if line run's L0 mode already. pmsfL2ToL0StateForce(3) -> Force the line to transition from L2 low power to L0 full power state. This transition requires the entry into L0 mode. This stops the out-of-service test and triggering the line to go back to normal operation. Only valid if line run's L2 mode already. The transitions pmsfL3ToL0StateForce (unlock) and pmsfL3StateForce (lock) should always be done via ifAdminState setting. This is valid only for Recommendations supporting L2 mode otherwise don't care!

This parameter indicates that the framer settings of the bearer shall be selected such that the impulse noise protection computed according to the formula specified in the relevant Recommendation is greater than or equal to the minimal impulse noise protection requirement. This flag shall have the same value for all the bearers of one line in the same direction. This parameter specifies the value for downstream direction.

This parameter indicates that the framer settings of the bearer shall be selected such that the impulse noise protection computed according to the formula specified in the relevant Recommendation is greater than or equal to the minimal impulse noise protection requirement. This flag shall have the same value for all the bearers of one line in the same direction. This parameter specifies the value for upstream direction.

The value of this object identifies the row in the XDSL channel configuration Profile Table, (sheXdslChannelProfileTable) that applies to DSL bearer channel #1. The channel profile name specified here must match the name of an existing row in the sheXdslChannelProfileTable table.

Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #1 when performing rate adaptation on Downstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - sheXdslLineChan1RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels on Downstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.

Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #1 when performing rate adaptation on Upstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - sheXdslConfChan1RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels on Upstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100 %.

The value of this object identifies the row in the XDSL channel configuration Profile Table, (sheXdslChannelProfileTable) that applies to DSL bearer channel #2. If the channel is unused, then the object is set to a zero length string.

Configure, if the counted 15Min history performance entrys should be stored for that line. Remark: Be aware, that there is a NE restriction to store performance entrys for a maximum number of 450 lines at the same time. Support with SHE R2.7.

Configure, if the counted 1Day history performance entrys should be stored for that line. Remark: Be aware, that there is a NE restriction to store performance entrys for a maximum number of 450 lines at the same time. Support with SHE R2.7.

If config violation check was enabled, this parameter will show the type of detected violations. It is DSL firmware depended if the line support this status information. The NE will set featureNotSupported(0) BIT to 1 in case the status information is not available for this line at all. Valid information: featureNotSupported(0) -> BIT is 1 -> the ConfigViolationCheck feature is not supported by this line checkMinINP(1) -> BIT is 1 -> the minINP-Check has detected a violation Note: New parameter with R2.8 maintenance.

modifyXdslLineEntry: sheXdslLineControlIndex sheXdslLineControlGsAction sheXdslLineControlConfProfile modifyXdslLineAlarmConfProfileEntry: sheXdslLineControlIndex sheXdslLineControlAlarmConfProfile modifyXdslLineDeltState: sheXdslLineControlIndex sheXdslLineControlLdsf setXdslLineDownPsdMaskProfileEntry: sheXdslLineControlIndex sheXdslLineControlCustomDownPsdMaskProfile setXdslLineUpPsdMaskProfileEntry: sheXdslLineControlIndex sheXdslLineControlCustomUpPsdMaskProfile setXdslLineNotchConfiguration: sheXdslLineControlIndex sheXdslLineControlCustomNotchProfile sheXdslLineControlRfiBandMask # New in SHE R2.6 modifyXdslLinePMSFState: sheXdslLineControlIndex sheXdslLineControlPMSF setXdslLineForceInpConfiguration sheXdslLineControlIndex sheXdslLineControlForceINPDs sheXdslLineControlForceINPUs setXdslLineChannelProfileConfiguration sheXdslLineControlIndex sheXdslLineControlChan1ConfProfile sheXdslLineControlChan1RaRatioDs sheXdslLineControlChan1RaRatioUs sheXdslLineControlChan2ConfProfile # New in SHE R2.7 modifyXdslLinePerformanceHistory: sheXdslLineControlIndex sheXdslLineControlPerformance15MinHistoryEnabled sheXdslLineControlPerformance1DayHistoryEnabled

IfIndex of the configured xdsl-interface.

The status of a user command.

The maximum wait time for the manager for a long running user command.

The result of the last user command.

The time stamp of the last command (end of command).

look at table

The value of this object identifies the row in the XDSL Line Configuration Profile Table, which applies for this XDSL line, and channels if applicable. For the used `dynamic' mode, in the case which the configuration profile has not been set, the value will be set to `DEFVAL'.

The value of this object identifies the row in the XDSL Line Alarm Configuration Profile Table, which applies to this XDSL line, and channels if applicable. For the used `dynamic' mode, in the case which the alarm profile has not been set, the value will be set to `DEFVAL'.

look at table.

look at table

look at table

look at table

look at table

look at table The transitions pmsfL3ToL0StateForce (unlock) and pmsfL3StateForce (lock) should always be done via ifAdminState setting.

look at table

look at table

The channel profile name specified here must match the name of an existing row in the sheXdslChannelProfileTable table.

Look at table.

Look at table

The channel profile name specified here must match the name of an existing row in the sheXdslChannelProfileTable table or should be an emty string if no channel 2 is used.

Configure, if the counted 15Min history performance entrys should be stored for that line. Remark: Be aware, that there is a NE restriction to store performance entrys for a maximum number of 450 lines at the same time. Support with SHE R2.7.

Configure, if the counted 1Day history performance entrys should be stored for that line. Remark: Be aware, that there is a NE restriction to store performance entrys for a maximum number of 450 lines at the same time. Support with SHE R2.7.

This table provides one row for each xtu. Each row contains the Physical Layer Parameters table for that xtu. XDSL physical interfaces are those ifEntries where ifType is equal to vdsl(97) or ADSL2 (230).

An entry in the xdslPhysTable.

Identifies whether the transceiver is the Xtuc or Xtur.

The vendor specific string that identifies the vendor equipment. The serial number consists of up to 32 ascii characters. Note: The content of this attribute is not longer applicable for xtuc-side.

The vendor ID code is a copy of the binary vendor identification field expressed as readable characters in hexadecimal notation. This field contain the g994.1 Vendor ID.

The vendor specific version number sent by this xtu as part of the initialization messages. It is a copy of the binary version number field expressed as readable characters in hexadecimal notation. Note: The content of this attribute is not longer applicable for xtuc-side.

Indicates current state of the xtu line. This is a bit-map of possible conditions. The various bit positions are: 0 noDefect There are no defects on the line. 1 lossOfFraming xtu failure due to not receiving a valid frame. 2 lossOfSignal xtu failure due to not receiving signal. 3 lossOfPower xtu failure due to loss of power. 4 lossOfSignalQuality Loss of Signal Quality is declared when the Noise Margin falls below the Minimum Noise Margin, or the bit-error-rate exceeds the configured BER value. 5 lossOfLink xtu failure due to inability to link with peer xtu. Set whenever the transceiver is in the 'Warm Start' state. 6 dataInitFailure xtu failure during initialization due to bit errors corrupting startup exchange data. That will map to 'Configuration error' (1) failure from G997.1 chapter 7.5.1.6. 7 configInitFailure xtu failure during initialization due to peer xtu not able to support requested configuration. That will map to 'Configuration not feasible on the line' (2) failure from G997.1 chapter 7.5.1.6. 8 protocolInitFailure xtu failure during initialization due to incompatible protocol used by the peer xtu. That will map to 'communication problem' (3) failure from G997.1 chapter 7.5.1.6. 9 noPeerVtuPresent xtu failure during initialization due to no activation sequence detected from peer xtu. That will map to 'No peer xTU detected' (4) failure from G997.1 chapter 7.5.1.6. All failures with no single mapping to G997.1 parameters should be understand as a more detailed map to 'Any other or unknown Initialization Failure cause' (5) from G997.1 chapter 7.5.1.6. Only xtu-c side can always deliever trusted information, because most failures will force a line interruption. This is intended to supplement ifOperStatus.

Measured total output power transmitted by this xTU (ACTATP). This is the measurement that was reported during the last activation sequence. Special values of -512 or -311 represent, that the transmit power is out of range.

Indicates the maximum currently attainable net data rate in steps of 1000 bits/second by the xtu. This value will be equal to or greater than xdslPhysCurrDataRate. Note: 1 kbps = 1000 bps.

Indicates the current net data rate in steps of 1000 bits/second by the xtu. This value will be less than or equal to xdslPhysCurrAttainableDataRate. Note: 1 kbps = 1000 bps.

Actual standard used for the connection. Only one bit could be set and means, that the corresponding standard is supported.

The net data rate at the time of the last xdslRateChangeTrap event. It is also set at initialization to prevent a trap being sent.

The vendor ID code is a copy of the binary vendor identification field expressed as readable characters in hexadecimal notation. This field contain the system vendor ID. Note: The content of this attribute is not longer applicable for xtuc-side.

Indicates current operational state of the xtu line. Values include idle, handshake, training, etc. Only valid for xtu-C side. Following states are supported: DSL_OPERSTATE_NOT_INITIALIZED = 0x00000000, DSL_OPERSTATE_EXCEPTION, = 0x00000001, DSL_OPERSTATE_IDLE_REQUEST = 0x000000FF, DSL_OPERSTATE_IDLE = 0x00000100, DSL_OPERSTATE_SILENT_REQUEST = 0x000001FF, DSL_OPERSTATE_SILENT = 0x00000200, DSL_OPERSTATE_HANDSHAKE = 0x00000300, DSL_OPERSTATE_FULL_INIT = 0x00000380, DSL_OPERSTATE_DISCOVERY = 0x00000400, DSL_OPERSTATE_TRAINING = 0x00000500, DSL_OPERSTATE_ANALYSIS = 0x00000600, DSL_OPERSTATE_EXCHANGE = 0x00000700, DSL_OPERSTATE_SHOWTIME_NO_SYNC = 0x00000800, DSL_OPERSTATE_SHOWTIME_TC_SYNC = 0x00000801, DSL_OPERSTATE_FASTRETRAIN = 0x00000900, DSL_OPERSTATE_LOWPOWER_L2 = 0x00000A00, DSL_OPERSTATE_LOOP_ACTIVE = 0x00000B00, DSL_OPERSTATE_LOOP_DATA_EXCHANGE = 0x00000B10, DSL_OPERSTATE_LOOP_COMPLETE = 0x00000C00, DSL_OPERSTATE_RESYNC = 0x00000D00, DSL_OPERSTATE_TEST = 0x01000000, DSL_OPERSTATE_LOWPOWER_L3 = 0x02000000, DSL_OPERSTATE_UNKNOWN = 0x03000000

Line Power Management State. Only valid for XTUC - side. XTUR will always show identical values like XTUC. Valid states: syncL0(0) - full transmission pwrDownL1(1) - reduced data rate (G992.2 only) pwrDownL2(2) - reduced data rate (G992.3, G992.4 and G992.5) noPwrL3(3) - no power transmitted

This parameter represents the last successful transmitted initialization state in the correspondig direction in the last full initialization performed on the line. Initialization states are defined in the individual xDSL Recommendations and are counted from 0 (if G.994.1 is used) or 1 (if G.994.1 is not used) up to showtime. This parameter must be interpreted along with the xDSL Transmission System. NOTE: State 0 .. 11 are identical for central office (xtuc) and remote side (xtur). State 12 .. 32 have different meanings on central office and remote side. Example: cQuiet4rReverb1(12) -> xtuc has state cQuiet4 and xtur has state rReverb1. State notAvailable(255) will be reported if the information is not available on IU.

This parameter is the average transmit PSD over the used subcarriers (subcarriers to which user data are allocated) for the corresponding direction (xTU-C for downstream and xTU-R for upstream) at the U-C reference point, at the instant of measurement. The PSD level ranges from -90 dBm/Hz (coded as -900) to 0 dBm/Hz (coded as 0) with 0.1 dB steps. A special value (coded as -901) indicates the parameter is out of range to be represented. NOTE: The actual power spectrum density is the sum (in dB) of the REFPSD and RMSGI. See 8.5.1/G.992.3. Note: Only valid for ADSL2 and ADSL2+ mode.

This parameter defines the xTU self-test result. It is coded as a 32-bit integer. The most significant octet of the self-test result is 00hex if the self-test passed and 01hex if the self-test failed. The interpretation of the other octets is vendor discretionary and can be interpreted in combination with G.994.1 and system Vendor IDs.

This table provides one row for each xtu channel.

An entry in the xdslChanTable. Indexed by ifIndex - PhysSide - ChanNum.

Interleave Delay for this channel. Interleave delay applies only to the interleave (slow) channel and defines the mapping (relative spacing) between subsequent input bytes at the interleaver input and their placement in the bit stream at the interleaver output. Larger numbers provide greater separation between consecutive input bytes in the output bit stream allowing for improved impulse noise immunity at the expense of payload latency. In the case where the channel type is fast, return a value of zero.

Actual CRC error count.

Actual transmit data rate on this channel. Note: 1 kbps = 1000 bps.

This parameter reports the actual impulse noise protection (INP) on the bearer channel in the L0 state. In the L1 or L2 state, the parameter contains the INP in the previous L0 state. The value is coded in fractions of DMT symbols with a granularity of 0.1 symbols. The range is from 0 to 25.4. A special value 255 indicates an ACTINP higher than 25.4.

Actual Forward Error Correction (FEC).

ncd or lcd failure status. This parameter is only valid for lines running ADSL mode.

Explains the number of used channel entry! (1) channel 1 (2) channel 2 (if exist)

The HEC_violation_count performance parameter is a count of the number of occurrences of a HEC anomaly in the ATM Data Path.

This table provides one row for each XDSL physical interface. XDSL physical interfaces are those ifEntries where ifType is equal to xdsl(97).

An entry in the xdslPerfDataTable.

Valid Intervals per definition found in HC-PerfHist-TC-MIB.

Invalid Intervals per definition found in HC-PerfHist-TC-MIB.

Count of seconds since the unit was last reset that there was Loss of Framing.

Count of seconds since the unit was last reset that there was Loss of Signal.

Count of seconds since the unit was last reset that there was Loss of Power.

Count of seconds since the unit was last reset that there was Loss of Link.

Count of Errored Seconds since the unit was last reset. An Errored Second is a one-second interval containing one or more CRC anomalies, or one or more LOS or LOF defects.

Count of Severely Errored Seconds since the unit was last reset. An SES is declared if, during a 1-second interval, there are 18 or more CRC-8 anomalies in one or more of the received bearer channels, or one or more LOS defects, or one or more SEF defects, or one or more LPR defects.

Count of Unavailable Seconds since the unit was last reset. The xDSL line becomes unavailable at the onset of 10 contiguous SES-Ls. These 10 SES-Ls shall be included in unavailable time. Once unavailable, the xDSL line becomes available at the onset of 10 contiguous seconds with no SES-Ls.

Count of the line initialization attempts since the unit was last reset. This count includes both successful and failed attempts. Remark: This parameter is shown for near and far end side because of table index design. Only the reported value for xtuc side is requested by the standard and should be used.

Total elapsed seconds in this interval.

Count of seconds during this interval that there was Loss of Framing.

Count of seconds during this interval that there was Loss of Signal.

Count of seconds during this interval that there was Loss of Power.

Count of seconds during this interval that there was Loss of Link.

Count of Errored Seconds during this interval. An Errored Second is a one-second interval containing one or more CRC anomalies, or one or more LOS or LOF defects.

Count of Severely Errored Seconds during this interval.

Count of Unavailable Seconds during this interval.

Count of the line initialization attempts during this interval. This count includes both successful and failed attempts. Remark: This parameter is shown for near and far end side because of table index design. Only the reported value for xtuc side is requested by the standard and should be used.

Valid Intervals per definition found in HC-PerfHist-TC-MIB.

Invalid Intervals per definition found in HC-PerfHist-TC-MIB.

Number of seconds that have elapsed since the beginning of the current 1-day interval.

Count of Loss of Framing (LOF) Seconds since the beginning of the current 1-day interval.

Count of Loss of Signal (LOS) Seconds since the beginning of the current 1-day interval.

Count of Loss of Power (LPR) Seconds since the beginning of the current 1-day interval.

Count of Loss of Link (LOL) Seconds since the beginning of the current 1-day interval.

Count of Errored Seconds (ES) since the beginning of the current 1-day interval.

Count of Severely Errored Seconds (SES) since the beginning of the current 1-day interval.

Count of Unavailable Seconds (UAS) since the beginning of the current 1-day interval.

Count of the line initialization attempts since the beginning of the current 1-day interval. This count includes both successful and failed attempts. Remark: This parameter is shown for near and far end side because of table index design. Only the reported value for xtuc side is requested by the standard and should be used.

This table provides one row for each xtu performance data collection interval. XDSL physical interfaces are those ifEntries where ifType is equal to xdsl(97) or adsl2 (230).

An entry in the xdslPerfIntervalTable.

Performance Data Interval number 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2 to 96 are optional.

This variable indicates if the data for this interval is valid.

This variable indicates the time of storing this interval.

Count of seconds in the interval when there was Loss of Framing.

Count of seconds in the interval when there was Loss of Signal.

Count of seconds in the interval when there was Loss of Power.

Count of seconds in the interval when there was Loss of Link.

Count of Errored Seconds (ES) in the interval. An Errored Second is a one-second interval containing one or more CRC anomalies, one or more LOS or LOF defects.

Count of Severely Errored Seconds in the interval.

Count of Unavailable Seconds in the interval.

Count of the line initialization attempts during this interval. This count includes both successful and failed attempts. Remark: This parameter is shown for near and far end side because of table index design. Only the reported value for xtuc side is requested by the standard and should be used.

This table provides one row for each XDSL performance data collection interval. This table contains live data from equipment. As such, it is NOT persistent.

An entry in the xdslPerf1DayIntervalTable.

History Data Interval number. Interval 1 is the most recent previous day; interval 7 is 7 days ago. Intervals 2 to 7 are optional.

The amount of time in the 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason.

Count of Loss of Frame (LOF) Seconds during the 1-day interval.

Count of Loss of Signal (LOS) Seconds during the 1-day interval.

Count of Loss of Power (LPR) Seconds during the 1-day interval.

Count of Loss of Link (LOL) Seconds during the 1-day interval.

Count of Errored Seconds (ES) during the 1-day interval.

Count of Severely Errored Seconds (SES) during the 1-day.

Count of Unavailable Seconds (UAS) during the 1-day interval.

Count of the line initialization attempts during the 1-day interval. This count includes both successful and failed attempts. Remark: This parameter is shown for near and far end side because of table index design. Only the reported value for xtuc side is requested by the standard and should be used.

This variable indicates the time of storing this interval.

This table provides one row for each xtu channel.

An entry in the xdslChanPerfDataTable. Indexed by ifIndex - PhysSide - ChanNum.

Valid Intervals per definition found in HC-PerfHist-TC-MIB.

Invalid Intervals per definition found in HC-PerfHist-TC-MIB.

This parameter is a count of FEC anomalies (the number of corrected code words) occurring in the bearer channel during the accumulation period.

That CV-P performance parameter is a count of the number of occurrences of a cv-n anomaly in the PTM Data Path.

Total elapsed seconds in this interval.

This parameter is a count of FEC anomalies (the number of corrected code words) occurring in the bearer channel during the accumulation period.

That CV-P performance parameter is a count of the number of occurrences of a cv-n anomaly in the PTM Data Path.

Valid Intervals per definition found in HC-PerfHist-TC-MIB.

Invalid Intervals per definition found in HC-PerfHist-TC-MIB.

Number of seconds that have elapsed since the beginning of the current 1-day interval.

This parameter is a count of FEC anomalies (the number of corrected code words) occurring in the bearer channel during the accumulation period.

That CV-P performance parameter is a count of the number of occurrences of a cv-n anomaly in the PTM Data Path.

The CRC-P performance parameter is a count of the number of occurrences of a CRC-n anomaly in the PTM Data Path.

The HEC_violation_count performance parameter is a count of the number of occurrences of a HEC anomaly in the ATM Data Path.

The delineated_total_cell_count performance parameter is a count of the total number of cells passed through the cell delineation process and HEC function operating on the ATM Data Path while in the SYNC state.

The User_total_cell_count performance parameter is a count of the total number of cells in the ATM Data Path.

The idle_bit_error_count performance parameter is a count of the number of bit errors in the idle cell payload received in the ATM Data Path.

The CRC-P performance parameter is a count of the number of occurrences of a CRC-n anomaly in the PTM Data Path.

The HEC_violation_count performance parameter is a count of the number of occurrences of a HEC anomaly in the ATM Data Path.

The delineated_total_cell_count performance parameter is a count of the total number of cells passed through the cell delineation process and HEC function operating on the ATM Data Path while in the SYNC state.

The User_total_cell_count performance parameter is a count of the total number of cells in the ATM Data Path.

The idle_bit_error_count performance parameter is a count of the number of bit errors in the idle cell payload received in the ATM Data Path.

The CRC-P performance parameter is a count of the number of occurrences of a CRC-n anomaly in the PTM Data Path.

The HEC_violation_count performance parameter is a count of the number of occurrences of a HEC anomaly in the ATM Data Path.

The delineated_total_cell_count performance parameter is a count of the total number of cells passed through the cell delineation process and HEC function operating on the ATM Data Path while in the SYNC state.

The User_total_cell_count performance parameter is a count of the total number of cells in the ATM Data Path.

The idle_bit_error_count performance parameter is a count of the number of bit errors in the idle cell payload received in the ATM Data Path.

This table provides one row for each xtu channel data collection interval. This table contains live data from equipment. As such, it is NOT persistent.

An entry in the xdslChanIntervalTable. Indexed by ifIndex - PhysSide - ChanNum - IntervalNumber.

Performance Data Interval number 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2 to 96 are optional.

This variable indicates if the data for this interval is valid.

This variable indicates the time of storing this interval.

This parameter is a count of FEC anomalies (the number of corrected code words) occurring in the bearer channel during the accumulation period.

That CV-P performance parameter is a count of the number of occurrences of a cv-n anomaly in the PTM Data Path.

The CRC-P performance parameter is a count of the number of occurrences of a CRC-n anomaly in the PTM Data Path.

The HEC_violation_count performance parameter is a count of the number of occurrences of a HEC anomaly in the ATM Data Path.

The delineated_total_cell_count performance parameter is a count of the total number of cells passed through the cell delineation process and HEC function operating on the ATM Data Path while in the SYNC state.

The User_total_cell_count performance parameter is a count of the total number of cells in the ATM Data Path.

The idle_bit_error_count performance parameter is a count of the number of bit errors in the idle cell payload received in the ATM Data Path.

This table provides one row for each XDSL performance data collection interval. This table contains live data from equipment. As such, it is NOT persistent.

An entry in the xdslChan1DayIntervalTable. Indexed by ifIndex - PhysSide - ChanNum - IntervalNumber.

History Data Interval number. Interval 1 is the most recent previous day; interval 7 is 7 days ago. Intervals 4 to 7 are optional.

The amount of time in the 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason.

This parameter is a count of FEC anomalies (the number of corrected code words) occurring in the bearer channel during the accumulation period.

That CV-P performance parameter is a count of the number of occurrences of a cv-n anomaly in the PTM Data Path.

The CRC-P performance parameter is a count of the number of occurrences of a CRC-n anomaly in the PTM Data Path.

The HEC_violation_count performance parameter is a count of the number of occurrences of a HEC anomaly in the ATM Data Path.

The delineated_total_cell_count performance parameter is a count of the total number of cells passed through the cell delineation process and HEC function operating on the ATM Data Path while in the SYNC state.

The User_total_cell_count performance parameter is a count of the total number of cells in the ATM Data Path.

The idle_bit_error_count performance parameter is a count of the number of bit errors in the idle cell payload received in the ATM Data Path.

This variable indicates the time of storing this interval.

This table contains information on the XDSL line configuration. One entry in this table reflects a profile defined by a manager which can be used to configure the XDSL line. Entries in this table MUST be maintained in a persistent manner.

Each entry consists of a list of parameters that represents the configuration of a xDSL line. Default profiles will always exist and its parameters will be set to vendor-specific values, unless otherwise specified in this document. Dynamic' profiles are implemented. There are five different default profiles in the NE, which could not be modified! 'DEFVAL' - default profile for interfaces with iftype 'vdsl' (97) for VDSL2 over isdn 'DEFVAL_VDSL2_P' - default profile for interfaces with iftype 'vdsl' (97) for VDSL2 over pots 'DEFVAL_ADSL_A' - default profile for interfaces with iftype 'adsl2' (230) for ADSL2+ over pots (annexA) 'DEFVAL_ADSL_B' - default profile for interfaces with iftype 'adsl2' (230) for ADSL2+ over isdn (annexB) 'DEFVAL_ADSL_J' - default profile for interfaces with iftype 'adsl2' (230) for ADSL2+ ADL (annexJ)

Index of this table.

This object identifies a row in this table. Dynamic' profiles are implemented.The profile name is user specified. There are five different default profiles in the NE, which could not be modified! 'DEFVAL' - default profile for interfaces with iftype 'vdsl' (97) for VDSL2 over isdn 'DEFVAL_VDSL2_P' - default profile for interfaces with iftype 'vdsl' (97) for VDSL2 over pots 'DEFVAL_ADSL_A' - default profile for interfaces with iftype 'adsl2' (230) for ADSL2+ over pots (annexA) 'DEFVAL_ADSL_B' - default profile for interfaces with iftype 'adsl2' (230) for ADSL2+ over isdn (annexB) 'DEFVAL_ADSL_J' - default profile for interfaces with iftype 'adsl2' (230) for ADSL2+ ADL (annexJ) This characters are not allowed: space : o

Specifies the rate selection behavior for the line in the downstream direction. fixed(1) forces the rate to the configured minimum rate adaptAtInit(2) adapts the line based upon line quality. adaptAtRuntime(3) seamless rateadapts during runtime based upon line quality Please note the following rule for margin configuration in case of usage mode (3): sheXdslLineConfDownMinSnrMgn < sheXdslLineConfVturDownshiftSnrMgn < sheXdslLineConfDownTargetSnrMgn < sheXdslLineConfVturUpshiftSnrMgn < sheXdslLineConfDownMaxSnrMgn

Specifies the rate selection behavior for the line in the upstream direction. fixed(1) forces the rate to the configured minimum rate adaptAtInit(2) adapts the line based upon line quality. adaptAtRuntime(3) seamless rateadapts during runtime based upon line quality Please note the following rule for margin configuration in case of usage mode (3): sheXdslLineConfUpMinSnrMgn < sheXdslLineConfVtucDownshiftSnrMgn < sheXdslLineConfUpTargetSnrMgn < sheXdslLineConfVtucUpshiftSnrMgn < sheXdslLineConfUpMaxSnrMgn

Specifies the maximum aggregate downstream power level in the range 0 to 25.5 dBm.

Specifies the maximum aggregate upstream power level in the range 0 to 25.5 dBm.

Maximum received upstream power. The XTU-C will force the XTU-R to reduce transmitted power, if this value will be exceed.

Specifies the maximum downstream Signal/Noise Margin in units of 0.1 dB, for a range of 0 to 31 dB. Rule: MaxSnr > TargetSnr > MinSnr A special value of 0xFFFF is used to indicate that no Maximum Noise Margin limit is to be applied (i.e., the maximum value is infinite).

Specifies the minimum downstream Signal/Noise Margin in units of 0.1dB, for a range of 0 to 31 dB. Rule: MaxSnr > TargetSnr > MinSnr

Specifies the target downstream Signal/Noise Margin in units of 0.1 dB, for a range of 0 to 31 dB. This is the Noise Margin the transceivers must achieve with a BER of sheXdslChannelProfileMaxBerDs or better to successfully complete initialization. Rule: MaxSnr > TargetSnr > MinSnr

Specifies the maximum upstream Signal/Noise Margin in units of 0.1 dB, for a range of 0 to 31 dB. Rule: MaxSnr > TargetSnr > MinSnr A special value of 0xFFFF is used to indicate that no Maximum Noise Margin limit is to be applied (i.e., the maximum value is infinite).

Specifies the minimum upstream Signal/Noise Margin in units of 0.1 dB, for a range of 0 to 31 dB. Rule: MaxSnr > TargetSnr > MinSnr

Specifies the target upstream Signal/Noise Margin in units of 0.1 dB, for a range of 0 to 31 dB. This is the Noise Margin the transceivers must achieve with a BER of sheXdslChannelProfileMaxBerUs or better to successfully complete initialization. Rule: MaxSnr > TargetSnr > MinSnr

Configured Signal/Noise Margin for rate downshift. If the upstream noise margin falls below this level, the modem should attempt to decrease its transmit rate.

Configured Signal/Noise Margin for rate upshift. If the upstream noise margin rises above this level, the modem should attempt to increase its transmit rate.

Minimum time that the current upstream margin is below DownshiftSnrMgn before a downshift occurs.

Minimum time that the current upstream margin is above UpshiftSnrMgn before an upshift occurs.

Configured Signal/Noise Margin for rate downshift. If the downstream noise margin falls below this level, the modem should attempt to decrease its transmit rate.

Configured Signal/Noise Margin for rate upshift. If the downstream noise margin rises above this level, the modem should attempt to increase its transmit rate.

Minimum time that the current downstream margin is below DownshiftSnrMgn before a downshift occurs.

Minimum time that the current downstream margin is above UpshiftSnrMgn before an upshift occurs.

Band plan notation according to G993.2. valid values: bandPlanItuAnnexAM1EU32(0), bandPlanItuAnnexAM9EU64(1), bandPlanItuAnnexAM1ADLU32(2), bandPlanItuAnnexAM9ADLU64(3), bandPlan997M1cA7(4), bandPlan997M1xM8(5), bandPlan997M1xM(6), bandPlan997M2xM8(7), bandPlan997M2xA(8), bandPlan997M2xM(9), bandPlan998M1xA(10), bandPlan998M1xB(11), bandPlan998M1xNUS0(12), bandPlan998M2xA(13), bandPlan998M2xM(14), bandPlan998M2xM17(15), bandPlan998M2xB(16), bandPlan998M2xB17(17), bandPlan998M2xNUS0(18), bandPlan998M2xNUS017(19), bandPlan997E30M2xNUS0(22), bandPlan998E17M2xA(25), bandPlan998E17M2xNUS0(26), bandPlanAnfpCal0Long(27), bandPlanAnfpCal0Medium(28), bandPlanAnfpCal0Short(29), bandPlanAnfpCal0EShort(30), bandPlanItuAnnexAM10EU128(40), bandPlanAnnexAM1Eu32(50), bandPlanAnnexAM2Eu36(51), bandPlanAnnexAM3Eu40(52), bandPlanAnnexAM4Eu44(53), bandPlanAnnexAM5Eu48(54), bandPlanAnnexAM6Eu52(55), bandPlanAnnexAM7Eu56(56), bandPlanAnnexAM8Eu60(57), bandPlanAnnexAM9Eu64(58), bandPlanAnnexAEu128(59), bandPlanAnnexAM1Adlu32(70), bandPlanAnnexAM2Adlu36(71), bandPlanAnnexAM3Adlu40(72), bandPlanAnnexAM4Adlu44(73), bandPlanAnnexAM5Adlu48(74), bandPlanAnnexAM6Adlu52(75), bandPlanAnnexAM7Adlu56(76), bandPlanAnnexAM8Adlu60(77), bandPlanAnnexAM9Adlu64(78), bandPlanAnnexAAdlu128(79), bandPlanAnnexB997M1CA7(100), bandPlanAnnexB997M1XM8(101), bandPlanAnnexB997M1XM(102), bandPlanAnnexB997M2XM8(103), bandPlanAnnexB997M2XA(104), bandPlanAnnexB997M2XM(105), bandPlanAnnexB997HPE17M1NUS0(106), bandPlanAnnexB997HPE30M1NUS0(107), bandPlanAnnexB997E17M2XA(108) -> replace bandPlanAnnexB997E17M2XNUS0 with R2.8 MIB 327 because of G993.2 standard update bandPlanAnnexB997E30M2XNUS0(109), bandPlanAnnexB998M1XA(120), bandPlanAnnexB998M1XB(121), bandPlanAnnexB998M1XNUS0(122), bandPlanAnnexB998M2XA(123), bandPlanAnnexB998M2XM(124), bandPlanAnnexB998M2XB(125), bandPlanAnnexB998M2XNUS0(126), bandPlanAnnexB998E17M2XNUS0(127), bandPlanAnnexB998E17M2XNUS0M(128), bandPlanAnnexB998ADE17M2XNUS0M(129), bandPlanAnnexB998ADE17M2XA(130), bandPlanAnnexB998ADE17M2XB(131), bandPlanAnnexB998E30M2XNUS0(132), bandPlanAnnexB998E30M2XNUS0M(133), bandPlanAnnexB998ADE30M2XNUS0M(134), bandPlanAnnexB998ADE30M2XNUS0A(135), bandPlanAnnexB998ADE17M2XM(140), bandPlanAnnexB998E17M2XA(141) Relevant only for Vdsl2 mode. REMARK: Check MSC documentation for valid band plan and profile combinations!! The bandplan numbers below 50 should not longer be used!

This attribute selects the Vdsl2 profile which should be used for configuration of basic parameters. Profile settings are defined in g993.2. Values to use: dslProfile8A(0), dslProfile8B(1), dslProfile8C(2), dslProfile8D(3), dslProfile12A(4), dslProfile12B(5), dslProfile17A(6), dslProfile30A(7), dslProfile17B(8), Relevant only for Vdsl2 mode. Be aware, that dslProfile30A use a different subcarrier spacing of 8.625 kHz! REMARK: Check MSC documentation for valid band plan and profile combinations!!

preferred used standard compliance. see g.997.1 clause 7.3.1.1.1 (ATSE). The following bits could be set: ansiT1413(0), g9921AdslPotsNonOverlapped(2), g9921AdslIsdnNonOverlapped(4), g9923Adsl2PotsNonOverlapped(18), g9923Adsl2IsdnNonOverlapped(20), g9923ADMAdsl2NonOverlappedAnnexJ(30), g9923ReachExtAdsl2PotsNonOverlappedM1(34), g9923ReachExtAdsl2PotsNonOverlappedM2(35), g9923ExtUpAdsl2PotsNonOverlapped(38), g9925Adsl2PlusPotsNonOverlapped(40), g9925Adsl2PlusIsdnNonOverlapped(42), g9925ADMAdsl2PlusNonOverlappedAnnexJ(48), g9925ExtUpAdsl2PlusPotsNonOverlapped(50), g9932Vdsl2NonOverlappedRegionA(56) g9932Vdsl2NonOverlappedRegionB(57), Customer can select a single mode or enable all possible standards and the system will select the mode depending on the detected remote side. At minimum, one bit has always to be set! Currently a mix of enabled VDSL and ADSL standards will be rejected by the NE. Same will be occure for a mix of ADSL pots and isdn standards. A configuration of this parameter, which causes a Standard change (ADSL->VDSL or back) could only made for NOT USED profiles!

This parameter indicates that the framer settings of the bearer shall be selected such that the impulse noise protection computed according to the formula specified in the relevant Recommendation is greater than or equal to the minimal impulse noise protection requirement. This flag shall have the same value for all the bearers of one line in the same direction. This parameter specifies the value for downstream direction. Remark: Moved to sheXdslLineTable with SHE R2.6 and not longer supported via line profile!!

This parameter indicates that the framer settings of the bearer shall be selected such that the impulse noise protection computed according to the formula specified in the relevant Recommendation is greater than or equal to the minimal impulse noise protection requirement. This flag shall have the same value for all the bearers of one line in the same direction. This parameter specifies the value for upstream direction. Remark: Moved to sheXdslLineTable with SHE R2.6 and not longer supported via line profile!!

The value of this object identifies the row in the XDSL channel configuration Profile Table, (sheXdslChannelProfileTable) that applies to DSL bearer channel #1. The channel profile name specified here must match the name of an existing row in the sheXdslChannelProfileTable table. Remark: Moved to sheXdslLineTable with SHE R2.6 and not longer supported via line profile!!

Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #1 when performing rate adaptation on Downstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - sheXdslLineConfChan1RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels on Downstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%. Remark: Moved to sheXdslLineTable with SHE R2.6 and not longer supported via line profile!!

Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #1 when performing rate adaptation on Upstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - sheXdslLineConfChan1RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels on Upstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100 %. Remark: Moved to sheXdslLineTable with SHE R2.6 and not longer supported via line profile!!

The value of this object identifies the row in the XDSL channel configuration Profile Table, (sheXdslChannelProfileTable) that applies to DSL bearer channel #2. If the channel is unused, then the object is set to a zero length string. The modification of this parameter which causes a switchover between single and dualLatency is only possible for lineProfiles which are not in use!! Remark: Moved to sheXdslLineTable with SHE R2.6 and not longer supported via line profile!!

createXdslLineConfProfile sheXdslLineConfProfileControlName ... modifyXdslLineConfProfile (A modification of sheXdslLineConfProfileControlUseVdsl2ProfileNumber, in a way that it causes a new subcarrier spacing is not allowed for profiles, which are assigned to a xdsl line!) sheXdslLineConfProfileControlIndex sheXdslLineConfProfileControlName ... deleteXdslLineConfProfile sheXdslLineConfProfileControlIndex sheXdslLineConfProfileControlName

Index of the configured xdsl line profile.

The status of a user command.

The maximum wait time for the manager for a long running user command.

The result of the last user command.

The time stamp of the last command (end of command).

look at table

Look at table.

Look at table.

Look at table.

Look at table.

look at table.

Look at table. Max > Target > Min value!

Look at table. Max > Target > Min value!

Look at table. Max > Target > Min value!

Look at table. Max > Target > Min value!

Look at table. Max > Target > Min value!

Look at table. Max > Target > Min value!

Configured Signal/Noise Margin for rate downshift. If the noise margin falls below this level, the modem should attempt to decrease its transmit rate.

Configured Signal/Noise Margin for rate upshift. If the noise margin rises above this level, the modem should attempt to increase its transmit rate.

Minimum time that the current margin is below DownshiftSnrMgn before a downshift occurs.

Minimum time that the current margin is above UpshiftSnrMgn before an upshift occurs.

Configured Signal/Noise Margin for rate downshift. If the noise margin falls below this level, the modem should attempt to decrease its transmit rate.

Configured Signal/Noise Margin for rate upshift. If the noise margin rises above this level, the modem should attempt to increase its transmit rate.

Minimum time that the current margin is below DownshiftSnrMgn before a downshift occurs.

Minimum time that the current margin is above UpshiftSnrMgn before an upshift occurs.

look at table Note: The bandplan numbers below 50 should not longer be used!

A modification of sheXdslLineConfProfileControlUseVdsl2ProfileNumber, in a way that it causes a new subcarrier spacing is not allowed for profiles, which are assigned to a xdsl line! Be aware, that dslProfile30A use a different subcarrier spacing of 8.625 kHz!

look at table.

look at table Remark: Moved to sheXdslLineTableControl with SHE R2.6 and not longer supported via line profile!!

look at table Remark: Moved to sheXdslLineTableControl with SHE R2.6 and not longer supported via line profile!!

The channel profile name specified here must match the name of an existing row in the sheXdslChannelProfileTable table. Remark: Moved to sheXdslLineTableControl with SHE R2.6 and not longer supported via line profile!!

Look at table. Remark: Moved to sheXdslLineTableControl with SHE R2.6 and not longer supported via line profile!!

Look at table Remark: Moved to sheXdslLineTableControl with SHE R2.6 and not longer supported via line profile!!

The channel profile name specified here must match the name of an existing row in the sheXdslChannelProfileTable table. Remark: Moved to sheXdslLineTableControl with SHE R2.6 and not longer supported via line profile!!

This table contains information on the XDSL line alarm configuration. One entry in this table reflects a profile defined by a manager which can be used to configure the XDSL line alarm thresholds. Entries in this table MUST be maintained in a persistent manner.

Each entry consists of a list of parameters that represents the configuration of a XDSL line alarm profile. A default profile with an index of 'DEFVAL', will always exist and its parameters will be set to vendor specific values, unless otherwise specified in this document. The default profile could not be modified!

Description.

Dynamic' profiles are implemented.The profile name is user specified. A default profile with an name of 'DEFVAL', will always exist and its parameters will be set to vendor specific values, unless otherwise specified in this document. This characters are not allowed: space : o

This object configures the threshold for the number of loss of frame seconds (lofs) within any given 15-minute performance data collection interval. If the value of loss of frame seconds in a particular 15-minute collection interval reaches/exceeds this value, a xdslPerfLofsThreshNotification notification will be generated. This configuration is set for xtuc and xtur side. Value 0 should be interpreted as disabled.

This object configures the threshold for the number of loss of signal seconds (loss) within any given 15-minute performance data collection interval. If the value of loss of signal seconds in a particular 15-minute collection interval reaches/exceeds this value, a xdslPerfLossThreshNotification notification will be generated. This configuration is set for xtuc and xtur side. Value 0 should be interpreted as disabled.

This object configures the threshold for the number of loss of power seconds (lprs) within any given 15-minute performance data collection interval. If the value of loss of power seconds in a particular 15-minute collection interval reaches/exceeds this value, a xdslPerfLprsThreshNotification notification will be generated. This configuration is set for xtuc and xtur side. Value 0 should be interpreted as disabled.

This object configures the threshold for the number of loss of link seconds (lols) within any given 15-minute performance data collection interval. If the value of loss of power seconds in a particular 15-minute collection interval reaches/exceeds this value, a xdslPerfLolsThreshNotification notification will be generated. This configuration is set for xtuc and xtur side. Value 0 should be interpreted as disabled.

This object configures the threshold for the number of errored seconds (ESs) within any given 15-minute performance data collection interval. If the value of errored seconds in a particular 15-minute collection interval reaches/exceeds this value, a xdslPerfESsThreshNotification notification will be generated. This configuration is set for xtuc and xtur side. Value 0 should be interpreted as disabled.

This object configures the threshold for the number of severely errored seconds (SESs) within any given 15-minute performance data collection interval. If the value of severely errored seconds in a particular 15-minute collection interval reaches/exceeds this value, a xdslPerfSESsThreshNotification notification will be generated. This configuration is set for xtuc and xtur side. Value 0 should be interpreted as disabled.

This object configures the threshold for the number of unavailable seconds (UASs) within any given 15-minute performance data collection interval. If the value of unavailable seconds in a particular 15-minute collection interval reaches/exceeds this value, a xdslPerfUASsThreshNotification notification will be generated. This configuration is set for xtuc and xtur side. Value 0 should be interpreted as disabled.

This object specifies if a xdslInitFailureNotification will be generated if an initialization failure occurs.

This object specifies if a xdslOperationalStateNotification will be generated if an operartional state change occurs.

This parameter control the downstream line monitoring for CPE's which do not support the nearest supported impulse noise protection (INP) value. This is related to MIB-parameter checks for ADSL2x links between CO side and CPE side. In particular it can be checked whether a configured (i.e. desired) parameter setting is supported by the attached CPE as well. This capability information is exchange during handshake phase. When activated, the consequence of parameter violation can be to generate just a alarm and go to showtime anyway or the CPE shall not synchronize at all, i.e. the link will not be established. Valid settings: checkMinINP(1) -> set BIT to 1 will enable the MinINP check abortOnINPViolation(2) -> set BIT to 1 will abort the trainings sequence and the line will not reach showtime state if a INP config violation was detectedcted Note: New parameter with R2.8 maintenance. It is DSL firmware depended if a line support this feature and if a separate abort-handling is possible. If no support is available, the configuration will be ignored.

createXdslLineAlarmConfProfile sheXdslLineAlarmConfProfileControlName ... modifyXdslLineAlarmConfProfile sheXdslLineAlarmConfProfileControlIndex sheXdslLineAlarmConfProfileControlName ... deleteXdslLineAlarmConfProfile sheXdslLineAlarmConfProfileControlIndex sheXdslLineAlarmConfProfileControlName

Index of the configured xdsl line alarm profile..

The status of a user command.

The maximum wait time for the manager for a long running user command.

The result of the last user command.

The time stamp of the last command (end of command).

look at table

Look at table.

Look at table.

Look at table.

Look at table.

Look at table.

Look at table.

Look at table.

Look at table.

look at table.

look at table. Note: New parameter with R2.8 maintenance.

This table contains information on the XDSL line configuration. One entry in this table reflects a profile defined by a manager which can be used to configure the XDSL line. Entries in this table MUST be maintained in a persistent manner.

Each entry consists of a list of parameters that represents the configuration of a xDSL line. Dynamic' profiles are implemented.The profile name is user specified. There are five different default profiles in the NE, which could not be modified! Check corresponding LineProfile-Entry for detailes.

downstream bit swapping

upstream bit swapping

This configuration parameter defines the assumed electrical length of cables (E-side cables) connecting exchange based DSL services to a remote flexibility point (cabinet), that may also host remotely located DSL that is subject to spectrally shaped downstream power backoff depending on this length. For this parameter the electrical length is defined as the loss (in dB) of an equivalent length of hypothetical cable at a reference frequency defined by the network operator or in spectrum management regulations. All values which can be represented by the format are valid values. If this value is zero, the DPBO in this section shall be disabled. If this value is not zero and sheXdslLineConfExtnDownPboEselMin is not 512 (disabled EselMin), sheXdslLineConfExtnDownPboEsel >= sheXdslLineConfExtnDownPboEselMin is required!

DPBOMUS defines the assumed Minimum Usable receive Signal PSD (in dBm/Hz) for exchange based services, used to modify parameter DPBOFMAX defined below. All values which can be represented by the format are valid values: 0 = 0 dBm/Hz .. -127.5 dBm/Hz (coded as 255).

DPBO shall be applied in the range starting at DPBOFMIN and should be configured as an subcarrier index. The resulting range of valid values is from 0 to 8832 kHz in steps of 4.3125 kHz..

The maximum subcarrier at which DPBO may be applied is DPBOFMAX. The resulting range of valid values is from 138 kHz to 29997.75 kHz in steps of 4.3125 kHz.

This parameter represents the minimum time (in seconds) between an exit from the L2 state and the next entry into the L2 state. It ranges from 0 to 255 seconds.

This parameter represents the minimum time (in seconds) between an Entry into the L2 state and the first Power Trim in the L2 state and between two consecutive Power Trims in the L2 State. It ranges from 0 to 255 seconds.

This parameter represents the maximum aggregate transmit power reduction (in dB) that can be performed through a single Power Trim in the L2 state. It ranges from 0 dB to 31 dB in steps of 1 dB.

Which Xdsl Power Management state is enabled and where the line may autonomously transition to. disable(0) -> none l3Enabled(1) -> idle state l1l2Enabled(2) -> low power state l1l2l3Enabled(3) -> all

Enable/Disable usage of subcarrier masking defined in sheXdslLineConfExtnCustomSubcarrierMask for DS direction and sheXdslLineConfExtnCustomUsSubcarrierMask for US direction. Only valid for ADSL, ADSL2 and ADSL2+ mode. Note: The parameter sheXdslLineConfExtnCustomUsSubcarrierMask is only valid for SHE R2.6 RP2 and following.

Each one of the 512 bits in this OCTET STRING array represents the corresponding bin. A value of one indicates that the corresponding subcarrier is enabled. Coding example: '8001FFFF....' enables first subcarrier (subcarrier 0), sixteenth subcarrier and all followings. Default value will be one (enable) for all subcarriers which means that the NE uses the subcarriers according the selected standard. Only valid for ADSL, ADSL2 and ADSL2+ mode. Depending on the used standard, only a subset of bin's will be evaluated by the NE. Example: G992.1 (ADSL) AnnexA bin 6-32 related to US and bin 33-255 related to DS direction. G992.1 (ADSL) AnnexB bin 32-63 related to US and bin 64-255 related to DS direction. For G.992.4, and G.992.5, it is defined in the corresponding recommendations. Note: With SHE R2.6 RP2, this parameter defines only the DS SubcarrierMask! The US SubcarrierMask was moved to sheXdslLineConfExtnCustomUsSubcarrierMask parameter.

This parameter represents the total maximum aggregate transmit power reduction (in dB) that can be performed in an L2 state. This is the sum of all reductions of L2 request and power trims. It ranges from 0 dB to 31 dB in steps of 1 dB.

Used PSD mask that is assumed to be permitted at the exchange. The set of breakpoints can be represented as [(t1, PSD1), (t2, PSD2), .. , (tN, PSDN)]. The subcarrier index (tN) shall be coded as an unsigned integer (16 bit, range 1..4095). The MIB PSD mask level (PSDN) shall be coded as an unsigned integer (16 bit) representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -127.5 dBm/Hz (coded as 255), in steps of 0.5 dBm/Hz. The maximum number of breakpoints for DPBOEPSD is 16. If less then maximum breakpoints will be defined, all used breakpoints should be configured in a consecutive way without spaces (t1 - t2 - t3.. and not t1 - t5 - t7..). The default value should be set according PSD settings for ADSL2+. Subcarrier PSD 59 -36.5 256 -36.5 314 -42 376 -46.5 499 -47.5

This configuration parameter defines a cable model in terms of three scalars DPBOESCMA, DPBOESCMB and DPBOESCMC that are used to estimate the frequency dependent loss of E-side cables calculated from the DPBOESEL parameter using the formula: ESCM(f) = (DPBOESCMA + DPBOESCMB*sqrt(f) + DPBOESCMC*f )*DPBOESCL Where ESCM is expressed in dB and f is expressed in MHz. DPBOESCMA, DPBOESCMB, DPBOESCMC shall be coded as unsigned integers representing a scalar value from -1 (coded as 0) to 1.5 (coded as 640) in step of 2^-8. All values are valid.

This configuration parameter defines a cable model in terms of three scalars DPBOESCMA, DPBOESCMB and DPBOESCMC that are used to estimate the frequency dependent loss of E-side cables calculated from the DPBOESEL parameter using the formula: ESCM(f) = (DPBOESCMA + DPBOESCMB*sqrt(f) + DPBOESCMC*f )*DPBOESCL Where ESCM is expressed in dB and f is expressed in MHz. DPBOESCMA, DPBOESCMB, DPBOESCMC shall be coded as unsigned integers representing a scalar value from -1 (coded as 0) to 1.5 (coded as 640) in step of 2^-8. All values are valid.

This configuration parameter defines a cable model in terms of three scalars DPBOESCMA, DPBOESCMB and DPBOESCMC that are used to estimate the frequency dependent loss of E-side cables calculated from the DPBOESEL parameter using the formula: ESCM(f) = (DPBOESCMA + DPBOESCMB*sqrt(f) + DPBOESCMC*f )*DPBOESCL Where ESCM is expressed in dB and f is expressed in MHz. DPBOESCMA, DPBOESCMB, DPBOESCMC shall be coded as unsigned integers representing a scalar value from -1 (coded as 0) to 1.5 (coded as 640) in step of 2^-8. All values are valid.

Is the value of A in the reference PSD, PSDREF(f)= -A - B * sqrt(f). The value is given for each US band except US0. Each single value consists of 2 octets. First couple of octets representing the value for band US1. Second for band US2, third for US3, fourth for US4 and the last couple represent the value for US5. All values can be set, but only if the respective band is realy in use the values will be taken, otherwise NE will ignore the settings. The simultaneous setting of values of UPBOA = 40 dBm/Hz and UPBOB = 0 dBm/Hz for a band shall cause UPBO to be disabled. This are the default setting for all band's. The valid range for a single index: 4000 .. 8095

Is the value of B in the reference PSD, PSDREF(f)= -A - B * sqrt(f). The value is given for each US band except US0. Each single value consists of 2 octets. First couple of octets representing the value band US1. Second for band US2, third for US3, fourth for US4 and the last couple represent the value for US5. All values can be set, but only if the respective band is realy in use the values will be taken, otherwise NE will ignore the settings. The simultaneous setting of values of UPBOA = 40 dBm/Hz and UPBOB = 0 dBm/Hz for a band shall cause UPBO to be disabled. This are the default setting for all band's. The valid range for a single index: 0 .. 4095

This parameter represents the maximum nominal transmit PSD in downstream direction during initialization and showtime.

This parameter represents the maximum nominal transmit PSD in upstream direction during initialization and showtime.

This configuration parameter defines the minimum assumed electrical length of cables (E-side cables) connecting exchange based DSL services to a remote flexibility point (cabinet), that may also host remotely located DSL that is subject to spectrally shaped downstream power backoff depending on this length. For this parameter the electrical length is defined as the loss (in dB) of an equivalent length of hypothetical cable at a reference frequency defined by the network operator or in spectrum management regulations. All values which can be represented by the format are valid values. Default: sheXdslLineConfExtnDownPboEselMin = 512 If this value is not 512 (disabled) and sheXdslLineConfExtnDownPboEsel is not zero (DPBO disabled), sheXdslLineConfExtnDownPboEsel >= sheXdslLineConfExtnDownPboEselMin is required!

DPBOMOF (mask overall floor) defines the absolut minimum of the used PSD mask (in dBm/Hz) for exchange based services. All values which can be represented by the format are valid values: 0 = 0 dBm/Hz .. -127.5 dBm/Hz (coded as 255). NOTE: This parameter is not longer supported with R2.6 RP2.

This parameter defines the electrical loop length expressed in dB at 1 MHz. The value could be coded in the range from 0 to 128 dB in steps of 0.1 dB.

This parameter is a flag that forces the xTU-R to use the electrical loop length of the MIB (defined in sheXdslLineConfExtnProfileUpPboKL) to compute UPBO. If not enabled, the electrical loop length shall be autonomously derived be the xTU's. Default value is disabled.

Enable Boost Mode. If disabled, the UPBO standard mode is used with the LOSS function calculated according to 7.3.1.2.13 of G.997.1.

This parameter defines the minimum rate of the message based overhead that shall be maintained by the xTU in the upstream direction. MSGMINus is expressed in bits per second and ranges from 4000 to 248 000 bit/s with 1000 bit/s steps.

This parameter defines the minimum rate of the message based overhead that shall be maintained by the xTU in the downstream direction. MSGMINds is expressed in bits per second and ranges from 4000 to 248 000 bit/s with 1000 bit/s steps.

Selects the PSD mask option to be used. This parameter is used only for annexes J and M of ITU-T Recs. G.992-3 and G.992.5. Other DSL standards will ignore the configured value!

Each one of the 512 bits in this OCTET STRING array represents the corresponding bin. A value of one indicates that the corresponding subcarrier is enabled. Coding example: '03FFFFFE00...' enables subcarrier's 6-32 and disable all followings. Default value will be one (enable) for all subcarriers which means that the NE uses the subcarriers according the selected standard. Only valid for ADSL, ADSL2 and ADSL2+ mode. Depending on the used standard, only a subset of bin's will be evaluated by the NE. Example: G992.1 (ADSL) AnnexA bin 6-32 related to US and bin 33-256 related to DS direction. G992.1 (ADSL) AnnexB bin 32-63 related to US and bin 64-256 related to DS direction. For G.992.4, and G.992.5, it is defined in the corresponding recommendations. Note: New parameter with SHE R2.6 RP2 and defines only the US SubcarrierMask! The DS SubcarrierMask is defined in sheXdslLineConfExtnCustomSubcarrierMask parameter.

This parameter enables the transmitter referred virtual noise in the downstream direction, defined in sheXdslLineConfExtnTxRefVnDown. If set to 1, the virtual noise is disabled. If set to 2, the virtual noise is enabled. Note: Configuration is only valid for VDSL2 mode.

This parameter enables the transmitter referred virtual noise in the upstream direction, defined in sheXdslLineConfExtnTxRefVnUp. If set to 1, the virtual noise is disabled. If set to 2, the virtual noise is enabled. Note: Configuration is only valid for VDSL2 mode.

This configuration parameter defines the downstream transmitter referred virtual noise (TXREFVNds). The TXREFVNds shall be specified through a set of breakpoints. Each breakpoint shall consist of a subcarrier index t, with a subcarrier spacing of 4.3125 kHz, and a noise PSD level (expressed in dBm/Hz) at that subcarrier. The set of breakpoints can then be represented as [(t1, PSD1), (t2, PSD2), . , (tN, PSDN)]. The subcarrier index shall be coded as an unsigned integer (16 bit, value range 1..4096, 0 means breakpoint not used). The noise level (16 bit) ranges from -40 dBm/Hz (coded as 0) to -140 dBm/Hz (coded as 200) in steps of 0.5 dBm/Hz. A special value (coded as 255) indicates a noise level of 0 W/Hz. The maximum number of breakpoints is 32. If less then maximum breakpoints will be defined, all used breakpoints should be configured in a consecutive way without spaces. Note: Configuration is only valid for VDSL2 mode.

This configuration parameter defines the upstream transmitter referred virtual noise (TXREFVNus). The TXREFVNus shall be specified through a set of breakpoints. Each breakpoint shall consist of a subcarrier index t, with a subcarrier spacing of 4.3125 kHz, and a noise PSD level (expressed in dBm/Hz) at that subcarrier. The set of breakpoints can then be represented as [(t1, PSD1), (t2, PSD2), . , (tN, PSDN)]. The subcarrier index shall be coded as an unsigned integer (16 bit, value range 1..4096, 0 means breakpoint not used). The noise level (16 bit) ranges from -40 dBm/Hz (coded as 0) to -140 dBm/Hz (coded as 200) in steps of 0.5 dBm/Hz. A special value (coded as 255) indicates a noise level of 0 W/Hz. The maximum number of breakpoints is 16. If less then maximum breakpoints will be defined, all used breakpoints should be configured in a consecutive way without spaces. Note: Configuration is only valid for VDSL2 mode.

modifyXdslLineConfExtnProfile sheXdslLineConfExtnProfileControlIndex ...

Index of the configured xdsl line profile.

The status of a user command.

The maximum wait time for the manager for a long running user command.

The result of the last user command.

The time stamp of the last command (end of command).

look at table

look at table

look at table

look at table

look at table

look at table

This parameter represents the minimum time (in seconds) between an exit from the L2 state and the next entry into the L2 state. It ranges from 0 to 255 seconds.

This parameter represents the minimum time (in seconds) between an Entry into the L2 state and the first Power Trim in the L2 state and between two consecutive Power Trims in the L2 State. It ranges from 0 to 255 seconds.

This parameter represents the maximum aggregate transmit power reduction (in dB) that can be performed through a single Power Trim in the L2 state.

Which DSL Power Management state is enabled. Currently powermanagment will not be supported by xdsl-lines.

look at table.

look at table.

look at table

look at table.

look at table.

look at table.

look at table.

look at table.

look at table.

look at table.

look at table.

look at table

look at table NOTE: This parameter is not longer supported with R2.6 RP2.

look at table.

Look at table.

Look at table.

Look at table.

Look at table.

This parameter is used only for annexes J and M of ITU-T Recs. G.992-3 and G.992.5. This configuration parameter defines which upstream PSD mask is enabled.

look at table.

Look at table.

Look at table.

Look at table.

Look at table.

Description.

Each entry describes a MIB based PSD mask. A downstream (usage) profile could support 32 breakpoints. A upstream profile could support 16 breakpoints.

Index for that PSDMaskProfile.

A name for that profile. This name will be used for referencing the used profile in the lineextnprofile. This characters are not allowed: space : o and empty string.

Defines the number of used breakpoints by this profile. As described in g.997.1, a maximum set of 16 or 32 breakpoints could be defined for MIB based PDS mask's in downstream direction. In upstream direction a maximum set of 16 breakpoints will be supported. If less then maximum breakpoints will be defined, all used breakpoints should be configured in a continuous way, that means: use Index01-Index04 if 4 breakpoints will be set and not Index01-Index03-Index11-Index32.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Type of usage custom psd mask profile for downstream or upstream direction. This parameter can only be set during profile creation!

createXdslPsdMaskProfile sheXdslPsdMaskProfileControlName sheXdslPsdMaskProfileControlUsage modifyXdslPsdMaskProfile sheXdslPsdMaskProfileControlIndex ... deleteXdslPsdMaskProfile sheXdslPsdMaskProfileControlIndex

Index of the configured xdsl psdmask profile entry.

The status of a user command.

The maximum wait time for the manager for a long running user command.

The result of the last user command.

The time stamp of the last command (end of command).

look at table

Defines the number of used breakpoints by this profile. As described in g.997.1, a maximum set of 16 or 32 breakpoints could be defined for MIB based PDS mask's. If less then maximum breakpoints will be defined, all used breakpoints should be configured in a consecutive way, that means: use Index01-Index04 if 4 breakpoints will be set and not Index01-Index03-Index11-Index32.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

Index of the subcarrier, where this breakpoint will be placed. If 0xffff, the index and the corresponding PsdLevel are not valid.

The MIB PSD mask level shall be coded as an unsigned integer representing the MIB PSD mask levels 0 dBm/Hz (coded as 0) to -97.5 dBm/Hz (coded as 195), in steps of 0.5 dBm/Hz.

look at table.

Description.

Each entry describes a MIB based CustomNotch profile. NOTE: For G.992.5, this configuration parameter defines the subset of downstream PSD mask breakpoints, as specified in PSDMASKds, that shall be used to notch an RFI band. This subset consists of couples of consecutive subcarrier indices belonging to breakpoints: [ti; ti + 1], corresponding to the low level of the notch. The specific interpolation around these points is defined in the relevant Recommendations (e.g., G.992.5). The configured breakpoint's in such a notch profile define only the low level subcarriers of the notch. The additional needed carriers and the psd level on these points will be evaluated from the NE according to the G992.5 recommendation. For G.993.2, this configuration parameter defines the bands where the PSD shall be reduced as specified in 7.2.1.2/G.993.2. Each band shall be represented by a start and stop subcarrier indices with a subcarrier spacing of 4.3125kHz. Up to 16 bands may be specified. This parameter defines the RFI bands for both upstream and downstream directions.

Index for that sheXdslCustomNotchProfile.

A name for that profile. This name will be used for referencing the used profile in the linetable. This characters are not allowed: space : o and empty string.

Defines the number of used notches by this profile. A maximum set of 16 custom notches could be defined. If less then 16 will be defined, all used notches should be configured in a consecutive way, that means: use Index01-Index04 if 4 notches will be set and not Index01-Index03-Index07-Index08. Be aware, that the NE can handle only 16 notches per line at time. If all free defined notches in this profile should be used, it is not allowed to enable additional predefined notches from the RFIBandMask !! If such notches are already activ, it is not possible to assign a notchprofile to such a line if the total amount of notches (RFIBand's + UsedNotches) is greater then 16.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

Index of the subcarrier, where this notch will start. If 0, the notch is not valid.

Index of the subcarrier, where this notch will stop. If 0, the notch is not valid.

createXdslCustomNotchProfile sheXdslCustomNotchProfileControlName ... modifyXdslCustomNotchProfile (not allowed if profile is assigned!) sheXdslCustomNotchProfileControlIndex ... deleteXdslCustomNotchProfile sheXdslCustomNotchProfileControlIndex

Index of the configured xdsl psdmask profile entry.

The status of a user command.

The maximum wait time for the manager for a long running user command.

The result of the last user command.

The time stamp of the last command (end of command).

look at table

look at table.

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

look at table

Because some of the defined LineStatus-Parameters should be presented per used band, this table is needed for supporting also Vdsl2 systems. Where adsl-systems use always one band per direction, Vdsl2 systems use a minimum of two bands per direction

Each entry contains information per used band. For a adsl-sytem, this table contains per line one entry per direction. A Vdsl2 system will contain a minimum of four entrys per line.

Second index for that table. 1 - downstream 2 - upstream

Index of the used band on this line. band0 (1) will only be used on Vdsl2 lines if the optional band 0 is used (upstream only). band1 (2) will be used on adsl lines (US and DS) and Xdsl2 lines (US1 and DS1) band2 (3) and more will only be used on Vdsl2 lines (US2 and DS2...).

The measured difference in the total power transmitted by the one xTU-x and the total power received by the other xTU-x over all subcarriers during diagnostics mode and initialization. It ranges from 0 to 1270 in units of 0.1 dB (Physical values are 0 to 127 dB). Special recommendations (G992.3 or G993.2) can restrict the used value range in detail. Note: A special value of 0x8000 (32768) means that the current line attenuation is not available (line not trained or band not used or measurement not finished). A special value of 1271 means that the current line attenuation is outOfRange for measurement.

The measured difference in the total power transmitted by the one xTU-x and the total power received by the other xTU-x over all subcarriers during Showtime. It ranges from 0 to 1270 in units of 0.1 dB (Physical values are 0 to 127 dB). Special recommendations (G992.3 or G993.2) can restrict the used value range in detail. Note: A special value of 0x8000 (32768) means that the current signal attenuation is not available (line not trained or band not used or measurement not finished). A special value of 1271 means that the current signal attenuation is outOfRange for measurement.

SNR Margin per band is the maximum increase in dB of the noise power received at the xTU-x, such that the BER requirements are met for all bearer channels. It ranges from -640 to 630 in units of 0.1 dB (Physical values are -64 to 63 dB). Special recommendations (G992.3 or G993.2) can restrict the used value range in detail. Note: A value of 0x8000 (32768) means that the current line margin is not available (line not trained or band not used or measurement not finished). A special value of -641 means that the current line margin is outOfRange for measurement.

getXdslLineDeltResult: sheXdslLineDeltStatusControlIndex Result's will be presented in the following status tables. sheXdslSCGDnStatusTable sheXdslSCGUpStatusTable Also the controlgroup members for Delt-Result (GroupSize, Scale, Mtime) will be filled. Command will be rejected if no DELT was successfully runnig before on the requested interface. getXdslLineShowtimeStatusResult: sheXdslLineDeltStatusControlIndex Result's will be presented in the following status tables. sheXdslSCDnStatusTable sheXdslSCUpStatusTable sheXdslSCGDnStatusTable (no HLinxx) sheXdslSCGUpStatusTable (no Hlinxx) Also the controlgroup members for Showtime-Result (MRefPsd) will be filled. Command will be rejected if requested interface is not in Showtime state.

IfIndex of the xdsl-interface, where DELT was running before and the result data are requested. Result's will be presented in the following status tables. sheXdslSCDnStatusTable sheXdslSCUpStatusTable sheXdslSCGDnStatusTable sheXdslSCGUpStatusTable

The status of a user command.

The maximum wait time for the manager for a long running user command.

The result of the last user command.

The time stamp of the last command (end of command).

The number of subcarriers in one subcarrier-group shall be equal to the highest power of 2 not greather than ceil((maxUsedCarrier+1)/512), where maxUsedCarrier is the index of the highest frequency subcarrier such that all higher-index subcarriers either have a channel characteristic Hlog lower than -96 dB or do not belong to the passband. Valid values are 1, 2, 4 or 8. 0 means notAvailable. This parameter is the number of subcarriers per group used to report SNRpsds.

The number of subcarriers in one subcarrier-group shall be equal to the highest power of 2 not greather than ceil((maxUsedCarrier+1)/512), where maxUsedCarrier is the index of the highest frequency subcarrier such that all higher-index subcarriers either have a channel characteristic Hlog lower than -96 dB or do not belong to the passband. Valid values are 1, 2, 4 or 8. 0 means notAvailable. This parameter is the number of subcarriers per group used to report SNRpsus.

SNR Measurement Time. The number of symbols used to measure the SNR values on the respective transmission direction. It should correspond to the value specified in the recommendation (e.g., the number of symbols in 1 second time interval). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated otherwise. This information is only available, if DELT was running and result data are requested from a single line.0 means not available.

SNR Measurement Time. The number of symbols used to measure the SNR values on the respective transmission direction. It should correspond to the value specified in the recommendation (e.g., the number of symbols in 1 second time interval). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated otherwise. This information is only available, if DELT was running and result data are requested from a single line.0 means not available.

The scale factor to be applied to the H(f) linear representation values for the respective transmission direction. This information is only available, if DELT was running and result data are requested from a single line.0 means not available.

The scale factor to be applied to the H(f) linear representation values for the respective transmission direction. This information is only available, if DELT was running and result data are requested from a single line.0 means not available.

The number of symbols used to measure the H(f) logarithmic measurement values for the respective transmission direction. This parameter should correspond to the value specified in the recommendation (e.g., the number of symbols in 1 second time interval). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated in initialization This information is only available, if DELT was running and result data are requested from a single line.0 means not available.

The number of symbols used to measure the H(f) logarithmic measurement values for the respective transmission direction. This parameter should correspond to the value specified in the recommendation (e.g., the number of symbols in 1 second time interval). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated in initialization This information is only available, if DELT was running and result data are requested from a single line.0 means not available.

The number of symbols used to measure the Quiet Line Noise values on the respective transmission direction. This parameter should correspond to the value specified in the recommendation (e.g., the number of symbols in 1 second time interval). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated in initialization. This information is only available, if DELT was running and result data are requested from a single line.0 means not available.

The number of symbols used to measure the Quiet Line Noise values on the respective transmission direction. This parameter should correspond to the value specified in the recommendation (e.g., the number of symbols in 1 second time interval). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated in initialization. This information is only available, if DELT was running and result data are requested from a single line. 0 means not available.

This parameter shall contain the set of breakpoints exchanged in the MREFPSDds fields of the OPRM message of G.993.2. Each breakpoint shall consist of a subcarrier index t and a MIB PSD mask level (expressed in dBm/Hz) at that subcarrier (four octets). The set of breakpoints can then be represented as [(t1, PSD1), (t2, PSD2), ..., (tN, PSDN)]. The subcarrier index shall be coded as an unsigned integer (two octets) representing the range from 0..4093. The MIB PSD mask level shall be coded as an unsigned integer (two octet) representing the MIB PSD mask levels in steps of 0.1dB with an offset of -140dBm/Hz. For example, a breakpoint value (t1, PSD1) of '04000320' means: PSD of 0x320 X 0.1 - 140 = -60 dBm/Hz on sub-carrier index 0x400 = 1024. The effective range for MRefPSD is -95..-35 dBM/Hz where given MIB value is 450..1050. The maximum number of breakpoints is 48. Only valid for lines running mode VDSL2 and if the line has reached Showtime state. Value could be requested with getXdslLineShowtimeStatusResult command.

This parameter shall contain the set of breakpoints exchanged in the MREFPSDus fields of the OPRM message of G.993.2. Each breakpoint shall consist of a subcarrier index t and a MIB PSD mask level (expressed in dBm/Hz) at that subcarrier (four octets). The set of breakpoints can then be represented as [(t1, PSD1), (t2, PSD2), ..., (tN, PSDN)]. The subcarrier index shall be coded as an unsigned integer (two octets) representing the range from 0..4093. The MIB PSD mask level shall be coded as an unsigned integer (two octet) representing the MIB PSD mask levels in steps of 0.1dB with an offset of -140dBm/Hz. For example, a breakpoint value (t1, PSD1) of '04000320' means: PSD of 0x320 X 0.1 - 140 = -60 dBm/Hz on sub-carrier index 0x400 = 1024. The effective range for MRefPSD is -95..-35 dBM/Hz where given MIB value is 450..1050. The maximum number of breakpoints is 32. Only valid for lines running mode VDSL2 and if the line has reached Showtime state. Value could be requested with getXdslLineShowtimeStatusResult command.

The number of subcarriers in one subcarrier-group shall be equal to the highest power of 2 not greather than ceil((maxUsedCarrier+1)/512), where maxUsedCarrier is the index of the highest frequency subcarrier such that all higher-index subcarriers either have a channel characteristic Hlog lower than -96 dB or do not belong to the passband. Valid values are 1, 2, 4 or 8. 0 means notAvailable. This parameter is the number of subcarriers per group used to report HLINpsds.

The number of subcarriers in one subcarrier-group shall be equal to the highest power of 2 not greather than ceil((maxUsedCarrier+1)/512), where maxUsedCarrier is the index of the highest frequency subcarrier such that all higher-index subcarriers either have a channel characteristic Hlog lower than -96 dB or do not belong to the passband. Valid values are 1, 2, 4 or 8. 0 means notAvailable. This parameter is the number of subcarriers per group used to report HLINpsus.

The number of subcarriers in one subcarrier-group shall be equal to the highest power of 2 not greather than ceil((maxUsedCarrier+1)/512), where maxUsedCarrier is the index of the highest frequency subcarrier such that all higher-index subcarriers either have a channel characteristic Hlog lower than -96 dB or do not belong to the passband. Valid values are 1, 2, 4 or 8. 0 means notAvailable. This parameter is the number of subcarriers per group used to report HLOGpsds.

The number of subcarriers in one subcarrier-group shall be equal to the highest power of 2 not greather than ceil((maxUsedCarrier+1)/512), where maxUsedCarrier is the index of the highest frequency subcarrier such that all higher-index subcarriers either have a channel characteristic Hlog lower than -96 dB or do not belong to the passband. Valid values are 1, 2, 4 or 8. 0 means notAvailable. This parameter is the number of subcarriers per group used to report HLOGpsus.

The number of subcarriers in one subcarrier-group shall be equal to the highest power of 2 not greather than ceil((maxUsedCarrier+1)/512), where maxUsedCarrier is the index of the highest frequency subcarrier such that all higher-index subcarriers either have a channel characteristic Hlog lower than -96 dB or do not belong to the passband. Valid values are 1, 2, 4 or 8. 0 means notAvailable. This parameter is the number of subcarriers per group used to report QLNpsds.

The number of subcarriers in one subcarrier-group shall be equal to the highest power of 2 not greather than ceil((maxUsedCarrier+1)/512), where maxUsedCarrier is the index of the highest frequency subcarrier such that all higher-index subcarriers either have a channel characteristic Hlog lower than -96 dB or do not belong to the passband. Valid values are 1, 2, 4 or 8. 0 means notAvailable. This parameter is the number of subcarriers per group used to report QLNpsus.

This parameter contains the downstream transmit spectrum shaping parameters expressed as the set of breakpoints exchanged during G.994.1. Each breakpoint shall consist of a subcarrier index t and a MIB PSD mask level at that subcarrier. The set of breakpoints can then be represented as [(t1, PSD1), (t2, PSD2), ..., (tN, PSDN)]. The subcarrier index shall be coded as an unsigned integer (two octets) representing the range from 0..511. The shaping parameter is an integer value in the 0 to 126 range. It is represented as a multiple of -0.5 dB. The value 126 should be interpreted as special value and means interpolation. The maximum number of breakpoints is 60. Only valid if lines runs in ADSL mode and showtime was reached.

This parameter contains the upstream transmit spectrum shaping parameters expressed as the set of breakpoints exchanged during G.994.1. Each breakpoint shall consist of a subcarrier index t and a MIB PSD mask level at that subcarrier. The set of breakpoints can then be represented as [(t1, PSD1), (t2, PSD2), ..., (tN, PSDN)]. The subcarrier index shall be coded as an unsigned integer (two octets) representing the range from 0..511. The shaping parameter is an integer value in the 0 to 126 range. It is represented as a multiple of -0.5 dB. The value 126 should be interpreted as special value and means interpolation. The maximum number of breakpoints is 60. Only valid if lines runs in ADSL mode and showtime was reached.

The table sheXdslSCDnStatusTable contains status parameters of xDSL sub-carriers for downstream direction. This table could only be requested for interfaces, which are in showtime state or after a successfull DELT run. The controlrequest commands 'getXdslLineDeltResult' or 'getXdslLineShowtimeStatusResult' are needed to send before, to fill these table for are requested interface.

The table sheXdslSCDnStatusEntry contains status parameters of xDSL2 sub-carriers for downstream direction. The index of this table is the real subcarrierIndex + 1 (real range 0..4095).

The index of this table is the real subcarrierIndex + 1 (real range 0..4095) in downstream direction.

This parameter defines the downstream bits allocation table for a particular sub-carrier. It is a integer values in the 0 to 15 range for subcarriers 1 to NSCds

This parameter defines the downstream gains allocation table a particular sub-carrier. It is a integer values in the 0 to 4093 range for subcarriers 1 to NSCds. The gain value is represented as a multiple of 1/512 on linear scale.

This parameter contains the downstream transmit spectrum shaping parameters expressed as the set of breakpoints exchanged during G.994.1. Each breakpoint consists of a subcarrier index and the associated shaping parameter. The shaping parameter is an integer value in the 0 to 126 range. It is represented as a multiple of -0.5 dB. A special value (255) indicates that the subcarrier is not transmitted. Only valid if lines runs in ADSL mode.

The table sheXdslSCDnStatusTable contains status parameters of xDSL sub-carriers for upstream direction. This table could only be requested for interfaces, which are in showtime state or after a successfull DELT run. The controlrequest commands 'getXdslLineDeltResult' or 'getXdslLineShowtimeStatusResult' are needed to send before, to fill these table for are requested interface.

The table sheXdslSCUpStatusEntry contains status parameters of xDSL2 sub-carriers for upstream direction. The index of this table is the real subcarrierIndex + 1 (real range 0..4095).

The index of this table is the real subcarrierIndex + 1 (real range 0..4095) in upstream direction.

This parameter defines the upstream bits allocation table for a particular sub-carrier. It is a integer values in the 0 to 15 range for subcarriers 1 to NSCus

This parameter defines the upstream gains allocation table a particular sub-carrier. It is a integer values in the 0 to 4093 range for subcarriers 1 to NSCus. The gain value is represented as a multiple of 1/512 on linear scale.

This parameter contains the upstream transmit spectrum shaping parameters expressed as the set of breakpoints exchanged during G.994.1. Each breakpoint consists of a subcarrier index and the associated shaping parameter. The shaping parameter is an integer value in the 0 to 126 range. It is represented as a multiple of -0.5 dB. A special value (255) indicates that the subcarrier is not transmitted. Only valid if lines runs in ADSL mode.

The table sheXdslSCGDnStatusTable contains status parameters of xDSL sub-carriers groups for downstream direction. This table could only be requested for interfaces, which are in showtime state or after a successfull DELT run. The controlrequest commands 'getXdslLineDeltResult' or 'getXdslLineShowtimeStatusResult' are needed to send before, to fill these table for are requested interface.

The table sheXdslSCGDnStatusEntry contains status parameters of xDSL2 sub-carrier groups for downstream direction. The index of this table are the subcarrier group index.

The index of a used subcarrier group in downstream direction.

This parameter is a real downstream SNR(f) values in dB. Represents the SNR(f = i* f) value for a particular sub-carrier index i, ranging from 1 to NSCds. The SNR(f) is represented as ( 32 + snr(i)/2), with snr(i) an 8 bit unsigned integer in the 0 to 254 range. A special value snr(i)=255 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the noise PSD is out of range to be represented.

This parameter is the real part a(i) of the 2 16-bit 2's complement signed integers. This parameter is a complex downstream Hlin(f) value in linear scale. Represents the Hlin(f = i* f) value for a particular sub-carrier index i, ranging from 1 to NSCds. The Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), where a(i) and b(i) 16-bit 2's complement signed integers in the (-2^15 + 1) to (+2^15 - 1) range. A special value a(i)=b(i)= -2^15 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the attenuation is out of range to be represented. This parameter is only available after a loop diagnostic procedure.

This parameter is the imagened part b(i) of the 2 16-bit 2's complement signed integers. This parameter is a complex downstream Hlin(f) value in linear scale. Represents the Hlin(f = i* f) value for a particular sub-carrier index i, ranging from 1 to NSCds. The Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), where a(i) and b(i) 16-bit 2's complement signed integers in the (-2^15 + 1) to (+2^15 - 1) range. A special value a(i)=b(i)= -2^15 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the attenuation is out of range to be represented. This parameter is only available after a loop diagnostic procedure.

This parameter is a real downstream Hlog(f) values in dB. Represents the real Hlog(f = i* delta f) value for a particular sub-carrier index i, ranging from 1 to NSCds. The real Hlog(f) value is represented as (6-m(i)/10), with m(i) 10 bit unsigned integer in the 0 to 1022 range. A special value m=1023 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the attenuation is out of range to be represented.

This parameter is a real downstream QLN(f) values in dBm/Hz. Represents the QLN(f = i* delta f) value for a particular sub-carrier index i, ranging from 1 to NSCds. The QLN(f) is represented as ( -23 -n(i)/2), with n(i) an 8 bit unsigned integer in the 0 to 254 range. A special value n(i)=255 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the noise PSD is out of range to be represented. This parameter is applicable in loop diagnostic procedure and initialization.

The table sheXdslSCGDnStatusTable contains status parameters of xDSL sub-carriers groups for upstream direction. This table could only be requested for interfaces, which are in showtime state or after a successfull DELT run. The controlrequest commands 'getXdslLineDeltResult' or 'getXdslLineShowtimeStatusResult' are needed to send before, to fill these table for are requested interface.

The table sheXdslSCGDnStatusEntry contains status parameters of xDSL2 sub-carrier groups for upstream direction. The index of this table are the subcarrier group index.

The index of a used subcarrier group in upstream direction.

This parameter is a real upstream SNR(f) values in dB. Represents the SNR(f = i* f) value for a particular sub-carrier index i, ranging from 1 to NSCus. The SNR(f) is represented as ( 32 + snr(i)/2), with snr(i) an 8 bit unsigned integer in the 0 to 254 range. A special value snr(i)=255 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the noise PSD is out of range to be represented.

This parameter is the real part a(i) of the 2 16-bit 2's complement signed integers. This parameter is a complex upstream Hlin(f) value in linear scale. Represents the Hlin(f = i* f) value for a particular sub-carrier index i, ranging from 1 to NSCus. The Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), where a(i) and b(i) 16-bit 2's complement signed integers in the (-2^15 + 1) to (+2^15 - 1) range. A special value a(i)=b(i)= -2^15 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the attenuation is out of range to be represented. This parameter is only available after a loop diagnostic procedure.

This parameter is the imagened part b(i) of the 2 16-bit 2's complement signed integers. This parameter is a complex upstream Hlin(f) value in linear scale. Represents the Hlin(f = i* f) value for a particular sub-carrier index i, ranging from 1 to NSCus. The Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), where a(i) and b(i) 16-bit 2's complement signed integers in the (-2^15 + 1) to (+2^15 - 1) range. A special value a(i)=b(i)= -2^15 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the attenuation is out of range to be represented. This parameter is only available after a loop diagnostic procedure.

This parameter is a real upstream Hlog(f) values in dB. Represents the real Hlog(f = i* delta f) value for a particular sub-carrier index i, ranging from 1 to NSCus. The real Hlog(f) value is represented as (6-m(i)/10), with m(i) 10 bit unsigned integer in the 0 to 1022 range. A special value m=1023 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the attenuation is out of range to be represented.

This parameter is a real upstream QLN(f) values in dBm/Hz. Represents the QLN(f = i* delta f) value for a particular sub-carrier index i, ranging from 1 to NSCus. The QLN(f) is represented as ( -23 -n(i)/2), with n(i) an 8 bit unsigned integer in the 0 to 254 range. A special value n(i)=255 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the noise PSD is out of range to be represented. This parameter is applicable in loop diagnostic procedure and initialization.

Description.

These table contains DSL channel profile configuration. Default profiles will always exist and its parameters will be set to vendor-specific values, unless otherwise specified in this document. Dynamic' profiles are implemented.The profile name is user specified. There are two different default profiles in the NE, which could not be modified! 'DEFVAL' - default profile for interfaces with iftype 'vdsl' (97) used by 'DEFVAL' lineprofile 'DEFVAL_ADSL' - default profile for interfaces with iftype 'adsl2' (230) used by 'DEFVAL_ADSL_A' and 'DEFVAL_ADSL_B' lineprofiles

Index of this table.

This object identifies a row in this table. Dynamic' profiles are implemented.The profile name is user specified. There are two different default profiles in the NE, which could not be modified! 'DEFVAL' - default profile for interfaces with iftype 'vdsl' (97) used by 'DEFVAL' and 'DEFVAL_VDSL2_P' lineprofile 'DEFVAL_ADSL' - default profile for interfaces with iftype 'adsl2' (230) used by 'DEFVAL_ADSL_A' and 'DEFVAL_ADSL_B' lineprofiles This characters are not allowed: space : o

Minimum Data Rate on Downstream direction. The minimum net data rate for the bearer channel, coded in kbps. Remark: For lines using an ADSL standard the maximum datarate value in ds direction is limited to 32736 kbps.

Minimum Data Rate on Upstream direction. The minimum net data rate for the bearer channel, coded in kbps. Remark: For lines using an ADSL standard the maximum datarate value in us direction is limited to 3520 kbps.

Minimum Reserved Data Rate on Downstream direction. The minimum reserved net data rate for the bearer channel, coded in kbps. This parameter is used only if the Rate Adaptation Mode in the direction of the line is set to DynamicRa. Remark: For lines using an ADSL standard the maximum datarate value in ds direction is limited to 32736 kbps.

Minimum Reserved Data Rate on Upstream direction. The minimum reserved net data rate for the bearer channel, coded in kbps. This parameter is used only if the Rate Adaptation Mode in the direction of the Line is set to DynamicRa. Remark: For lines using an ADSL standard the maximum datarate value in us direction is limited to 3520 kbps.

Maximum Data Rate on Downstream direction. The maximum net data rate for the bearer channel, coded in kbps. Remark: For lines using an ADSL standard the maximum datarate value in ds direction is limited to 32736 kbps.

Maximum Data Rate on Upstream direction. The maximum net data rate for the bearer channel, coded in kbps. Remark: For lines using an ADSL standard the maximum datarate value in us direction is limited to 3520 kbps.

Minimum Data Rate in Low Power state on Downstream direction. The minimum net data rate for the bearer channel, coded in kbps, during the low power state (L1 in G.992.2, L2 in G.992.3). Remark: For lines using an ADSL standard the maximum datarate value in ds direction is limited to 32736 kbps.

Maximum Interleave Delay on Downstream direction. The maximum one-way interleaving delay introduced by the PMS-TC on Downstream direction. The xTUs shall choose the S (factor) and D (depth) values such that the actual one-way interleaving delay (XdslChanInterleaveDelay) is as close as possible to, but less than or equal to this parameter. There are three special values defined: 0 -> 'no bound (S0)' - indicates no delay bound is being imposed 1 -> 'none (fast, S1)' - indicates the Fast Latency Path shall be used in the G.992.1 and S and D shall be selected such that S <= 1 and D = 1 in ITU-T Recommendations G.992.2, G.992.3, G.992.4, G.992.5 and G.993.2 255 -> '1 (VDSL only, S2)' - indicates a delay bound of 1 ms in ITU-T Recommendation G.993.2. If the value 1 is selected, then the configured value for sheXdslChannelProfileMinINPDs should be null (0).

Maximum Interleave Delay on Upstream direction. The maximum one-way interleaving delay introduced by the PMS-TC on Upstream direction. The xTUs shall choose the S (factor) and D (depth) values such that the actual one-way interleaving delay (XdslChanInterleaveDelay) is as close as possible to, but less than or equal to this parameter. There are three special values defined: 0 -> 'no bound (S0)' - indicates no delay bound is being imposed 1 -> 'none (fast, S1)' - indicates the Fast Latency Path shall be used in the G.992.1 and S and D shall be selected such that S <= 1 and D = 1 in ITU-T Recommendations G.992.2, G.992.3, G.992.4, G.992.5 and G.993.2 255 -> '1 (VDSL only, S2)' - indicates a delay bound of 1 ms in ITU-T Recommendation G.993.2. If the value 1 is selected, then the configured value for sheXdslChannelProfileMinINPUs should be null (0).

Minimum Impulse Noise Protection on Downstream direction. The minimum impulse noise protection for the bearer channel, expressed in symbols. The parameter can take the following values: null -> 0 -> i.e., INP not required halfSymbol -> 50 -> i.e., INP length is 1/2 symbol and 1-16 symbols in steps of 1 symbol.

Minimum Impulse Noise Protection on Upstream direction. The minimum impulse noise protection for the bearer channel, expressed in symbols. The parameter can take the following values: null -> 0 -> i.e., INP not required halfSymbol -> 50 -> i.e., INP length is 1/2 symbol and 1-16 symbols in steps of 1 symbol.

Maximum Bit Error Ratio on Downstream direction. The maximum bit error ratio for the bearer channel. The parameter can take the following values (for 1E-3, 1E-5 or 1E-7): eMinus3 (0), eMinus5 (1), eMinus7 (2)

Maximum Bit Error Ratio on Upstream direction. The maximum bit error ratio for the bearer channel. The parameter can take the following values (for 1E-3, 1E-5 or 1E-7): eMinus3 (0), eMinus5 (1), eMinus7 (2)

Configured rate change threshold causing an xdslRateChangeDownShiftTrap. A trap is produced when for downstream direction: ChanCurrTxRate <= ChanPrevTxRate minus the value of this object. A value of `0' will disable the trap.

Configured rate change threshold causing an xdslRateChangeUpShiftTrap. A trap is produced when for downstream direction: ChanCurrTxRate >= ChanPrevTxRate plus the value of this object. A value of `0' will disable the trap.

Configured rate change threshold causing an xdslRateChangeDownShiftTrap. A trap is produced when for upstream direction: ChanCurrTxRate <= ChanPrevTxRate minus the value of this object. A value of `0' will disable the trap.

Configured rate change threshold causing an xdslRateChangeUpShiftTrap. A trap is produced when for upstream direction: ChanCurrTxRate >= ChanPrevTxRate plus the value of this object. A value of `0' will disable the trap.

createXdslChannelProfileEntry: sheXdslChannelProfileControlName modifyXdslChannelProfileEntry: sheXdslLineControlIndex ...all group members deleteXdslChannelProfileEntry: sheXdslChannelProfileControlIndex NOTE: During create, the NE will select a free index value. Modification is not allowed for used profiles. Delete is not allowed for used profiles.

Index of a channel profile table entry for modify or delete.

The status of a user command.

The maximum wait time for the manager for a long running user command.

The result of the last user command.

The time stamp of the last command (end of command).

The name for a new created profile.

Look at table.

Look at table.

Look at table.

Look at table.

Look at table.

Look at table.

Look at table.

look at table.

look at table.

look at table

look at table

look at table

look at table

Configured rate change threshold causing an xdslRateChangeDownShiftTrap.

Configured rate change threshold causing an xdslRateChangeUpShiftTrap.

Configured rate change threshold causing an xdslRateChangeDownShiftTrap.

Configured rate change threshold causing an xdslRateChangeUpShiftTrap.

Loss of Framing 15-minute interval threshold (xdslThresh15MinLofs) reached.

Loss of Signal 15-minute interval threshold (xdslThresh15MinLoss) reached.

Loss of Power 15-minute interval threshold (xdslThresh15MinLprs) reached.

Loss of Link 15-minute interval threshold (xdslThresh15MinLols) reached.

Errored Seconds 15-minute interval threshold (xdslThresh15MinESs) reached.

Severely Errored Seconds 15-minute interval threshold (xdslThresh15MinSESs) reached.

Unavailable Seconds 15-minute interval threshold (xdslThresh15MinUASs) reached.

Xtu initialization failed. See xdslPhysCurrStatus for potential reasons.

Configuration trap.

Configuration trap.

Configuration trap.

Configuration trap.

Configuration trap.

Configuration notification.

Configuration trap.

Configuration trap.

Configuration trap.

Configuration notification.

Configuration notification.

Configuration notification.

Configuration notification.

Configuration notification.

Configuration notification.

Xtu-C operational state changed. See xdslPhysCurrOperationalState.

Request result trap for long running configuration command of a dsl line.

Request result trap for long running configuration command of a dsl line profile.

Request result trap for long running configuration command of a dsl line extention profile.

Request result trap for long running configuration command of a dsl alarm profile.

Request result trap for long running configuration command of a dsl psdmask profile.

Configuration trap.

This notification will inform the TMN about changes for sheXdslLineLdsfResult if a loop test was startet by operator or on remote request.

Result trap for long running command of delt status request.

Configuration trap.

Configuration trap.

Configuration trap.

Result trap for long running command of showtime status request.

Description.

Description.

Description.

Request result trap for long running configuration command of a dsl line.

The configured rate change downshift threshold for a dsl channel was reached.

The configured rate change upshift threshold for a dsl channel was reached.

Configuration trap.

Configuration trap.

Configuration trap.

Configuration trap.

The downstream Signal to Noise Margin exceeded xdslLineConfDownMaxSnrMgn. The object xdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the XTU-R.

The downstream Signal to Noise Margin fell below xdslLineConfDownMinSnrMgn. The object xdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the XTU-R.

The upstream Signal to Noise Margin exceeded xdslLineConfUpMaxSnrMgn. The object xdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the XTU-C.

The upstream Signal to Noise Margin fell below xdslLineConfUpMinSnrMgn. The object xdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the XTU-C.

xTUC failure due to not receiving signal

xTUC failure due to not receiving valid frame.

xTUC failure due to inability to link with xTUR

xTUR failure due to loss of power

Loss of Signal Quality is declared when the Noise Margin falls below the Minimum Noise Margin, or the bit-error-rate exceeds the configured level.

The line activation procedure on the IU returns with an error and the line will not start training sequence!

The xTUC has detected a HW defect for this line.

Only if config violation check was enabled for a line, the alarm will be send if a violation was detected. The alarm will always be send, doesn't matter if the line will reach showtime state or not. The line configuration and connected xtur equipment has to be checked. The alarm will be cleared if the line was disabled or retrain without config violation.

The VccTp-Table.

This table contains the VccTp-Configurations. There will be one entry for every xdsl-interface available per default. This default entry should never be deleted. If the underlaying xdsl-line (SublayerIndex) use VDSL2 as currently supported standard, all ATM specific configurations in this table for THIS line are don't care!!

Index for that table. The index will follow this rule: VccTpIndex = (VccTpSubLayerIndex << 4) + VccTpNumber

ifIndex of the underlaying xdsl-interface.

This is the logical number of VccTP on the corresponding interface. Maximum value is 8.

The VPI - Value. Only valid if sublayer uses a ADSL standard.

The Vci - Value. Only valid if sublayer uses a ADSL standard. NOTE: If the NE support atm bonding according G998.1, the usable VCI range for ATM channels which should be bonded is restricted to 32..255. Background is, that only 8 bit could be used for VCI coding in the modified ATM-Header if atm bonding is supported. The other 8 bit's of the VCI field from the standard ATM-Header are needed for SID (sequence index) coding. The result is, that only VccTp's with a VCI configuration smaller then 256 could be used in a bonding scenario!

Used encapsulation over AAL5. Only valid if sublayer uses a ADSL standard.

Enable/disable single VccTp. Default value is enabled.

Index to the AlarmSeverityProfileTable. Defines the actual AlarmSeverities for all alarms per VccTp.

This attribute defines the usage of a dsl bearer channel by this VccTp. The availability of dsl channels depends on the configuration of the underlaying dsl line (VccTpSublayerIndex points to this line). Valid values for configuration: channel1(1) - always available (default) channel2(2) - only in dualLatency mode available Note: Depending on the used DslLineProfile configuration, the following scenarios are possible: 1. default state: ->line uses single channel only ->VccTp's uses always the available channel. ->A modification of sheXdslVccTpUsedDslChannel will be rejected! 2. modify line profile ->line uses dualLatency (channel 2 is configured) ->VccTp's uses the same channel as before. 3. modify VccTp entry ->line uses dualLatency ->the slected VccTp uses channel1 or channel2 only according to the configuration. 4. modify line profile ->line goes back to use single channel1 only ->VccTp's uses the available channel -> notification will be send if a change is needed.

The type of loop test to be started. For EndToEnd loop test loop location ID is FF..FF. Only valid if sublayer uses a ADSL standard.

Possible values: endToEndSuccess(2), endToEndFailure(3), aborted(4), progress(5), notAvailable(65535)

Enable/Disable performance counters for this VccTp. If enabled, results will be shown in sheXdslVccTpPerformanceTable. Support with SHE R2.7.

createDslVccTp: sheXdslVccTpControlSubLayerIndex sheXdslVccTpControlVpi sheXdslVccTpControlVci sheXdslVccTpControlEncapsulation deleteDslVccTp: sheXdslVccTpControlIndex modifyDslVccTp: sheXdslVccTpControlIndex sheXdslVccTpControlVpi sheXdslVccTpControlVci sheXdslVccTpControlEncapsulation sheXdslVccTpControlAlarmSeverityIndex modifyDslVccTpLoopTest: sheXdslVccTpControlIndex sheXdslVccTpControlLoopTest modifyDslVccTpAdminState: sheXdslVccTpControlIndex sheXdslVccTpControlAdminState Only in dualLatency mode possible!! modifyDslVccTpUsedDslChannel: sheXdslVccTpControlIndex sheXdslVccTpControlUsedDslChannel ## R 2.6 deleteDslVccTpPerformanceCounters: sheXdslVccTpControlIndex ## R 2.7 modifyDslVccTpPerformanceCountEnable: sheXdslVccTpControlIndex sheXdslVccTpControlPerformanceCountEnabled

Index of the Table-entry to be configured.

The status of a user command.

The maximum wait time for the manager for a long running user command.

The result of the last user command.

The time stamp of the last command (end of command).

IfIndex of the underlaying dsl-interface.

Vpi

Vci NOTE: If the NE support atm bonding according G998.1, the usable VCI range for ATM channels which should be bonded is restricted to 32..255. Background is, that only 8 bit could be used for VCI coding in the modified ATM-Header if atm bonding is supported. The other 8 bit's of the VCI field from the standard ATM-Header are needed for SID (sequence index) coding. The result is, that only VccTp's with a VCI configuration smaller then 256 could be used in a bonding scenario!

Used encapsulation over AAL5.

look at table

Index of the used AlarmSeverityProfile.

Look at table. In singleLatency mode , no configuration is possible.

Actual LoopTest-Value. Only None or endToEnd will be accepted.

Enable/Disable performance counters for this VccTp. If enabled, results will be shown in sheXdslVccTpPerformanceTable. Support with SHE R2.7.

Configuration notification.

Configuration notification.

Configuration notification.

RDI detected.

AIS detected.