HDSL2-SHDSL-LINE-MIB

Unsigned32 (0..8) · repeaters

This object provisions the number of repeaters/regenerators in this HDSL2/SHDSL span.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..32) · OCTET STRING · hint 255t

This object is a pointer to a span configuration profile in the hdsl2ShdslSpanConfProfileTable, which applies to this span. The value of this object is the index of the referenced profile in the hdsl2ShdslSpanConfProfileTable. Note that span configuration profiles are only applicable to SHDSL lines. HDSL2 lines MUST reference the default profile, 'DEFVAL'. By default, this object will have the value 'DEFVAL' (the index of the default profile). Any attempt to set this object to a value that is not the value of the index for an active entry in the profile table, hdsl2ShdslSpanConfProfileTable, MUST be rejected.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..32) · OCTET STRING · hint 255t

This object is a pointer to an alarm configuration profile in the hdsl2ShdslEndpointAlarmConfProfileTable. The value of this object is the index of the referenced profile in the hdsl2ShdslEndpointAlarmConfProfileTable. The alarm threshold configuration in the referenced profile will be used by default for all segment endpoints in this span. Individual endpoints may override this profile by explicitly specifying some other profile in the hdsl2ShdslEndpointConfTable. By default, this object will have the value 'DEFVAL' (the index of the default profile). Any attempt to set this object to a value that is not the value of the index for an active entry in the profile table, hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected.

Unsigned32 (0..8)

Contains the actual number of repeaters/regenerators discovered in this HDSL2/SHDSL span.

Unsigned32 · bps

Contains the maximum attainable line rate in this HDSL2/SHDSL span. This object provides the maximum rate the line is capable of achieving. This is based upon measurements made during line probing. This rate includes payload (user data) and any applicable framing overhead.

Unsigned32 · bps

Contains the actual line rate in this HDSL2/SHDSL span. This SHOULD equal ifSpeed. This rate includes payload (user data) and any applicable framing overhead

Hdsl2ShdslTransmissionModeTypeContains the regional setting of the HDSL2/SHDSL span, represented as a bit-map of possible settings. The various bit positions are as follows: Bit Meaning Description 1 region 1 Indicates ITU-T G.991.2 Annex A. 2 region 2 Indicates ITU-T G.991.2 Annex B. · BITS

Contains the current Power Spectral Density (PSD) regional setting of the HDSL2/SHDSL span.

Unsigned32 · bps

Contains the maximum attainable payload (user data) line rate in this HDSL2/SHDSL span. This object provides the maximum rate the line is capable of achieving. This is based upon measurements made during line probing. Any framing overhead is not included.

Unsigned32 · bps

Contains the actual line rate in this HDSL2/SHDSL span. Any framing overhead is not included.

Hdsl2ShdslUnitId1 = xtuC2 = xtuR3 = xru14 = xru25 = xru36 = xru47 = xru58 = xru69 = xru710 = xru8This is the unique identification for all units in an HDSL2/SHDSL span. It is based on the EOC unit addressing scheme with reference to the xtuC. · Integer32

Each entry in this table corresponds to a physical element in an HDSL2/SHDSL span. It is based on the EOC unit addressing scheme with reference to the xtuC.

OCTET STRING SIZE (8)

Vendor ID as reported in an Inventory Response message. ⓘ

OCTET STRING SIZE (12)

Vendor model number as reported in an Inventory Response message. ⓘ

OCTET STRING SIZE (12)

Vendor serial number as reported in an Inventory Response message. ⓘ

Integer32

Vendor EOC version as reported in a Discovery Response message. ⓘ

Integer32

Version of the HDSL2/SHDSL standard implemented, as reported in an Inventory Response message. ⓘ

OCTET STRING SIZE (3)

Vendor list number as reported in an Inventory Response message. ⓘ

OCTET STRING SIZE (2)

Vendor issue number as reported in an Inventory Response message. ⓘ

OCTET STRING SIZE (6)

Vendor software version as reported in an Inventory Response message. ⓘ

OCTET STRING SIZE (10)

Equipment code conforming to ANSI T1.213, Coded Identification of Equipment Entities. ⓘ

OCTET STRING SIZE (12)

