Network Working Group M. Morgenstern Internet-Draft ECI Telecom Ltd. Expires: July 5, 2006 S. Baillie U. Bonollo NEC Australia January 2006 Definitions of Managed Objects for Very High Speed Digital Subscriber Line 2 (VDSL2) draft-ietf-adslmib-vdsl2-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on July 5, 2006. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes objects used for managing parameters of the "Very High Speed Digital Subscriber Line 2 (VDSL2)" interface type, which are also applicable for managing ADSL, ADSL2, and ADSL2+ Morgenstern, et al. Expires July 5, 2006 [Page 1] Internet-Draft VDSL2-LINE MIB January 2006 interfaces. Table of Contents 1. The Internet-Standard Management Framework . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Relationship to other MIBs . . . . . . . . . . . . . . . 4 2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 6 2.3. Conventions Used in the MIB Module . . . . . . . . . . . 7 2.4. Structure . . . . . . . . . . . . . . . . . . . . . . . . 13 2.5. Persistence . . . . . . . . . . . . . . . . . . . . . . . 16 2.6. Line Topology . . . . . . . . . . . . . . . . . . . . . . 18 2.7. Counters, Interval Buckets, and Thresholds . . . . . . . 19 2.8. Profiles . . . . . . . . . . . . . . . . . . . . . . . . 21 2.9. Notifications . . . . . . . . . . . . . . . . . . . . . . 25 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 26 4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 153 5. Security Considerations . . . . . . . . . . . . . . . . . . . 153 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 160 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 161 7.1. Normative References . . . . . . . . . . . . . . . . . . 161 7.2. Informative References . . . . . . . . . . . . . . . . . 162 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 163 Intellectual Property and Copyright Statements . . . . . . . . . 164 Morgenstern, et al. Expires July 5, 2006 [Page 2] Internet-Draft VDSL2-LINE MIB January 2006 1. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to Section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 2. Overview This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet community for the purpose of managing VDSL2, ADSL, ADSL2, and ADSL2+ lines. The MIB module described in RFC 2662 [RFC2662] describes objects used for managing Asymmetric Bit-Rate DSL (ADSL) interfaces per [T1E1.413], [G.992.1], and [G.992.2]. These object descriptions are based upon the specifications for the ADSL Embedded Operations Channel (EOC) as defined in American National Standards Institute (ANSI) T1E1.413/1995 [T1E1.413] and International Telecommunication Union (ITU-T) G.992.1 [G.992.1] and G.992.2 [G.992.2]. The MIB module described in RFC xxxx (draft-ietf-adslmib-adsl2-05.txt) is a wider management model that includes, in addition to ADSL technology, the ADSL2 and ADSL2+ technologies per G.992.3, G.992.4, and G.992.5 ([G.992.3], [G.992.4], and [G.992.5] respectively). This document does not obsolete RFC 2662 [RFC2662], or RFC xxxx (draft-ietf-adslmib-adsl2-05.txt) but rather provides a more comprehensive management model that addresses the VDSL2 technology per G.993.2 ([G.993.2]) as well as ADSL, ADSL2 and ADSL2+ technologies. Additionally, the management framework for VDSL2 lines [TR-129] specified by the Digital Subscriber Line Forum (DSLF) has been taken Morgenstern, et al. Expires July 5, 2006 [Page 3] Internet-Draft VDSL2-LINE MIB January 2006 into consideration. That framework is based on ITU-T G.997.1 standard [G.997.1]. Note that the management model according to this document does not allow managing VDSL technology per G.993.1 ([G.993.1]). VDSL lines MUST be managed by RFC 3728 [RFC3728]. The MIB module is located in the MIB tree under MIB 2 transmission, as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of this document. 2.1. Relationship to other MIBs This section outlines the relationship of this MIB module with other MIB modules described in RFCs. Specifically, IF-MIB as presented in RFC 2863 [RFC2863] is discussed. 2.1.1. General IF-MIB Integration (RFC 2863) The VDSL2 Line MIB specifies the detailed attributes of a data interface. As such, it needs to integrate with RFC 2863 [RFC2863]. The IANA has assigned the following ifTypes, which may be applicable for VDSL2 lines as well as for ADSL, ADSL2 and ADSL2+ lines: IANAifType ::= TEXTUAL-CONVENTION ... SYNTAX INTEGER { ... channel(70), -- channel ADSL (94), -- Asymmetric Digital Subscriber Loop ... Interleave(124), -- Interleaved Channel Fast(125), -- Fast Channel ... ADSL2 (230), -- Asymmetric Digital Subscriber Loop 2 VDSL2 (xxx), -- Very High Speed Digital Subscriber Loop 2 ... } ADSL lines that are identified with ifType=ADSL (94) MUST be managed with the MIB specified by RFC2662. ADSL, ADSL2, and ADSL2+ lines identified with ifType=ADSL2 (230) MUST be managed with the MIB specified by RFC xxxx (draft-ietf-adslmib-adsl2-05.txt). VDSL2, ADSL, ADSL2, and ADSL2+ lines identified with ifType=VDSL2 (xxx) MUST be managed with the MIB specified by this document. In any case, the SNMP agent may use either ifType=Interleave (124) or Fast (125) for each channel, e.g., depending on whether or not it is Morgenstern, et al. Expires July 5, 2006 [Page 4] Internet-Draft VDSL2-LINE MIB January 2006 capable of using an interleaver on that channel. It may use the ifType=channel (70) when all channels are capable of using an interleaver (e.g., for ADSL2 xtus). Note that the ifFixedLengthGroup from RFC 2863 [RFC2863] MUST be supported and that the ifRcvAddressGroup does not apply to this MIB module. 2.1.2. Usage of ifTable The MIB branch identified by ifType contains tables appropriate for the interface types described above. Most such tables extend the ifEntry table, and are indexed by ifIndex. For interfaces in systems implementing this MIB module, those table entries indexed by ifIndex MUST be persistent. The following attributes are part of the mandatory ifGeneralInformationGroup in the Interfaces MIB [RFC2863], and are not duplicated in the VDSL2 Line MIB. =================================================================== Morgenstern, et al. Expires July 5, 2006 [Page 5] Internet-Draft VDSL2-LINE MIB January 2006 ifIndex Interface index. ifDescr See interfaces MIB. ifType VDSL2 (230) or Channel (70) or Interleave (124) or Fast (125) ifSpeed Set as appropriate. ifPhysAddress This object MUST have an octet string with zero length. ifAdminStatus See interfaces MIB. ifOperStatus See interfaces MIB. ifLastChange See interfaces MIB. ifName See interfaces MIB. ifAlias See interfaces MIB. ifLinkUpDownTrapEnable Default to enabled(1). ifHighSpeed Set as appropriate. ifConnectorPresent Set as appropriate. =================================================================== Figure 1: Use of ifTable Objects 2.2. IANA Considerations The VDSL2-LINE-MIB module requires the allocation of a new ifType value for Very High Speed Digital Subscriber Loop Version 2, to distinguish between ADSL lines that are managed with the RFC2662 management model, ADSL/ADSL2 and ADSL2+ lines that are managed with the RFC xxxx (draft-ietf-adslmib-adsl2-05.txt) management model, and VDSL2/ADSL/ADSL2 and ADSL2+ lines that are managed with the model defined in this document. Also the VDSL2-LINE-MIB module requires the allocation of a single object identifier for its MODULE-IDENTITY. The IANA should allocate this object identifier in the transmission subtree. Morgenstern, et al. Expires July 5, 2006 [Page 6] Internet-Draft VDSL2-LINE MIB January 2006 2.3. Conventions Used in the MIB Module 2.3.1. Naming Conventions atuc ADSL/ADSL2 or ADSL2+ line termination unit - Central office atur ADSL/ADSL2 or ADSL2+ line termination unit - Remote site CRC Cyclical redundancy check DELT Dual Ended Loop Test ES Errored second FEC Forward Error Correction LOF Loss of framing LOS Loss of signal LOSS LOS Second SES Severely-errored second SNR Signal-to-noise ratio UAS Unavailable second vtuc VDSL2 line termination unit - Central office vtur VDSL2 line termination unit - Remote site Xtuc ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit - Central office Xtur ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit - Remote site xtu A terminal unit; either an Xtuc or Xtur 2.3.2. Textual Conventions The following textual conventions are defined to reflect the line topology in the MIB module (further discussed in the following section), the various transmission modes, power states, synchronization states, possible values for various configuration parameters, status parameters, and other parameter types. o Xdsl2Unit: Attributes with this syntax uniquely identify each unit in the VDSL2/ADSL/ADSL2/ADSL2+ link. It mirrors the EOC addressing mechanism: xtuc(1) - central office (CO) terminal unit xtur(2) - customer premises equipment (CPE) terminal unit o Xdsl2Direction: Attributes with this syntax uniquely identify a transmission direction in a VDSL2/ADSL/ADSL2/ADSL2+ link. Upstream direction Morgenstern, et al. Expires July 5, 2006 [Page 7] Internet-Draft VDSL2-LINE MIB January 2006 is a transmission from the customer premises equipment (CPE) towards the central office (CO), while downstream direction is a transmission from the CO towards the CPE. upstream(1) - Transmission from the CPE to the CO downstream(2) - Transmission from the CO to the CPE o Xdsl2TransmissionModeType: Attributes with this syntax reference the list of possible transmission modes for VDSL2/ADSL/ADSL2 or ADSL2+. Specified as a BITS construct, there are currently a few dozen transmission modes in the list. o Xdsl2RaMode: Attributes with this syntax reference if and how Rate-Adaptive synchronization is being used on the respective VDSL2/ADSL/ADSL2 or ADSL2+ link: manual (1) - No Rate-Adaptation. The initialization process attempts to synchronize to a specified rate. rainit (2) - Rate-Adaptation during initialization process only, which attempts to synchronize to a rate between minimum and maximum specified values. dynamicRa (3) - Dynamic Rate-Adaptation during initialization process as well as during SHOWTIME. o Xdsl2InitResult: Attributes with this syntax reference the recent result of a full initialization attempt: noFail (0) - Successful initialization configError (1) - Configuration failure configNotFeasible (2) - Configuration details not supported commFail (3) - Communication failure noPeerAtu (4) - Peer ATU not detected otherCause (5) - Other initialization failure reason o Xdsl2OperationModes: Attributes with this syntax uniquely identify an XDSL mode, which is a category associated with each transmission mode defined for the VDSL2/ADSL/ADSL2 or ADSL2+ link. Part of the line configuration profile depends on the XDSL Mode: Morgenstern, et al. Expires July 5, 2006 [Page 8] Internet-Draft VDSL2-LINE MIB January 2006 ------***************************************************** ----- The following list will be changed. Instead of the ----- the current list we'll add a list that follows the xTSE ------***************************************************** defMode (1), - The default/generic PSD configuration. The default configuration will be used when no other matching mode specific configuration can be found. adsl (2), - ADSL (POTS or ISDN) adsl2Pots (3), - ADSL2 (ISDN) adsl2Isdn (4), - ADSL2 (ISDN) adsl2PlusPots (5), - ADSL2+ (POTS) adsl2PlusIsdn (6), - ADSL2+ (ISDN) adsl2ReachExtended (7)- Reach Extended ADSL2 o Xdsl2PowerMngState: Attributes with this syntax uniquely identify each power management state defined for the VDSL2/ADSL/ADSL2 or ADSL2+ link. For VDSL2 links only L0 and L3 states are supported: l0(1) - L0 - Full power management state l1(2) - L1 - Low power management state (for G.992.2) l2(3) - L2 - Low power management state (for G.992.3, G.992.4, and G.992.5) l3(4) - L3 - Idle power management state o Xdsl2ConfPmsForce: Attributes with this syntax are configuration parameters that reference the desired power management state for the VDSL2/ADSL/ ADSL2 or ADSL2+ link. For VDSL2 links only L0 and L3 states are supported: l3toL0 (0) - Perform a transition from L3 to L0 (Full power management state) l0toL2 (2) - Perform a transition from L0 to L2 (Low power management state) l0orL2toL3 (3) - Perform a transition into L3 (Idle power management state) o Xdsl2LConfProfPmMode: Attributes with this syntax are configuration parameters that reference the power modes/states into which the xTU-C or xTU-R may autonomously transit. Morgenstern, et al. Expires July 5, 2006 [Page 9] Internet-Draft VDSL2-LINE MIB January 2006 This is a BITS structure that allows control of the following transit options: allowTransitionsToIdle (0) - xTU may autonomously transit to idle (L3) state. allowTransitionsToLowPower (1)- xTU may autonomously transit to low-power (L2) state. o Xdsl2LineLdsf: Attributes with this syntax are configuration parameters that control the Loop Diagnostic mode for the VDSL2/ADSL/ADSL2 or ADSL2+ link: inhibit (0) - Inhibit Loop Diagnostic mode force (1) - Force/Initiate Loop Diagnostic mode o Xdsl2LdsfResult: Attributes with this syntax are status parameters that report the result of the recent Loop Diagnostic mode issued for the VDSL2/ ADSL/ADSL2 or ADSL2+ link: 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 because the relevant line is administratively 'Up'. tableFull (10) - The NE cannot initiate the command, due to reaching the maximum number of rows in the results table. noResources (11) - The NE cannot initiate the command, due to lack of internal memory resources. Morgenstern, et al. Expires July 5, 2006 [Page 10] Internet-Draft VDSL2-LINE MIB January 2006 o Xdsl2SymbolProtection: Attributes with this syntax are configuration parameters that reference the minimum length impulse noise protection (INP) in terms of number of symbols: noProtection (1) - INP not required halfSymbol (2) - INP length = 1/2 symbol singleSymbol (3) - INP length = 1 symbol twoSymbols (4) - INP length = 2 symbols threeSymbols (5) - INP length = 3 symbols fourSymbols (6) - INP length = 4 symbols fiveSymbols (7) - INP length = 5 symbols sixSymbols (8) - INP length = 6 symbols sevenSymbols (9) - INP length = 7 symbols eightSymbols (10) - INP length = 8 symbols nineSymbols (11) - INP length = 9 symbols tenSymbols (12) - INP length = 10 symbols elevenSymbols (13) - INP length = 11 symbols twelveSymbols (14) - INP length = 12 symbols thirteeSymbols (15)- INP length = 13 symbols fourteenSymbols (16)-INP length = 14 symbols fifteenSymbols (17)- INP length = 15 symbols sixteenSymbols (18)- INP length = 16 symbols o Xdsl2MaxBer: Attributes with this syntax are configuration parameters that reference the maximum Bit Error Rate (BER): eminus3 (1) - Maximum BER=E^-3 eminus5 (2) - Maximum BER=E^-5 eminus7 (3) - Maximum BER=E^-7 o Xdsl2ScMaskDs: Attributes with this syntax are configuration parameters that reference the downstream sub-carrier mask. It is a bitmap of up to 4096 bits. o Xdsl2ScMaskUs: Attributes with this syntax are configuration parameters that reference the upstream sub-carrier mask. It is a bitmap of up to 4096 bits. Morgenstern, et al. Expires July 5, 2006 [Page 11] Internet-Draft VDSL2-LINE MIB January 2006 o Xdsl2RfiDs: Attributes with this syntax are configuration parameters that reference the downstream notch filters. It is a bitmap of up to 4096 bits. o Xdsl2PsdMaskDs: Attributes with this syntax are configuration parameters that reference the downstream power spectrum density (PSD) mask. It is a structure of up to 32 breakpoints, where each breakpoint occupies 3 octets. o Xdsl2PsdMaskUs: Attributes with this syntax are configuration parameters that reference the upstream power spectrum density (PSD) mask. It is a structure of up to 16 breakpoints, where each breakpoint occupies 3 octets. o Xdsl2Tssi: Attributes with this syntax are status parameters that reference the transmit spectrum shaping (TSSi). It is a structure of up to 32 breakpoints, where each breakpoint occupies 3 octets. o Xdsl2LastTransmittedState: Attributes with this syntax reference the list of initialization states for VDSL2/ADSL/ADSL2 or ADSL2+ modems. The list of states for CO side modems is different from the list of states for the CPE side modems. Specified as an enumeration type, there are currently a few dozen states in the list per each unit side (i.e., CO and CPE). o Xdsl2LineStatus: Attributes with this syntax are status parameters that reflect the failure status for a given endpoint of VDSL2/ADSL/ADSL2 or ADSL2+ link. This is a BITS structure that can report the following failures: Morgenstern, et al. Expires July 5, 2006 [Page 12] Internet-Draft VDSL2-LINE MIB January 2006 noDefect (0) - This bit position positively reports that no defect or failure exist. lossOfFraming (1) - Loss of frame synchronization lossOfSignal (2) - Loss of signal lossOfPower (3) - Loss of power. Usually this failure may be reported for CPE units only initFailure (4) - Recent initialization process failed. Never active on xTU-R. o Xdsl2ChAtmStatus: Attributes with this syntax are status parameters that reflect the failure status for Transmission Convergence (TC) layer of a given ATM interface (data path over a VDSL2/ADSL/ADSL2 or ADSL2+ link). This is a BITS structure that can report the following failures: noDefect (0) - This bit position positively reports that no defect or failure exist. noCellDelineation (1) - The link was successfully initialized but cell delineation was never acquired on the associated ATM data path. lossOfCellDelineation (2)- Loss of cell delineation on the associated ATM data path o Xdsl2ChPtmStatus: Attributes with this syntax are status parameters that reflect the failure status for a given PTM interface (packet data path over a VDSL2/ADSL/ADSL2 or ADSL2+ link). This is a BITS structure that can report the following failures: noDefect (0) - This bit position positively reports that no defect or failure exist. outOfSync (1) - Out of synchronization. 2.4. Structure The MIB module is structured into following MIB groups: o Line Configuration, Maintenance, and Status Group: This group supports MIB objects for configuring parameters for the Morgenstern, et al. Expires July 5, 2006 [Page 13] Internet-Draft VDSL2-LINE MIB January 2006 VDSL2/ADSL/ADSL2 or ADSL2+ line and retrieving line status information. It also supports MIB objects for configuring a requested power state or initiating a Dual Ended Line Test (DELT) process in the VDSL2/ADSL/ADSL2 or ADSL2+ line. It contains the following table: - xdsl2LineTable o Channel Status Group: This group supports MIB objects for retrieving channel layer status information. It contains the following table: - xdsl2ChannelStatusTable o Subcarrier Status Group: This group supports MIB objects for retrieving the sub-carrier layer status information, mostly collected by a Dual Ended Line Test (DELT) process. It contains the following table: - xdsl2SCStatusTable o Unit Inventory Group: This group supports MIB objects for retrieving Unit inventory information about units in VDSL2/ADSL/ADSL2 or ADSL2+ lines via the EOC. It contains the following table: - xdsl2LineInventoryTable o Current Performance Group: This group supports MIB objects that provide the current performance information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, units and channels level. It contains the following tables: - xdsl2PMLineCurrTable - xdsl2PMLineCurrInitTable - xdsl2PMChCurrTable o 15-Minute Interval Performance Group: This group supports MIB objects that provide historic performance information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, units and channels level in 15-minute intervals. It contains the following tables: Morgenstern, et al. Expires July 5, 2006 [Page 14] Internet-Draft VDSL2-LINE MIB January 2006 - xdsl2PMLineHist15MinTable - xdsl2PMLineInitHist15MinTable - xdsl2PMChHist15MinTable o 1-Day Interval Performance Group: This group supports MIB objects that provide historic performance information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, units and channels level in 1-day intervals. It contains the following tables: - xdsl2PMLineHist1DayTable - xdsl2PMLineInitHist1DayTable - xdsl2PMChHist1DTable o Configuration Template and Profile Group: This group supports MIB objects for defining configuration profiles for VDSL2/ADSL/ADSL2 and ADSL2+ lines and channels, as well as configuration templates. Each configuration template is comprised of one line configuration profile and one or more channel configuration profiles. This group contains the following tables: - xdsl2LineConfTemplateTable - xdsl2LineConfProfTable - xdsl2LineConfProfModeSpecTable - xdsl2ChConfProfileTable o Alarm Configuration Template and Profile Group: This group supports MIB objects for defining alarm profiles for VDSL2/ADSL/ADSL2 and ADSL2+ lines and channels, as well as alarm templates. Each alarm template is comprised of one line alarm profile and one or more channel alarm profiles. This group contains the following tables: - xdsl2LineAlarmConfTemplateTable - xdsl2LineAlarmConfProfileTable - xdsl2ChAlarmConfProfileTable o Notifications Group: This group defines the notifications supported for VDLS2/ADSL/ ADSL2 and ADSL2+ lines: Morgenstern, et al. Expires July 5, 2006 [Page 15] Internet-Draft VDSL2-LINE MIB January 2006 - xdsl2LinePerfFECSThreshXtuc - xdsl2LinePerfFECSThreshXtur - xdsl2LinePerfESThreshXtuc - xdsl2LinePerfESThreshXtur - xdsl2LinePerfSESThreshXtuc - xdsl2LinePerfSESThreshXtur - xdsl2LinePerfLOSSThreshXtuc - xdsl2LinePerfLOSSThreshXtur - xdsl2LinePerfUASThreshXtuc - xdsl2LinePerfUASThreshXtur - xdsl2LinePerfCodingViolationsThreshXtuc - xdsl2LinePerfCodingViolationsThreshXtur - xdsl2LinePerfCorrectedThreshXtuc - xdsl2LinePerfCorrectedThreshXtur - xdsl2LinePerfFailedFullInitThresh - xdsl2LinePerfFailedShortInitThresh - xdsl2LineStatusChangeXtuc - xdsl2LineStatusChangeXtur 2.5. Persistence All read-create objects and most read-write objects defined in this MIB module SHOULD be stored persistently. Following is an exhaustive list of these persistent objects: ------***************************************************** ----- The following list will probably be partially changed ------***************************************************** xdsl2LineCnfgTemplate xdsl2LineAlarmCnfgTemplate xdsl2LineCmndConfPmsf xdsl2LineCmndConfLdsf xdsl2LineCmndAutomodeColdStart xdsl2LConfTempTemplateName xdsl2LConfTempLineProfile xdsl2LConfTempChan1ConfProfile xdsl2LConfTempChan1RaRatioDs xdsl2LConfTempChan1RaRatioUs xdsl2LConfTempChan2ConfProfile xdsl2LConfTempChan2RaRatioDs xdsl2LConfTempChan2RaRatioUs xdsl2LConfTempChan3ConfProfile xdsl2LConfTempChan3RaRatioDs xdsl2LConfTempChan3RaRatioUs xdsl2LConfTempChan4ConfProfile xdsl2LConfTempChan4RaRatioDs xdsl2LConfTempChan4RaRatioUs xdsl2LConfTempRowStatus Morgenstern, et al. Expires July 5, 2006 [Page 16] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2LConfProfProfileName xdsl2LConfProfScMaskDs xdsl2LConfProfScMaskUs xdsl2LConfProfRfiBandsDs xdsl2LConfProfRaModeDs xdsl2LConfProfRaModeUs xdsl2LConfProfRaUsNrmDs xdsl2LConfProfRaUsNrmUs xdsl2LConfProfRaUsTimeDs xdsl2LConfProfRaUsTimeUs xdsl2LConfProfRaDsNrmsDs xdsl2LConfProfRaDsNrmsUs xdsl2LConfProfRaDsTimeDs xdsl2LConfProfRaDsTimeUs xdsl2LConfProfTargetSnrmDs xdsl2LConfProfTargetSnrmUs xdsl2LConfProfMaxSnrmDs xdsl2LConfProfMaxSnrmUs xdsl2LConfProfMinSnrmDs xdsl2LConfProfMinSnrmUs xdsl2LConfProfMsgMinUs xdsl2LConfProfMsgMinDs xdsl2LConfProfXtuTransSysEna xdsl2LConfProfPmMode xdsl2LConfProfL0Time xdsl2LConfProfL2Time xdsl2LConfProfL2Atpr xdsl2LConfProfL2Atprt xdsl2LconfProfRowStatus xdsl2LconfProfAdslMode xdsl2LConfProfMaxNomPsdDs xdsl2LConfProfMaxNomPsdUs xdsl2LConfProfMaxNomAtpDs xdsl2LConfProfMaxNomAtpUs xdsl2LConfProfMaxAggRxPwrUs xdsl2LConfProfPsdMaskDs xdsl2LConfProfPsdMaskUs xdsl2LConfProfPsdMaskSelectUs xdsl2LConfProfModeSpecRowStatus xdsl2ChConfProfProfileName xdsl2ChConfProfMinDataRateDs xdsl2ChConfProfMinDataRateUs xdsl2ChConfProfMinResDataRateDs xdsl2ChConfProfMinResDataRateUs xdsl2ChConfProfMaxDataRateDs xdsl2ChConfProfMaxDataRateUs xdsl2ChConfProfMinDataRateLowPwrDs xdsl2ChConfProfMaxDelayDs Morgenstern, et al. Expires July 5, 2006 [Page 17] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2ChConfProfMaxDelayUs xdsl2ChConfProfMinProtectionDs xdsl2ChConfProfMinProtectionUs xdsl2ChConfProfMaxBerDs xdsl2ChConfProfMaxBerUs xdsl2ChConfProfUsDataRateDs xdsl2ChConfProfDsDataRateDs xdsl2ChConfProfUsDataRateUs xdsl2ChConfProfDsDataRateUs xdsl2ChConfProfImaEnabled xdsl2ChConfProfRowStatus xdsl2LAlarmConfTempTemplateName xdsl2LAlarmConfTempLineProfile xdsl2LAlarmConfTempChan1ConfProfile xdsl2LAlarmConfTempChan2ConfProfile xdsl2LAlarmConfTempChan3ConfProfile xdsl2LAlarmConfTempChan4ConfProfile xdsl2LAlarmConfTempRowStatus xdsl2LineAlarmConfProfileName xdsl2LineAlarmConfProfileXtucThresh15MinFecs xdsl2LineAlarmConfProfileXtucThresh15MinEs xdsl2LineAlarmConfProfileXtucThresh15MinSes xdsl2LineAlarmConfProfileXtucThresh15MinLoss xdsl2LineAlarmConfProfileXtucThresh15MinUas xdsl2LineAlarmConfProfileXturThresh15MinFecs xdsl2LineAlarmConfProfileXturThresh15MinEs xdsl2LineAlarmConfProfileXturThresh15MinSes xdsl2LineAlarmConfProfileXturThresh15MinLoss xdsl2LineAlarmConfProfileXturThresh15MinUas xdsl2LineAlarmConfProfileThresh15MinFailedFullInt xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt xdsl2LineAlarmConfProfileRowStatus xdsl2ChAlarmConfProfileName xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations xdsl2ChAlarmConfProfileXtucThresh15MinCorrected xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations xdsl2ChAlarmConfProfileXturThresh15MinCorrected xdsl2ChAlarmConfProfileRowStatus Note also that the interface indices in this MIB are maintained persistently. View-based Access Control Model (VACM) data relating to these SHOULD be stored persistently as well [RFC3410]. 2.6. Line Topology A VDSL2/ADSL/ADSL2 and ADSL2+ Line consists of two units: atuc or vtuc (a central office termination unit) and atur or vtur (a remote termination unit). There are up to 4 channels (maximum number of Morgenstern, et al. Expires July 5, 2006 [Page 18] Internet-Draft VDSL2-LINE MIB January 2006 channels depends on the specific DSL technology), each carrying an independent information flow, as shown in the figure below. <-- Network Side Customer Side --> || +-------+ +-------+ + |<---------------------1------------------->| + + atuc |<---------------------2------------------->| atur + | or <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| or | + vtuc |<---------------------3------------------->| vtuc + + |<---------------------4------------------->| + +-------+ +-------+ Key: VDSL2/ADSL/ADSL2/ADSL2+ Span <~~~~> VDSL2/ADSL/ADSL2/ADSL2+ twisted-pair -1- Channel #1 carried over the line -2- Optional channel #2 carried over the line -3- Optional channel #3 carried over the line -4- Optional channel #4 carried over the line Figure 2: General topology for a VDSL2/ADSL/ADSL2/ADSL2+ Line 2.7. Counters, Interval Buckets, and Thresholds 2.7.1. Counters Managed There are various types of counters specified in this MIB. Each counter refers either to the whole VDSL2/ADSL/ADSL2/ADSL2+ line, to one of the xtu entities, or to one of the bearer channels. o On the whole line level For full initializations, failed full initializations, short initializations, and for failed short initializations there are event counters, current 15-minute and 0 to 96 15-minute history bucket(s) of "interval-counters", as well as current and 0 to 30 previous 1-day interval-counter(s). Each current 15-minute "failed" event bucket has an associated threshold notification. o On the xtu level For the LOS Seconds, ES, SES, FEC seconds, and UAS, there are event counters, current 15-minute and 0 to 96 15-minute history bucket(s) of "interval-counters", as well as current and 0 to 30 previous 1-day interval-counter(s). Each current 15-minute event bucket has an Morgenstern, et al. Expires July 5, 2006 [Page 19] Internet-Draft VDSL2-LINE MIB January 2006 associated threshold notification. o On the bearer channel level For the coding violations (CRC anomalies) and corrected blocks (i.e., FEC events) there are event counters, current 15-minute and 0 to 96 15-minute history bucket(s) of "interval-counters", as well as current and 0 to 30 previous 1-day interval-counter(s). Each current 15-minute event bucket has an associated threshold notification. 2.7.2. Minimum Number Of Buckets Although it is possible to support up to 96 15-minute history buckets of "interval-counters", systems implementing this MIB module SHOULD practically support at least 16 buckets, as specified in ITU-T G.997.1, paragraph 7.2.7.2. Similarly, it is possible to support up to 30 previous 1-day "interval-counters", but systems implementing this MIB module SHOULD support at least 1 previous day buckets. 2.7.3. Interval Buckets Initialization There is no requirement for an agent to ensure a fixed relationship between the start of a 15-minute interval and any wall clock; however, some implementations may align the 15-minute intervals with quarter hours. Likewise, an implementation may choose to align one day intervals with the start of a day. Counters are not reset when an xtU is reinitialized, only when the agent is reset or reinitialized (or under specific request outside the scope of this MIB module). 2.7.4. Interval Buckets Validity As in RFC 3593 [RFC3593] and RFC 2662 [RFC2662], in case the data for an interval is suspect or known to be invalid, the agent MUST report the interval as invalid. If the current 15-minute event bucket is determined to be invalid, the element management system SHOULD ignore its content and the agent MUST NOT generate notifications based upon the value of the event bucket. A valid 15-minute event bucket SHOULD usually count the events for exactly 15 minutes. Similarly, a valid 1-day event bucket SHOULD usually count the events for exactly 24 hours. However, the following scenarios are exceptional: Morgenstern, et al. Expires July 5, 2006 [Page 20] Internet-Draft VDSL2-LINE MIB January 2006 1) For implementations that align the 15-minute intervals with quarter hours, and the 1-day intervals with start of a day, the management system may still start the PM process not aligned with the wall clock. Such a management system may wish to retrieve even partial information for the first event buckets, rather than declaring them all as invalid. 2) For an event bucket that suffered relatively short outages, the management system may wish to retrieve the available PM outcomes, rather than declaring the whole event bucket as invalid. This is more important for 1-day event buckets. 3) An event bucket may be shorter or longer than the formal duration if a clock adjustment was performed during the interval. This MIB allows supporting the exceptional scenarios described above by reporting the actual Monitoring Time of a monitoring interval. This parameter is relevant only for Valid intervals, but is useful for these exceptional scenarios: a) The management system MAY still declare a partial PM interval as Valid and report the actual number of seconds the interval lasted. b) If the interval was shortened or extended due to clock corrections, the management system SHOULD report the actual number of seconds the interval lasted, beside reporting that the interval is Valid. 2.8. Profiles As a managed node can handle a large number of xtUs, (e.g., hundreds or perhaps thousands of lines), provisioning every parameter on every xtU may become burdensome. Moreover, most lines are provisioned identically with the same set of parameters. To simplify the provisioning process, this MIB module makes use of profiles and templates. A configuration profile is a set of parameters that can be shared by multiple entities. There are configuration profiles to address the line level provisioning and another type of profile that addresses the channel level provisioning parameters. A configuration template is actually a profile-of-profiles. That is, a template is comprised of one line configuration profile and one or more channel configuration profiles. A template provides the complete configuration of a line. The same configuration can be shared by multiple lines. Similarly to the configuration profiles and templates, this MIB module makes use of templates and profiles for specifying the alarm thresholds associated with performance parameters. This allows provisioning multiple lines with the same criteria for generating Morgenstern, et al. Expires July 5, 2006 [Page 21] Internet-Draft VDSL2-LINE MIB January 2006 threshold crossing notifications. The following paragraphs describe templates and profiles used in this MIB module 2.8.1. Configuration Profiles And Templates o Line Configuration Profiles - Line configuration profiles contain parameters for configuring the low layer of VDLS2/ADSL/ADSL2 and ADSL2+ lines. They are defined in the xdsl2LineConfProfTable. The line configuration includes issues such as the specific VDSL2/ ADSL/ADSL2 or ADSL2+ modes to enable on the respective line, power spectrum parameters, rate adaptation criteria, and SNR margin related parameters. A subset of the line configuration parameters depends upon the specific ADSL Mode allowed (i.e., Does the profile allow VDSL2, ADSL, ADSL2 and/or ADSL2+?) as well as what annex/annexes of the standard are allowed. This is the reason a line profile MUST include one or more mode-specific extensions. o Channel Configuration Profiles - Channel configuration profiles contain parameters for configuring bearer channels over the VDSL2/ ADSL/ADSL2 and ADSL2+ lines. They are sometimes considered as the service layer configuration of the VDSL2/ADSL/ADSL2 and ADSL2+ lines. They are defined in the xdsl2ChConfProfTable. The channel configuration includes issues such as the desired minimum and maximum rate on each traffic flow direction and impulse noise protection parameters. o Line Configuration Templates - Line configuration templates allow combining line configuration profiles and channel configuration profiles to a comprehensive configuration of the VDSL2/ADSL/ADSL2 and ADSL2+ line. They are defined in the xdsl2LineConfTemplateTable. The line configuration template includes one index (OID) of a line configuration profile and one to four indexes of channel configuration profiles. The template also addresses the issue of distributing the excess available data rate on each traffic flow direction (i.e., the data rate left after each channel is allocated a data rate to satisfy its minimum requested data rate) among the various channels. 2.8.2. Alarm Configuration Profiles And Templates Morgenstern, et al. Expires July 5, 2006 [Page 22] Internet-Draft VDSL2-LINE MIB January 2006 o Line Alarm Configuration Profiles - Line level Alarm configuration profiles contain the threshold values for Performance Monitoring (PM) parameters, counted either on the whole line level or on an xtu level. Thresholds are required only for failures and anomalies. E.g., there are thresholds for failed initializations and LOS seconds, but not for the aggregate number of full initializations. These profiles are defined in the adsl2LineAlarmConfProfTable. o Channel Alarm Configuration Profiles - Channel level Alarm configuration profiles contain the threshold values for PM parameters counted on a bearer channel level. Thresholds are defined for two types of anomalies: corrected blocks and coding violations. These profiles are defined in the xdsl2ChAlarmConfProfTable. o Line Alarm Configuration Templates - Line Alarm configuration templates allow combining line level alarm configuration profiles and channel level alarm configuration profiles to a comprehensive configuration of the PM thresholds for VDSL2/ADSL/ADSL2 and ADSL2+ line. They are defined in the xdsl2LineAlarmConfTemplateTable. The line alarm configuration template includes one index (OID) of a line level alarm configuration profile and one to four indexes of channel level alarm configuration profiles. 2.8.3. Managing Profiles And Templates The index value for each profile and template is a locally-unique, administratively assigned name having the textual convention 'SnmpAdminString' (RFC 3411 [RFC3411]). One or more lines may be configured to share parameters of a single configuration template (e.g., xdsl2LConfTempTemplateName = 'silver') by setting its xdsl2LCnfgLineTemplate objects to the value of this template. One or more lines may be configured to share parameters of a single Alarm configuration template (e.g., xdsl2LAlarmConfTempTemplateName = 'silver') by setting its xdsl2LCnfgAlarmTemplate objects to the value of this template. Before a template can be deleted or taken out of service it MUST be first unreferenced from all associated lines. Implementations MAY also reject template modification while it is associated with any line. Implementations MUST reject template modification while its row status is set to 'active'. Morgenstern, et al. Expires July 5, 2006 [Page 23] Internet-Draft VDSL2-LINE MIB January 2006 Before a profile can be deleted or taken out of service it MUST be first unreferenced from all associated templates. Implementations MAY also reject profile modification while it is referenced by any template. Implementations MUST reject profile modification while its row status is set to 'active'. Implementations MUST provide a default profile whose name is 'DEFVAL' for each profile and template type. The values of the associated parameters will be vendor-specific unless otherwise indicated in this document. Before a line's templates have been set, these templates will be automatically used by setting xdsl2LCnfgLineTemplate and xdsl2LCnfgAlarmTemplate to 'DEFVAL' where appropriate. This default profile name, 'DEFVAL', is considered reserved in the context of profiles and templates defined in this MIB module. Profiles and templates are created, assigned, and deleted dynamically using the profile name and profile row status in each of the profile tables. If the implementation allows modifying a profile or template while it is associated with a line, then such changes MUST take effect immediately. These changes MAY result in a restart (hard reset or soft restart) of the units on the line. 2.8.4. Managing Multiple Bearer Channels The number of bearer channels is configured by setting the template attributes xdsl2LConfTempChan1ConfProfile, xdsl2LConfTempChan2ConfProfile, xdsl2LConfTempChan3ConfProfile, and xdsl2LConfTempChan4ConfProfile and then assigning that template to a DSL line using the xdsl2LineCnfgTemplate attribute. When the number of bearer channels for a DSL line changes, the SNMP agent will automatically create or destroy rows in channel-related tables associated with that line. For example, when a DSL line is operating with one bearer channel, there will be zero rows in channel-related tables for channels two, three, and four. The SNMP agent MUST create and destroy channel related rows as follows : o When the number of bearer channels for a DSL line changes to a higher number, the SNMP agent will automatically create rows in the xdsl2ChannelStatusTable, and xdsl2PMChCurrTable tables for that line. o When the number of bearer channels for a DSL line changes to a lower number, the SNMP agent will automatically destroy rows in the xdsl2ChannelStatusTable, xdsl2PMChCurrTable,xdsl2PMChHist15MinTable and xdsl2PMChHist1DTable tables for that line. Morgenstern, et al. Expires July 5, 2006 [Page 24] Internet-Draft VDSL2-LINE MIB January 2006 2.9. Notifications The ability to generate the SNMP notifications coldStart/WarmStart (per [RFC3418]), which are per agent (e.g., per Digital Subscriber Line Access Multiplexer, or DSLAM, in such a device), and linkUp/ linkDown (per [RFC2863]), which are per interface (i.e., VDSL2/ADSL/ ADSL2 or ADSL2+ line) is required. A linkDown notification MAY be generated whenever any of ES, SES, CRC Anomaly, LOS, LOF, or UAS event occurs. The corresponding linkUp notification MAY be sent when all link failure conditions are cleared. The notifications defined in this MIB module are for status change (e.g., initialization failure) and for the threshold crossings associated with the following events: Full initialization failures, short initialization failures, ES, SES, FEC Seconds, LOS Seconds, UAS, FEC Seconds, FEC events, and CRC anomalies. Each threshold has its own enable/threshold value. When that value is 0, the notification is disabled. The xdsl2LStatusStatusAtur and adsl2LStatusStatusAtuc are bitmasks representing all outstanding error conditions associated with the AtuR and xtuc (respectively). Note that since the xtur status is obtained via the EOC, this information may be unavailable in case the xtur is unreachable via EOC during a line error condition. Therefore, not all conditions may always be included in its current status. Notifications corresponding to the bit fields in those two status objects are defined. Note that there are other status parameters that refer to the AtuR (e.g., downstream line attenuation). Those parameters also depend on the availability of EOC between the central office xtu and the remote xtu. A threshold notification occurs whenever the corresponding current 15-minute interval error counter becomes equal to, or exceeds the threshold value. Only one notification SHOULD be sent per interval per interface. Since the current 15-minute counter is reset to 0 every 15 minutes, and if the condition persists, the notification may recur as often as every 15 minutes. For example, to get a notification whenever a "loss of" event occurs (but at most once every 15 minutes), set the corresponding threshold to 1. The agent will generate a notification when the event originally occurs. Notifications, other than the threshold notifications listed above, SHOULD be rate limited (throttled) such that there is an implementation-specific gap between the generation of consecutive Morgenstern, et al. Expires July 5, 2006 [Page 25] Internet-Draft VDSL2-LINE MIB January 2006 notifications of the same event. When notifications are rate limited, they are dropped and not queued for sending at a future time. This is intended to be a general rate-limiting statement for notifications that otherwise have no explicit rate limiting assertions in this document. Note that the Network Management System, or NMS, may receive a linkDown notification, as well, if enabled (via ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 minute interval, the counter is reset. When the first second goes by and the event occurs, the current interval bucket will be 1, which equals the threshold, and the notification will be sent again. 3. Definitions VDSL2-LINE-TC-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, transmission FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC; vdsl2TCMIB MODULE-IDENTITY LAST-UPDATED "200601220000Z" -- January 22, 2006 ORGANIZATION "ADSLMIB Working Group" CONTACT-INFO "WG-email: adslmib@ietf.org Info: https://www1.ietf.org/mailman/listinfo/adslmib Chair: Mike Sneed Sand Channel Systems Postal: P.O. Box 37324 Raleigh NC 27627-732 Email: sneedmike@hotmail.com Phone: +1 206 600 7022 Co-Chair: Menachem Dodge ECI Telecom Ltd. Postal: 30 Hasivim St. Petach Tikva 49517, Israel. Morgenstern, et al. Expires July 5, 2006 [Page 26] Internet-Draft VDSL2-LINE MIB January 2006 Email: mbdodge@ieee.org Phone: +972 3 926 8421 Co-editor: Moti Morgenstern ECI Telecom Ltd. Postal: 30 Hasivim St. Petach Tikva 49517, Israel. Email: moti.morgenstern@ecitele.com Phone: +972 3 926 6258 Co-editor: Scott Baillie NEC Australia Postal: 649-655 Springvale Road, Mulgrave, Victoria 3170, Australia. Email: scott.baillie@nec.com.au Phone: +61 3 9264 3986 Co-editor: Umberto Bonollo NEC Australia Postal: 649-655 Springvale Road, Mulgrave, Victoria 3170, Australia. Email: umberto.bonollo@nec.com.au Phone: +61 3 9264 3385 " DESCRIPTION "This MIB Module provides Textual Conventions to be used by the VDSL2-LINE-MIB module for the purpose of managing VDSL2, ADSL, ADSL2 and ADSL2+ lines. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC XXXX: see the RFC itself for full legal notices." -- RFC Ed.: replace XXXX with assigned number & remove this note REVISION "200601220000Z" -- January 22, 2006 DESCRIPTION "Initial version, published as RFC XXXX." -- RFC Ed.: replace XX with assigned number & remove this note ::= { transmission xxx 2} -- vdsl2MIB 2 -- IANA, the xxx here must be the same as the one assigned -- to the vdsl2MIB below. -- RFC Ed.: Please fill in xxx once assigned by IANA. ------------------------------------------------ -- Textual Conventions -- ------------------------------------------------ Morgenstern, et al. Expires July 5, 2006 [Page 27] Internet-Draft VDSL2-LINE MIB January 2006 Xdsl2Unit ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Identifies a transceiver as being either xtuc or xtur. A VDSL2/ADSL/ADSL2 or ADSL2+ line consists of two transceivers, an xtuc and an xtur. In the case of ADSL/ADSL2 and ADSL2+ those two transceivers are also called atuc and atur. In the case of VDSL2 those two transceivers are also called vtuc and vtur. Attributes with this syntax reference the two sides of a line. Specified as an INTEGER, the two values are: xtuc(1) -- central office transceiver xtur(2) -- remote site transceiver" SYNTAX INTEGER { xtuc(1), xtur(2) } Xdsl2Direction ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Identifies the direction of a band as being either upstream or downstream. Specified as an INTEGER, the two values are: upstream(1) downstream(2)" SYNTAX INTEGER { upstream(1), downstream(2) } ------***************************************************** ----- The following TC doesn't include yet the VDSL2 bits ------***************************************************** Xdsl2TransmissionModeType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A set of ADSL2 line transmission modes, with one bit per mode. The notes (F) and (L) denote Full-Rate and Lite/splitterless respectively: Bit 00 : Regional Std. (ANSI T1.413) (F) Bit 01 : Regional Std. (ETSI DTS/TM06006) (F) Bit 02 : G.992.1 POTS non-overlapped (F) Morgenstern, et al. Expires July 5, 2006 [Page 28] Internet-Draft VDSL2-LINE MIB January 2006 Bit 03 : G.992.1 POTS overlapped (F) Bit 04 : G.992.1 ISDN non-overlapped (F) Bit 05 : G.992.1 ISDN overlapped (F) Bit 06 : G.992.1 TCM-ISDN non-overlapped (F) Bit 07 : G.992.1 TCM-ISDN overlapped (F) Bit 08 : G.992.2 POTS non-overlapped (L) Bit 09 : G.992.2 POTS overlapped (L) Bit 10 : G.992.2 with TCM-ISDN non-overlapped (L) Bit 11 : G.992.2 with TCM-ISDN overlapped (L) Bit 12 : G.992.1 TCM-ISDN symmetric (F) --- not in G.997.1 Bit 13-17: Reserved Bit 18 : G.992.3 POTS non-overlapped (F) Bit 19 : G.992.3 POTS overlapped (F) Bit 20 : G.992.3 ISDN non-overlapped (F) Bit 21 : G.992.3 ISDN overlapped (F) Bit 22-23: Reserved Bit 24 : G.992.4 POTS non-overlapped (L) Bit 25 : G.992.4 POTS overlapped (L) Bit 26-27: Reserved Bit 28 : G.992.3 Annex I All-Digital non-overlapped (F) Bit 29 : G.992.3 Annex I All-Digital overlapped (F) Bit 30 : G.992.3 Annex J All-Digital non-overlapped (F) Bit 31 : G.992.3 Annex J All-Digital overlapped (F) Bit 32 : G.992.4 Annex I All-Digital non-overlapped (L) Bit 33 : G.992.4 Annex I All-Digital overlapped (L) Bit 34 : G.992.3 Annex L POTS non-overlapped, mode 1, wide U/S (F) Bit 35 : G.992.3 Annex L POTS non-overlapped, mode 2, narrow U/S(F) Bit 36 : G.992.3 Annex L POTS overlapped, mode 3, wide U/S (F) Bit 37 : G.992.3 Annex L POTS overlapped, mode 4, narrow U/S (F) Bit 38 : G.992.3 Annex M POTS non-overlapped (F) Bit 39 : G.992.3 Annex M POTS overlapped (F) Bit 40 : G.992.5 POTS non-overlapped (F) Bit 41 : G.992.5 POTS overlapped (F) Bit 42 : G.992.5 ISDN non-overlapped (F) Bit 43 : G.992.5 ISDN overlapped (F) Bit 44-45: Reserved Bit 46 : G.992.5 Annex I All-Digital non-overlapped (F) Bit 47 : G.992.5 Annex I All-Digital overlapped (F) Bit 48 : G.992.5 Annex J All-Digital non-overlapped (F) Bit 49 : G.992.5 Annex J All-Digital overlapped (F) Bit 50 : G.992.5 Annex M POTS non-overlapped (F) Bit 51 : G.992.5 Annex M POTS overlapped (F) Bit 52-55: Reserved" SYNTAX BITS { Morgenstern, et al. Expires July 5, 2006 [Page 29] Internet-Draft VDSL2-LINE MIB January 2006 ansit1413(0), etsi(1), q9921PotsNonOverlapped(2), q9921PotsOverlapped(3), q9921IsdnNonOverlapped(4), q9921isdnOverlapped(5), q9921tcmIsdnNonOverlapped(6), q9921tcmIsdnOverlapped(7), q9922potsNonOverlapeed(8), q9922potsOverlapped(9), q9922tcmIsdnNonOverlapped(10), q9922tcmIsdnOverlapped(11), q9921tcmIsdnSymmetric(12), reserved1(13), reserved2(14), reserved3(15), reserved4(16), reserved5(17), q9923PotsNonOverlapped(18), q9923PotsOverlapped(19), q9923IsdnNonOverlapped(20), q9923isdnOverlapped(21), reserved6(22), reserved7(23), q9924potsNonOverlapeed(24), q9924potsOverlapped(25), reserved8(26), reserved9(27), q9923AnnexIAllDigNonOverlapped(28), q9923AnnexIAllDigOverlapped(29), q9923AnnexJAllDigNonOverlapped(30), q9923AnnexJAllDigOverlapped(31), q9924AnnexIAllDigNonOverlapped(32), q9924AnnexIAllDigOverlapped(33), q9923AnnexLMode1NonOverlapped(34), q9923AnnexLMode2NonOverlapped(35), q9923AnnexLMode3Overlapped(36), q9923AnnexLMode4Overlapped(37), q9923AnnexMPotsNonOverlapped(38), q9923AnnexMPotsOverlapped(39), q9925PotsNonOverlapped(40), q9925PotsOverlapped(41), q9925IsdnNonOverlapped(42), q9925isdnOverlapped(43), reserved10(44), reserved11(45), q9925AnnexIAllDigNonOverlapped(46), q9925AnnexIAllDigOverlapped(47), Morgenstern, et al. Expires July 5, 2006 [Page 30] Internet-Draft VDSL2-LINE MIB January 2006 q9925AnnexJAllDigNonOverlapped(48), q9925AnnexJAllDigOverlapped(49), q9925AnnexMPotsNonOverlapped(50), q9925AnnexMPotsOverlapped(51), reserved12(52), reserved13(53), reserved14(54), reserved15(55) } Xdsl2RaMode ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Specifies the rate adaptation behavior for the line. The three possible behaviors are: manual (1) - No Rate-Adaptation. The initialization process attempts to synchronize to a specified rate. rainit (2) - Rate-Adaptation during initialization process only, which attempts to synchronize to a rate between minimum and maximum specified values. dynamicRa (3)- Dynamic Rate-Adaptation during initialization process as well as during SHOWTIME" SYNTAX INTEGER { manual(1), raInit(2), dynamicRa(3) } Xdsl2InitResult ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Specifies the result of full initialization attempt; the six possible result values are: noFail (0) - Successful initialization configError (1) - Configuration failure configNotFeasible (2) - Configuration details not supported commFail (3) - Communication failure noPeerAtu (4) - Peer ATU not detected otherCause (5) - Other initialization failure reason" SYNTAX INTEGER { noFail(0), configError(1), configNotFeasible(2), commFail(3), noPeerAtu(4), otherCause(5) } Morgenstern, et al. Expires July 5, 2006 [Page 31] Internet-Draft VDSL2-LINE MIB January 2006 ------***************************************************** ----- The following TC is subject to thorough changes ------***************************************************** Xdsl2OperationModes ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The VDSL2 management model specified includes an xDSL Mode attribute which identifies an instance of xDSL Mode-Specific PSD Configuration object in the xDSL Line Profile. The following classes of xDSL operating mode are defined. " SYNTAX INTEGER { defMode (1), adsl (2), adsl2Pots (3), adsl2Isdn (4), adsl2PlusPots (5), adsl2PlusIsdn (6), adsl2ReachExtended (7) } Xdsl2PowerMngState ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Attributes with this syntax uniquely identify each power management state defined for the VDSL2/ADSL/ADSL2 or ADSL2+ link. In VDSL2 only L0 and L3 states are defined. The possible values are: l0(1) - L0 - Full power management state l1(2) - L1 - Low power management state (for G.992.2) l2(3) - L2 - Low power management state (for G.992.3, G.992.4, and G.992.5) l3(4) - L3 - Idle power management state" SYNTAX INTEGER { l0(1), l1(2), l2(3), l3(4) } Xdsl2ConfPmsForce ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Attributes with this syntax are configuration parameters that reference the desired power management state for the VDSL2/ADSL/ADSL2 or ADSL2+ link In VDSL2 only L0 and L3 states are defined: Morgenstern, et al. Expires July 5, 2006 [Page 32] Internet-Draft VDSL2-LINE MIB January 2006 l3toL0 (0) - Perform a transition from L3 to L0 (Full power management state) l0toL2 (2) - Perform a transition from L0 to L2 (Low power management state) l0orL2toL3 (3) - Perform a transition into L3 (Idle power management state)" SYNTAX INTEGER { l3toL0 (0), l0toL2 (2), l0orL2toL3 (3) } Xdsl2LConfProfPmMode ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Attributes with this syntax are configuration parameters that reference the power modes/states into which the xTU-C or xTU-R may autonomously transit. It is a BITS structure that allows control of the following transit options: allowTransitionsToIdle (0) - xTU may autonomously transit to idle (L3) state. allowTransitionsToLowPower (1)- xTU may autonomously transit to low-power (L2) state." SYNTAX BITS { allowTransitionsToIdle(0), allowTransitionsToLowPower(1) } Xdsl2LineLdsf ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Attributes with this syntax are configuration parameters that control the Loop Diagnostic mode for a VDSL2/ADSL/ADSL2 or ADSL2+ link. The possible values are: inhibit (0) - Inhibit Loop Diagnostic mode force (1) - Force/Initiate Loop Diagnostic mode" SYNTAX INTEGER { inhibit(0), force(1) } Xdsl2LdsfResult ::= TEXTUAL-CONVENTION STATUS current Morgenstern, et al. Expires July 5, 2006 [Page 33] Internet-Draft VDSL2-LINE MIB January 2006 DESCRIPTION "Possible failure reasons associated with performing Dual Ended Loop Test (DELT) on a DSL 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'. tableFull (10)- The NE cannot initiate the command, due to reaching the maximum number of rows in the results table. noResources (11)- The NE cannot initiate the command, due to lack of internal memory resources." SYNTAX INTEGER { none (1), success (2), inProgress (3), unsupported (4), cannotRun (5), aborted (6), failed (7), illegalMode (8), adminUp (9), tableFull (10), noResources (11) } Xdsl2SymbolProtection ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Attributes with this syntax are configuration parameters that reference the minimum length impulse noise protection (INP) in terms of number of symbols. The possible values are: noProtection (i.e., INP not required), halfSymbol (i.e., INP Morgenstern, et al. Expires July 5, 2006 [Page 34] Internet-Draft VDSL2-LINE MIB January 2006 length is 1/2 symbol), and 1-16 symbols in steps of 1 symbol" SYNTAX INTEGER { noProtection (1), halfSymbol (2), singleSymbol (3), twoSymbols (4), threeSymbols (5), fourSymbols (6), fiveSymbols (7), sixSymbols (8), sevenSymbols (9), eightSymbols (10), nineSymbols (11), tenSymbols (12), elevenSymbols (13), twelveSymbols (14), thirteeSymbols (15), fourteenSymbols (16), fifteenSymbols (17), sixteenSymbols (18) } Xdsl2MaxBer ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Attributes with this syntax are configuration parameters that reference the maximum Bit Error Rate (BER). The possible values are: eminus3 (1) - Maximum BER=E^-3 eminus5 (2) - Maximum BER=E^-5 eminus7 (3) - Maximum BER=E^-7" SYNTAX INTEGER { eminus3(1), eminus5(2), eminus7(3) } Xdsl2ScMaskDs ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Each one of the 4096 bits in this OCTET STRING array represents the corresponding bin in the downstream direction. A value of one indicates that the bin is not in use." SYNTAX OCTET STRING (SIZE(0..512)) Xdsl2ScMaskUs ::= TEXTUAL-CONVENTION Morgenstern, et al. Expires July 5, 2006 [Page 35] Internet-Draft VDSL2-LINE MIB January 2006 STATUS current DESCRIPTION "Each one of the 4096 bits in this OCTET STRING array represents the corresponding bin in the upstream direction. A value of one indicates that the bin is not in use." SYNTAX OCTET STRING (SIZE(0..512)) Xdsl2RfiDs ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Each one of the 4096 bits in this OCTET STRING array represents the corresponding bin in the downstream direction. A value of one indicates that the bin is part of a notch filter." SYNTAX OCTET STRING (SIZE(0..512)) Xdsl2PsdMaskDs ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This is a structure that represents up to 32 PSD Mask breakpoints. Each breakpoint occupies 3 octets: The first two octets hold the index of the sub-carrier associated with the breakpoint. The third octet holds the PSD reduction at the breakpoint from 0 (0dBm/Hz) to 255 (-127.5 dBm/Hz) using units of 0.5dBm/Hz." SYNTAX OCTET STRING (SIZE(0..96)) Xdsl2PsdMaskUs ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This is a structure that represents up to 16 PSD Mask breakpoints. Each breakpoint occupies 3 octets: The first two octets hold the index of the sub-carrier associated with the breakpoint. The third octet holds the PSD reduction at the breakpoint from 0 (0dBm/Hz) to 255 (-127.5 dBm/Hz) using units of 0.5dBm/Hz." SYNTAX OCTET STRING (SIZE(0..48)) Xdsl2Tssi ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This is a structure that represents up to Morgenstern, et al. Expires July 5, 2006 [Page 36] Internet-Draft VDSL2-LINE MIB January 2006 32 transmit spectrum shaping (TSSi) breakpoints. Each breakpoint occupies 3 octets: The first two octets hold the index of the sub-carrier associated with the breakpoint. The third octet holds the shaping parameter at the breakpoint. It is a value from 0 to 127 (units of -0.5dB). The special value 127 indicates that the sub-carrier is not transmitted." SYNTAX OCTET STRING (SIZE(0..96)) ------***************************************************** ----- The following TC we should add VDSL2 related states ------***************************************************** Xdsl2LastTransmittedState ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This parameter represents the last successful transmitted initialization state in the last full initialization performed on the line States are per the specific xDSL technology and are numbered from 0 (if G.994.1 is used) or 1 (if G.994.1 is not used) up to Showtime." SYNTAX INTEGER { atucG9941(0), atucQuiet1(1), atucComb1(2), atucQuiet2(3), atucComb2(4), atucIcomb1(5), atucLineprob(6), atucQuiet3(7), atucComb3(8), atucIComb2(9), atucMsgfmt(10), atucMsgpcb(11), atucQuiet4(12), atucReverb1(13), atucTref1(14), atucReverb2(15), atucEct(16), atucReverb3(17), atucTref2(18), atucReverb4(19), atucSegue1(20), atucMsg1(21), atucReverb5(22), atucSegue2(23), atucMedley(24), Morgenstern, et al. Expires July 5, 2006 [Page 37] Internet-Draft VDSL2-LINE MIB January 2006 atucExchmarker(25), atucMsg2(26), atucReverb6(27), atucSegue3(28), atucParams(29), atucReverb7(30), atucSegue4(31), atucShowtime(32), -- aturG9941(100), aturQuiet1(101), aturComb1(102), aturQuiet2(103), aturComb2(104), aturIcomb1(105), aturLineprob(106), aturQuiet3(107), aturComb3(108), aturIcomb2(109), aturMsgfmt(110), aturMsgpcb(111), aturReverb1(112), aturQuiet4(113), aturReverb2(114), aturQuiet5(115), aturReverb3(116), aturEct(117), aturReverb4(118), aturSegue1(119), aturReverb5(120), aturSegue2(121), aturMsg1(122), aturMedley(123), aturExchmarker(124), aturMsg2(125), aturReverb6(126), aturSegue3(127), aturParams(128), aturReverb7(129), aturSegue4(130), aturShowtime(131) } Xdsl2LineStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Attributes with this syntax are status parameters that reflect the failure status for a given endpoint of Morgenstern, et al. Expires July 5, 2006 [Page 38] Internet-Draft VDSL2-LINE MIB January 2006 VDSL2/ADSL/ADSL2 or ADSL2+ link. This BITS structure can report the following failures: noDefect (0) - This bit position positively reports that no defect or failure exist. lossOfFraming (1) - Loss of frame synchronization lossOfSignal (2) - Loss of signal lossOfPower (3) - Loss of power. Usually this failure may be reported for CPE units only initFailure (4) - Recent initialization process failed. Never active on xTU-R." SYNTAX BITS { noDefect(0), lossOfFraming(1), lossOfSignal(2), lossOfPower(3), initFailure(4) } Xdsl2ChAtmStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Attributes with this syntax are status parameters that reflect the failure status for Transmission Convergence (TC) layer of a given ATM interface (data path over a VDSL2/ADSL/ ADSL2 or ADSL2+ link). This BITS structure can report the following failures: noDefect (0) - This bit position positively reports that no defect or failure exist. noCellDelineation (1) - The link was successfully initialized but cell delineation was never acquired on the associated ATM data path. lossOfCellDelineation (2)- Loss of cell delineation on the associated ATM data path" SYNTAX BITS { noDefect(0), noCellDelineation(1), lossOfCellDelineation(2) } Morgenstern, et al. Expires July 5, 2006 [Page 39] Internet-Draft VDSL2-LINE MIB January 2006 Xsl2ChPtmStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Attributes with this syntax are status parameters that reflect the failure status for a given PTM interface (packet data path over a VDSL2/ADSL/ADSL2 or ADSL2+ link). This BITS structure can report the following failures: noDefect (0) - This bit position positively reports that no defect or failure exist. outOfSync (1) - Out of synchronization. " SYNTAX BITS { noDefect(0), outOfSync(1) } END VSL2-LINE-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, transmission, Unsigned32, NOTIFICATION-TYPE, Integer32, Counter32 FROM SNMPv2-SMI ifIndex FROM IF-MIB TruthValue, RowStatus FROM SNMPv2-TC SnmpAdminString FROM SNMP-FRAMEWORK-MIB HCPerfIntervalThreshold, HCPerfTimeElapsed FROM HC-PerfHist-TC-MIB -- [RFC3705] Morgenstern, et al. Expires July 5, 2006 [Page 40] Internet-Draft VDSL2-LINE MIB January 2006 Xdsl2Unit, Xdsl2Direction, Xdsl2TransmissionModeType, Xdsl2RaMode, Xdsl2InitResult, Xdsl2OperationModes, Xdsl2PowerMngState, Xdsl2ConfPmsForce, Xdsl2LConfProfPmMode, Xdsl2LineLdsf, Xdsl2LdsfResult, Xdsl2SymbolProtection, Xdsl2MaxBer, Xdsl2ScMaskDs, Xdsl2ScMaskUs, Xdsl2RfiDs, Xdsl2PsdMaskDs, Xdsl2PsdMaskUs, Xdsl2Tssi, Xdsl2LastTransmittedState, Xdsl2LineStatus, Xdsl2ChAtmStatus, Xdsl2ChPtmStatus FROM VSL2-LINE-TC-MIB -- [This document] MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF; vsl2MIB MODULE-IDENTITY LAST-UPDATED "200601220000Z" -- January 22, 2006 ORGANIZATION "ADSLMIB Working Group" CONTACT-INFO "WG-email: adslmib@ietf.org Info: https://www1.ietf.org/mailman/listinfo/adslmib Chair: Mike Sneed Sand Channel Systems Postal: P.O. Box 37324 Raleigh NC 27627-732 Email: sneedmike@hotmail.com Phone: +1 206 600 7022 Co-Chair: Menachem Dodge ECI Telecom Ltd. Postal: 30 Hasivim St. Petach Tikva 49517, Morgenstern, et al. Expires July 5, 2006 [Page 41] Internet-Draft VDSL2-LINE MIB January 2006 Israel. Email: mbdodge@ieee.org Phone: +972 3 926 8421 Co-editor: Moti Morgenstern ECI Telecom Ltd. Postal: 30 Hasivim St. Petach Tikva 49517, Israel. Email: moti.morgenstern@ecitele.com Phone: +972 3 926 6258 Co-editor: Scott Baillie NEC Australia Postal: 649-655 Springvale Road, Mulgrave, Victoria 3170, Australia. Email: scott.baillie@nec.com.au Phone: +61 3 9264 3986 Co-editor: Umberto Bonollo NEC Australia Postal: 649-655 Springvale Road, Mulgrave, Victoria 3170, Australia. Email: umberto.bonollo@nec.com.au Phone: +61 3 9264 3385 " DESCRIPTION " This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet community for the purpose of managing VDSL2, ADSL, ADSL2, and ADSL2+ lines. The MIB module described in RFC 2662 [RFC2662] defines objects used for managing Asymmetric Bit-Rate DSL (ADSL) interfaces per [T1E1.413], [G.992.1], and [G.992.2]. These object descriptions are based upon the specifications for the ADSL Embedded Operations Channel (EOC) as defined in American National Standards Institute (ANSI) T1E1.413 [T1E1.413] and International Telecommunication Union (ITU-T) G.992.1 [G.992.1] and G.992.2 [G.992.2]. The MIB module described in RFC xxxx [RFCxxx] defines objects used for managing ADSL2 interfaces per [G.992.3] and [G.992.4], and ADSL2+ interfaces per [g.992.5]. That MIB is also capable of managing ADSL interfaces per [T1E1.413], Morgenstern, et al. Expires July 5, 2006 [Page 42] Internet-Draft VDSL2-LINE MIB January 2006 [G.992.1], and [G.992.2]. This document does not obsolete RFC 2662 [RFC2662] and RFCxxxx [RFCxxxx], but rather provides a more comprehensive management model that manages VDSL2 interfaces per G.993.2 [G.993.2] as well as ADSL, ADSL2 and ADSL2+ technologies per T1E1.413, G.992.1, G.992.2, G.992.3, G.992.4, and G.992.5 ([T1E1.413], [G.992.1], [G.992.2], [G.992.3], [G.992.4], and [G.992.5] respectively). Additionally, the management framework for VDSL2 lines specified by the Digital Subscriber Line Forum (DSLF) has been taken into consideration [TR-129]. That framework is based on ITU-T G.997.1 standard [G.997.1]. The MIB module is located in the MIB tree under MIB 2 transmission, as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of this document. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC XXXX: see the RFC itself for full legal notices." -- RFC Ed.: replace XXXX with assigned number & remove this note REVISION "200601220000Z" -- January 22, 2006 DESCRIPTION "Initial version, published as RFC XXXX." -- RFC Ed.: replace XXXX with assigned number & remove this note ::= { transmission xxx } -- IANA, we suggest to put it under { transmission xxx } because -- this is the first available number. -- RFC Ed.: Please fill in xxx once assigned by IANA. vdsl2 OBJECT IDENTIFIER ::= { vdsl2MIB 1 } ------------------------------------------------ xdsl2Line OBJECT IDENTIFIER ::= { vdsl2 1 } xdsl2Status OBJECT IDENTIFIER ::= { vdsl2 2 } xdsl2Inventory OBJECT IDENTIFIER ::= { vdsl2 3 } xdsl2PM OBJECT IDENTIFIER ::= { vdsl2 4 } xdsl2Profile OBJECT IDENTIFIER ::= { vdsl2 5 } xdsl2Scalar OBJECT IDENTIFIER ::= { vdsl2 6 } xdsl2Notifications OBJECT IDENTIFIER ::= { vdsl2 0 } xdsl2Conformance OBJECT IDENTIFIER ::= { vdsl2 8 } ------------------------------------------------ xdsl2PMLine OBJECT IDENTIFIER ::= { xdsl2PM 1 } xdsl2PMChannel OBJECT IDENTIFIER ::= { xdsl2PM 2 } ------------------------------------------------ Morgenstern, et al. Expires July 5, 2006 [Page 43] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2ProfileLine OBJECT IDENTIFIER ::= { xdsl2Profile 1 } xdsl2ProfileChannel OBJECT IDENTIFIER ::= { xdsl2Profile 2 } xdsl2ProfileAlarmConf OBJECT IDENTIFIER ::= { xdsl2Profile 3 } ------------------------------------------------ xdsl2ScalarSC OBJECT IDENTIFIER ::= { xdsl2Scalar 1 } ------------------------------------------------ ------***************************************************** ----- Should revise all references in this MIB ------***************************************************** ------------------------------------------------ -- xdsl2LineTable -- ------------------------------------------------ xdsl2LineTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2LineEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table adsl2LineTable contains configuration, command and status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line. The index of this table is an interface index where the interface has an ifType of vdsl2(xxx). Several objects in this table MUST be maintained in a persistent manner. " ::= { xdsl2Line 1 } xdsl2LineEntry OBJECT-TYPE SYNTAX Adsl2LineEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2LineTable contains configuration, commands and status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line." INDEX { ifIndex } ::= { xdsl2LineTable 1 } Xdsl2LineEntry ::= SEQUENCE { xdsl2LineCnfgTemplate SnmpAdminString, xdsl2LineAlarmCnfgTemplate SnmpAdminString, xdsl2LineCmndConfPmsf Xdsl2ConfPmsForce, xdsl2LineCmndConfLdsf Xdsl2LineLdsf, xdsl2LineCmndConfLdsfFailReason Xdsl2LdsfResult, xdsl2LineCmndAutomodeColdStart TruthValue, Morgenstern, et al. Expires July 5, 2006 [Page 44] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2LineStatusXtuTransSys Xdsl2TransmissionModeType, xdsl2LineStatusPwrMngState Xdsl2PowerMngState, xdsl2LineStatusInitResult Xdsl2InitResult, xdsl2LineStatusLastStateDs Xdsl2LastTransmittedState, xdsl2LineStatusLastStateUs Xdsl2LastTransmittedState, xdsl2LineStatusXtur Xdsl2LineStatus, xdsl2LineStatusXtuc Xdsl2LineStatus, xdsl2LineStatusLnAttenDs Unsigned32, xdsl2LineStatusLnAttenUs Unsigned32, xdsl2LineStatusSigAttenDs Unsigned32, xdsl2LineStatusSigAttenUs Unsigned32, xdsl2LineStatusSnrMarginDs Integer32, xdsl2LineStatusSnrMarginUs Integer32, xdsl2LineStatusAttainableRateDs Unsigned32, xdsl2LineStatusAttainableRateUs Unsigned32, xdsl2LineStatusActPsdDs Integer32, xdsl2LineStatusActPsdUs Integer32, xdsl2LineStatusActAtpDs Integer32, xdsl2LineStatusActAtpUs Integer32 } xdsl2LineCnfgTemplate OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(1..32)) MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the row in the xDSL2 Line Configuration Templates Table, (xdsl2LineConfTemplateTable), which applies for this line. This object MUST be maintained in a persistent manner." REFERENCE "DSL Forum TR-129, paragraph 5.1.1" DEFVAL { "DEFVAL" } ::= { xdsl2LineEntry 1 } xdsl2LineAlarmCnfgTemplate OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(1..32)) MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the row in the xDSL2 Line Alarm Configuration Template Table, (xdsl2LineAlarmConfTemplateTable), which applies to this line. This object MUST be maintained in a persistent manner." REFERENCE "DSL Forum TR-129, paragraph 5.1.1" DEFVAL { "DEFVAL" } ::= { xdsl2LineEntry 2 } Morgenstern, et al. Expires July 5, 2006 [Page 45] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2LineCmndConfPmsf OBJECT-TYPE SYNTAX Xdsl2ConfPmsForce MAX-ACCESS read-write STATUS current DESCRIPTION "Power management state forced. Defines the line states to be forced by the near-end xTU on this line. The various possible values are: l3toL0 (0), l0toL2 (2), l0orL2toL3 (3). This object MUST be maintained in a persistent manner." REFERENCE "ITU-T G.997.1, paragraph 7.3.1.1.3" DEFVAL { l3toL0 } ::= { xdsl2LineEntry 3 } xdsl2LineCmndConfLdsf OBJECT-TYPE SYNTAX Xdsl2LineLdsf MAX-ACCESS read-write STATUS current DESCRIPTION "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. This object MUST be maintained in a persistent manner. However, in case the operator forces loop diagnostics mode then the access node should reset the object (inhibit) when loop diagnostics mode procedures are completed." REFERENCE "ITU-T G.997.1, paragraph 7.3.1.1.8" DEFVAL { inhibit } ::= { xdsl2LineEntry 4 } xdsl2LineCmndConfLdsfFailReason OBJECT-TYPE SYNTAX Xdsl2LdsfResult MAX-ACCESS read-only STATUS current DESCRIPTION "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 Morgenstern, et al. Expires July 5, 2006 [Page 46] Internet-Draft VDSL2-LINE MIB January 2006 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'. tableFull (10)- The NE cannot initiate the command, due to reaching the maximum number of rows in the results table. noResources (11)- The NE cannot initiate the command, due to lack of internal memory resources." DEFVAL { none } ::= { xdsl2LineEntry 5 } xdsl2LineCmndAutomodeColdStart OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Automode cold start forced. This parameter is defined in order to improve testing of the performance of xTUs supporting automode when it is enabled in the MIB. Change the value of this parameter to 'true' indicates a change in loop conditions applied to the devices under test. The xTUs shall reset any historical information used for automode and for shortening G.994.1 handshake and initialization. Automode is the case where multiple operation-modes are enabled through the xdsl2LConfProfAtuTransSysEna object in the line configuration profile being used for the line, and where the selection of the actual operation-mode depends not only on the common capabilities of both xTUs (as exchanged in G.994.1), but also on achievable data rates under given loop conditions. This object MUST be maintained in a persistent manner." REFERENCE "ITU-T G.997.1, paragraph 7.3.1.1.10" DEFVAL { false } Morgenstern, et al. Expires July 5, 2006 [Page 47] Internet-Draft VDSL2-LINE MIB January 2006 ::= { xdsl2LineEntry 6 } xdsl2LineStatusAtuTransSys OBJECT-TYPE SYNTAX Xdsl2TransmissionModeType MAX-ACCESS read-only STATUS current DESCRIPTION "The xTU Transmission System (xTS) in use. It is coded in a bit-map representation with one bit set to '1' (the selected coding for the DSL line). This parameter may be derived from the handshaking procedures defined in Recommendation G.994.1. A set of xDSL line transmission modes, with one bit per mode. " REFERENCE "ITU-T G.997.1, paragraph 7.3.1.1.1" ::= { xdsl2LineEntry 7 } xdsl2LineStatusPwrMngState OBJECT-TYPE SYNTAX Xdsl2PowerMngState MAX-ACCESS read-only STATUS current DESCRIPTION "The current power management state. One of four possible power management states: L0 - Synchronized and full transmission (i.e., Showtime), L1 - Low Power with reduced net data rate (G.992.2 only), L2 - Low Power with reduced net data rate (G.992.3 and G.992.4 only), L3 - No power The various possible values are:l0(1), l1(2), l2(3), l3(4)." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.2" ::= { xdsl2LineEntry 8 } xdsl2LineStatusInitResult OBJECT-TYPE SYNTAX Xdsl2InitResult MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the result of the last full initialization performed on the line. It is an enumeration type with the following values: noFailure(0), configError(1), configNotFeasible(2), commFail(3), noPeerAtu(4), otherCause(5)." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.3" ::= { xdsl2LineEntry 9 } xdsl2LineStatusLastStateDs OBJECT-TYPE SYNTAX Xdsl2LastTransmittedState MAX-ACCESS read-only Morgenstern, et al. Expires July 5, 2006 [Page 48] Internet-Draft VDSL2-LINE MIB January 2006 STATUS current DESCRIPTION "The last successful transmitted initialization state in the downstream direction in the last full initialization performed on the line." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.4" ::= { xdsl2LineEntry 10 } xdsl2LineStatusLastStateUs OBJECT-TYPE SYNTAX Xdsl2LastTransmittedState MAX-ACCESS read-only STATUS current DESCRIPTION "The last successful transmitted initialization state in the upstream direction in the last full initialization performed on the line." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.5" ::= { xdsl2LineEntry 11 } xdsl2LineStatusXtur OBJECT-TYPE SYNTAX Xdsl2LineStatus MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates current state (existing failures) of the xTU-R. This is a bit-map of possible conditions. " REFERENCE "ITU-T G.997.1, paragraph 7.1.1.2" ::= { xdsl2LineEntry 12 } xdsl2LineStatusXtuc OBJECT-TYPE SYNTAX Xdsl2LineStatus MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates current state (existing failures) of the xTU-C. This is a bit-map of possible conditions. " REFERENCE "ITU-T G.997.1, paragraph 7.1.1.1" ::= { xdsl2LineEntry 13 } xdsl2LineStatusLnAttenDs OBJECT-TYPE SYNTAX Unsigned32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "The measured difference in the total power transmitted by the xTU-C and the total power received by the xTU-R over all sub- carriers during diagnostics mode and initialization. It Morgenstern, et al. Expires July 5, 2006 [Page 49] Internet-Draft VDSL2-LINE MIB January 2006 ranges from 0 to 1270 units of 0.1 dB (Physical values are 0 to 127 dB). A value of all 1's indicates the line attenuation is out of range to be represented." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.6" ::= { xdsl2LineEntry 14 } xdsl2LineStatusLnAttenUs OBJECT-TYPE SYNTAX Unsigned32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "The measured difference in the total power transmitted by the xTU-R and the total power received by the xTU-C over all sub- carriers during diagnostics mode and initialization. It ranges from 0 to 1270 units of 0.1 dB (Physical values are 0 to 127 dB). A value of all 1's indicates the line attenuation is out of range to be represented." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.7" ::= { xdsl2LineEntry 15 } xdsl2LineStatusSigAttenDs OBJECT-TYPE SYNTAX Unsigned32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "The measured difference in the total power transmitted by the xTU-C and the total power received by the xTU-R over all sub- carriers during Showtime. It ranges from 0 to 1270 units of 0.1 dB (Physical values are 0 to 127 dB). A value of all 1's indicates the line attenuation is out of range to be represented." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.8" ::= { xdsl2LineEntry 16 } xdsl2LineStatusSigAttenUs OBJECT-TYPE SYNTAX Unsigned32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "The measured difference in the total power transmitted by the xTU-R and the total power received by the xTU-C over all sub- carriers during Showtime. It ranges from 0 to 1270 units of 0.1 dB (Physical values are 0 to 127 dB). A value of all 1's indicates the line attenuation is out of range to be represented." Morgenstern, et al. Expires July 5, 2006 [Page 50] Internet-Draft VDSL2-LINE MIB January 2006 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.9" ::= { xdsl2LineEntry 17 } xdsl2LineStatusSnrMarginDs OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "Downstream SNR Margin is the maximum increase in dB of the noise power received at the xTU-R, such that the BER requirements are met for all downstream bearer channels. It ranges from -640 to 630 units of 0.1 dB (Physical values are -64 to 63 dB). A value of all 1's indicates the line attenuation is out of range to be represented." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.10" ::= { xdsl2LineEntry 18 } xdsl2LineStatusSnrMarginUs OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "Upstream SNR Margin is the maximum increase in dB of the noise power received at the xTU-C, such that the BER requirements are met for all downstream bearer channels. It ranges from -640 to 630 units of 0.1 dB (Physical values are -64 to 63 dB). A value of all 1's indicates the line attenuation is out of range to be represented." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.11" ::= { xdsl2LineEntry 19 } xdsl2LineStatusAttainableRateDs OBJECT-TYPE SYNTAX Unsigned32 UNITS "bits/second" MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum Attainable Data Rate Downstream. The maximum downstream net data rate currently attainable by the xTU-C transmitter and the xTU-R receiver, coded in bit/s." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.12" ::= { xdsl2LineEntry 20 } xdsl2LineStatusAttainableRateUs OBJECT-TYPE SYNTAX Unsigned32 UNITS "bits/second" Morgenstern, et al. Expires July 5, 2006 [Page 51] Internet-Draft VDSL2-LINE MIB January 2006 MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum Attainable Data Rate Upstream. The maximum upstream net data rate currently attainable by the xTU-R transmitter and the xTU-C receiver, coded in bit/s." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.13" ::= { xdsl2LineEntry 21 } xdsl2LineStatusActPsdDs OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "Actual Power Spectrum Density (PSD) Downstream. The average downstream transmit PSD over the sub-carriers used for downstream. It ranges from -900 to 0 units of 0.1 dB (Physical values are -90 to 0 dBm/Hz). A value of all 1's indicates the measurement is out of range to be represented." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.14" ::= { xdsl2LineEntry 22 } xdsl2LineStatusActPsdUs OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "Actual Power Spectrum Density (PSD) Upstream. The average upstream transmit PSD over the sub-carriers used for upstream. It ranges from -900 to 0 units of 0.1 dB (Physical values are -90 to 0 dBm/Hz). A value of all 1's indicates the measurement is out of range to be represented." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.15" ::= { xdsl2LineEntry 23 } xdsl2LineStatusActAtpDs OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "Actual Aggregate Transmit Power Downstream. The total amount of transmit power delivered by the xTU-C at the U-C reference point, at the instant of measurement. It ranges from -310 to 310 units of 0.1 dB (Physical values are -31 to 31 dBm). A value of all 1's indicates the measurement is out of range to Morgenstern, et al. Expires July 5, 2006 [Page 52] Internet-Draft VDSL2-LINE MIB January 2006 be represented." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.16" ::= { xdsl2LineEntry 24 } xdsl2LineStatusActAtpUs OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "Actual Aggregate Transmit Power Upstream. The total amount of transmit power delivered by the xTU-R at the U-R reference point, at the instant of measurement. It ranges from -310 to 310 units of 0.1 dB (Physical values are -31 to 31 dBm). A value of all 1's indicates the measurement is out of range to be represented." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.17" ::= { xdsl2LineEntry 25 } ------------------------------------------------ -- xdsl2ChannelStatusTable -- ------------------------------------------------ xdsl2ChannelStatusTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2ChannelStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2ChannelStatusTable contains status parameters of VDSL2/ADSL/ADSL2 or ADSL2+ channel. This table contains live data from equipment. As such, it is NOT persistent." ::= { xdsl2Status 1 } xdsl2ChannelStatusEntry OBJECT-TYPE SYNTAX Xdsl2ChannelStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2ChannelStatusTable contains status parameters of VDSL2/ADSL/ADSL2 or ADSL2+ channel. The index of this table is an interface index where the interface has an ifType value that is applicable for a DSL channel and the termination unit." INDEX { ifIndex, xdsl2ChStatusUnit } ::= { adsl2ChannelStatusTable 1 } Adsl2ChannelStatusEntry ::= Morgenstern, et al. Expires July 5, 2006 [Page 53] Internet-Draft VDSL2-LINE MIB January 2006 SEQUENCE { adsl2ChStatusUnit Xdsl2Unit, xdsl2ChStatusChannelNum Unsigned32, xdsl2ChStatusActDataRate Unsigned32, xdsl2ChStatusPrevDataRate Unsigned32, xdsl2ChStatusActDelay Unsigned32, xdsl2ChStatusAtmStatus Xdsl2ChAtmStatus, xdsl2ChStatusPtmStatus Xdsl2ChPtmStatus } xdsl2ChStatusUnit OBJECT-TYPE SYNTAX Xdsl2Unit MAX-ACCESS not-accessible STATUS current DESCRIPTION "The termination unit xtuc(1) or xtur(2)." ::= { xdsl2ChannelStatusEntry 1 } xdsl2ChStatusChannelNum OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Provides the bearer channel number associated with this row (i.e., the channel ifIndex). This enables determining the channel configuration profile and the channel thresholds profile applicable for this bearer channel." ::= { xdsl2ChannelStatusEntry 2 } xdsl2ChStatusActDataRate OBJECT-TYPE SYNTAX Unsigned32(0..200000000) UNITS "bits/second" MAX-ACCESS read-only STATUS current DESCRIPTION "The actual net data rate that the bearer channel is operating at, if in L0 power management state. In L1 or L2 states, it relates to the previous L0 state. The data rate is coded in bit/s." REFERENCE "ITU-T G.997.1, paragraph 7.5.2.1" ::= { xdsl2ChannelStatusEntry 3 } xdsl2ChStatusPrevDataRate OBJECT-TYPE SYNTAX Unsigned32(0..200000000) UNITS "bits/second" MAX-ACCESS read-only STATUS current Morgenstern, et al. Expires July 5, 2006 [Page 54] Internet-Draft VDSL2-LINE MIB January 2006 DESCRIPTION "The previous net data rate that the bearer channel was operating at just before the latest rate change event. This could be a full or short initialization, fast retrain, DRA or power management transitions, excluding transitions between L0 state and L1 or L2 states. The data rate is coded in bit/s." REFERENCE "ITU-T G.997.1, paragraph 7.5.2.2" ::= { xdsl2ChannelStatusEntry 4 } xdsl2ChStatusActDelay OBJECT-TYPE SYNTAX Unsigned32(0..8176) UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The actual one-way interleaving delay introduced by the PMS-TC in the direction of the bearer channel, if in L0 power management state. In L1 or L2 states, it relates to the previous L0 state. It is coded in ms (rounded to the nearest ms)." REFERENCE "ITU-T G.997.1, paragraph 7.5.2.3" ::= { xdsl2ChannelStatusEntry 5 } xdsl2ChStatusAtmStatus OBJECT-TYPE SYNTAX Xdsl2ChAtmStatus MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates current state (existing failures) of the DSL channel in case its Data Path is ATM. This is a bit-map of possible conditions. The various bit positions are: noFailure(0), noCellDelineation(1), lossOfCellDelineation (2). In case the channel is not of ATM Data Path the object is set to '0'." REFERENCE "ITU-T G.997.1, paragraph 7.1.4" ::= { xdsl2ChannelStatusEntry 6 } xdsl2ChStatusPtmStatus OBJECT-TYPE SYNTAX Xdsl2ChPtmStatus MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates current state (existing failures) of the DSL channel in case its Data Path is PTM. This is a bit-map of possible conditions. The various bit positions are: noFailure(0), Morgenstern, et al. Expires July 5, 2006 [Page 55] Internet-Draft VDSL2-LINE MIB January 2006 outOfSync (1). In case the channel is not of PTM Data Path the object is set to '0'." REFERENCE "ITU-T G.997.1, paragraph 7.1.5" ::= { xdsl2ChannelStatusEntry 7 } ------------------------------------------------ -- Scalars that relate to the xdsl2SCStatusTable. ------------------------------------------------ xdsl2ScalarSCMaxInterfaces OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "This value determines the upper size of xdsl2SCStatusTable. The maximum number of entries in xdsl2SCStatusTable is equal to two times the value of this attribute." ::= { xdsl2ScalarSC 1 } xdsl2ScalarSCAvailInterfaces OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "This value determines the amount of space that is currently available in xdsl2SCStatusTable. The number of entries available in xdsl2SCStatusTable is equal to two times the value of this attribute." ::= { xdsl2ScalarSC 2 } ------***************************************************** ----- Should revise The following table. ----- 1. There should be a reference to the SC groups ----- 2. We should solve the issue of too long data structures ----- caused by supporting 4096 sub-carriers. ------***************************************************** ------------------------------------------------ -- xdsl2SCStatusTable -- ------------------------------------------------ xdsl2SCStatusTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2SCStatusEntry MAX-ACCESS not-accessible STATUS current Morgenstern, et al. Expires July 5, 2006 [Page 56] Internet-Draft VDSL2-LINE MIB January 2006 DESCRIPTION "The table xdsl2SCStatusTable contains status parameters of VDSL2/ADSL/ADSL2 and ADSL2+ sub-carriers. This table contains live data from equipment. As such, it is NOT persistent." ::= { xdsl2Status 2 } xdsl2SCStatusEntry OBJECT-TYPE SYNTAX Xdsl2SCStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table Hfxdsl2SCStatusEntry contains status parameters of VDSL2/ADSL/ADSL2 and ADSL2+ sub-carriers. The index of this table is an interface index where the interface has an ifType of vdsl2(xxx)." INDEX { ifIndex, xdsl2SCStatusDirection } ::= { xdsl2SCStatusTable 1 } Xdsl2SCStatusEntry ::= SEQUENCE { xdsl2SCStatusDirection Xdsl2Direction, xdsl2SCStatusMtime Unsigned32, xdsl2SCStatusSnr OCTET STRING, xdsl2SCStatusBitsAlloc OCTET STRING, xdsl2SCStatusGainAlloc OCTET STRING, xdsl2SCStatusTssi Xdsl2Tssi, xdsl2SCStatusLinScale Unsigned32, xdsl2SCStatusLinReal OCTET STRING, xdsl2SCStatusLinImg OCTET STRING, xdsl2SCStatusLogMt Unsigned32, xdsl2SCStatusLog OCTET STRING, xdsl2SCStatusQlnMt Unsigned32, xdsl2SCStatusQln OCTET STRING, xdsl2SCStatusLnAtten Unsigned32, xdsl2SCStatusSigAtten Unsigned32, xdsl2SCStatusSnrMargin Integer32, xdsl2SCStatusAttainableRate Unsigned32, xdsl2SCStatusActAtp Integer32, xdsl2SCStatusRowStatus RowStatus } xdsl2SCStatusDirection OBJECT-TYPE SYNTAX Xdsl2Direction MAX-ACCESS not-accessible STATUS current DESCRIPTION "The direction of the sub-carrier either Morgenstern, et al. Expires July 5, 2006 [Page 57] Internet-Draft VDSL2-LINE MIB January 2006 upstream or downstream" ::= { xdsl2SCStatusEntry 1 } xdsl2SCStatusMtime OBJECT-TYPE SYNTAX Unsigned32 UNITS "symbols" MAX-ACCESS read-only STATUS current DESCRIPTION "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 for G.992.3). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated otherwise" REFERENCE "ITU-T G.997.1, paragraph 7.5.1.20.1 (SNRMTds) and paragraph 7.5.1.20.3 (SNRMTus)" ::= { xdsl2SCStatusEntry 2 } xdsl2SCStatusSnr OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..512)) MAX-ACCESS read-only STATUS current DESCRIPTION "The SNR Margin per sub-carrier, expressing the ratio between the received signal power and received noise power per subscriber. It is an array of 512 bytes, designed for supporting up to 512 (downstream) sub-carriers. The number of utilized octets on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred here as NSC. Byte i (0 <= i < NSC) is set to a value in the range 0 to 254 to indicate that the respective downstream or upstream sub- carrier i has SNR of: (-32 + Xdsl2SubcarrierSnr(i)/2) in dB (i.e., -32 to 95dB). The special value 255 means that no measurement could be done for the subcarrier because it is out of the PSD mask passband or that the noise PSD is out of range to be represented. Each value in this array is 8 bits wide." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.20.2 (SNRpsds) and paragraph 7.5.1.20.4 (SNRpsus)" ::= { xdsl2SCStatusEntry 3 } xdsl2SCStatusBitsAlloc OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..256)) UNITS "bits" MAX-ACCESS read-only Morgenstern, et al. Expires July 5, 2006 [Page 58] Internet-Draft VDSL2-LINE MIB January 2006 STATUS current DESCRIPTION "The bits allocation per sub-carrier. An array of 256 bytes (512 nibbles), designed for supporting up to 512 (downstream) sub-carriers. The number of utilized nibbles on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred here as NSC. Nibble i (0 <= i < NSC) is set to a value in the range 0 to 15 to indicate that the respective downstream or upstream sub-carrier i has the same amount of bits allocation." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.21.1 (BITSpsds) and paragraph 7.5.1.21.2 (BITSpsus)" ::= { xdsl2SCStatusEntry 4 } xdsl2SCStatusGainAlloc OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..1024)) MAX-ACCESS read-only STATUS current DESCRIPTION "The gain allocation per sub-carrier. An array of 512 16-bits values, designed for supporting up to 512 (downstream) sub- carriers. The number of utilized octets on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred here as NSC. Value i (0 <= i < NSC) is in the range 0 to 4093 to indicate that the respective downstream or upstream sub-carrier i has the same amount of gain value. The gain value is represented as a multiple of 1/512 on linear scale. Each value in this array is 16 bits wide and is stored in big endian format." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.21.3 (GAINSpsds) and paragraph 7.5.1.21.4 (GAINSpsus)" ::= { xdsl2SCStatusEntry 5 } xdsl2SCStatusTssi OBJECT-TYPE SYNTAX Xdsl2Tssi MAX-ACCESS read-only STATUS current DESCRIPTION "The transmit spectrum shaping (TSSi) breakpoints expressed as the set of breakpoints exchanged during G.994.1. Each breakpoint is a pair of values occupying 3 octets with the following structure: First 2 octets - Index of the subcarrier used in the context of the breakpoint. Third octet - The shaping parameter at the breakpoint. Morgenstern, et al. Expires July 5, 2006 [Page 59] Internet-Draft VDSL2-LINE MIB January 2006 Subcarrier index is an unsigned number in the range 1 to either NSCds (downstream direction) or NSCus (upstream direction). The shaping parameter value is in the range 0 to 127 (units of -0.5dB). The special value 127 indicates that the subcarrier is not transmitted." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.21.5 (TSSpsds) and paragraph 7.5.1.21.6 (TSSpsus)" ::= { xdsl2SCStatusEntry 6 } xdsl2SCStatusLinScale OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The scale factor to be applied to the H(f) linear representation values for the respective transmission direction. This parameter is only available after a loop diagnostic procedure." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.18.1 (HLINSCds) and paragraph 7.5.1.18.5 (HLINSCus)" ::= { xdsl2SCStatusEntry 7 } xdsl2SCStatusLinReal OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..1024)) MAX-ACCESS read-only STATUS current DESCRIPTION "An array of up to 512 complex H(f) linear representation values in linear scale for the respective transmission direction. It is designed to support up to 512 (downstream) sub-carriers. The number of utilized values on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred here as NSC. Each array entry represents the real component [referred here as a(i)] of Hlin(f = i*Df) value for a particular sub-carrier index i (0 <= i < NSC). Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), where scale is Xdsl2SubcarrierLinScale and a(i) and b(i) [provided by the Xdsl2SubcarrierLinImg object] are in the range (-2^15+1) to (+2^15-1). 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. Each value in this array is 16 bits wide and is stored in big endian format." Morgenstern, et al. Expires July 5, 2006 [Page 60] Internet-Draft VDSL2-LINE MIB January 2006 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.18.2 (HLINpsds) and paragraph 7.5.1.18.6 (HLINpsds)" ::= { xdsl2SCStatusEntry 8 } xdsl2SCStatusLinImg OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..1024)) MAX-ACCESS read-only STATUS current DESCRIPTION "An array of up to 512 complex H(f) linear representation values in linear scale for the respective transmission direction. It is designed to support up to 512 (downstream) sub-carriers. The number of utilized values on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred here as NSC. Each array entry represents the imaginary component [referred here as b(i)] of Hlin(f = i*Df) value for a particular sub- carrier index i (0 <= i < NSC). Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), where scale is Xdsl2SubcarrierLinScale and a(i) [provided by the Xdsl2SubcarrierLinReal object] and b(i) are in the range (-2^15+1) to (+2^15-1). 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. Each value in this array is 16 bits wide and is stored in big endian format." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.18.2 (HLINpsds) and paragraph 7.5.1.18.6 (HLINpsds)" ::= { xdsl2SCStatusEntry 9 } xdsl2SCStatusLogMt OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "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 for G.992.3). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated in initialization" REFERENCE "ITU-T G.997.1, paragraph 7.5.1.18.3 (HLOGMTds) and paragraph 7.5.1.18.7 (HLOGMTus)" Morgenstern, et al. Expires July 5, 2006 [Page 61] Internet-Draft VDSL2-LINE MIB January 2006 ::= { xdsl2SCStatusEntry 10 } xdsl2SCStatusLog OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..1024)) MAX-ACCESS read-only STATUS current DESCRIPTION "An array of up to 512 real H(f) logarithmic representation values in dB for the respective transmission direction. It is designed to support up to 512 (downstream) sub-carriers The number of utilized values on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred here as NSC. Each array entry represents the real Hlog(f = i*Df) value for a particular sub-carrier index i, (0 <= i < NSC). The real Hlog(f) value is represented as (6-m(i)/10), with m(i) in the range 0 to 1022. 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 applicable in loop diagnostic procedure and initialization. Each value in this array is 16 bits wide and is stored in big endian format." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.18.4 (HLOGpsds) and paragraph 7.5.1.18.8 (HLOGpsus)" ::= { xdsl2SCStatusEntry 11 } xdsl2SCStatusQlnMt OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "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 for G.992.3). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated in initialization " REFERENCE "ITU-T G.997.1, paragraph 7.5.1.19.1 (QLNMTds) and paragraph 7.5.1.19.3 (QLNMTus)" ::= { xdsl2SCStatusEntry 12 } xdsl2SCStatusQln OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..512)) UNITS "dBm/Hz" MAX-ACCESS read-only STATUS current Morgenstern, et al. Expires July 5, 2006 [Page 62] Internet-Draft VDSL2-LINE MIB January 2006 DESCRIPTION "An array of up to 512 real Quiet Line Noise values in dBm/Hz for the respective transmission direction. It is designed for up to 512 (downstream) sub-carriers The number of utilized values on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred here as NSC. Each array entry represents the QLN(f = i*Df) value for a particular sub-carrier index i, (0 <= i < NSC). The QLN(f) is represented as ( -23-n(i)/2), with n(i) in the range 0 to 254. 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. Each value in this array is 8 bits wide." REFERENCE "ITU-T G.997.1, paragraph 7.5.1.19.2 (QLNpsds) and paragraph 7.5.1.19.4 (QLNpsus)" ::= { xdsl2SCStatusEntry 13 } xdsl2SCStatusLnAtten OBJECT-TYPE SYNTAX Unsigned32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "When referring to the downstream direction, it is the measured difference in the total power transmitted by the XTU-C and the total power received by the XTU-R over all sub-carriers during diagnostics mode. When referring to the upstream direction, it is the measured difference in the total power transmitted by the XTU-R and the total power received by the XTU-C over all sub-carriers during diagnostics mode. It ranges from 0 to 1270 units of 0.1 dB (Physical values are 0 to 127 dB). A value of all 1's indicates the line attenuation is out of range to be represented. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated. " REFERENCE "ITU-T G.997.1, paragraph 7.5.1.6 (LATNds) and paragraph 7.5.1.7 (LATNus)" ::= { xdsl2SCStatusEntry 14 } xdsl2SCStatusSigAtten OBJECT-TYPE SYNTAX Unsigned32 UNITS "0.1 dB" Morgenstern, et al. Expires July 5, 2006 [Page 63] Internet-Draft VDSL2-LINE MIB January 2006 MAX-ACCESS read-only STATUS current DESCRIPTION "When referring to the downstream direction, it is the measured difference in the total power transmitted by the XTU-C and the total power received by the XTU-R over all sub carriers during Showtime after the diagnostics mode. When referring to the upstream direction, it is the measured difference in the total power transmitted by the XTU-R and the total power received by the XTU-C over all sub carriers during Showtime after the diagnostics mode. It ranges from 0 to 1270 units of 0.1 dB (Physical values are 0 to 127 dB). A value of all 1's indicates the line attenuation is out of range to be represented. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated. " REFERENCE "ITU-T G.997.1, paragraph 7.5.1.8 (SATNds) and paragraph 7.5.1.9 (SATNus)" ::= { xdsl2SCStatusEntry 15 } xdsl2SCStatusSnrMargin OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "SNR Margin is the maximum increase in dB of the noise power received at the XTU (XTU-R on downstream direction and XATU-C on upstream direction), such that the BER requirements are met for all bearer channels received at the XTU. It ranges from -640 to 630 units of 0.1 dB (Physical values are -64 to 63 dB). A value of all 1's indicates the SNR margin is out of range to be represented. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated. " REFERENCE "ITU-T G.997.1, paragraph 7.5.1.10 (SNRMds) and paragraph 7.5.1.11 (SNRMus)" ::= { xdsl2SCStatusEntry 16 } xdsl2SCStatusAttainableRate OBJECT-TYPE SYNTAX Unsigned32 UNITS "bits/second" MAX-ACCESS read-only STATUS current Morgenstern, et al. Expires July 5, 2006 [Page 64] Internet-Draft VDSL2-LINE MIB January 2006 DESCRIPTION "Maximum Attainable Data Rate. The maximum net data rate currently attainable by the XTU-C transmitter and XTU-R receiver (when referring to downstream direction) or by the XTU-R transmitter and XTU-C receiver (when referring to upstream direction). Value is coded in bits/s. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated. " REFERENCE "ITU-T G.997.1, paragraph 7.5.1.12 (ATTNDRds) and paragraph 7.5.1.13 (ATTNDRus)" ::= { xdsl2SCStatusEntry 17 } xdsl2SCStatusActAtp OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 dB" MAX-ACCESS read-only STATUS current DESCRIPTION "Actual Aggregate Transmit Power from the XTU (XTU-R on downstream direction and XTU-C on upstream direction), at the instant of measurement. It ranges from -310 to 310 units of 0.1 dB (Physical values are -31 to 31 dBm). A value of all 1's indicates the measurement is out of range to be represented. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated. " REFERENCE "ITU-T G.997.1, paragraph 7.5.1.14 (ACTPSDds) and paragraph 7.5.1.15 (ACTPSDus)" ::= { xdsl2SCStatusEntry 18 } xdsl2SCStatusRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-write STATUS current DESCRIPTION "Row Status. The SNMP agent should create a row in this table for storing the results of a DELT performed on the associated line, if such a row does not already exist. The SNMP agent may have limited resources; therefore, if multiple rows co-exist in the table, it may fail to add new rows to the table or allocate memory resources for a new DELT process. If that occurs, the SNMP agent responds with either the value 'tableFull' or the value 'noResources' (for xdsl2LineCmndConfLdsfFailReason Morgenstern, et al. Expires July 5, 2006 [Page 65] Internet-Draft VDSL2-LINE MIB January 2006 object in xdsl2LineTable) The management system (the operator) may delete rows according to any scheme. E.g., after retrieving the results." ::= { xdsl2SCStatusEntry 19 } ------------------------------------------------ -- xdsl2LineInventoryTable -- ------------------------------------------------ xdsl2LineInventoryTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2LineInventoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2LineInventoryTable contains inventory of DSL termination unit. The objects in this table are NOT persistent." ::= { xdsl2Inventory 1 } xdsl2LineInventoryEntry OBJECT-TYPE SYNTAX Xdsl2LineInventoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2LineInventoryTable contains inventory of DSL termination unit. The index of this table is an interface index where the interface has an ifType of vdsl2(xxx)." INDEX { ifIndex, xdsl2LInvUnit } ::= { xdsl2LineInventoryTable 1 } Xdsl2LineInventoryEntry ::= SEQUENCE { xdsl2LInvUnit Xdsl2Unit, xdsl2LInvG994VendorId OCTET STRING, xdsl2LInvSystemVendorId OCTET STRING, xdsl2LInvVersionNumber OCTET STRING, xdsl2LInvSerialNumber OCTET STRING, xdsl2LInvSelfTestResult OCTET STRING, xdsl2LInvTransmissionCapabilities Xdsl2TransmissionModeType } xdsl2LInvUnit OBJECT-TYPE SYNTAX Xdsl2Unit MAX-ACCESS not-accessible STATUS current DESCRIPTION "The termination unit xtuc{1} or xtur{2}." ::= { xdsl2LineInventoryEntry 1 } Morgenstern, et al. Expires July 5, 2006 [Page 66] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2LInvG994VendorId OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "The ATU G.994.1 Vendor ID as inserted in the G.994.1 CL/CLR message. It consists of 8 binary octets, including a country code followed by a (regionally allocated) provider code, as defined in Recommendation T.35." REFERENCE "ITU-T G.997.1, paragraph 7.4" ::= { xdsl2LineInventoryEntry 2 } xdsl2LInvSystemVendorId OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "The ATU System Vendor ID (identifies the XTU system integrator) as inserted in the Overhead Messages (both XTUs for G.992.3 and G.992.4) or in the Embedded Operations Channel (only XTU-R in G.992.1 and G.992.2). It consists of 8 binary octets, with same format as used for Xdsl2InvG994VendorId." REFERENCE "ITU-T G.997.1, paragraph 7.4" ::= { xdsl2LineInventoryEntry 3 } xdsl2LInvVersionNumber OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "The XTU version number (vendor specific information) as inserted in the Overhead Messages (both XTUs for G.992.3 and G.992.4) or in the Embedded Operations Channel (only XTU-R in G.992.1 and G.992.2). It consists of up to 16 binary octets." REFERENCE "ITU-T G.997.1, paragraph 7.4" ::= { xdsl2LineInventoryEntry 4 } xdsl2LInvSerialNumber OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..32)) MAX-ACCESS read-only STATUS current DESCRIPTION "The XTU serial number (vendor specific information) as inserted in the Overhead Messages (both XTUs for G.992.3 and G.992.4) or in the Embedded Operations Channel (only XTU-R in G.992.1 and G.992.2). It is vendor specific information. It consists of up to 32 ASCII characters." Morgenstern, et al. Expires July 5, 2006 [Page 67] Internet-Draft VDSL2-LINE MIB January 2006 REFERENCE "ITU-T G.997.1, paragraph 7.4" ::= { xdsl2LineInventoryEntry 5 } xdsl2LInvSelfTestResult OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..4)) MAX-ACCESS read-only STATUS current DESCRIPTION "The XTU self-test result, coded as a 32-bit integer. The most significant octet of this object is '0' if the self-test passed, and '1' if the self-test failed. The interpretation of the other octets is vendor discretionary." REFERENCE "ITU-T G.997.1, paragraph 7.4" ::= { xdsl2LineInventoryEntry 6 } xdsl2LInvTransmissionCapabilities OBJECT-TYPE SYNTAX Xdsl2TransmissionModeType MAX-ACCESS read-only STATUS current DESCRIPTION "The XTU transmission system capability list of the different coding types. It is coded in a bit-map representation with 1 or more bits set. A bit set to '1' means that the XTU supports the respective coding. The value may be derived from the handshaking procedures defined in G.994.1. A set of xDSL line transmission modes, with one bit per mode." REFERENCE "ITU-T G.997.1, paragraph 7.4" ::= { xdsl2LineInventoryEntry 7 } ------------------------------------------------ -- xdsl2LineConfTemplateTable -- ------------------------------------------------ xdsl2LineConfTemplateTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2LineConfTemplateEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/ ADSL2 and ADSL2+ line configuration template. Entries in this table MUST be maintained in a persistent manner." ::= { xdsl2ProfileLine 1 } xdsl2LineConfTemplateEntry OBJECT-TYPE SYNTAX Xdsl2LineConfTemplateEntry MAX-ACCESS not-accessible Morgenstern, et al. Expires July 5, 2006 [Page 68] Internet-Draft VDSL2-LINE MIB January 2006 STATUS current DESCRIPTION "The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/ ADSL2 and ADSL2+ line configuration template. A default template with an index of 'DEFVAL' will always exist and its parameters will be set to vendor-specific values, unless otherwise specified in this document" INDEX { xdsl2LConfTempTemplateName } ::= { xdsl2LineConfTemplateTable 1 } Xdsl2LineConfTemplateEntry ::= SEQUENCE { xdsl2LConfTempTemplateName SnmpAdminString, xdsl2LConfTempLineProfile SnmpAdminString, xdsl2LConfTempChan1ConfProfile SnmpAdminString, xdsl2LConfTempChan1RaRatioDs Unsigned32, xdsl2LConfTempChan1RaRatioUs Unsigned32, xdsl2LConfTempChan2ConfProfile SnmpAdminString, xdsl2LConfTempChan2RaRatioDs Unsigned32, xdsl2LConfTempChan2RaRatioUs Unsigned32, xdsl2LConfTempChan3ConfProfile SnmpAdminString, xdsl2LConfTempChan3RaRatioDs Unsigned32, xdsl2LConfTempChan3RaRatioUs Unsigned32, xdsl2LConfTempChan4ConfProfile SnmpAdminString, xdsl2LConfTempChan4RaRatioDs Unsigned32, xdsl2LConfTempChan4RaRatioUs Unsigned32, xdsl2LConfTempRowStatus RowStatus } xdsl2LConfTempTemplateName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(1..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object identifies a row in this table." REFERENCE "DSL Forum TR-90, paragraph 5.1.4" ::= { xdsl2LineConfTemplateEntry 1 } xdsl2LConfTempLineProfile OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(1..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object identifies the row in the VDSL2/ADSL/ ADSL2 and ADSL2+ line configuration Profile Table, (Xdsl2LineConfProfileTable), which applies for this DSL line." Morgenstern, et al. Expires July 5, 2006 [Page 69] Internet-Draft VDSL2-LINE MIB January 2006 REFERENCE "DSL Forum TR-90, paragraph 5.1.4" DEFVAL { "DEFVAL" } ::= { xdsl2LineConfTemplateEntry 2 } xdsl2LConfTempChan1ConfProfile OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(1..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object identifies the row in the VDSL2/ADSL/ ADSL2 and ADSL2+ channel configuration Profile Table, (Xdsl2ChanConfProfileTable) that applies to DSL bearer channel #1. The channel profile name specified here must match the name of an existing row in the xdsl2ChConfProfileTable table." DEFVAL { "DEFVAL" } ::= { xdsl2LineConfTemplateEntry 3 } xdsl2LConfTempChan1RaRatioDs OBJECT-TYPE SYNTAX Unsigned32(0..100) UNITS "percents" MAX-ACCESS read-create STATUS current DESCRIPTION "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 - Xdsl2ConfTemplateChan1RaRatioDs 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%." REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" DEFVAL { 100 } ::= { xdsl2LineConfTemplateEntry 4 } xdsl2LConfTempChan1RaRatioUs OBJECT-TYPE SYNTAX Unsigned32(0..100) UNITS "percents" MAX-ACCESS read-create STATUS current DESCRIPTION "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 Morgenstern, et al. Expires July 5, 2006 [Page 70] Internet-Draft VDSL2-LINE MIB January 2006 100 - Xdsl2ConfTemplateChan1RaRatioUs 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 %." REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" DEFVAL { 100 } ::= { xdsl2LineConfTemplateEntry 5 } xdsl2LConfTempChan2ConfProfile OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object identifies the row in the VDSL2/ADSL/ ADSL2 and ADSL2+ channel configuration Profile Table, (Xdsl2ChanConfProfileTable) that applies to DSL bearer channel #2. If the channel is unused, then the object is set to a zero length string. This object may be set to a zero length string only if xdsl2LConfTempChan3ConfProfile contains a zero length string." DEFVAL { "" } ::= { xdsl2LineConfTemplateEntry 6 } xdsl2LConfTempChan2RaRatioDs OBJECT-TYPE SYNTAX Unsigned32(0..100) UNITS "percents" MAX-ACCESS read-create STATUS current DESCRIPTION "Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #2 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 - Xdsl2ConfTemplateChan2RaRatioDs 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%." REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" DEFVAL { 0 } ::= { xdsl2LineConfTemplateEntry 7 } xdsl2LConfTempChan2RaRatioUs OBJECT-TYPE SYNTAX Unsigned32(0..100) UNITS "percents" Morgenstern, et al. Expires July 5, 2006 [Page 71] Internet-Draft VDSL2-LINE MIB January 2006 MAX-ACCESS read-create STATUS current DESCRIPTION "Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #2 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 - Xdsl2ConfTemplateChan2RaRatioUs 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 %." REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" DEFVAL { 0 } ::= { xdsl2LineConfTemplateEntry 8 } xdsl2LConfTempChan3ConfProfile OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object identifies the row in the VDSL2/ADSL/ ADSL2 and ADSL2+ channel configuration Profile Table, (Xdsl2ChanConfProfileTable) that applies to DSL bearer channel #3. If the channel is unused, then the object is set to a zero length string. This object may be set to a zero length string only if xdsl2LConfTempChan4ConfProfile contains a zero length string. This object may be set to a non-zero length string only if xdsl2LConfTempChan2ConfProfile contains a non-zero length string." DEFVAL { "" } ::= { xdsl2LineConfTemplateEntry 9 } xdsl2LConfTempChan3RaRatioDs OBJECT-TYPE SYNTAX Unsigned32(0..100) UNITS "percents" MAX-ACCESS read-create STATUS current DESCRIPTION "Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #3 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 - Xdsl2ConfTemplateChan3RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels on Downstream Morgenstern, et al. Expires July 5, 2006 [Page 72] Internet-Draft VDSL2-LINE MIB January 2006 direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%." REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" DEFVAL { 0 } ::= { xdsl2LineConfTemplateEntry 10 } xdsl2LConfTempChan3RaRatioUs OBJECT-TYPE SYNTAX Unsigned32(0..100) UNITS "percents" MAX-ACCESS read-create STATUS current DESCRIPTION "Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #3 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 - Xdsl2ConfTemplateChan3RaRatioUs 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%." REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" DEFVAL { 0 } ::= { xdsl2LineConfTemplateEntry 11 } xdsl2LConfTempChan4ConfProfile OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object identifies the row in the VDSL2/ADSL/ ADSL2 and ADSL2+ channel configuration Profile Table, (Xdsl2ChanConfProfileTable) that applies to DSL bearer channel #4. If the channel is unused, then the object is set to a zero length string. This object may be set to a non-zero length string only if xdsl2LConfTempChan3ConfProfile contains a non-zero length string." DEFVAL { "" } ::= { xdsl2LineConfTemplateEntry 12 } xdsl2LConfTempChan4RaRatioDs OBJECT-TYPE SYNTAX Unsigned32(0..100) UNITS "percents" MAX-ACCESS read-create STATUS current DESCRIPTION "Rate Adaptation Ratio. The ratio (in %) that should be taken Morgenstern, et al. Expires July 5, 2006 [Page 73] Internet-Draft VDSL2-LINE MIB January 2006 into account for the bearer channel #4 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 - xdsl2LConfTempChan4RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels. The sum of rate adaptation ratios over all bearers on the same direction shall sum to 100%." REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" DEFVAL { 0 } ::= { xdsl2LineConfTemplateEntry 13 } xdsl2LConfTempChan4RaRatioUs OBJECT-TYPE SYNTAX Unsigned32(0..100) UNITS "percents" MAX-ACCESS read-create STATUS current DESCRIPTION "Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #4 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 - xdsl2LConfTempChan4RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels. The sum of rate adaptation ratios over all bearers on the same direction shall sum to 100%." REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" DEFVAL { 0 } ::= { xdsl2LineConfTemplateEntry 14 } xdsl2LConfTempRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to create a new row or to modify or delete an existing row in this table. A template is activated by setting this object to 'active'. When 'active' is set, the system will validate the template. Template modification is prohibited while this object is set to 'active'. Before a template can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), Morgenstern, et al. Expires July 5, 2006 [Page 74] Internet-Draft VDSL2-LINE MIB January 2006 it must be first unreferenced from all associated lines." ::= { xdsl2LineConfTemplateEntry 15 } ------------------------------------------ -- xdsl2LineConfProfTable -- ------------------------------------------ xdsl2LineConfProfTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2LineConfProfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2LineConfProfTable contains VDSL2/ADSL/ ADSL2 and ADSL2+ line configuration profile. Entries in this table MUST be maintained in a persistent manner." ::= { xdsl2ProfileLine 2 } xdsl2LineConfProfEntry OBJECT-TYPE SYNTAX Xdsl2LineConfProfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2LineConfProfTable contains VDSL2/ADSL/ ADSL2 and ADSL2+ line configuration 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" INDEX { xdsl2LConfProfProfileName } ::= { xdsl2LineConfProfTable 1 } Xdsl2LineConfProfEntry ::= SEQUENCE { xdsl2LConfProfProfileName SnmpAdminString, xdsl2LConfProfScMaskDs Xdsl2ScMaskDs, xdsl2LConfProfScMaskUs Xdsl2ScMaskUs, xdsl2LConfProfRfiBandsDs Xdsl2RfiDs, xdsl2LConfProfRaModeDs Xdsl2RaMode, xdsl2LConfProfRaModeUs Xdsl2RaMode, xdsl2LConfProfRaUsNrmDs Unsigned32, xdsl2LConfProfRaUsNrmUs Unsigned32, xdsl2LConfProfRaUsTimeDs Unsigned32, xdsl2LConfProfRaUsTimeUs Unsigned32, xdsl2LConfProfRaDsNrmsDs Unsigned32, xdsl2LConfProfRaDsNrmsUs Unsigned32, Morgenstern, et al. Expires July 5, 2006 [Page 75] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2LConfProfRaDsTimeDs Unsigned32, xdsl2LConfProfRaDsTimeUs Unsigned32, xdsl2LConfProfTargetSnrmDs Unsigned32, xdsl2LConfProfTargetSnrmUs Unsigned32, xdsl2LConfProfMaxSnrmDs Unsigned32, xdsl2LConfProfMaxSnrmUs Unsigned32, xdsl2LConfProfMinSnrmDs Unsigned32, xdsl2LConfProfMinSnrmUs Unsigned32, xdsl2LConfProfMsgMinUs Unsigned32, xdsl2LConfProfMsgMinDs Unsigned32, xdsl2LConfProfXtuTransSysEna Xdsl2TransmissionModeType, xdsl2LConfProfPmMode Xdsl2LConfProfPmMode, xdsl2LConfProfL0Time Unsigned32, xdsl2LConfProfL2Time Unsigned32, xdsl2LConfProfL2Atpr Unsigned32, xdsl2LConfProfL2Atprt Unsigned32, xdsl2LConfProfRowStatus RowStatus } xdsl2LConfProfProfileName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(1..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object identifies a row in this table." ::= { xdsl2LineConfProfEntry 1 } xdsl2LConfProfScMaskDs OBJECT-TYPE SYNTAX Xdsl2ScMaskDs MAX-ACCESS read-create STATUS current DESCRIPTION "Sub-carriers mask. A bitmap of 4096 bits that allows masking up to 4096 downstream sub-carriers, depending on NSCds. If bit i (0 <= i < NSCds) is set to '1', the respective downstream sub-carrier i is masked, and if set to '0', the respective sub-carrier is unmasked. Note that there should always be unmasked sub-carriers (i.e., the object cannot be all 1's). Also note that if NSCds < 4096, all bits i (NSCds i <= 4096) should be set to '1'." REFERENCE "ITU-T G.997.1, paragraph 7.3.1.2.6" ::= { xdsl2LineConfProfEntry 2 } xdsl2LConfProfScMaskUs OBJECT-TYPE SYNTAX Xdsl2ScMaskUs MAX-ACCESS read-create STATUS current DESCRIPTION Morgenstern, et al. Expires July 5, 2006 [Page 76] Internet-Draft VDSL2-LINE MIB January 2006 "Sub-carriers mask. A bitmap of 4096 bits that allows masking up to 4096 downstream sub-carriers, depending on NSCds. If bit i (0 <= i < NSCus) is set to '1', the respective upstream sub-carrier i is masked, and if set to '0', the respective sub-carrier is unmasked. Note that there should always be unmasked sub-carriers (i.e., the object cannot be all 1's). Also note that if NSCus < 4096, all bits i (NSCus < i <= 4096) should be set to '1'." REFERENCE "ITU-T G.997.1, paragraph 7.3.1.2.7" ::= { xdsl2LineConfProfEntry 3 } xdsl2LConfProfRfiBandsDs OBJECT-TYPE SYNTAX Xdsl2RfiDs MAX-ACCESS read-create STATUS current DESCRIPTION "The subset of downstream PSD mask breakpoints that shall be used to notch an RFI band. The specific interpolation around these points is defined in G.992.5. It is a bitmap of 4096 bits that allows referring to up to 4096 downstream sub-carriers, depending on NSCds. If bit i (0 <= i < NSCds) is set to '1', the respective downstream sub-carrier i is part of a notch filter, and if set to '0', the respective sub-carrier is not part of a notch filter. This information complements the specification provided by xdsl2LconfProfPsdMaskDs. Note that if NSCds < 4096, all bits i (NSCds= 1 for one or more bearer channels OR Morgenstern, et al. Expires July 5, 2006 [Page 110] Internet-Draft VDSL2-LINE MIB January 2006 LOS >= 1 OR SEF >=1 OR LPR >= 1 xtu-r: FEBE >= 1 for one or more bearer channels OR LOS-FE >=1 OR RDI >=1 OR LPR-FE >=1 . This parameter is inhibited during UAS." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrEntry 6 } xdsl2PMLCurr15MSes OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was: xtu-c: (CRC-8 summed over all bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 xtu-r: (FEBE summed over all bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1 . This parameter is inhibited during UAS." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrEntry 7 } xdsl2PMLCurr15MLoss OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was LOS (or LOS-FE for xtu-r)." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrEntry 8 } xdsl2PMLCurr15MUas OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely-errored seconds, and ends at the onset of 10 contiguous seconds with no severely-errored seconds." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrEntry 9 } xdsl2PMLCurr1DayValidIntervals OBJECT-TYPE Morgenstern, et al. Expires July 5, 2006 [Page 111] Internet-Draft VDSL2-LINE MIB January 2006 SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Valid intervals." ::= { xdsl2PMLineCurrEntry 10 } xdsl2PMLCurr1DayInvalidIntervals OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Invalid intervals." ::= { xdsl2PMLineCurrEntry 11 } xdsl2PMLCurr1DayTimeElapsed OBJECT-TYPE SYNTAX HCPerfTimeElapsed UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total elapsed seconds in this interval." ::= { xdsl2PMLineCurrEntry 12 } xdsl2PMLCurr1DayFecs OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrEntry 13 } xdsl2PMLCurr1DayEs OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was: xtu-c: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 xtu-r: FEBE >= 1 for one or more bearer channels OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS." Morgenstern, et al. Expires July 5, 2006 [Page 112] Internet-Draft VDSL2-LINE MIB January 2006 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrEntry 14 } xdsl2PMLCurr1DaySes OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was: xtu-c: (CRC-8 summed over all bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 xtu-r: (FEBE summed over all bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1 This parameter is inhibited during UAS." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrEntry 15 } xdsl2PMLCurr1DayLoss OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was LOS (or LOS-FE for xtu-r)." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrEntry 16 } xdsl2PMLCurr1DayUas OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely -errored seconds, and ends at the onset of 10 contiguous seconds with no severely-errored seconds." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrEntry 17 } ------------------------------------------------ -- PM line init current counters -- ------------------------------------------------ xdsl2PMLineCurrInitTable OBJECT-TYPE Morgenstern, et al. Expires July 5, 2006 [Page 113] Internet-Draft VDSL2-LINE MIB January 2006 SYNTAX SEQUENCE OF Xdsl2PMLineCurrInitEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMLineCurrInitTable contains current initialization counters of DSL line. The objects in this table are NOT persistent." ::= { xdsl2PMLine 2 } xdsl2PMLineCurrInitEntry OBJECT-TYPE SYNTAX Xdsl2PMLineCurrInitEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMLineCurrInitTable contains current initialization counters of DSL line. The index of this table is an interface index where the interface has an ifType of vdsl2(xxx) and the termination unit." INDEX { ifIndex } ::= { xdsl2PMLineCurrInitTable 1 } Xdsl2PMLineCurrInitEntry ::= SEQUENCE { xdsl2PMLCurrInit15MTimeElapsed Unsigned32, xdsl2PMLCurrInit15MFullInits Unsigned32, xdsl2PMLCurrInit15MFailedFullInits Unsigned32, xdsl2PMLCurrInit15MShortInits Unsigned32, xdsl2PMLCurrInit15MFailedShortInits Unsigned32, xdsl2PMLCurrInit1DayTimeElapsed Unsigned32, xdsl2PMLCurrInit1DayFullInits Unsigned32, xdsl2PMLCurrInit1DayFailedFullInits Unsigned32, xdsl2PMLCurrInit1DayShortInits Unsigned32, xdsl2PMLCurrInit1DayFailedShortInits Unsigned32 } xdsl2PMLCurrInit15MTimeElapsed OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total elapsed seconds in this interval." ::= { xdsl2PMLineCurrInitEntry 1 } xdsl2PMLCurrInit15MFullInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only Morgenstern, et al. Expires July 5, 2006 [Page 114] Internet-Draft VDSL2-LINE MIB January 2006 STATUS current DESCRIPTION "Count of full initializations attempted on the line (successful and failed) during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrInitEntry 2 } xdsl2PMLCurrInit15MFailedFullInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of failed full initializations on the line during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrInitEntry 3 } xdsl2PMLCurrInit15MShortInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of short initializations attempted on the line (successful and failed) during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrInitEntry 4 } xdsl2PMLCurrInit15MFailedShortInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of failed short initializations on the line during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrInitEntry 5 } xdsl2PMLCurrInit1DayTimeElapsed OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total elapsed seconds in this interval." ::= { xdsl2PMLineCurrInitEntry 6 } xdsl2PMLCurrInit1DayFullInits OBJECT-TYPE SYNTAX Unsigned32 Morgenstern, et al. Expires July 5, 2006 [Page 115] Internet-Draft VDSL2-LINE MIB January 2006 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of full initializations attempted on the line (successful and failed) during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrInitEntry 7 } xdsl2PMLCurrInit1DayFailedFullInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of failed full initializations on the line during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrInitEntry 8 } xdsl2PMLCurrInit1DayShortInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of short initializations attempted on the line (successful and failed) during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrInitEntry 9 } xdsl2PMLCurrInit1DayFailedShortInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of failed short initializations on the line during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineCurrInitEntry 10 } ------------------------------------------- -- PM line history 15 Minutes -- ------------------------------------------- xdsl2PMLineHist15MinTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2PMLineHist15MinEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION Morgenstern, et al. Expires July 5, 2006 [Page 116] Internet-Draft VDSL2-LINE MIB January 2006 "The table xdsl2PMLineHist15MinTable contains PM line history for 15min intervals of DSL line. The objects in this table are NOT persistent." ::= { xdsl2PMLine 3 } xdsl2PMLineHist15MinEntry OBJECT-TYPE SYNTAX Xdsl2PMLineHist15MinEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMLineHist15MinTable contains PM line history for 15min intervals of DSL line. The index of this table is an interface index where the interface has an ifType of vdsl2(xxx), the termination unit, and an interval number." INDEX { ifIndex, xdsl2PMLHist15MUnit, xdsl2PMLHist15MInterval } ::= { xdsl2PMLineHist15MinTable 1 } Xdsl2PMLineHist15MinEntry ::= SEQUENCE { xdsl2PMLHist15MUnit Xdsl2Unit, xdsl2PMLHist15MInterval Unsigned32, xdsl2PMLHist15MMonitoredTime Unsigned32, xdsl2PMLHist15MFecs Counter32, xdsl2PMLHist15MEs Counter32, xdsl2PMLHist15MSes Counter32, xdsl2PMLHist15MLoss Counter32, xdsl2PMLHist15MUas Counter32, xdsl2PMLHist15MValidInterval TruthValue } xdsl2PMLHist15MUnit OBJECT-TYPE SYNTAX Xdsl2Unit MAX-ACCESS not-accessible STATUS current DESCRIPTION "The termination unit xtuc{1} or xtur{2}." ::= { xdsl2PMLineHist15MinEntry 1 } xdsl2PMLHist15MInterval OBJECT-TYPE SYNTAX Unsigned32 (1..96) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The interval number." ::= { xdsl2PMLineHist15MinEntry 2 } Morgenstern, et al. Expires July 5, 2006 [Page 117] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2PMLHist15MMonitoredTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total seconds monitored in this interval." ::= { xdsl2PMLineHist15MinEntry 3 } xdsl2PMLHist15MFecs OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineHist15MinEntry 4 } xdsl2PMLHist15MEs OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was: xtu-c: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 xtu-r: FEBE >= 1 for one or more bearer channels OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineHist15MinEntry 5 } xdsl2PMLHist15MSes OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was: xtu-c: (CRC-8 summed over all bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 xtu-r: (FEBE summed over all bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS." Morgenstern, et al. Expires July 5, 2006 [Page 118] Internet-Draft VDSL2-LINE MIB January 2006 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineHist15MinEntry 6 } xdsl2PMLHist15MLoss OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was LOS (or LOS-FE for xtu-r)." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineHist15MinEntry 7 } xdsl2PMLHist15MUas OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely -errored seconds, and ends at the onset of 10 contiguous seconds with no severely-errored seconds." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineHist15MinEntry 8 } xdsl2PMLHist15MValidInterval OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicates if the data for this interval is valid." ::= { xdsl2PMLineHist15MinEntry 9 } --------------------------------------- -- PM line history 1 Day -- --------------------------------------- xdsl2PMLineHist1DayTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2PMLineHist1DayEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMLineHist1DayTable contains PM line history for 24 hours intervals of DSL line. The objects in this Morgenstern, et al. Expires July 5, 2006 [Page 119] Internet-Draft VDSL2-LINE MIB January 2006 table are NOT persistent." ::= { xdsl2PMLine 4 } xdsl2PMLineHist1DayEntry OBJECT-TYPE SYNTAX Xdsl2PMLineHist1DayEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMLineHist1DayTable contains PM line history for 24 hours intervals of DSL line. The indexes of this table is an interface index where the interface has an ifType of vdsl2(xxx), the termination unit and an interval number." INDEX { ifIndex, xdsl2PMLHist1DUnit, xdsl2PMLHist1DInterval } ::= { xdsl2PMLineHist1DayTable 1 } Xdsl2PMLineHist1DayEntry ::= SEQUENCE { xdsl2PMLHist1DUnit Xdsl2Unit, xdsl2PMLHist1DInterval Unsigned32, xdsl2PMLHist1DMonitoredTime Unsigned32, xdsl2PMLHist1DFecs Counter32, xdsl2PMLHist1DEs Counter32, xdsl2PMLHist1DSes Counter32, xdsl2PMLHist1DLoss Counter32, xdsl2PMLHist1DUas Counter32, xdsl2PMLHist1DValidInterval TruthValue } xdsl2PMLHist1DUnit OBJECT-TYPE SYNTAX Xdsl2Unit MAX-ACCESS not-accessible STATUS current DESCRIPTION "The termination unit." ::= { xdsl2PMLineHist1DayEntry 1 } xdsl2PMLHist1DInterval OBJECT-TYPE SYNTAX Unsigned32 (1..30) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The interval number." ::= { xdsl2PMLineHist1DayEntry 2 } Morgenstern, et al. Expires July 5, 2006 [Page 120] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2PMLHist1DMonitoredTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total seconds monitored in this interval." ::= { xdsl2PMLineHist1DayEntry 3 } xdsl2PMLHist1DFecs OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineHist1DayEntry 4 } xdsl2PMLHist1DEs OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was: xtu-c: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 xtu-r: FEBE >= 1 for one or more bearer channels OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineHist1DayEntry 5 } xdsl2PMLHist1DSes OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was: xtu-c: (CRC-8 summed over all bearer channels) >= 18 OR LOS >= 1 OR SEF >> 1 OR LPR >= 1 xtu-r: (FEBE summed over all bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS." Morgenstern, et al. Expires July 5, 2006 [Page 121] Internet-Draft VDSL2-LINE MIB January 2006 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineHist1DayEntry 6 } xdsl2PMLHist1DLoss OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds during this interval that there was LOS (or LOS-FE for xtu-r)." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineHist1DayEntry 7 } xdsl2PMLHist1DUas OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely -errored seconds, and ends at the onset of 10 contiguous seconds with no severely-errored seconds." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineHist1DayEntry 8 } xdsl2PMLHist1DValidInterval OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicates if the data for this interval is valid." ::= { xdsl2PMLineHist1DayEntry 9 } ------------------------------------------- -- PM line init history 15 Minutes -- ------------------------------------------- xdsl2PMLineInitHist15MinTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2PMLineInitHist15MinEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION Morgenstern, et al. Expires July 5, 2006 [Page 122] Internet-Draft VDSL2-LINE MIB January 2006 "The table xdsl2PMLineInitHist15MinTable contains PM line initialization history for 15 minutes intervals of DSL line. The objects in this table are NOT persistent." ::= { xdsl2PMLine 5 } xdsl2PMLineInitHist15MinEntry OBJECT-TYPE SYNTAX Xdsl2PMLineInitHist15MinEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMLineInitHist15MinTable contains PM line initialization history for 15 minutes intervals of DSL line. The index of this table is an interface index where the interface has an ifType of vdsl2(xxx) and an interval number." INDEX { ifIndex, xdsl2PMLHistInit15MInterval } ::= { xdsl2PMLineInitHist15MinTable 1 } Xdsl2PMLineInitHist15MinEntry ::= SEQUENCE { xdsl2PMLHistInit15MInterval Unsigned32, xdsl2PMLHistInit15MMonitoredTime Unsigned32, xdsl2PMLHistInit15MFullInits Unsigned32, xdsl2PMLHistInit15MFailedFullInits Unsigned32, xdsl2PMLHistInit15MShortInits Unsigned32, xdsl2PMLHistInit15MFailedShortInits Unsigned32, xdsl2PMLHistInit15MValidInterval TruthValue } xdsl2PMLHistInit15MInterval OBJECT-TYPE SYNTAX Unsigned32 (1..96) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The interval number." ::= { xdsl2PMLineInitHist15MinEntry 1 } xdsl2PMLHistInit15MMonitoredTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total seconds monitored in this interval." ::= { xdsl2PMLineInitHist15MinEntry 2 } Morgenstern, et al. Expires July 5, 2006 [Page 123] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2PMLHistInit15MFullInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of full initializations attempted on the line (successful and failed) during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineInitHist15MinEntry 3 } xdsl2PMLHistInit15MFailedFullInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of failed full initializations on the line during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineInitHist15MinEntry 4 } xdsl2PMLHistInit15MShortInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of short initializations attempted on the line (successful and failed) during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineInitHist15MinEntry 5 } xdsl2PMLHistInit15MFailedShortInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of failed short initializations on the line during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineInitHist15MinEntry 6 } xdsl2PMLHistInit15MValidInterval OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicates if the data for this interval is valid." ::= { xdsl2PMLineInitHist15MinEntry 7 } Morgenstern, et al. Expires July 5, 2006 [Page 124] Internet-Draft VDSL2-LINE MIB January 2006 ------------------------------------------- -- PM line init history 1 Day -- ------------------------------------------- xdsl2PMLineInitHist1DayTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2PMLineInitHist1DayEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMLineInitHist1DayTable contains PM line initialization history for 24 hours intervals of DSL line. The objects in this table are NOT persistent." ::= { xdsl2PMLine 6 } xdsl2PMLineInitHist1DayEntry OBJECT-TYPE SYNTAX Xdsl2PMLineInitHist1DayEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMLineInitHist1DayTable contains PM line initialization history for 24 hours intervals of DSL line. The indexes of this table is an interface index where the interface has an ifType of vdsl2(xxx) and an interval number." INDEX { ifIndex, xdsl2PMLHistinit1DInterval } ::= { xdsl2PMLineInitHist1DayTable 1 } Xdsl2PMLineInitHist1DayEntry ::= SEQUENCE { xdsl2PMLHistinit1DInterval Unsigned32, xdsl2PMLHistinit1DMonitoredTime Unsigned32, xdsl2PMLHistinit1DFullInits Unsigned32, xdsl2PMLHistinit1DFailedFullInits Unsigned32, xdsl2PMLHistinit1DShortInits Unsigned32, xdsl2PMLHistinit1DFailedShortInits Unsigned32, xdsl2PMLHistinit1DValidInterval TruthValue } xdsl2PMLHistinit1DInterval OBJECT-TYPE SYNTAX Unsigned32 (1..30) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The interval number." ::= { xdsl2PMLineInitHist1DayEntry 1 } xdsl2PMLHistinit1DMonitoredTime OBJECT-TYPE SYNTAX Unsigned32 Morgenstern, et al. Expires July 5, 2006 [Page 125] Internet-Draft VDSL2-LINE MIB January 2006 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total seconds monitored in this interval." ::= { xdsl2PMLineInitHist1DayEntry 2 } xdsl2PMLHistinit1DFullInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of full initializations attempted on the line (successful and failed) during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineInitHist1DayEntry 3 } xdsl2PMLHistinit1DFailedFullInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of failed full initializations on the line during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineInitHist1DayEntry 4 } xdsl2PMLHistinit1DShortInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of short initializations attempted on the line (successful and failed) during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineInitHist1DayEntry 5 } xdsl2PMLHistinit1DFailedShortInits OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of failed short initializations on the line during this interval." REFERENCE "ITU-T G.997.1, paragraph 7.2.1" ::= { xdsl2PMLineInitHist1DayEntry 6 } xdsl2PMLHistinit1DValidInterval OBJECT-TYPE Morgenstern, et al. Expires July 5, 2006 [Page 126] Internet-Draft VDSL2-LINE MIB January 2006 SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicates if the data for this interval is valid." ::= { xdsl2PMLineInitHist1DayEntry 7 } --------------------------------------------------- -- PM channel current counters -- --------------------------------------------------- xdsl2PMChCurrTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2PMChCurrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMChCurrTable contains current Performance Monitoring results of DSL channel. The objects in this table are NOT persistent." ::= { xdsl2PMChannel 1 } xdsl2PMChCurrEntry OBJECT-TYPE SYNTAX Xdsl2PMChCurrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMChCurrTable contains current Performance Monitoring results of DSL channel. The indexes of this table is an interface index where the interface has an ifType value which is applicable for a DSL channel and the termination unit." INDEX { ifIndex, xdsl2PMChCurrUnit } ::= { xdsl2PMChCurrTable 1 } Xdsl2PMChCurrEntry ::= SEQUENCE { xdsl2PMChCurrUnit Xdsl2Unit, xdsl2PMChCurrValidIntervals Unsigned32, xdsl2PMChCurrInvalidIntervals Unsigned32, xdsl2PMChCurr15MTimeElapsed HCPerfTimeElapsed, xdsl2PMChCurr15MCodingViolations Unsigned32, xdsl2PMChCurr15MCorrectedBlocks Unsigned32, xdsl2PMChCurr1DayValidIntervals Unsigned32, xdsl2PMChCurr1DayInvalidIntervals Unsigned32, xdsl2PMChCurr1DayTimeElapsed HCPerfTimeElapsed, xdsl2PMChCurr1DayCodingViolations Unsigned32, Morgenstern, et al. Expires July 5, 2006 [Page 127] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2PMChCurr1DayCorrectedBlocks Unsigned32 } xdsl2PMChCurrUnit OBJECT-TYPE SYNTAX Xdsl2Unit MAX-ACCESS not-accessible STATUS current DESCRIPTION "The termination unit." ::= { xdsl2PMChCurrEntry 1 } xdsl2PMChCurrValidIntervals OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Valid intervals." ::= { xdsl2PMChCurrEntry 2 } xdsl2PMChCurrInvalidIntervals OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Invalid intervals." ::= { xdsl2PMChCurrEntry 3 } xdsl2PMChCurr15MTimeElapsed OBJECT-TYPE SYNTAX HCPerfTimeElapsed UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total elapsed seconds in this interval." ::= { xdsl2PMChCurrEntry 4 } xdsl2PMChCurr15MCodingViolations OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of CRC-8 (FEBE for xtu-r) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly should increment each of the counters related to the individual channels." REFERENCE "ITU-T G.997.1, paragraph 7.2.2" Morgenstern, et al. Expires July 5, 2006 [Page 128] Internet-Draft VDSL2-LINE MIB January 2006 ::= { xdsl2PMChCurrEntry 5 } xdsl2PMChCurr15MCorrectedBlocks OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of FEC (FFEC for xtu-r) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly should increment each of the counters related to the individual channels." REFERENCE "ITU-T G.997.1, paragraph 7.2.2" ::= { xdsl2PMChCurrEntry 6 } xdsl2PMChCurr1DayValidIntervals OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Valid intervals." ::= { xdsl2PMChCurrEntry 7 } xdsl2PMChCurr1DayInvalidIntervals OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Invalid intervals." ::= { xdsl2PMChCurrEntry 8 } xdsl2PMChCurr1DayTimeElapsed OBJECT-TYPE SYNTAX HCPerfTimeElapsed UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total elapsed seconds in this interval." ::= { xdsl2PMChCurrEntry 9 } xdsl2PMChCurr1DayCodingViolations OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of CRC-8 (FEBE for xtu-r) anomalies occurring in the channel during the interval. This parameter is inhibited Morgenstern, et al. Expires July 5, 2006 [Page 129] Internet-Draft VDSL2-LINE MIB January 2006 during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly should increment each of the counters related to the individual channels." REFERENCE "ITU-T G.997.1, paragraph 7.2.2" ::= { xdsl2PMChCurrEntry 10 } xdsl2PMChCurr1DayCorrectedBlocks OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of FEC (FFEC for xtu-r) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly should increment each of the counters related to the individual channels." REFERENCE "ITU-T G.997.1, paragraph 7.2.2" ::= { xdsl2PMChCurrEntry 11 } ------------------------------------------- -- PM channel history 15 Minutes -- ------------------------------------------- xdsl2PMChHist15MinTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2PMChHist15MinEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMChCurrTable contains current Performance Monitoring results of DSL channel. The objects in this table are NOT persistent." ::= { xdsl2PMChannel 2 } xdsl2PMChHist15MinEntry OBJECT-TYPE SYNTAX Xdsl2PMChHist15MinEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMChCurrTable contains current Performance Monitoring results of DSL channel. The indexes of this table is an interface index where the interface has an ifType value which is applicable for a DSL channel, the termination unit and the interval number." INDEX { ifIndex, Morgenstern, et al. Expires July 5, 2006 [Page 130] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2PMChHist15MUnit, xdsl2PMChHist15MInterval } ::= { xdsl2PMChHist15MinTable 1 } Xdsl2PMChHist15MinEntry ::= SEQUENCE { xdsl2PMChHist15MUnit Xdsl2Unit, xdsl2PMChHist15MInterval Unsigned32, xdsl2PMChHist15MMonitoredTime Unsigned32, xdsl2PMChHist15MCodingViolations Unsigned32, xdsl2PMChHist15MCorrectedBlocks Unsigned32, xdsl2PMChHist15MValidInterval TruthValue } xdsl2PMChHist15MUnit OBJECT-TYPE SYNTAX Xdsl2Unit MAX-ACCESS not-accessible STATUS current DESCRIPTION "The termination unit." ::= { xdsl2PMChHist15MinEntry 1 } xdsl2PMChHist15MInterval OBJECT-TYPE SYNTAX Unsigned32 (1..96) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The interval number." ::= { xdsl2PMChHist15MinEntry 2 } xdsl2PMChHist15MMonitoredTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total seconds monitored in this interval." ::= { xdsl2PMChHist15MinEntry 3 } xdsl2PMChHist15MCodingViolations OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of CRC-8 (FEBE for xtu-r) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly should Morgenstern, et al. Expires July 5, 2006 [Page 131] Internet-Draft VDSL2-LINE MIB January 2006 increment each of the counters related to the individual channels." REFERENCE "ITU-T G.997.1, paragraph 7.2.2" ::= { xdsl2PMChHist15MinEntry 4 } xdsl2PMChHist15MCorrectedBlocks OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of FEC (FFEC for xtu-r) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly should increment each of the counters related to the individual channels." REFERENCE "ITU-T G.997.1, paragraph 7.2.2" ::= { xdsl2PMChHist15MinEntry 5 } xdsl2PMChHist15MValidInterval OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicates if the data for this interval is valid." ::= { xdsl2PMChHist15MinEntry 6 } ------------------------------------------ -- PM channel history 1 Day -- ------------------------------------------ xdsl2PMChHist1DTable OBJECT-TYPE SYNTAX SEQUENCE OF Xdsl2PMChHist1DEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table xdsl2PMChHist1DayTable contains PM channel history for 1 day intervals of DSL. The objects in this table are NOT persistent." ::= { xdsl2PMChannel 3 } xdsl2PMChHist1DEntry OBJECT-TYPE SYNTAX Xdsl2PMChHist1DEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION Morgenstern, et al. Expires July 5, 2006 [Page 132] Internet-Draft VDSL2-LINE MIB January 2006 "The table xdsl2PMChHist1DayTable contains PM channel history for 1 day intervals of DSL. The indexes of this table is an interface index where the interface has an ifType value which is applicable for a DSL channel, the termination unit and the interval number." INDEX { ifIndex, xdsl2PMChHist1DUnit, xdsl2PMChHist1DInterval } ::= { xdsl2PMChHist1DTable 1 } Xdsl2PMChHist1DEntry ::= SEQUENCE { xdsl2PMChHist1DUnit Xdsl2Unit, xdsl2PMChHist1DInterval Unsigned32, xdsl2PMChHist1DMonitoredTime Unsigned32, xdsl2PMChHist1DCodingViolations Unsigned32, xdsl2PMChHist1DCorrectedBlocks Unsigned32, xdsl2PMChHist1DValidInterval TruthValue } xdsl2PMChHist1DUnit OBJECT-TYPE SYNTAX Xdsl2Unit MAX-ACCESS not-accessible STATUS current DESCRIPTION "The termination unit." ::= { xdsl2PMChHist1DEntry 1 } xdsl2PMChHist1DInterval OBJECT-TYPE SYNTAX Unsigned32 (1..30) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The interval number." ::= { xdsl2PMChHist1DEntry 2 } xdsl2PMChHist1DMonitoredTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total seconds monitored in this interval." ::= { xdsl2PMChHist1DEntry 3 } xdsl2PMChHist1DCodingViolations OBJECT-TYPE Morgenstern, et al. Expires July 5, 2006 [Page 133] Internet-Draft VDSL2-LINE MIB January 2006 SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of CRC-8 (FEBE for xtu-r) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly should increment each of the counters related to the individual channels." REFERENCE "ITU-T G.997.1, paragraph 7.2.2" ::= { xdsl2PMChHist1DEntry 4 } xdsl2PMChHist1DCorrectedBlocks OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of FEC (FFEC for xtu-r) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly should increment each of the counters related to the individual channels." REFERENCE "ITU-T G.997.1, paragraph 7.2.2" ::= { xdsl2PMChHist1DEntry 5 } xdsl2PMChHist1DValidInterval OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicates if the data for this interval is valid." ::= { xdsl2PMChHist1DEntry 6 } ------------------------------------------- -- Notifications Group -- ------------------------------------------- xdsl2LinePerfFECSThreshXtuc NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurr15MFecs, xdsl2LineAlarmConfProfileXtucThresh15MinFecs } STATUS current DESCRIPTION Morgenstern, et al. Expires July 5, 2006 [Page 134] Internet-Draft VDSL2-LINE MIB January 2006 "This notification indicates that the FEC seconds threshold has been reached/exceeded for the referred XTU-C." ::= { xdsl2Notifications 1 } xdsl2LinePerfFECSThreshXtur NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurr15MFecs, xdsl2LineAlarmConfProfileXturThresh15MinFecs } STATUS current DESCRIPTION "This notification indicates that the FEC seconds threshold has been reached/exceeded for the referred XTU-R." ::= { xdsl2Notifications 2 } xdsl2LinePerfESThreshXtuc NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurr15MEs, xdsl2LineAlarmConfProfileXtucThresh15MinEs } STATUS current DESCRIPTION "This notification indicates that the errored seconds threshold has been reached/exceeded for the referred XTU-C." ::= { xdsl2Notifications 3 } xdsl2LinePerfESThreshXtur NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurr15MEs, xdsl2LineAlarmConfProfileXturThresh15MinEs } STATUS current DESCRIPTION "This notification indicates that the errored seconds threshold has been reached/exceeded for the referred XTU-R." ::= { xdsl2Notifications 4 } xdsl2LinePerfSESThreshXtuc NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurr15MSes, xdsl2LineAlarmConfProfileXtucThresh15MinSes } STATUS current DESCRIPTION Morgenstern, et al. Expires July 5, 2006 [Page 135] Internet-Draft VDSL2-LINE MIB January 2006 "This notification indicates that the severely-errored seconds threshold has been reached/exceeded for the referred XTU-C." ::= { xdsl2Notifications 5 } xdsl2LinePerfSESThreshXtur NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurr15MSes, xdsl2LineAlarmConfProfileXturThresh15MinSes } STATUS current DESCRIPTION "This notification indicates that the severely-errored seconds threshold has been reached/exceeded for the referred XTU-R." ::= { xdsl2Notifications 6 } xdsl2LinePerfLOSSThreshXtuc NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurr15MLoss, xdsl2LineAlarmConfProfileXtucThresh15MinLoss } STATUS current DESCRIPTION "This notification indicates that the LOS seconds threshold has been reached/exceeded for the referred XTU-C." ::= { xdsl2Notifications 7 } xdsl2LinePerfLOSSThreshXtur NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurr15MLoss, xdsl2LineAlarmConfProfileXturThresh15MinLoss } STATUS current DESCRIPTION "This notification indicates that the LOS seconds threshold has been reached/exceeded for the referred XTU-R." ::= { xdsl2Notifications 8 } xdsl2LinePerfUASThreshXtuc NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurr15MUas, xdsl2LineAlarmConfProfileXtucThresh15MinUas } STATUS current DESCRIPTION Morgenstern, et al. Expires July 5, 2006 [Page 136] Internet-Draft VDSL2-LINE MIB January 2006 "This notification indicates that the unavailable seconds threshold has been reached/exceeded for the referred XTU-C." ::= { xdsl2Notifications 9 } xdsl2LinePerfUASThreshXtur NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurr15MUas, xdsl2LineAlarmConfProfileXturThresh15MinUas } STATUS current DESCRIPTION "This notification indicates that the unavailable seconds threshold has been reached/exceeded for the referred XTU-R." ::= { xdsl2Notifications 10 } xdsl2LinePerfCodingViolationsThreshXtuc NOTIFICATION-TYPE OBJECTS { xdsl2PMChCurr15MCodingViolations, xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations } STATUS current DESCRIPTION "This notification indicates that the coding violations threshold has been reached/exceeded for the referred XTU-C." ::= { xdsl2Notifications 11 } xdsl2LinePerfCodingViolationsThreshXtur NOTIFICATION-TYPE OBJECTS { xdsl2PMChCurr15MCodingViolations, xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations } STATUS current DESCRIPTION "This notification indicates that the coding violations threshold has been reached/exceeded for the referred XTU-R." ::= { xdsl2Notifications 12 } xdsl2LinePerfCorrectedThreshXtuc NOTIFICATION-TYPE OBJECTS { xdsl2PMChCurr15MCorrectedBlocks, xdsl2ChAlarmConfProfileXtucThresh15MinCorrected } STATUS current DESCRIPTION Morgenstern, et al. Expires July 5, 2006 [Page 137] Internet-Draft VDSL2-LINE MIB January 2006 "This notification indicates that the corrected blocks (FEC events) threshold has been reached/exceeded for the referred XTU-C." ::= { xdsl2Notifications 13 } xdsl2LinePerfCorrectedThreshXtur NOTIFICATION-TYPE OBJECTS { xdsl2PMChCurr15MCorrectedBlocks, xdsl2ChAlarmConfProfileXturThresh15MinCorrected } STATUS current DESCRIPTION "This notification indicates that the corrected blocks (FEC events) threshold has been reached/exceeded for the referred XTU-R." ::= { xdsl2Notifications 14 } xdsl2LinePerfFailedFullInitThresh NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurrInit15MFailedFullInits, xdsl2LineAlarmConfProfileThresh15MinFailedFullInt } STATUS current DESCRIPTION "This notification indicates that the failed full initializations threshold has been reached/exceeded for the referred ADSL/ADSL2 or ADSL2 line." ::= { xdsl2Notifications 15 } xdsl2LinePerfFailedShortInitThresh NOTIFICATION-TYPE OBJECTS { xdsl2PMLCurrInit15MFailedShortInits, xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt } STATUS current DESCRIPTION "This notification indicates that the failed short initializations threshold has been reached/exceeded for the referred VDSL2/ADSL/ADSL2 or ADSL2+ line." ::= { xdsl2Notifications 16 } xdsl2LineStatusChangeXtuc NOTIFICATION-TYPE OBJECTS { xdsl2LineStatusXtuc Morgenstern, et al. Expires July 5, 2006 [Page 138] Internet-Draft VDSL2-LINE MIB January 2006 } STATUS current DESCRIPTION "This notification indicates that a status change is detected for the referred XTU-C." ::= { xdsl2Notifications 17 } xdsl2LineStatusChangeXtur NOTIFICATION-TYPE OBJECTS { xdsl2LineStatusXtur } STATUS current DESCRIPTION "This notification indicates that a status change is detected for the referred XTU-R." ::= { xdsl2Notifications 18 } -- conformance information vdsl2Groups OBJECT IDENTIFIER ::= { vdsl2Conformance 1 } vdsl2Compliances OBJECT IDENTIFIER ::= { vdsl2Conformance 2 } vdsl2LineMibCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which manage VDSL2/ADSL/ADSL2 and ADSL2+ interfaces." MODULE -- this module MANDATORY-GROUPS { vdsl2LineGroup, vdsl2ChannelStatusGroup, vdsl2SCStatusGroup, vdsl2LineInventoryGroup, vdsl2LineConfTemplateGroup, vdsl2LineConfProfGroup, vdsl2LineConfProfModeSpecGroup, vdsl2ChConfProfileGroup, vdsl2LineAlarmConfTemplateGroup, vdsl2PMLineCurrGroup, vdsl2PMLineCurrInitGroup, vdsl2PMLineHist15MinGroup, vdsl2PMLineHist1DayGroup, vdsl2PMLineInitHist15MinGroup, vdsl2PMLineInitHist1DayGroup, vdsl2PMChCurrGroup, Morgenstern, et al. Expires July 5, 2006 [Page 139] Internet-Draft VDSL2-LINE MIB January 2006 vdsl2PMChHist15MinGroup, vdsl2PMChHist1DGroup } GROUP vdsl2ChannelStatusAtmGroup DESCRIPTION "The group of status objects required when the data path is ATM." GROUP vdsl2ChannelStatusPtmGroup DESCRIPTION "The group of status objects required when the data path is PTM." GROUP vdsl2LineConfProfRaGroup DESCRIPTION "The group of objects required for controlling the rate adaptive behavior of the line." GROUP vdsl2LineConfProfMsgMinGroup DESCRIPTION "The group of objects required for controlling the rate reserved for Overhead traffic." GROUP vdsl2LineAlarmConfProfileGroup DESCRIPTION "The group of objects that define the alarm thresholds on line level PM counters." GROUP vdsl2ChAlarmConfProfileGroup DESCRIPTION "The group of objects that define the alarm thresholds on channel level PM counters." GROUP vdsl2ChConfProfileAtmGroup DESCRIPTION "The group of configuration objects required when the data path is ATM." GROUP vdsl2ChConfProfileMinResGroup DESCRIPTION "The group of configuration objects required for the reserved data rate." GROUP vdsl2PMLineCurrInitShortGroup DESCRIPTION "The group of PM counters for the current intervals short initializations." Morgenstern, et al. Expires July 5, 2006 [Page 140] Internet-Draft VDSL2-LINE MIB January 2006 GROUP vdsl2PMLineInitHist15MinShortGroup DESCRIPTION "The group of PM counters for the previous 15 minutes intervals short initializations." GROUP vdsl2PMLineInitHist1DayShortGroup DESCRIPTION "The group of PM counters for the previous 24 hours intervals short initializations." GROUP vdsl2ScalarSCGroup DESCRIPTION "The group of objects that report the available memory resources for DELT processes." GROUP vdsl2ThreshNotificationGroup DESCRIPTION "The group of thresholds crossing notifications." GROUP vdsl2StatusChangeNotificationGroup DESCRIPTION "The group of status change notifications." ::= { vdsl2Compliances 1 } -- units of conformance vdsl2LineGroup OBJECT-GROUP OBJECTS { xdsl2LineCnfgTemplate, xdsl2LineAlarmCnfgTemplate, xdsl2LineCmndConfPmsf, xdsl2LineCmndConfLdsf, xdsl2LineCmndConfLdsfFailReason, xdsl2LineCmndAutomodeColdStart, xdsl2LineStatusXtuTransSys, xdsl2LineStatusPwrMngState, xdsl2LineStatusInitResult, xdsl2LineStatusLastStateDs, xdsl2LineStatusLastStateUs, xdsl2LineStatusXtur, xdsl2LineStatusXtuc, xdsl2LineStatusLnAttenDs, xdsl2LineStatusLnAttenUs, xdsl2LineStatusSigAttenDs, xdsl2LineStatusSigAttenUs, xdsl2LineStatusSnrMarginDs, Morgenstern, et al. Expires July 5, 2006 [Page 141] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2LineStatusSnrMarginUs, xdsl2LineStatusAttainableRateDs, xdsl2LineStatusAttainableRateUs, xdsl2LineStatusActPsdDs, xdsl2LineStatusActPsdUs, xdsl2LineStatusActAtpDs, xdsl2LineStatusActAtpUs } STATUS current DESCRIPTION "The group of configuration, status, and commands objects on the line level." ::= { vdsl2Groups 1 } vdsl2ChannelStatusGroup OBJECT-GROUP OBJECTS { xdsl2ChStatusChannelNum, xdsl2ChStatusActDataRate, xdsl2ChStatusPrevDataRate, xdsl2ChStatusActDelay } STATUS current DESCRIPTION "The group of status objects on the channel level." ::= { vdsl2Groups 2 } vdsl2ChannelStatusAtmGroup OBJECT-GROUP OBJECTS { xdsl2ChStatusAtmStatus } STATUS current DESCRIPTION "The group of status objects on the data path level when it is ATM." ::= { vdsl2Groups 3 } vdsl2ChannelStatusPtmGroup OBJECT-GROUP OBJECTS { xdsl2ChStatusPtmStatus } STATUS current DESCRIPTION "The group of status objects on the data path level when it is PTM." ::= { vdsl2Groups 4 } Morgenstern, et al. Expires July 5, 2006 [Page 142] Internet-Draft VDSL2-LINE MIB January 2006 vdsl2SCStatusGroup OBJECT-GROUP OBJECTS { xdsl2SCStatusMtime, xdsl2SCStatusSnr, xdsl2SCStatusBitsAlloc, xdsl2SCStatusGainAlloc, xdsl2SCStatusTssi, xdsl2SCStatusLinScale, xdsl2SCStatusLinReal, xdsl2SCStatusLinImg, xdsl2SCStatusLogMt, xdsl2SCStatusLog, xdsl2SCStatusQlnMt, xdsl2SCStatusQln, xdsl2SCStatusLnAtten, xdsl2SCStatusSigAtten, xdsl2SCStatusSnrMargin, xdsl2SCStatusAttainableRate, xdsl2SCStatusActAtp, xdsl2SCStatusRowStatus } STATUS current DESCRIPTION "The group of status objects on the sub-carrier level. They are updated as a result of a DELT process." ::= { vdsl2Groups 5 } vdsl2LineInventoryGroup OBJECT-GROUP OBJECTS { xdsl2LInvG994VendorId, xdsl2LInvSystemVendorId, xdsl2LInvVersionNumber, xdsl2LInvSerialNumber, xdsl2LInvSelfTestResult, xdsl2LInvTransmissionCapabilities } STATUS current DESCRIPTION "The group of inventory objects per xTU." ::= { vdsl2Groups 6 } vdsl2LineConfTemplateGroup OBJECT-GROUP OBJECTS { xdsl2LConfTempLineProfile, xdsl2LConfTempChan1ConfProfile, Morgenstern, et al. Expires July 5, 2006 [Page 143] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2LConfTempChan1RaRatioDs, xdsl2LConfTempChan1RaRatioUs, xdsl2LConfTempChan2ConfProfile, xdsl2LConfTempChan2RaRatioDs, xdsl2LConfTempChan2RaRatioUs, xdsl2LConfTempChan3ConfProfile, xdsl2LConfTempChan3RaRatioDs, xdsl2LConfTempChan3RaRatioUs, xdsl2LConfTempChan4ConfProfile, xdsl2LConfTempChan4RaRatioDs, xdsl2LConfTempChan4RaRatioUs, xdsl2LConfTempRowStatus } STATUS current DESCRIPTION "The group of objects in a line configuration template." ::= { vdsl2Groups 7 } vdsl2LineConfProfGroup OBJECT-GROUP OBJECTS { xdsl2LConfProfScMaskDs, xdsl2LConfProfScMaskUs, xdsl2LConfProfRfiBandsDs, xdsl2LConfProfRaModeDs, xdsl2LConfProfRaModeUs, xdsl2LConfProfTargetSnrmDs, xdsl2LConfProfTargetSnrmUs, xdsl2LConfProfMaxSnrmDs, xdsl2LConfProfMaxSnrmUs, xdsl2LConfProfMinSnrmDs, xdsl2LConfProfMinSnrmUs, xdsl2LConfProfAtuTransSysEna, xdsl2LConfProfPmMode, xdsl2LConfProfL0Time, xdsl2LConfProfL2Time, xdsl2LConfProfL2Atpr, xdsl2LConfProfL2Atprt, xdsl2LConfProfRowStatus } STATUS current DESCRIPTION "The group of objects in a line configuration profile." ::= { vdsl2Groups 8 } vdsl2LineConfProfRaGroup OBJECT-GROUP OBJECTS { Morgenstern, et al. Expires July 5, 2006 [Page 144] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2LConfProfRaUsNrmDs, xdsl2LConfProfRaUsNrmUs, xdsl2LConfProfRaUsTimeDs, xdsl2LConfProfRaUsTimeUs, xdsl2LConfProfRaDsNrmsDs, xdsl2LConfProfRaDsNrmsUs, xdsl2LConfProfRaDsTimeDs, xdsl2LConfProfRaDsTimeUs } STATUS current DESCRIPTION "The group of objects required for controlling the rate adaptive behavior of the line." ::= { vdsl2Groups 9 } vdsl2LineConfProfMsgMinGroup OBJECT-GROUP OBJECTS { xdsl2LConfProfMsgMinUs, xdsl2LConfProfMsgMinDs } STATUS current DESCRIPTION "The group of objects required for controlling the rate reserved for Overhead traffic." ::= { vdsl2Groups 10 } vdsl2LineConfProfModeSpecGroup OBJECT-GROUP OBJECTS { xdsl2LConfProfMaxNomPsdDs, xdsl2LConfProfMaxNomPsdUs, xdsl2LConfProfMaxNomAtpDs, xdsl2LConfProfMaxNomAtpUs, xdsl2LConfProfMaxAggRxPwrUs, xdsl2LConfProfPsdMaskDs, xdsl2LConfProfPsdMaskUs, xdsl2LConfProfPsdMaskSelectUs, xdsl2LConfProfModeSpecRowStatus } STATUS current DESCRIPTION "The group of objects in a line configuration profile that have an instance for each operation mode allowed." ::= { vdsl2Groups 11 } vdsl2ChConfProfileGroup OBJECT-GROUP OBJECTS Morgenstern, et al. Expires July 5, 2006 [Page 145] Internet-Draft VDSL2-LINE MIB January 2006 { xdsl2ChConfProfMinDataRateDs, xdsl2ChConfProfMinDataRateUs, xdsl2ChConfProfMaxDataRateDs, xdsl2ChConfProfMaxDataRateUs, xdsl2ChConfProfMinDataRateLowPwrDs, xdsl2ChConfProfMaxDelayDs, xdsl2ChConfProfMaxDelayUs, xdsl2ChConfProfMinProtectionDs, xdsl2ChConfProfMinProtectionUs, xdsl2ChConfProfMaxBerDs, xdsl2ChConfProfMaxBerUs, xdsl2ChConfProfUsDataRateDs, xdsl2ChConfProfDsDataRateDs, xdsl2ChConfProfUsDataRateUs, xdsl2ChConfProfDsDataRateUs, xdsl2ChConfProfRowStatus } STATUS current DESCRIPTION "The group of objects in a channel configuration profile." ::= { vdsl2Groups 12 } vdsl2ChConfProfileAtmGroup OBJECT-GROUP OBJECTS { xdsl2ChConfProfImaEnabled, xdsl2ChStatusAtmStatus } STATUS current DESCRIPTION "The group of configuration objects required when the data path is ATM." ::= { vdsl2Groups 13 } vdsl2ChConfProfileMinResGroup OBJECT-GROUP OBJECTS { xdsl2ChConfProfMinResDataRateDs, xdsl2ChConfProfMinResDataRateUs } STATUS current DESCRIPTION "The group of configuration objects required for the reserved data rate." ::= { vdsl2Groups 14 } vdsl2LineAlarmConfTemplateGroup OBJECT-GROUP Morgenstern, et al. Expires July 5, 2006 [Page 146] Internet-Draft VDSL2-LINE MIB January 2006 OBJECTS { xdsl2LAlarmConfTempLineProfile, xdsl2LAlarmConfTempChan1ConfProfile, xdsl2LAlarmConfTempChan2ConfProfile, xdsl2LAlarmConfTempChan3ConfProfile, xdsl2LAlarmConfTempChan4ConfProfile, xdsl2LAlarmConfTempRowStatus } STATUS current DESCRIPTION "The group of objects in a line alarm template." ::= { vdsl2Groups 15 } vdsl2LineAlarmConfProfileGroup OBJECT-GROUP OBJECTS { xdsl2LineAlarmConfProfileXtucThresh15MinFecs, xdsl2LineAlarmConfProfileXtucThresh15MinEs, xdsl2LineAlarmConfProfileXtucThresh15MinSes, xdsl2LineAlarmConfProfileXtucThresh15MinLoss, xdsl2LineAlarmConfProfileXtucThresh15MinUas, xdsl2LineAlarmConfProfileXturThresh15MinFecs, xdsl2LineAlarmConfProfileXturThresh15MinEs, xdsl2LineAlarmConfProfileXturThresh15MinSes, xdsl2LineAlarmConfProfileXturThresh15MinLoss, xdsl2LineAlarmConfProfileXturThresh15MinUas, xdsl2LineAlarmConfProfileThresh15MinFailedFullInt, xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt, xdsl2LineAlarmConfProfileRowStatus } STATUS current DESCRIPTION "The group of objects in a line alarm profile." ::= { vdsl2Groups 16 } vdsl2ChAlarmConfProfileGroup OBJECT-GROUP OBJECTS { xdsl2ChAlarmConfProfileAtucThresh15MinCodingViolations, xdsl2ChAlarmConfProfileAtucThresh15MinCorrected, xdsl2ChAlarmConfProfileAturThresh15MinCodingViolations, xdsl2ChAlarmConfProfileAturThresh15MinCorrected, xdsl2ChAlarmConfProfileRowStatus } STATUS current DESCRIPTION Morgenstern, et al. Expires July 5, 2006 [Page 147] Internet-Draft VDSL2-LINE MIB January 2006 "The group of objects in a channel alarm profile." ::= { vdsl2Groups 17 } vdsl2PMLineCurrGroup OBJECT-GROUP OBJECTS { xdsl2PMLCurrValidIntervals, xdsl2PMLCurrInvalidIntervals, xdsl2PMLCurr15MTimeElapsed, xdsl2PMLCurr15MFecs, xdsl2PMLCurr15MEs, xdsl2PMLCurr15MSes, xdsl2PMLCurr15MLoss, xdsl2PMLCurr15MUas, xdsl2PMLCurr1DayValidIntervals, xdsl2PMLCurr1DayInvalidIntervals, xdsl2PMLCurr1DayTimeElapsed, xdsl2PMLCurr1DayFecs, xdsl2PMLCurr1DayEs, xdsl2PMLCurr1DaySes, xdsl2PMLCurr1DayLoss, xdsl2PMLCurr1DayUas } STATUS current DESCRIPTION "The group of objects that report the line level counters for current PM intervals." ::= { vdsl2Groups 18 } vdsl2PMLineCurrInitGroup OBJECT-GROUP OBJECTS { xdsl2PMLCurrInit15MTimeElapsed, xdsl2PMLCurrInit15MFullInits, xdsl2PMLCurrInit15MFailedFullInits, xdsl2PMLCurrInit1DayTimeElapsed, xdsl2PMLCurrInit1DayFullInits, xdsl2PMLCurrInit1DayFailedFullInits } STATUS current DESCRIPTION "The group of objects that report the full initializations counters for current PM intervals." ::= { vdsl2Groups 19 } vdsl2PMLineCurrInitShortGroup OBJECT-GROUP OBJECTS { Morgenstern, et al. Expires July 5, 2006 [Page 148] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2PMLCurrInit15MShortInits, xdsl2PMLCurrInit15MFailedShortInits, xdsl2PMLCurrInit1DayShortInits, xdsl2PMLCurrInit1DayFailedShortInits } STATUS current DESCRIPTION "The group of objects that report the short initializations counters for current PM intervals." ::= { vdsl2Groups 20 } vdsl2PMLineHist15MinGroup OBJECT-GROUP OBJECTS { xdsl2PMLHist15MMonitoredTime, xdsl2PMLHist15MFecs, xdsl2PMLHist15MEs, xdsl2PMLHist15MSes, xdsl2PMLHist15MLoss, xdsl2PMLHist15MUas, xdsl2PMLHist15MValidInterval } STATUS current DESCRIPTION "The group of line level PM counters for the previous 15 minutes intervals." ::= { vdsl2Groups 21 } vdsl2PMLineHist1DayGroup OBJECT-GROUP OBJECTS { xdsl2PMLHist1DMonitoredTime, xdsl2PMLHist1DFecs, xdsl2PMLHist1DEs, xdsl2PMLHist1DSes, xdsl2PMLHist1DLoss, xdsl2PMLHist1DUas, xdsl2PMLHist1DValidInterval } STATUS current DESCRIPTION "The group of line level PM counters for the previous 24 hours intervals." ::= { vdsl2Groups 22 } vdsl2PMLineInitHist15MinGroup OBJECT-GROUP OBJECTS { Morgenstern, et al. Expires July 5, 2006 [Page 149] Internet-Draft VDSL2-LINE MIB January 2006 xdsl2PMLHistInit15MMonitoredTime, xdsl2PMLHistInit15MFullInits, xdsl2PMLHistInit15MFailedFullInits, xdsl2PMLHistInit15MValidInterval } STATUS current DESCRIPTION "The group of PM counters for the previous 15 minutes intervals full initializations." ::= { vdsl2Groups 23 } vdsl2PMLineInitHist15MinShortGroup OBJECT-GROUP OBJECTS { xdsl2PMLHistInit15MShortInits, xdsl2PMLHistInit15MFailedShortInits } STATUS current DESCRIPTION "The group of PM counters for the previous 15 minutes intervals short initializations." ::= { vdsl2Groups 24 } vdsl2PMLineInitHist1DayGroup OBJECT-GROUP OBJECTS { xdsl2PMLHistinit1DMonitoredTime, xdsl2PMLHistinit1DFullInits, xdsl2PMLHistinit1DFailedFullInits, xdsl2PMLHistinit1DValidInterval } STATUS current DESCRIPTION "The group of PM counters for the previous 24 hours intervals full initializations." ::= { vdsl2Groups 25 } vdsl2PMLineInitHist1DayShortGroup OBJECT-GROUP OBJECTS { xdsl2PMLHistinit1DShortInits, xdsl2PMLHistinit1DFailedShortInits } STATUS current DESCRIPTION "The group of PM counters for the previous 24 hours intervals short initializations." ::= { vdsl2Groups 26 } Morgenstern, et al. Expires July 5, 2006 [Page 150] Internet-Draft VDSL2-LINE MIB January 2006 vdsl2PMChCurrGroup OBJECT-GROUP OBJECTS { xdsl2PMChCurrValidIntervals, xdsl2PMChCurrInvalidIntervals, xdsl2PMChCurr15MTimeElapsed, xdsl2PMChCurr15MCodingViolations, xdsl2PMChCurr15MCorrectedBlocks, xdsl2PMChCurr1DayValidIntervals, xdsl2PMChCurr1DayInvalidIntervals, xdsl2PMChCurr1DayTimeElapsed, xdsl2PMChCurr1DayCodingViolations, xdsl2PMChCurr1DayCorrectedBlocks } STATUS current DESCRIPTION "The group of objects that report the channel level counters for current PM intervals." ::= { vdsl2Groups 27 } vdsl2PMChHist15MinGroup OBJECT-GROUP OBJECTS { xdsl2PMChHist15MMonitoredTime, xdsl2PMChHist15MCodingViolations, xdsl2PMChHist15MCorrectedBlocks, xdsl2PMChHist15MValidInterval } STATUS current DESCRIPTION "The group of objects that report the channel level counters for previous 15 minutes PM intervals." ::= { vdsl2Groups 28 } vdsl2PMChHist1DGroup OBJECT-GROUP OBJECTS { xdsl2PMChHist1DMonitoredTime, xdsl2PMChHist1DCodingViolations, xdsl2PMChHist1DCorrectedBlocks, xdsl2PMChHist1DValidInterval } STATUS current DESCRIPTION "The group of objects that report the channel level counters for previous 24 hours PM intervals." ::= { vdsl2Groups 29 } Morgenstern, et al. Expires July 5, 2006 [Page 151] Internet-Draft VDSL2-LINE MIB January 2006 vdsl2ScalarSCGroup OBJECT-GROUP OBJECTS { xdsl2ScalarSCMaxInterfaces, xdsl2ScalarSCAvailInterfaces } STATUS current DESCRIPTION "The group of objects that report the available memory resources for DELT processes." ::= { vdsl2Groups 30 } vdsl2ThreshNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { xdsl2LinePerfFECSThreshAtuc, xdsl2LinePerfFECSThreshAtur, xdsl2LinePerfESThreshAtuc, xdsl2LinePerfESThreshAtur, xdsl2LinePerfSESThreshAtuc, xdsl2LinePerfSESThreshAtur, xdsl2LinePerfLOSSThreshAtuc, xdsl2LinePerfLOSSThreshAtur, xdsl2LinePerfUASThreshAtuc, xdsl2LinePerfUASThreshAtur, xdsl2LinePerfCodingViolationsThreshAtuc, xdsl2LinePerfCodingViolationsThreshAtur, xdsl2LinePerfCorrectedThreshAtuc, xdsl2LinePerfCorrectedThreshAtur, xdsl2LinePerfFailedFullInitThresh, xdsl2LinePerfFailedShortInitThresh } STATUS current DESCRIPTION "This group supports notifications of significant conditions associated with DSL lines." ::= { vdsl2Groups 31 } vdsl2StatusChangeNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { xdsl2LineStatusChangeAtuc, xdsl2LineStatusChangeAtur } STATUS current DESCRIPTION "This group supports notifications of thresholds crossing associated with DSL lines." Morgenstern, et al. Expires July 5, 2006 [Page 152] Internet-Draft VDSL2-LINE MIB January 2006 ::= { vdsl2Groups 32 } END 4. Implementation Analysis A management application intended to manage ADSL links (e.g., G.992.1) with this MIB module MUST be modified to adapt itself to certain differences between RFC 2662 [RFC2662] and this MIB module, including the following aspects: o Though the configuration templates/profiles allow referring to 1-4 bearer channels, ADSL links are limited to 2 channels at most o Though the channel configuration profile allows higher data rates, ADSL links are limited to downstream/upstream data rate as assumed in RFC 2662 [RFC2662] o The Impulse Noise Protection (INP) configuration parameters are given by minimum protection and maximum delay parameters. o The line configuration profile includes a sub-table that addresses mode-specific parameters. For ADSL links, the management application SHOULD create a row in that table for the 'adsl' mode. o The line configuration profile includes parameters that are irrelevant for ADSL links. Similarly, many status parameters in the MIB are irrelevant for certain ADSL modes. Therefore, it is advised to consult with ITU G.997.1 standard [G.997.1] regarding the scope and relevance of each parameter in this MIB. 5. Security Considerations There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability: o adsl2LineTable The table consists of the following objects that support SET operations: Morgenstern, et al. Expires July 5, 2006 [Page 153] Internet-Draft VDSL2-LINE MIB January 2006 * xdsl2LineCnfgTemplate * xdsl2LineAlarmCnfgTemplate * xdsl2LineCmndConfPmsf * xdsl2LineCmndConfLdsf * xdsl2LineCmndAutomodeColdStart Unauthorized changes to xdsl2LineCnfgTemplate could have a major adverse operational effect on many lines simultaneously. Unauthorized changes to xdsl2LineAlarmCnfgTemplate could have a contrary effect on notifications. Unauthorized changes to xdsl2LineCmndConfPmsf could have an adverse affect on the power consumption of a line and may disrupt an operational service. Unauthorized changes to xdsl2LineCmndConfLdsf could cause an unscheduled line test to be carried out on the line. Unauthorized changes to xdsl2LineCmndAutomodeColdStart could cause an unscheduled cold reset to the line. o adsl2SCStatusTable This table contains one object, xdsl2SCStatusRowStatus, that supports SET operations. Unauthorized changes could result in line test results being deleted prematurely. o xdsl2LineConfTemplateTable The table consists of the following objects that support SET operations: * xdsl2LConfTempLineProfile * xdsl2LConfTempChan1ConfProfile * xdsl2LConfTempChan1RaRatioDs * xdsl2LConfTempChan1RaRatioUs * xdsl2LConfTempChan2ConfProfile * xdsl2LConfTempChan2RaRatioDs * xdsl2LConfTempChan2RaRatioUs * xdsl2LConfTempChan3ConfProfile * xdsl2LConfTempChan3RaRatioDs * xdsl2LConfTempChan3RaRatioUs * xdsl2LConfTempChan4ConfProfile * xdsl2LConfTempChan4RaRatioDs * xdsl2LConfTempChan4RaRatioUs Morgenstern, et al. Expires July 5, 2006 [Page 154] Internet-Draft VDSL2-LINE MIB January 2006 * xdsl2LConfTempRowStatus Unauthorized changes to xdsl2LConfTempLineProfile, xdsl2LConfTempChan1ConfProfile, xdsl2LConfTempChan2ConfProfile, xdsl2LConfTempChan3ConfProfile, or xdsl2LConfTempChan4ConfProfile could have an adverse operational effect on several lines; could change several lines over to running in unwanted levels of operation; or could result in several services undergoing changes in the number of channels that carry the service. Unauthorized changes to xdsl2LConfTempChan1RaRatioDs, xdsl2LConfTempChan2RaRatioDs, xdsl2LConfTempChan3RaRatioDs, or xdsl2LConfTempChan4RaRatioDs, would alter the relative rate allocations among all channels belonging to a line. This could have an adverse operational effect on several lines. Unauthorized changes to xdsl2LConfTempRowStatus could result in templates being created or brought into service prematurely; or could result in templates being inadvertently deleted or taken out of service. o xdsl2LineConfProfTable The table consists of the following objects that support SET operations: * xdsl2LConfProfScMaskDs * xdsl2LConfProfScMaskUs * xdsl2LConfProfRfiBandsDs * xdsl2LConfProfRaModeDs * xdsl2LConfProfRaModeUs * xdsl2LConfProfRaUsNrmDs * xdsl2LConfProfRaUsNrmUs * xdsl2LConfProfRaUsTimeDs * xdsl2LConfProfRaUsTimeUs * xdsl2LConfProfRaDsNrmsDs * xdsl2LConfProfRaDsNrmsUs * xdsl2LConfProfRaDsTimeDs * xdsl2LConfProfRaDsTimeUs * xdsl2LConfProfTargetSnrmDs * xdsl2LConfProfTargetSnrmUs * xdsl2LConfProfMaxSnrmDs * xdsl2LConfProfMaxSnrmUs * xdsl2LConfProfMinSnrmDs * xdsl2LConfProfMinSnrmUs * xdsl2LConfProfMsgMinUs Morgenstern, et al. Expires July 5, 2006 [Page 155] Internet-Draft VDSL2-LINE MIB January 2006 * xdsl2LConfProfMsgMinDs * xdsl2LConfProfAtuTransSysEna * xdsl2LConfProfPmMode * xdsl2LConfProfL0Time * xdsl2LConfProfL2Time * xdsl2LConfProfL2Atpr * xdsl2LConfProfL2Atprt * xdsl2LConfProfRowStatus Unauthorized changes resulting in the setting of any of the above objects to an incorrect value could have an adverse operational effect on several lines. Also, unauthorized changes to xdsl2LConfProfRowStatus could result in unwanted line profiles being created or brought into service prematurely; or could result in line profiles being inadvertently deleted or taken out of service. o xdsl2LineConfProfModeSpecTable The table consists of the following objects that support SET operations: * xdsl2LConfProfMaxNomPsdDs * xdsl2LConfProfMaxNomPsdUs * xdsl2LConfProfMaxNomAtpDs * xdsl2LConfProfMaxNomAtpUs * xdsl2LConfProfMaxAggRxPwrUs * xdsl2LConfProfPsdMaskDs * xdsl2LConfProfPsdMaskUs * xdsl2LConfProfPsdMaskSelectUs * xdsl2LConfProfModeSpecRowStatus Unauthorized changes resulting in the setting of any of the above objects to an incorrect value could have an adverse operational effect on several lines. Also, unauthorized changes to xdsl2LConfProfModeSpecRowStatus could result in unwanted PSD configurations being created or brought into service prematurely; or could result in PSD configurations being inadvertently deleted or taken out of service. o xdsl2ChConfProfileTable The table consists of the following objects that support SET operations: Morgenstern, et al. Expires July 5, 2006 [Page 156] Internet-Draft VDSL2-LINE MIB January 2006 * xdsl2ChConfProfMinDataRateDs * xdsl2ChConfProfMinDataRateUs * xdsl2ChConfProfMinResDataRateDs * xdsl2ChConfProfMinResDataRateUs * xdsl2ChConfProfMaxDataRateDs * xdsl2ChConfProfMaxDataRateUs * xdsl2ChConfProfMinDataRateLowPwrDs * xdsl2ChConfProfMaxDelayDs * xdsl2ChConfProfMaxDelayUs * xdsl2ChConfProfMinProtectionDs * xdsl2ChConfProfMinProtectionUs * xdsl2ChConfProfMaxBerDs * xdsl2ChConfProfMaxBerUs * xdsl2ChConfProfUsDataRateDs * xdsl2ChConfProfDsDataRateDs * xdsl2ChConfProfUsDataRateUs * xdsl2ChConfProfDsDataRateUs * xdsl2ChConfProfImaEnabled * xdsl2ChConfProfRowStatus Unauthorized changes resulting in the setting of any of the above objects to an incorrect value could have an adverse operational effect on several lines. Also, unauthorized changes to xdsl2ChConfProfRowStatus could result in unwanted channel profiles being created or brought into service prematurely; or could result in channel profiles being inadvertently deleted or taken out of service. o xdsl2LineAlarmConfTemplateTable The table consists of the following objects that support SET operations: * xdsl2LAlarmConfTempLineProfile * xdsl2LAlarmConfTempChan1ConfProfile * xdsl2LalarmConfTempChan2ConfProfile * xdsl2LalarmConfTempChan3ConfProfile * xdsl2LalarmConfTempChan4ConfProfile * xdsl2LAlarmConfTempRowStatus Unauthorized changes to xdsl2LAlarmConfTempLineProfile, xdsl2LAlarmConfTempChan1ConfProfile, xdsl2LAlarmConfTempChan2ConfProfile, xdsl2LAlarmConfTempChan3ConfProfile, or xdsl2LAlarmConfTempChan4ConfProfile could have an adverse effect on the management of notifications generated at the scope of several to many lines; or could change several to many lines over Morgenstern, et al. Expires July 5, 2006 [Page 157] Internet-Draft VDSL2-LINE MIB January 2006 to running with unwanted management rates for generated notifications. Unauthorized changes to xdsl2LAlarmConfTempRowStatus could result in alarm templates being created or brought into service prematurely; or could result in alarm templates being inadvertently deleted or taken out of service. o xdsl2LineAlarmConfProfileTable The table consists of the following objects that support SET operations: * xdsl2LineAlarmConfProfileXtucThresh15MinFecs * xdsl2LineAlarmConfProfileXtucThresh15MinEs * xdsl2LineAlarmConfProfileXtucThresh15MinSes * xdsl2LineAlarmConfProfileXtucThresh15MinLoss * xdsl2LineAlarmConfProfileXtucThresh15MinUas * xdsl2LineAlarmConfProfileXturThresh15MinFecs * xdsl2LineAlarmConfProfileXturThresh15MinEs * xdsl2LineAlarmConfProfileXturThresh15MinSes * xdsl2LineAlarmConfProfileXturThresh15MinLoss * xdsl2LineAlarmConfProfileXturThresh15MinUas * xdsl2LineAlarmConfProfileThresh15MinFailedFullInt * xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt * xdsl2LineAlarmConfProfileRowStatus Increasing any of the threshold values could result in a notification being suppressed or deferred. Setting a threshold to 0 could result in a notification being suppressed. Suppressing or deferring a notification could prevent the timely delivery of important diagnostic information. Decreasing any of the threshold values could result in a notification being sent from the network falsely reporting a threshold crossing. Changing a threshold value could also have an impact on the amount of notifications the agent sends. The Notifications Section of this document has a paragraph which provides general guidance on the rate limiting of notifications. Agent implementations not providing rate limiting could result in notifications being generated at an uncontrolled rate. Unauthorized changes to a threshold value could result in an undesired notification rate. Unauthorized changes to row status could result in unwanted line alarm profiles being created or brought into service. Also, changes to the row status could result in line alarm profiles being inadvertently deleted or taken out of service. Morgenstern, et al. Expires July 5, 2006 [Page 158] Internet-Draft VDSL2-LINE MIB January 2006 o xdsl2ChAlarmConfProfileTable The table consists of the following objects that support SET operations: * xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations * xdsl2ChAlarmConfProfileXtucThresh15MinCorrected * xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations * xdsl2ChAlarmConfProfileXturThresh15MinCorrected * xdsl2ChAlarmConfProfileRowStatus * xdsl2LineAlarmConfProfileXturThresh15MinFecs * xdsl2LineAlarmConfProfileXturThresh15MinEs * xdsl2LineAlarmConfProfileXturThresh15MinSes * xdsl2LineAlarmConfProfileXturThresh15MinLoss * xdsl2LineAlarmConfProfileXturThresh15MinUas * xdsl2LineAlarmConfProfileThresh15MinFailedFullInt * xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt * xdsl2LineAlarmConfProfileRowStatus Increasing any of the threshold values could result in a notification being suppressed or deferred. Setting a threshold to 0 could result in a notification being suppressed. Suppressing or deferring a notification could prevent the timely delivery of important diagnostic information. Decreasing any of the threshold values could result in a notification being sent from the network falsely reporting a threshold crossing. Changing a threshold value could also have an impact on the amount of notifications the agent sends. The Notifications Section of this document has a paragraph which provides general guidance on the rate limiting of notifications. Agent implementations not providing rate limiting could result in notifications being generated at an uncontrolled rate. Unauthorized changes to a threshold value could result in an undesired notification rate. Unauthorized changes to row status could result in unwanted channel alarm profiles being created or brought into service. Also, changes to the row status could result in channel alarm profiles being inadvertently deleted or taken out of service. Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: Morgenstern, et al. Expires July 5, 2006 [Page 159] Internet-Draft VDSL2-LINE MIB January 2006 o xdsl2LineInventoryTable Access to these objects would allow an intruder to obtain information about which vendor's equipment is in use on the network. Further, such information is considered sensitive in many environments for competitive reasons. * xdsl2LInvG994VendorId * xdsl2LInvSystemVendorId * xdsl2LInvVersionNumber * xdsl2LInvSerialNumber * xdsl2LInvSelfTestResult * xdsl2LInvTransmissionCapabilities SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], Section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). It is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access only to those objects whose principals (users) have legitimate rights to indeed GET or SET (change/create/delete) them. 6. Acknowledgments The authors are deeply grateful to the authors of the HDSL2 LINE MIB (RFC 4319), Clay Sikes and Bob Ray, for contributing to accelerating the work on this document. The structure of this document as well as several paragraphs originate in their document. Other contributions and advice were received from the following: Randy Presuhn (Mindspring) Chen Jian (Huawei) Bert Wijnen (Lucent) Clay Sikes (Zhone) Morgenstern, et al. Expires July 5, 2006 [Page 160] Internet-Draft VDSL2-LINE MIB January 2006 7. References 7.1. Normative References [G.992.1] "Asymmetric digital subscriber line (ADSL) transceivers", ITU-T G.992.1, 1999. [G.992.2] "Splitterless asymmetric digital subscriber line (ADSL) transceivers", ITU-T G.992.2, 1999. [G.992.3] "Asymmetric digital subscriber line transceivers 2 (ADSL2)", ITU-T G.992.3, 2002. [G.992.4] "Splitterless asymmetric digital subscriber line transceivers 2 (Splitterless ADSL2)", ITU-T G.992.4, 2002. [G.992.5] "Asymmetric digital subscriber line (ADSL) transceivers - Extended bandwidth ADSL2 (ADSL2+)", ITU-T G.992.5, 2003. [G.993.1] "Very-high speed Digital Subscriber Line Transceivers", ITU-T G.993.1, June 2004. [G.993.2] "Very-high speed Digital Subscriber Line Transceivers 2 (VDSL2 draft)", ITU-T G.993.2, February 2006. [G.997.1] "Physical layer management for digital subscriber line (DSL) transceivers", ITU-T G.997.1, May 2003. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Morgenstern, et al. Expires July 5, 2006 [Page 161] Internet-Draft VDSL2-LINE MIB January 2006 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002. [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 3593, September 2003. [RFC3705] Ray, B. and R. Abbi, "High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 3705, February 2004. [T1E1.413] J. Bingham & F. Van der Putten, "Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interface. (T1.413 Issue 2)", ANSI T1E1.413-1998, June 1998. [TR-129] Adams, P., "Protocol Independent Object Model for Managing VDSL2", DSL Forum TR-129, March 2005. 7.2. Informative References [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects for the ADSL Lines", RFC 2662, August 1999. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC3418] Presuhn, R., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002. [RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL)", RFC 3728, February 2004. Morgenstern, et al. Expires July 5, 2006 [Page 162] Internet-Draft VDSL2-LINE MIB January 2006 Authors' Addresses Moti Morgenstern ECI Telecom Ltd. 30 Hasivim St. Petach Tikva 49517 Israel Phone: +972 3 926 6258 Fax: +972 3 928 7342 Email: moti.Morgenstern@ecitele.com Scott Baillie NEC Australia 649-655 Springvale Road Mulgrave, Victoria 3170 Australia Phone: +61 3 9264 3986 Fax: +61 3 9264 3892 Email: scott.baillie@nec.com.au Umberto Bonollo NEC Australia 649-655 Springvale Road Mulgrave, Victoria 3170 Australia Phone: +61 3 9264 3385 Fax: +61 3 9264 3892 Email: umberto.bonollo@nec.com.au Morgenstern, et al. Expires July 5, 2006 [Page 163] Internet-Draft VDSL2-LINE MIB January 2006 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2006). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Morgenstern, et al. Expires July 5, 2006 [Page 164]