Other vendor information as reported in an Inventory Response message. ⓘ

Hdsl2ShdslTransmissionModeTypeContains the regional setting of the HDSL2/SHDSL span, represented as a bit-map of possible settings. The various bit positions are as follows: Bit Meaning Description 1 region 1 Indicates ITU-T G.991.2 Annex A. 2 region 2 Indicates ITU-T G.991.2 Annex B. · BITS

Contains the transmission mode capability of the SHDSL unit.

Hdsl2ShdslUnitSide1 = networkSide2 = customerSideThis is the referenced side of an HDSL2/SHDSL unit - Network or Customer side. The side facing the Network is the Network side, while the side facing the Customer is the Customer side. · Integer32

The side of the unit associated with this segment endpoint -- Network/Customer side -- as per the Hdsl2ShdslUnitSide textual convention.

Hdsl2ShdslWirePair1 = wirePair12 = wirePair23 = wirePair34 = wirePair4This is the referenced pair of wires in an HDSL2/SHDSL segment. HDSL2 only supports a single pair (wirePair1 or two wire), SHDSL lines support an optional second pair (wirePair2 or four wire), and G.shdsl.bis support an optional third pair (wirePair3 or six wire) and an optional fourth pair (wirePair4 or eight wire). · Integer32

The wire pair of the modem associated with this segment endpoint as per the Hdsl2ShdslWirePair textual convention.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t

This object configures the alarm threshold values to be used for this segment endpoint. The values are obtained from the alarm configuration profile referenced by this object. The value of this object is the index of the referenced profile in the hdsl2ShdslEndpointAlarmConfProfileTable, or NULL (a zero-length SnmpAdminString). If the value is a zero-length SnmpAdminString, the endpoint uses the default Alarm Configuration Profile for the associated span as per the hdsl2ShdslSpanConfAlarmProfile object in the hdsl2ShdslSpanConfTable. The default value of this object is a zero-length SnmpAdminString. Any attempt to set this object to a value that is not the value of the index for an active entry in the profile table, hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected.

Integer32 (-127..128) · dB

The current loop attenuation for this endpoint as reported in a Network or Customer Side Performance Status message. ⓘ

Integer32 (-127..128) · dB

The current SNR margin for this endpoint as reported in a Status Response/SNR message. ⓘ

BITS

Contains the current state of the endpoint. This is a bit-map of possible conditions. The various bit positions are as follows: noDefect There are no defects on the line. powerBackoff Indicates enhanced Power Backoff. deviceFault Indicates that a vendor-dependent diagnostic or self-test fault has been detected. dcContinuityFault Indicates vendor-dependent conditions that interfere with span powering such as short and open circuits. snrMarginAlarm Indicates that the SNR margin has dropped below the alarm threshold. loopAttenuationAlarm Indicates that the loop attenuation exceeds the alarm threshold. loswFailureAlarm Indicates a forward LOSW alarm. configInitFailure Endpoint failure during initialization due to paired endpoint not able to support requested configuration. protocolInitFailure Endpoint failure during initialization due to incompatible protocol used by the paired endpoint. noNeighborPresent Endpoint failure during initialization due to no activation sequence detected from paired endpoint. loopbackActive A loopback is currently active at this segment endpoint. This is intended to supplement ifOperStatus. Note that there is a 1:1 relationship between the status bits defined in this object and the notification thresholds defined elsewhere in this MIB module. ⓘ

Counter32 · seconds

Count of Errored Seconds (ES) on this endpoint since the xU was last restarted. ⓘ

Counter32 · seconds

Count of Severely Errored Seconds (SES) on this endpoint since the xU was last restarted. ⓘ

Counter32 · detected CRC Anomalies

Count of CRC anomalies on this endpoint since the xU was last restarted. ⓘ

Counter32 · seconds

Count of Loss of Sync Word (LOSW) Seconds on this endpoint since the xU was last restarted. ⓘ

Counter32 · seconds

Count of Unavailable Seconds (UAS) on this endpoint since the xU was last restarted. ⓘ

Hdsl2ShdslPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the current interval exceeds the maximum value, the agent will return the maximum value. For 15-minute intervals, the range is limited to (0..899). For 24-hour intervals, the range is limited to (0..86399). (0..86399) · Unsigned32 · hint d · seconds

Total elapsed seconds in the current 15-minute interval.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

Count of Errored Seconds (ES) in the current 15-minute interval. ⓘ

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

Count of Severely Errored Seconds (SES) in the current 15-minute interval. ⓘ

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · detected CRC Anomalies

Count of CRC anomalies in the current 15-minute interval. ⓘ

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

Count of Loss of Sync Word (LOSW) Seconds in the current 15-minute interval. ⓘ

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

Count of Unavailable Seconds (UAS) in the current 15-minute interval. ⓘ

Hdsl2ShdslPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the current interval exceeds the maximum value, the agent will return the maximum value. For 15-minute intervals, the range is limited to (0..899). For 24-hour intervals, the range is limited to (0..86399). (0..86399) · Unsigned32 · hint d · seconds

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

Hdsl2ShdslPerfCurrDayCountA gauge associated with interface performance measurements in a current 1-day (24 hour) measurement interval. The value of this gauge starts at zero at the beginning of an interval and is increased when associated events occur, until the end of the 1-day interval. At that time, the value of the gauge is stored in the previous 1-day history interval, as defined in a companion object of type Hdsl2Shdsl1DayIntevalCount, and the current interval gauge is restarted at zero. In the case where the agent has no valid data available for this interval, the corresponding object instance is not available, and upon a retrieval request, a corresponding error message shall be returned to indicate that this instance does not exist. Please note that zero is a valid value. · Gauge32 · hint d · seconds

Count of Errored Seconds (ES) during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed. ⓘ

Hdsl2ShdslPerfCurrDayCountA gauge associated with interface performance measurements in a current 1-day (24 hour) measurement interval. The value of this gauge starts at zero at the beginning of an interval and is increased when associated events occur, until the end of the 1-day interval. At that time, the value of the gauge is stored in the previous 1-day history interval, as defined in a companion object of type Hdsl2Shdsl1DayIntevalCount, and the current interval gauge is restarted at zero. In the case where the agent has no valid data available for this interval, the corresponding object instance is not available, and upon a retrieval request, a corresponding error message shall be returned to indicate that this instance does not exist. Please note that zero is a valid value. · Gauge32 · hint d · seconds

Count of Severely Errored Seconds (SES) during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed. ⓘ

Hdsl2ShdslPerfCurrDayCountA gauge associated with interface performance measurements in a current 1-day (24 hour) measurement interval. The value of this gauge starts at zero at the beginning of an interval and is increased when associated events occur, until the end of the 1-day interval. At that time, the value of the gauge is stored in the previous 1-day history interval, as defined in a companion object of type Hdsl2Shdsl1DayIntevalCount, and the current interval gauge is restarted at zero. In the case where the agent has no valid data available for this interval, the corresponding object instance is not available, and upon a retrieval request, a corresponding error message shall be returned to indicate that this instance does not exist. Please note that zero is a valid value. · Gauge32 · hint d · detected CRC Anomalies

Count of CRC anomalies during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed. ⓘ

Hdsl2ShdslPerfCurrDayCountA gauge associated with interface performance measurements in a current 1-day (24 hour) measurement interval. The value of this gauge starts at zero at the beginning of an interval and is increased when associated events occur, until the end of the 1-day interval. At that time, the value of the gauge is stored in the previous 1-day history interval, as defined in a companion object of type Hdsl2Shdsl1DayIntevalCount, and the current interval gauge is restarted at zero. In the case where the agent has no valid data available for this interval, the corresponding object instance is not available, and upon a retrieval request, a corresponding error message shall be returned to indicate that this instance does not exist. Please note that zero is a valid value. · Gauge32 · hint d · seconds

Count of Loss of Sync Word (LOSW) Seconds during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed. ⓘ

Hdsl2ShdslPerfCurrDayCountA gauge associated with interface performance measurements in a current 1-day (24 hour) measurement interval. The value of this gauge starts at zero at the beginning of an interval and is increased when associated events occur, until the end of the 1-day interval. At that time, the value of the gauge is stored in the previous 1-day history interval, as defined in a companion object of type Hdsl2Shdsl1DayIntevalCount, and the current interval gauge is restarted at zero. In the case where the agent has no valid data available for this interval, the corresponding object instance is not available, and upon a retrieval request, a corresponding error message shall be returned to indicate that this instance does not exist. Please note that zero is a valid value. · Gauge32 · hint d · seconds

Count of Unavailable Seconds (UAS) during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed. ⓘ

INTEGER1 = normal2 = reversed · Integer32

This object indicates the state of the tip/ring for the wire pair.

INTEGER1 = preActivation2 = activation3 = data · Integer32

This object indicates the activation or training state of the wire pair. ⓘ

Unsigned32 (1..96)

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

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

Count of Errored Seconds (ES) during the interval. ⓘ

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

Count of Severely Errored Seconds (SES) during the interval. ⓘ

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · detected CRC Anomalies

Count of CRC anomalies during the interval. ⓘ

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

Count of Loss of Sync Word (LOSW) Seconds during the interval. ⓘ

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

Count of Unavailable Seconds (UAS) during the interval. ⓘ

Unsigned32 (1..30)

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

Hdsl2ShdslPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the current interval exceeds the maximum value, the agent will return the maximum value. For 15-minute intervals, the range is limited to (0..899). For 24-hour intervals, the range is limited to (0..86399). (0..86399) · Unsigned32 · hint d · seconds

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.

Hdsl2Shdsl1DayIntervalCountA counter associated with interface performance measurements during the most previous 1-day (24 hour) measurement interval. The value of this gauge is equal to the value of the current day gauge, as defined in a companion object of type Hdsl2ShdslPerfCurrDayCount, at the end of its most recent interval. In the case where the agent has no valid data available for this interval, the corresponding object instance is not available, and upon a retrieval request, a corresponding error message shall be returned to indicate that this instance does not exist. · Gauge32 · hint d · seconds

Count of Errored Seconds (ES) during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs. ⓘ

Hdsl2Shdsl1DayIntervalCountA counter associated with interface performance measurements during the most previous 1-day (24 hour) measurement interval. The value of this gauge is equal to the value of the current day gauge, as defined in a companion object of type Hdsl2ShdslPerfCurrDayCount, at the end of its most recent interval. In the case where the agent has no valid data available for this interval, the corresponding object instance is not available, and upon a retrieval request, a corresponding error message shall be returned to indicate that this instance does not exist. · Gauge32 · hint d · seconds

Count of Severely Errored Seconds (SES) during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs. ⓘ

Hdsl2Shdsl1DayIntervalCountA counter associated with interface performance measurements during the most previous 1-day (24 hour) measurement interval. The value of this gauge is equal to the value of the current day gauge, as defined in a companion object of type Hdsl2ShdslPerfCurrDayCount, at the end of its most recent interval. In the case where the agent has no valid data available for this interval, the corresponding object instance is not available, and upon a retrieval request, a corresponding error message shall be returned to indicate that this instance does not exist. · Gauge32 · hint d · detected CRC Anomalies

Count of CRC anomalies during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs. ⓘ

Hdsl2Shdsl1DayIntervalCountA counter associated with interface performance measurements during the most previous 1-day (24 hour) measurement interval. The value of this gauge is equal to the value of the current day gauge, as defined in a companion object of type Hdsl2ShdslPerfCurrDayCount, at the end of its most recent interval. In the case where the agent has no valid data available for this interval, the corresponding object instance is not available, and upon a retrieval request, a corresponding error message shall be returned to indicate that this instance does not exist. · Gauge32 · hint d · seconds

Count of Loss of Sync Word (LOSW) Seconds during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs. ⓘ

Hdsl2Shdsl1DayIntervalCountA counter associated with interface performance measurements during the most previous 1-day (24 hour) measurement interval. The value of this gauge is equal to the value of the current day gauge, as defined in a companion object of type Hdsl2ShdslPerfCurrDayCount, at the end of its most recent interval. In the case where the agent has no valid data available for this interval, the corresponding object instance is not available, and upon a retrieval request, a corresponding error message shall be returned to indicate that this instance does not exist. · Gauge32 · hint d · seconds

Count of Unavailable Seconds (UAS) during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs. ⓘ

INTEGER1 = noLoopback2 = normalLoopback3 = specialLoopback · Integer32

This object controls configuration of loopbacks for the associated segment endpoint. The status of the loopback is obtained via the hdsl2ShdslEndpointCurrStatus object.

INTEGER1 = normal2 = reversed · Integer32

This object indicates the state of the tip/ring pair at the associated segment endpoint.

INTEGER1 = default2 = enhanced · Integer32

This object configures the receiver at the associated segment endpoint to operate in default or enhanced power backoff mode.

INTEGER1 = ready2 = restart · Integer32

This object enables the manager to trigger a soft restart of the modem at the associated segment endpoint. The manager may only set this object to the 'restart(2)' value, which initiates a restart. The agent will perform a restart after approximately 5 seconds. Following the 5 second period, the agent will restore the object to the 'ready(1)' state.

Integer32 (0..4095) · minutes

This object configures the timeout value for loopbacks initiated at segments endpoints contained in the associated unit. A value of 0 disables the timeout.

INTEGER1 = local2 = span · Integer32

This object indicates the DC power source being used by the associated unit.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..32) · OCTET STRING · hint 255t

This object is the unique index associated with this profile. Entries in this table are referenced via the object hdsl2ShdslSpanConfProfile in Hdsl2ShdslSpanConfEntry.

INTEGER1 = twoWire2 = fourWire3 = sixWire4 = eightWire · Integer32

This object configures the two-wire or optional four-wire, six-wire, or eight-wire operation for SHDSL lines.

Unsigned32 · bps

This object configures the minimum transmission rate for the associated SHDSL Line in bits-per-second (bps) and includes both payload (user data) and any applicable framing overhead. If the minimum line rate equals the maximum line rate (hdsl2ShdslSpanMaxLineRate), the line rate is considered 'fixed'. If the minimum line rate is less than the maximum line rate, the line rate is considered 'rate-adaptive'.

Unsigned32 · bps

This object configures the maximum transmission rate for the associated SHDSL Line in bits-per-second (bps) and includes both payload (user data) and any applicable framing overhead. If the minimum line rate equals the maximum line rate (hdsl2ShdslSpanMaxLineRate), the line rate is considered 'fixed'. If the minimum line rate is less than the maximum line rate, the line rate is considered 'rate-adaptive'.

INTEGER1 = symmetric2 = asymmetric · Integer32

This object configures use of symmetric/asymmetric PSD (Power Spectral Density) Mask for the associated SHDSL Line. Support for symmetric PSD is mandatory for all supported data rates. Support for asymmetric PSD is optional.

Hdsl2ShdslTransmissionModeTypeContains the regional setting of the HDSL2/SHDSL span, represented as a bit-map of possible settings. The various bit positions are as follows: Bit Meaning Description 1 region 1 Indicates ITU-T G.991.2 Annex A. 2 region 2 Indicates ITU-T G.991.2 Annex B. · BITS

This object specifies the regional setting for the SHDSL line.

INTEGER1 = enabled2 = disabled · Integer32

This object enables/disables support for remote management of the units in an SHDSL line from the STU-R via the EOC.

INTEGER1 = noPower2 = powerFeed3 = wettingCurrent · Integer32

This object enables/disables support for optional power feeding in an SHDSL line.

Integer32 (-10..21) · dB

This object specifies the downstream current condition target SNR margin for an SHDSL line. The SNR margin is the difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.

Integer32 (-10..21) · dB

This object specifies the downstream worst-case target SNR margin for an SHDSL line. The SNR margin is the difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.

Integer32 (-10..21) · dB

This object specifies the upstream current-condition target SNR margin for an SHDSL line. The SNR margin is the difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.

Integer32 (-10..21) · dB

This object specifies the upstream worst-case target SNR margin for an SHDSL line. The SNR margin is the difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.

BITS

Indicates whether a target SNR margin is enabled or disabled. This is a bit-map of possible settings. The various bit positions are as follows: currCondDown - current-condition downstream target SNR margin enabled worstCaseDown - worst-case downstream target SNR margin enabled currCondUp - current-condition upstream target SNR margin enabled worstCaseUp - worst-case upstream target SNR margin enabled.

Hdsl2ShdslClockReferenceType1 = localClk2 = networkClk3 = dataOrNetworkClk4 = dataClkThe various STU-C symbol clock references for the HDSL2/SHDSL span, represented as an enumeration. · Integer32

This object configures the clock reference for the STU-C in an SHDSL Line.

INTEGER1 = disable2 = enable · Integer32

This object enables/disables support for Line Probe of the units in an SHDSL line. When Line Probe is enabled, the system performs Line Probing to find the best possible rate. If Line Probe is disabled, the rate adaptation phase is skipped to shorten set up time.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object controls creation/deletion of the associated entry in this table per the semantics of RowStatus. If an active entry is referenced in hdsl2ShdslSpanConfProfile, the entry MUST remain active until all references are removed.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..32) · OCTET STRING · hint 255t

This object is the unique index associated with this profile.

Integer32 (-127..128) · dB

This object configures the loop attenuation alarm threshold. When the current value of hdsl2ShdslEndpointCurrAtn reaches or exceeds this threshold, an hdsl2ShdslLoopAttenCrossing MAY be generated.

Integer32 (-127..128) · dB

This object configures the SNR margin alarm threshold. When the current value of hdsl2ShdslEndpointCurrSnrMgn reaches or drops below this threshold, a hdsl2ShdslSNRMarginCrossing MAY be generated.

Hdsl2ShdslPerfIntervalThresholdThis convention defines a range of values that may be set in a fault threshold alarm control. As the number of seconds in a 15-minute interval numbers at most 900, objects of this type may have a range of 0...900, where the value of 0 disables the alarm. (0..900) · Unsigned32 · hint d · seconds

This object configures the threshold for the number of Errored Seconds (ES) 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, an hdsl2ShdslPerfESThresh MAY be generated. At most, one notification will be sent per interval per endpoint.

Hdsl2ShdslPerfIntervalThresholdThis convention defines a range of values that may be set in a fault threshold alarm control. As the number of seconds in a 15-minute interval numbers at most 900, objects of this type may have a range of 0...900, where the value of 0 disables the alarm. (0..900) · Unsigned32 · hint d · seconds

This object configures the threshold for the number of Severely Errored Seconds (SES) 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, an hdsl2ShdslPerfSESThresh MAY be generated. At most, one notification will be sent per interval per endpoint.

Integer32 · detected CRC Anomalies

This object configures the threshold for the number of CRC anomalies within any given 15-minute performance data collection interval. If the value of CRC anomalies in a particular 15-minute collection interval reaches/exceeds this value, an hdsl2ShdslPerfCRCanomaliesThresh MAY be generated. At most, one notification will be sent per interval per endpoint.

Hdsl2ShdslPerfIntervalThresholdThis convention defines a range of values that may be set in a fault threshold alarm control. As the number of seconds in a 15-minute interval numbers at most 900, objects of this type may have a range of 0...900, where the value of 0 disables the alarm. (0..900) · Unsigned32 · hint d · seconds

This object configures the threshold for the number of Loss of Sync Word (LOSW) Seconds within any given 15-minute performance data collection interval. If the value of LOSW in a particular 15-minute collection interval reaches/exceeds this value, an hdsl2ShdslPerfLOSWSThresh MAY be generated. At most, one notification will be sent per interval per endpoint.

Hdsl2ShdslPerfIntervalThresholdThis convention defines a range of values that may be set in a fault threshold alarm control. As the number of seconds in a 15-minute interval numbers at most 900, objects of this type may have a range of 0...900, where the value of 0 disables the alarm. (0..900) · Unsigned32 · hint d · seconds

This object configures the threshold for the number of Unavailable Seconds (UAS) within any given 15-minute performance data collection interval. If the value of UAS in a particular 15-minute collection interval reaches/exceeds this value, an hdsl2ShdslPerfUASThresh MAY be generated. At most, one notification will be sent per interval per endpoint.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object controls creation/deletion of the associated entry in this table as per the semantics of RowStatus. If an active entry is referenced in either hdsl2ShdslSpanConfAlarmProfile or hdsl2ShdslEndpointAlarmConfProfile, the entry MUST remain active until all references are removed.