Tech-invite3GPPspaceIETFspace
959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 5066

Ethernet in the First Mile Copper (EFMCu) Interfaces MIB

Pages: 90
Proposed Standard
Updated by:  7124
Part 3 of 4 – Pages 51 to 84
First   Prev   Next

Top   ToC   RFC5066 - Page 51   prevText
      efmCuPmeCapabilityEntry OBJECT-TYPE
        SYNTAX      EfmCuPmeCapabilityEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "An entry in the EFMCu PME Capability table.
          Each entry represents common aspects of an EFMCu PME port
          indexed by the ifIndex.  Note that an EFMCu PME port can be
          stacked below a single PCS port, also indexed by ifIndex,
          possibly together with other PME ports if PAF is enabled."
        INDEX  { ifIndex }
        ::= { efmCuPmeCapabilityTable 1 }

      EfmCuPmeCapabilityEntry ::=
        SEQUENCE {
          efmCuPmeSubTypesSupported     BITS
        }

      efmCuPmeSubTypesSupported  OBJECT-TYPE
        SYNTAX      BITS {
          ieee2BaseTLO(0),
          ieee2BaseTLR(1),
          ieee10PassTSO(2),
          ieee10PassTSR(3)
        }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "PME supported subtypes.  This is a bitmap of possible
          subtypes.  The various bit positions are:
            ieee2BaseTLO    - PME is capable of operating as 2BaseTL-O
            ieee2BaseTLR    - PME is capable of operating as 2BaseTL-R
            ieee10PassTSO   - PME is capable of operating as 10PassTS-O
            ieee10PassTSR   - PME is capable of operating as 10PassTS-R

          The desired mode of operation is determined by
          efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the
          current operating mode.

          If a Clause 45 MDIO Interface to the PCS is present, then this
          object combines the 10PASS-TS capable and 2BASE-TL capable
          bits in the 10P/2B PMA/PMD speed ability register and the
          CO supported and CPE supported bits in the 10P/2B PMA/PMD
          status register."
        REFERENCE
          "[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2,
          45.2.1.12.3"
        ::= { efmCuPmeCapabilityEntry 1 }
Top   ToC   RFC5066 - Page 52
      efmCuPmeStatusTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF EfmCuPmeStatusEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "This table provides common status information of EFMCu
          2BASE-TL/10PASS-TS PME ports.  Status information specific
          to 10PASS-TS PME is represented in efmCuPme10PStatusTable.

          This table contains live data from the equipment.  As such,
          it is NOT persistent."
        ::= { efmCuPme 3 }

      efmCuPmeStatusEntry OBJECT-TYPE
        SYNTAX      EfmCuPmeStatusEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "An entry in the EFMCu PME Status table.
          Each entry represents common aspects of an EFMCu PME port
          indexed by the ifIndex.  Note that an EFMCu PME port can be
          stacked below a single PCS port, also indexed by ifIndex,
          possibly together with other PME ports if PAF is enabled."
        INDEX  { ifIndex }
        ::= { efmCuPmeStatusTable 1 }

      EfmCuPmeStatusEntry ::=
        SEQUENCE {
          efmCuPmeOperStatus            INTEGER,
          efmCuPmeFltStatus             BITS,
          efmCuPmeOperSubType           INTEGER,
          efmCuPmeOperProfile           EfmProfileIndexOrZero,
          efmCuPmeSnrMgn                Integer32,
          efmCuPmePeerSnrMgn            Integer32,
          efmCuPmeLineAtn               Integer32,
          efmCuPmePeerLineAtn           Integer32,
          efmCuPmeEquivalentLength      Unsigned32,
          efmCuPmeTCCodingErrors        Counter32,
          efmCuPmeTCCrcErrors           Counter32
        }

      efmCuPmeOperStatus  OBJECT-TYPE
        SYNTAX      INTEGER {
          up(1),
          downNotReady(2),
          downReady(3),
          init(4)
        }
Top   ToC   RFC5066 - Page 53
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "Current PME link Operational Status.  Possible values are:
            up(1)           - The link is Up and ready to pass
                              64/65-octet encoded frames or fragments.
            downNotReady(2) - The link is Down and the PME does not
                              detect Handshake tones from its peer.
                              This value may indicate a possible
                              problem with the peer PME.
            downReady(3)    - The link is Down and the PME detects
                              Handshake tones from its peer.
            init(4)         - The link is Initializing, as a result of
                              ifAdminStatus being set to 'up' for a
                              particular PME or a PCS to which the PME
                              is connected.

          This object is intended to supplement the Down(2) state of
          ifOperStatus.

          This object partially maps to the Clause 30 attribute
          aPMEStatus.

          If a Clause 45 MDIO Interface to the PME is present, then this
          object partially maps to PMA/PMD link status bits in 10P/2B
          PMA/PMD status register."
        REFERENCE
          "[802.3ah] 30.11.2.1.3, 45.2.1.12.4"
        ::= { efmCuPmeStatusEntry 1 }

      efmCuPmeFltStatus  OBJECT-TYPE
        SYNTAX      BITS {
          lossOfFraming(0),
          snrMgnDefect(1),
          lineAtnDefect(2),
          deviceFault(3),
          configInitFailure(4),
          protocolInitFailure(5)
        }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "Current/Last PME link Fault Status.  This is a bitmap of
          possible conditions.  The various bit positions are:

            lossOfFraming       - Loss of Framing for 10P or
                                  Loss of Sync word for 2B PMD or
                                  Loss of 64/65-octet framing.
Top   ToC   RFC5066 - Page 54
            snrMgnDefect        - SNR margin dropped below the
                                  threshold.
            lineAtnDefect       - Line Attenuation exceeds the
                                  threshold.
            deviceFault         - Indicates a vendor-dependent
                                  diagnostic or self-test fault
                                  has been detected.
            configInitFailure   - Configuration initialization failure,
                                  due to inability of the PME link to
                                  support the configuration profile,
                                  requested during initialization.
            protocolInitFailure - Protocol initialization failure, due
                                  to an incompatible protocol used by
                                  the peer PME during init (that could
                                  happen if a peer PMD is a regular
                                  G.SDHSL/VDSL modem instead of a
                                  2BASE-TL/10PASS-TS PME).

          This object is intended to supplement ifOperStatus in IF-MIB.

          This object holds information about the last fault.
          efmCuPmeFltStatus is cleared by the device restart.
          In addition, lossOfFraming, configInitFailure, and
          protocolInitFailure are cleared by PME init;
          deviceFault is cleared by successful diagnostics/test;
          snrMgnDefect and lineAtnDefect are cleared by SNR margin
          and Line attenuation, respectively, returning to norm and by
          PME init.

          This object partially maps to the Clause 30 attribute
          aPMEStatus.

          If a Clause 45 MDIO Interface to the PME is present, then this
          object consolidates information from various PMA/PMD
          registers, namely: Fault bit in PMA/PMD status 1 register,
          10P/2B PMA/PMD link loss register,
          10P outgoing indicator bits status register,
          10P incoming indicator bits status register,
          2B state defects register."
        REFERENCE
          "[802.3ah] 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38,
          45.2.1.39, 45.2.1.54"
        ::= { efmCuPmeStatusEntry 2 }

      efmCuPmeOperSubType  OBJECT-TYPE
        SYNTAX      INTEGER {
          ieee2BaseTLO(1),
          ieee2BaseTLR(2),
Top   ToC   RFC5066 - Page 55
          ieee10PassTSO(3),
          ieee10PassTSR(4)
        }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "Current operational subtype of the PME.
          Possible values are:
            ieee2BaseTLO           - PME operates as 2BaseTL-O
            ieee2BaseTLR           - PME operates as 2BaseTL-R
            ieee10PassTSO          - PME operates as 10PassTS-O
            ieee10PassTSR          - PME operates as 10PassTS-R

          The desired operational subtype of the PME can be configured
          via the efmCuPmeAdminSubType variable.

          If a Clause 45 MDIO Interface to the PMA/PMD is present, then
          this object combines values of the Port subtype select
          bits, the PMA/PMD type selection bits in the 10P/2B
          PMA/PMD control register, and the PMA/PMD link status bits in
          the 10P/2B PMA/PMD status register."
        REFERENCE
          "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4"
        ::= { efmCuPmeStatusEntry 3 }

      efmCuPmeOperProfile  OBJECT-TYPE
        SYNTAX      EfmProfileIndexOrZero
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "PME current operating profile.  This object is a pointer to
          an entry in either the efmCuPme2BProfileTable or the
          efmCuPme10PProfileTable, depending on the current operating
          SubType of the PME as indicated by efmCuPmeOperSubType.
          Note that a profile entry to which efmCuPmeOperProfile is
          pointing can be created automatically to reflect achieved
          parameters in adaptive (not fixed) initialization,
          i.e., values of efmCuPmeOperProfile and efmCuAdminProfile or
          efmCuPmeAdminProfile may differ.
          The value of zero indicates that the PME is Down or
          Initializing.

          This object partially maps to the aOperatingProfile attribute
          in Clause 30."
        REFERENCE
          "[802.3ah] 30.11.2.1.7"
        ::= { efmCuPmeStatusEntry 4 }
Top   ToC   RFC5066 - Page 56
      efmCuPmeSnrMgn OBJECT-TYPE
        SYNTAX      Integer32(-127..128|65535)
        UNITS       "dB"
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The current Signal to Noise Ratio (SNR) margin with respect
          to the received signal as perceived by the local PME.
          The value of 65535 is returned when the PME is Down or
          Initializing.

          This object maps to the aPMESNRMgn attribute in Clause 30.

          If a Clause 45 MDIO Interface is present, then this
          object maps to the 10P/2B RX SNR margin register."
        REFERENCE
          "[802.3ah] 30.11.2.1.4, 45.2.1.16"
        ::= { efmCuPmeStatusEntry 5 }

      efmCuPmePeerSnrMgn OBJECT-TYPE
        SYNTAX      Integer32(-127..128|65535)
        UNITS       "dB"
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The current SNR margin in dB with respect to the received
          signal, as perceived by the remote (link partner) PME.
          The value of 65535 is returned when the PME is Down or
          Initializing.

          This object is irrelevant for the -R PME subtypes.  The value
          of 65535 SHALL be returned in this case.

          If a Clause 45 MDIO Interface is present, then this
          object maps to the 10P/2B link partner RX SNR margin
          register."
        REFERENCE
          "[802.3ah] 45.2.1.17"
        ::= { efmCuPmeStatusEntry 6}

      efmCuPmeLineAtn OBJECT-TYPE
        SYNTAX      Integer32(-127..128|65535)
        UNITS       "dB"
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The current Line Attenuation in dB as perceived by the local
          PME.
Top   ToC   RFC5066 - Page 57
          The value of 65535 is returned when the PME is Down or
          Initializing.

          If a Clause 45 MDIO Interface is present, then this
          object maps to the Line Attenuation register."
        REFERENCE
          "[802.3ah] 45.2.1.18"
        ::= { efmCuPmeStatusEntry 7 }

      efmCuPmePeerLineAtn OBJECT-TYPE
        SYNTAX      Integer32(-127..128|65535)
        UNITS       "dB"
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The current Line Attenuation in dB as perceived by the remote
          (link partner) PME.
          The value of 65535 is returned when the PME is Down or
          Initializing.

          This object is irrelevant for the -R PME subtypes.  The value
          of 65535 SHALL be returned in this case.

          If a Clause 45 MDIO Interface is present, then this
          object maps to the 20P/2B link partner Line Attenuation
          register."
        REFERENCE
          "[802.3ah] 45.2.1.19"
        ::= { efmCuPmeStatusEntry 8 }

      efmCuPmeEquivalentLength  OBJECT-TYPE
        SYNTAX      Unsigned32(0..8192|65535)
        UNITS       "m"
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "An estimate of the equivalent loop's physical length in
          meters, as perceived by the PME after the link is established.
          An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
          perfect square root attenuation characteristic, without any
          bridged taps.
          The value of 65535 is returned if the link is Down or
          Initializing or the PME is unable to estimate the equivalent
          length.

          For a 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME
          is present, then this object maps to the 10P Electrical Length
          register."
Top   ToC   RFC5066 - Page 58
        REFERENCE
          "[802.3ah] 45.2.1.21"
        ::= { efmCuPmeStatusEntry 9 }

      efmCuPmeTCCodingErrors OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The number of 64/65-octet encapsulation errors.  This counter
          is incremented for each 64/65-octet encapsulation error
          detected by the 64/65-octet receive function.

          This object maps to aTCCodingViolations attribute in
          Clause 30.

          If a Clause 45 MDIO Interface to the PME TC is present, then
          this object maps to the TC coding violations register
          (see 45.2.6.12).

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[802.3ah] 61.3.3.1, 30.11.2.1.5, 45.2.6.12"
        ::= { efmCuPmeStatusEntry 10 }

      efmCuPmeTCCrcErrors OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The number of TC-CRC errors.  This counter is incremented for
          each TC-CRC error detected by the 64/65-octet receive function
          (see 61.3.3.3 and Figure 61-19).

          This object maps to aTCCRCErrors attribute in
          Clause 30.

          If a Clause 45 MDIO Interface to the PME TC is present, then
          this object maps to the TC CRC error register
          (see 45.2.6.11).

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
Top   ToC   RFC5066 - Page 59
        REFERENCE
          "[802.3ah] 61.3.3.3, 30.11.2.1.10, 45.2.6.11"
        ::= { efmCuPmeStatusEntry 11 }

     -- 2BASE-TL specific PME group

      efmCuPme2B      OBJECT IDENTIFIER ::= { efmCuPme 5 }

      efmCuPme2BProfileTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF EfmCuPme2BProfileEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "This table supports definitions of administrative and
          operating profiles for 2BASE-TL PMEs.
          The first 14 entries in this table SHALL always be defined as
          follows (see 802.3ah Annex 63A):
          -------+-------+-------+-----+------+-------------+-----------
          Profile MinRate MaxRate Power Region Constellation Comment
           index  (Kbps)  (Kbps)  (dBm)
          -------+-------+-------+-----+------+-------------+-----------
             1     5696    5696    13.5    1   32-TCPAM      default
             2     3072    3072    13.5    1   32-TCPAM
             3     2048    2048    13.5    1   16-TCPAM
             4     1024    1024    13.5    1   16-TCPAM
             5      704     704    13.5    1   16-TCPAM
             6      512     512    13.5    1   16-TCPAM
             7     5696    5696    14.5    2   32-TCPAM
             8     3072    3072    14.5    2   32-TCPAM
             9     2048    2048    14.5    2   16-TCPAM
            10     1024    1024    13.5    2   16-TCPAM
            11      704     704    13.5    2   16-TCPAM
            12      512     512    13.5    2   16-TCPAM
            13      192    5696       0    1   0             best effort
            14      192    5696       0    2   0             best effort
          -------+-------+-------+-----+------+-------------+-----------

          These default entries SHALL be created during agent
          initialization and MUST NOT be deleted.

          Entries following the first 14 can be dynamically created and
          deleted to provide custom administrative (configuration)
          profiles and automatic operating profiles.

          This table MUST be maintained in a persistent manner."
        REFERENCE
          "[802.3ah] Annex 63A, 30.11.2.1.6"
        ::= { efmCuPme2B  2 }
Top   ToC   RFC5066 - Page 60
      efmCuPme2BProfileEntry OBJECT-TYPE
        SYNTAX      EfmCuPme2BProfileEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "Each entry corresponds to a single 2BASE-TL PME profile.
          Each profile contains a set of parameters, used either for
          configuration or representation of a 2BASE-TL PME.
          In case a particular profile is referenced via the
          efmCuPmeAdminProfile object (or efmCuAdminProfile if
          efmCuPmeAdminProfile is zero), it represents the desired
          parameters for the 2BaseTL-O PME initialization.
          If a profile is referenced via an efmCuPmeOperProfile object,
          it represents the current operating parameters of an
          operational PME.

          Profiles may be created/deleted using the row creation/
          deletion mechanism via efmCuPme2BProfileRowStatus.  If an
          active entry is referenced, the entry MUST remain 'active'
          until all references are removed.
          Default entries MUST NOT be removed."
        INDEX { efmCuPme2BProfileIndex }
        ::= { efmCuPme2BProfileTable 1 }

      EfmCuPme2BProfileEntry ::=
        SEQUENCE {
          efmCuPme2BProfileIndex           EfmProfileIndex,
          efmCuPme2BProfileDescr           SnmpAdminString,
          efmCuPme2BRegion                 INTEGER,
          efmCuPme2BsMode                  EfmProfileIndexOrZero,
          efmCuPme2BMinDataRate            Unsigned32,
          efmCuPme2BMaxDataRate            Unsigned32,
          efmCuPme2BPower                  Unsigned32,
          efmCuPme2BConstellation          INTEGER,
          efmCuPme2BProfileRowStatus       RowStatus
        }

      efmCuPme2BProfileIndex OBJECT-TYPE
        SYNTAX      EfmProfileIndex
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "2BASE-TL PME profile index.
          This object is the unique index associated with this profile.
          Entries in this table are referenced via efmCuAdminProfile or
          efmCuPmeAdminProfile objects."
        ::= { efmCuPme2BProfileEntry 1 }
Top   ToC   RFC5066 - Page 61
      efmCuPme2BProfileDescr OBJECT-TYPE
        SYNTAX      SnmpAdminString
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "A textual string containing information about a 2BASE-TL PME
          profile.  The string may include information about the data
          rate and spectral limitations of this particular profile."
        ::= { efmCuPme2BProfileEntry 2 }

      efmCuPme2BRegion  OBJECT-TYPE
        SYNTAX      INTEGER {
          region1(1),
          region2(2)
        }
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "Regional settings for a 2BASE-TL PME, as specified in the
          relevant Regional Annex of [G.991.2].
          Regional settings specify the Power Spectral Density (PSD)
          mask and the Power Back-Off (PBO) values, and place
          limitations on the max allowed data rate, power, and
          constellation.

          Possible values for this object are:
            region1      - Annexes A and F (e.g., North America)
            region2      - Annexes B and G (e.g., Europe)

          Annex A/B specify regional settings for data rates 192-2304
          Kbps using 16-TCPAM encoding.
          Annex F/G specify regional settings for rates 2320-3840 Kbps
          using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM
          encoding.

          If a Clause 45 MDIO Interface to the PME is present, then this
          object partially maps to the Region bits in the 2B general
          parameter register."
        REFERENCE
          "[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G"
        ::= { efmCuPme2BProfileEntry 3 }

      efmCuPme2BsMode  OBJECT-TYPE
        SYNTAX      EfmProfileIndexOrZero
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "Desired custom Spectral Mode for a 2BASE-TL PME.  This object
Top   ToC   RFC5066 - Page 62
          is a pointer to an entry in efmCuPme2BsModeTable and a block
          of entries in efmCuPme2BRateReachTable, which together define
          (country-specific) reach-dependent rate limitations in
          addition to those defined by efmCuPme2BRegion.

          The value of this object is the index of the referenced
          spectral mode.
          The value of zero (default) indicates that no specific
          spectral mode is applicable.

          Attempts to set this object to a value that is not the value
          of the index for an active entry in the corresponding spectral
          mode table MUST be rejected."
        REFERENCE
          "efmCuPme2BsModeTable, efmCuPme2BRateReachTable"
        DEFVAL { 0 }
        ::= { efmCuPme2BProfileEntry 4 }

      efmCuPme2BMinDataRate  OBJECT-TYPE
        SYNTAX  Unsigned32(192..5696)
        UNITS       "Kbps"
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "Minimum Data Rate for the 2BASE-TL PME.
          This object can take values of (n x 64)Kbps,
          where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.

          The data rate of the 2BASE-TL PME is considered 'fixed' when
          the value of this object equals that of efmCuPme2BMaxDataRate.
          If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
          the administrative profile, the data rate is considered
          'adaptive', and SHALL be set to the maximum attainable rate
          not exceeding efmCuPme2BMaxDataRate, under the spectral
          limitations placed by the efmCuPme2BRegion and
          efmCuPme2BsMode.

          Note that the current operational data rate of the PME is
          represented by the ifSpeed object of IF-MIB.

          If a Clause 45 MDIO Interface to the PME is present, then this
          object maps to the Min Data Rate1 bits in the 2B PMD
          parameters register.

          This object MUST be maintained in a persistent manner."
        REFERENCE
          "[802.3ah] 45.2.1.43"
        ::= { efmCuPme2BProfileEntry 5 }
Top   ToC   RFC5066 - Page 63
      efmCuPme2BMaxDataRate  OBJECT-TYPE
        SYNTAX  Unsigned32(192..5696)
        UNITS       "Kbps"
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "Maximum Data Rate for the 2BASE-TL PME.
          This object can take values of (n x 64)Kbps,
          where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.

          The data rate of the 2BASE-TL PME is considered 'fixed' when
          the value of this object equals that of efmCuPme2BMinDataRate.
          If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
          the administrative profile, the data rate is considered
          'adaptive', and SHALL be set to the maximum attainable rate
          not exceeding efmCuPme2BMaxDataRate, under the spectral
          limitations placed by the efmCuPme2BRegion and
          efmCuPme2BsMode.

          Note that the current operational data rate of the PME is
          represented by the ifSpeed object of IF-MIB.

          If a Clause 45 MDIO Interface to the PME is present, then this
          object maps to the Max Data Rate1 bits in the 2B PMD
          parameters register.

          This object MUST be maintained in a persistent manner."
        REFERENCE
          "[802.3ah] 45.2.1.43"
        ::= { efmCuPme2BProfileEntry 6 }

      efmCuPme2BPower  OBJECT-TYPE
        SYNTAX      Unsigned32(0|10..42)
        UNITS       "0.5 dBm"
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "Signal Transmit Power.  Multiple of 0.5 dBm.
          The value of 0 in the administrative profile means that the
          signal transmit power is not fixed and SHALL be set to
          maximize the attainable rate, under the spectral limitations
          placed by the efmCuPme2BRegion and efmCuPme2BsMode.

          If a Clause 45 MDIO Interface to the PME is present, then this
          object maps to the Power1 bits in the 2B PMD parameters
          register."
        REFERENCE
          "[802.3ah] 45.2.1.43"
Top   ToC   RFC5066 - Page 64
        ::= { efmCuPme2BProfileEntry 7 }

      efmCuPme2BConstellation  OBJECT-TYPE
        SYNTAX      INTEGER {
          adaptive(0),
          tcpam16(1),
          tcpam32(2)
        }
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "TCPAM Constellation of the 2BASE-TL PME.
          The possible values are:
            adaptive(0)    - either 16- or 32-TCPAM
            tcpam16(1)     - 16-TCPAM
            tcpam32(2)     - 32-TCPAM

          The value of adaptive(0) in the administrative profile means
          that the constellation is not fixed and SHALL be set to
          maximize the attainable rate, under the spectral limitations
          placed by the efmCuPme2BRegion and efmCuPme2BsMode.

          If a Clause 45 MDIO Interface to the PME is present, then this
          object maps to the Constellation1 bits in the 2B general
          parameter register."
        REFERENCE
           "[802.3ah] 45.2.1.43"
        ::= { efmCuPme2BProfileEntry 8 }

      efmCuPme2BProfileRowStatus OBJECT-TYPE
        SYNTAX      RowStatus
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "This object controls the creation, modification, or deletion
          of the associated entry in the efmCuPme2BProfileTable per the
          semantics of RowStatus.

          If an 'active' entry is referenced via efmCuAdminProfile or
          efmCuPmeAdminProfile instance(s), the entry MUST remain
          'active'.

          An 'active' entry SHALL NOT be modified.  In order to modify
          an existing entry, it MUST be taken out of service (by setting
          this object to 'notInService'), modified, and set 'active'
          again."
        ::= { efmCuPme2BProfileEntry 9 }
Top   ToC   RFC5066 - Page 65
      efmCuPme2BsModeTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF EfmCuPme2BsModeEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "This table, together with efmCu2BReachRateTable, supports
          definition of administrative custom spectral modes for
          2BASE-TL PMEs, describing spectral limitations in addition to
          those specified by efmCuPme2BRegion.

          In some countries, spectral regulations (e.g., UK ANFP) limit
          the length of the loops for certain data rates.  This table
          allows these country-specific limitations to be specified.

          Entries in this table referenced by the efmCuPme2BsMode
          MUST NOT be deleted until all the active references are
          removed.

          This table MUST be maintained in a persistent manner."
        REFERENCE
          "efmCu2BReachRateTable"
        ::= { efmCuPme2B  3 }

      efmCuPme2BsModeEntry OBJECT-TYPE
        SYNTAX      EfmCuPme2BsModeEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "Each entry specifies a spectral mode description and its
          index, which is used to reference corresponding entries in the
          efmCu2BReachRateTable.

          Entries may be created/deleted using the row creation/
          deletion mechanism via efmCuPme2BsModeRowStatus."
        INDEX { efmCuPme2BsModeIndex }
        ::= { efmCuPme2BsModeTable 1 }

      EfmCuPme2BsModeEntry ::=
        SEQUENCE {
          efmCuPme2BsModeIndex             EfmProfileIndex,
          efmCuPme2BsModeDescr             SnmpAdminString,
          efmCuPme2BsModeRowStatus         RowStatus
        }

      efmCuPme2BsModeIndex OBJECT-TYPE
        SYNTAX      EfmProfileIndex
        MAX-ACCESS  not-accessible
        STATUS      current
Top   ToC   RFC5066 - Page 66
        DESCRIPTION
          "2BASE-TL PME Spectral Mode index.
          This object is the unique index associated with this spectral
          mode.
          Entries in this table are referenced via the efmCuPme2BsMode
          object."
        ::= { efmCuPme2BsModeEntry 1 }

      efmCuPme2BsModeDescr OBJECT-TYPE
        SYNTAX      SnmpAdminString
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "A textual string containing information about a 2BASE-TL PME
          spectral mode.  The string may include information about
          corresponding (country-specific) spectral regulations
          and rate/reach limitations of this particular spectral mode."
        ::= { efmCuPme2BsModeEntry 2 }

      efmCuPme2BsModeRowStatus OBJECT-TYPE
        SYNTAX      RowStatus
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "This object controls creation, modification, or deletion of
          the associated entry in efmCuPme2BsModeTable per the semantics
          of RowStatus.

          If an 'active' entry is referenced via efmCuPme2BsMode
          instance(s), the entry MUST remain 'active'.

          An 'active' entry SHALL NOT be modified.  In order to modify
          an existing entry, it MUST be taken out of service (by setting
          this object to 'notInService'), modified, and set 'active'
          again."
        ::= { efmCuPme2BsModeEntry 3 }


      efmCuPme2BReachRateTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF EfmCuPme2BReachRateEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "This table supports the definition of administrative custom
          spectral modes for 2BASE-TL PMEs, providing spectral
          limitations in addition to those specified by
          efmCuPme2BRegion.
Top   ToC   RFC5066 - Page 67
          The spectral regulations in some countries (e.g., UK ANFP)
          limit the length of the loops for certain data rates.
          This table allows these country-specific limitations to be
          specified.

          Below is an example of this table for [ANFP]:
          ----------+-------+-------
          Equivalent MaxRate MaxRate
            Length    PAM16   PAM32
              (m)     (Kbps)  (Kbps)
          ----------+-------+-------
              975      2304    5696
             1125      2304    5504
             1275      2304    5120
             1350      2304    4864
             1425      2304    4544
             1500      2304    4288
             1575      2304    3968
             1650      2304    3776
             1725      2304    3520
             1800      2304    3264
             1875      2304    3072
             1950      2048    2688
             2100      1792    2368
             2250      1536       0
             2400      1408       0
             2550      1280       0
             2775      1152       0
             2925      1152       0
             3150      1088       0
             3375      1024       0
          ----------+-------+-------

          Entries in this table referenced by an efmCuPme2BsMode
          instance MUST NOT be deleted.

          This table MUST be maintained in a persistent manner."
        REFERENCE
          "[ANFP]"
        ::= { efmCuPme2B  4 }

      efmCuPme2BReachRateEntry OBJECT-TYPE
        SYNTAX      EfmCuPme2BReachRateEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "Each entry specifies maximum 2BASE-TL PME data rates
          allowed for a certain equivalent loop length, when using
Top   ToC   RFC5066 - Page 68
          16-TCPAM or 32-TCPAM encoding.

          When a 2BASE-TL PME is initialized, its data rate MUST NOT
          exceed one of the following limitations:
          - the value of efmCuPme2BMaxDataRate
          - maximum data rate allowed by efmCuPme2BRegion and
            efmCuPme2BPower
          - maximum data rate for a given encoding specified in the
            efmCuPme2BsModeEntry, corresponding to the equivalent loop
            length, estimated by the PME

          It is RECOMMENDED that the efmCuPme2BEquivalentLength values
          are assigned in increasing order, starting from the minimum
          value.

          Entries may be created/deleted using the row creation/
          deletion mechanism via efmCuPme2ReachRateRowStatus."
        INDEX { efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex }
        ::= { efmCuPme2BReachRateTable 1 }

      EfmCuPme2BReachRateEntry ::=
        SEQUENCE {
          efmCuPme2BReachRateIndex         EfmProfileIndex,
          efmCuPme2BEquivalentLength       Unsigned32,
          efmCuPme2BMaxDataRatePam16       Unsigned32,
          efmCuPme2BMaxDataRatePam32       Unsigned32,
          efmCuPme2BReachRateRowStatus     RowStatus
        }

      efmCuPme2BReachRateIndex OBJECT-TYPE
        SYNTAX      EfmProfileIndex
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "2BASE-TL custom spectral mode Reach-Rate table index.
          This object is the unique index associated with each entry."
        ::= { efmCuPme2BReachRateEntry 1 }

      efmCuPme2BEquivalentLength  OBJECT-TYPE
        SYNTAX      Unsigned32(0..8192)
        UNITS       "m"
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "Maximum allowed equivalent loop's physical length in meters
          for the specified data rates.
          An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
          perfect square root attenuation characteristic, without any
Top   ToC   RFC5066 - Page 69
          bridged taps."
        ::= { efmCuPme2BReachRateEntry 2 }

      efmCuPme2BMaxDataRatePam16  OBJECT-TYPE
        SYNTAX      Unsigned32(0|192..5696)
        UNITS       "Kbps"
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "Maximum data rate for a 2BASE-TL PME at the specified
          equivalent loop's length using TC-PAM16 encoding.
          The value of zero means that TC-PAM16 encoding should not be
          used at this distance."
        ::= { efmCuPme2BReachRateEntry 3 }

      efmCuPme2BMaxDataRatePam32  OBJECT-TYPE
        SYNTAX      Unsigned32(0|192..5696)
        UNITS       "Kbps"
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "Maximum data rate for a 2BASE-TL PME at the specified
          equivalent loop's length using TC-PAM32 encoding.
          The value of zero means that TC-PAM32 encoding should not be
          used at this distance."
        ::= { efmCuPme2BReachRateEntry 4 }

      efmCuPme2BReachRateRowStatus OBJECT-TYPE
        SYNTAX      RowStatus
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "This object controls the creation, modification, or deletion
          of the associated entry in the efmCuPme2BReachRateTable per
          the semantics of RowStatus.

          If an 'active' entry is referenced via efmCuPme2BsMode
          instance(s), the entry MUST remain 'active'.

          An 'active' entry SHALL NOT be modified.  In order to modify
          an existing entry, it MUST be taken out of service (by setting
          this object to 'notInService'), modified, and set 'active'
          again."
        ::= { efmCuPme2BReachRateEntry 5 }


     -- 10PASS-TS specific PME group
Top   ToC   RFC5066 - Page 70
      efmCuPme10P      OBJECT IDENTIFIER ::= { efmCuPme 6 }

      efmCuPme10PProfileTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF EfmCuPme10PProfileEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "This table supports definitions of configuration profiles for
          10PASS-TS PMEs.
          The first 22 entries in this table SHALL always be defined as
          follows (see 802.3ah Annex 62B.3, table 62B-1):
          -------+--------+----+---------+-----+-----+---------------
          Profile Bandplan UPBO BandNotch DRate URate Comment
           Index  PSDMask#  p#    p#        p#    p#
          -------+--------+----+---------+-----+-----+---------------
             1      1      3    2,6,10,11    20    20 default profile
             2     13      5    0            20    20
             3      1      1    0            20    20
             4     16      0    0           100   100
             5     16      0    0            70    50
             6      6      0    0            50    10
             7     17      0    0            30    30
             8      8      0    0            30     5
             9      4      0    0            25    25
            10      4      0    0            15    15
            11     23      0    0            10    10
            12     23      0    0             5     5
            13     16      0    2,5,9,11    100   100
            14     16      0    2,5,9,11     70    50
            15      6      0    2,6,10,11    50    10
            16     17      0    2,5,9,11     30    30
            17      8      0    2,6,10,11    30     5
            18      4      0    2,6,10,11    25    25
            19      4      0    2,6,10,11    15    15
            20     23      0    2,5,9,11     10    10
            21     23      0    2,5,9,11      5     5
            22     30      0    0           200    50
          -------+--------+----+---------+-----+-----+---------------

          These default entries SHALL be created during agent
          initialization and MUST NOT be deleted.

          Entries following the first 22 can be dynamically created and
          deleted to provide custom administrative (configuration)
          profiles and automatic operating profiles.

          This table MUST be maintained in a persistent manner."
        REFERENCE
Top   ToC   RFC5066 - Page 71
          "[802.3ah] Annex 62B.3, 30.11.2.1.6"
        ::= { efmCuPme10P  1 }

      efmCuPme10PProfileEntry OBJECT-TYPE
        SYNTAX      EfmCuPme10PProfileEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "Each entry corresponds to a single 10PASS-TS PME profile.

          Each profile contains a set of parameters, used either for
          configuration or representation of a 10PASS-TS PME.
          In case a particular profile is referenced via the
          efmCuPmeAdminProfile object (or efmCuAdminProfile if
          efmCuPmeAdminProfile is zero), it represents the desired
          parameters for the 10PassTS-O PME initialization.
          If a profile is referenced via an efmCuPmeOperProfile object,
          it represents the current operating parameters of the PME.

          Profiles may be created/deleted using the row creation/
          deletion mechanism via efmCuPme10PProfileRowStatus.  If an
          'active' entry is referenced, the entry MUST remain 'active'
          until all references are removed.
          Default entries MUST NOT be removed."
        INDEX { efmCuPme10PProfileIndex }
        ::= { efmCuPme10PProfileTable 1 }

      EfmCuPme10PProfileEntry ::=
        SEQUENCE {
          efmCuPme10PProfileIndex           EfmProfileIndex,
          efmCuPme10PProfileDescr           SnmpAdminString,
          efmCuPme10PBandplanPSDMskProfile  INTEGER,
          efmCuPme10PUPBOReferenceProfile   INTEGER,
          efmCuPme10PBandNotchProfiles      BITS,
          efmCuPme10PPayloadDRateProfile    INTEGER,
          efmCuPme10PPayloadURateProfile    INTEGER,
          efmCuPme10PProfileRowStatus       RowStatus
        }

      efmCuPme10PProfileIndex OBJECT-TYPE
        SYNTAX      EfmProfileIndex
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "10PASS-TS PME profile index.
          This object is the unique index associated with this profile.
          Entries in this table are referenced via efmCuAdminProfile or
          efmCuPmeAdminProfile."
Top   ToC   RFC5066 - Page 72
        ::= { efmCuPme10PProfileEntry 1 }

      efmCuPme10PProfileDescr OBJECT-TYPE
        SYNTAX      SnmpAdminString
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "A textual string containing information about a 10PASS-TS PME
          profile.  The string may include information about data rate
          and spectral limitations of this particular profile."
        ::= { efmCuPme10PProfileEntry 2 }

      efmCuPme10PBandplanPSDMskProfile  OBJECT-TYPE
        SYNTAX  INTEGER {
          profile1(1),
          profile2(2),
          profile3(3),
          profile4(4),
          profile5(5),
          profile6(6),
          profile7(7),
          profile8(8),
          profile9(9),
          profile10(10),
          profile11(11),
          profile12(12),
          profile13(13),
          profile14(14),
          profile15(15),
          profile16(16),
          profile17(17),
          profile18(18),
          profile19(19),
          profile20(20),
          profile21(21),
          profile22(22),
          profile23(23),
          profile24(24),
          profile25(25),
          profile26(26),
          profile27(27),
          profile28(28),
          profile29(29),
          profile30(30)
        }
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
Top   ToC   RFC5066 - Page 73
          "The 10PASS-TS PME Bandplan and PSD Mask Profile, as specified
          in 802.3ah Annex 62A, table 62A-1.  Possible values are:
          --------------+------------------------+------------+--------
          Profile Name    PSD Mask                  Bands      G.993.1
                                                  0/1/2/3/4/5  Bandplan
          --------------+------------------------+------------+--------
          profile1(1)    T1.424 FTTCab.M1         x/D/U/D/U    A
          profile2(2)    T1.424 FTTEx.M1          x/D/U/D/U    A
          profile3(3)    T1.424 FTTCab.M2         x/D/U/D/U    A
          profile4(4)    T1.424 FTTEx.M2          x/D/U/D/U    A
          profile5(5)    T1.424 FTTCab.M1         D/D/U/D/U    A
          profile6(6)    T1.424 FTTEx.M1          D/D/U/D/U    A
          profile7(7)    T1.424 FTTCab.M2         D/D/U/D/U    A
          profile8(8)    T1.424 FTTEx.M2          D/D/U/D/U    A
          profile9(9)    T1.424 FTTCab.M1         U/D/U/D/x    A
          profile10(10)  T1.424 FTTEx.M1          U/D/U/D/x    A
          profile11(11)  T1.424 FTTCab.M2         U/D/U/D/x    A
          profile12(12)  T1.424 FTTEx.M2          U/D/U/D/x    A
          profile13(13)  TS 101 270-1 Pcab.M1.A   x/D/U/D/U    B
          profile14(14)  TS 101 270-1 Pcab.M1.B   x/D/U/D/U    B
          profile15(15)  TS 101 270-1 Pex.P1.M1   x/D/U/D/U    B
          profile16(16)  TS 101 270-1 Pex.P2.M1   x/D/U/D/U    B
          profile17(17)  TS 101 270-1 Pcab.M2     x/D/U/D/U    B
          profile18(18)  TS 101 270-1 Pex.P1.M2   x/D/U/D/U    B
          profile19(19)  TS 101 270-1 Pex.P2.M2   x/D/U/D/U    B
          profile20(20)  TS 101 270-1 Pcab.M1.A   U/D/U/D/x    B
          profile21(21)  TS 101 270-1 Pcab.M1.B   U/D/U/D/x    B
          profile22(22)  TS 101 270-1 Pex.P1.M1   U/D/U/D/x    B
          profile23(23)  TS 101 270-1 Pex.P2.M1   U/D/U/D/x    B
          profile24(24)  TS 101 270-1 Pcab.M2     U/D/U/D/x    B
          profile25(25)  TS 101 270-1 Pex.P1.M2   U/D/U/D/x    B
          profile26(26)  TS 101 270-1 Pex.P2.M2   U/D/U/D/x    B
          profile27(27)  G.993.1 F.1.2.1          x/D/U/D/U    Annex F
          profile28(28)  G.993.1 F.1.2.2          x/D/U/D/U    Annex F
          profile29(29)  G.993.1 F.1.2.3          x/D/U/D/U    Annex F
          profile30(30)  T1.424 FTTCab.M1 (ext.)  x/D/U/D/U/D  Annex A
          --------------+------------------------+------------+--------
          "
        REFERENCE
          "[802.3ah] Annex 62A"
        ::= { efmCuPme10PProfileEntry 3 }

      efmCuPme10PUPBOReferenceProfile  OBJECT-TYPE
        SYNTAX  INTEGER {
          profile0(0),
          profile1(1),
          profile2(2),
          profile3(3),
Top   ToC   RFC5066 - Page 74
          profile4(4),
          profile5(5),
          profile6(6),
          profile7(7),
          profile8(8),
          profile9(9)
        }
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "The 10PASS-TS PME Upstream Power Back-Off (UPBO) Reference
          PSD Profile, as specified in 802.3 Annex 62A, table 62A-3.
          Possible values are:
          ------------+-----------------------------
          Profile Name   Reference PSD
          ------------+-----------------------------
          profile0(0)  no profile
          profile1(1)  T1.424        Noise A    M1
          profile2(2)  T1.424        Noise A    M2
          profile3(3)  T1.424        Noise F    M1
          profile4(4)  T1.424        Noise F    M2
          profile5(5)  TS 101 270-1  Noise A&B
          profile6(6)  TS 101 270-1  Noise C
          profile7(7)  TS 101 270-1  Noise D
          profile8(8)  TS 101 270-1  Noise E
          profile9(9)  TS 101 270-1  Noise F
          ------------+-----------------------------
          "
        REFERENCE
          "[802.3ah] Annex 62A.3.5"
        ::= { efmCuPme10PProfileEntry 4 }

      efmCuPme10PBandNotchProfiles  OBJECT-TYPE
        SYNTAX  BITS {
          profile0(0),
          profile1(1),
          profile2(2),
          profile3(3),
          profile4(4),
          profile5(5),
          profile6(6),
          profile7(7),
          profile8(8),
          profile9(9),
          profile10(10),
          profile11(11)
        }
        MAX-ACCESS  read-create
Top   ToC   RFC5066 - Page 75
        STATUS      current
        DESCRIPTION
          "The 10PASS-TS PME Egress Control Band Notch Profile bitmap,
          as specified in 802.3 Annex 62A, table 62A-4.  Possible values
          are:
          --------------+--------+------+------------+------+------
          Profile Name   G.991.3  T1.424 TS 101 270-1 StartF EndF
                         table    table  table        (MHz)  (MHz)
          --------------+--------+------+------------+------+------
          profile0(0)    no profile
          profile1(1)    F-5 #01  -      -            1.810  1.825
          profile2(2)    6-2      15-1   17           1.810  2.000
          profile3(3)    F-5 #02  -      -            1.907  1.912
          profile4(4)    F-5 #03  -      -            3.500  3.575
          profile5(5)    6-2      -      17           3.500  3.800
          profile6(6)    -        15-1   -            3.500  4.000
          profile7(7)    F-5 #04  -      -            3.747  3.754
          profile8(8)    F-5 #05  -      -            3.791  3.805
          profile9(9)    6-2      -      17           7.000  7.100
          profile10(10)  F-5 #06  15-1   -            7.000  7.300
          profile11(11)  6-2      15-1   1            10.100 10.150
          --------------+--------+------+------------+------+------

          Any combination of profiles can be specified by ORing
          individual profiles, for example, a value of 0x2230 selects
          profiles 2, 6, 10, and 11."
        REFERENCE
          "[802.3ah] Annex 62A.3.5"
        ::= { efmCuPme10PProfileEntry 5 }

      efmCuPme10PPayloadDRateProfile  OBJECT-TYPE
        SYNTAX      INTEGER {
          profile5(5),
          profile10(10),
          profile15(15),
          profile20(20),
          profile25(25),
          profile30(30),
          profile50(50),
          profile70(70),
          profile100(100),
          profile140(140),
          profile200(200)
        }
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "The 10PASS-TS PME Downstream Payload Rate Profile, as
Top   ToC   RFC5066 - Page 76
          specified in 802.3 Annex 62A.  Possible values are:
            profile5(5)      - 2.5 Mbps
            profile10(10)    - 5 Mbps
            profile15(15)    - 7.5 Mbps
            profile20(20)    - 10 Mbps
            profile25(25)    - 12.5 Mbps
            profile30(30)    - 15 Mbps
            profile50(50)    - 25 Mbps
            profile70(70)    - 35 Mbps
            profile100(100)  - 50 Mbps
            profile140(140)  - 70 Mbps
            profile200(200)  - 100 Mbps

          Each value represents a target for the PME's Downstream
          Payload Bitrate as seen at the MII.  If the payload rate of
          the selected profile cannot be achieved based on the loop
          environment, bandplan, and PSD mask, the PME initialization
          SHALL fail."
        REFERENCE
          "[802.3ah] Annex 62A.3.6"
        ::= { efmCuPme10PProfileEntry 6 }

      efmCuPme10PPayloadURateProfile  OBJECT-TYPE
        SYNTAX      INTEGER {
          profile5(5),
          profile10(10),
          profile15(15),
          profile20(20),
          profile25(25),
          profile30(30),
          profile50(50),
          profile70(70),
          profile100(100)
        }
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "The 10PASS-TS PME Upstream Payload Rate Profile, as specified
           in 802.3 Annex 62A.  Possible values are:
            profile5(5)       - 2.5 Mbps
            profile10(10)     - 5 Mbps
            profile15(15)     - 7.5 Mbps
            profile20(20)     - 10 Mbps
            profile25(25)     - 12.5 Mbps
            profile30(30)     - 15 Mbps
            profile50(50)     - 25 Mbps
            profile70(70)     - 35 Mbps
            profile100(100)   - 50 Mbps
Top   ToC   RFC5066 - Page 77
          Each value represents a target for the PME's Upstream Payload
          Bitrate as seen at the MII.  If the payload rate of the
          selected profile cannot be achieved based on the loop
          environment, bandplan, and PSD mask, the PME initialization
          SHALL fail."
        REFERENCE
          "[802.3ah] Annex 62A.3.6"
        ::= { efmCuPme10PProfileEntry 7 }

      efmCuPme10PProfileRowStatus OBJECT-TYPE
        SYNTAX      RowStatus
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "This object controls creation, modification, or deletion of
          the associated entry in efmCuPme10PProfileTable per the
          semantics of RowStatus.

          If an active entry is referenced via efmCuAdminProfile or
          efmCuPmeAdminProfile, the entry MUST remain 'active' until
          all references are removed.

          An 'active' entry SHALL NOT be modified.  In order to modify
          an existing entry, it MUST be taken out of service (by setting
          this object to 'notInService'), modified, and set 'active'
          again."
        ::= { efmCuPme10PProfileEntry 8 }


      efmCuPme10PStatusTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF EfmCuPme10PStatusEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "This table provides status information of EFMCu 10PASS-TS
          PMEs (modems).

          This table contains live data from the equipment.  As such,
          it is NOT persistent."
        ::= { efmCuPme10P 2 }

      efmCuPme10PStatusEntry OBJECT-TYPE
        SYNTAX      EfmCuPme10PStatusEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "An entry in the EFMCu 10PASS-TS PME Status table."
        INDEX  { ifIndex }
Top   ToC   RFC5066 - Page 78
        ::= { efmCuPme10PStatusTable 1 }

      EfmCuPme10PStatusEntry ::=
        SEQUENCE {
          efmCuPme10PFECCorrectedBlocks     Counter32,
          efmCuPme10PFECUncorrectedBlocks   Counter32
        }

      efmCuPme10PFECCorrectedBlocks  OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The number of received and corrected Forward Error Correction
          (FEC) codewords in this 10PASS-TS PME.

          This object maps to the aPMEFECCorrectedBlocks attribute in
          Clause 30.

          If a Clause 45 MDIO Interface to the PMA/PMD is present,
          then this object maps to the 10P FEC correctable errors
          register.

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[802.3ah] 45.2.1.22, 30.11.2.1.8"
        ::= { efmCuPme10PStatusEntry 1 }

      efmCuPme10PFECUncorrectedBlocks  OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The number of received uncorrectable FEC codewords in this
          10PASS-TS PME.

          This object maps to the aPMEFECUncorrectableBlocks attribute
          in Clause 30.

          If a Clause 45 MDIO Interface to the PMA/PMD is present,
          then this object maps to the 10P FEC uncorrectable errors
          register.

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
Top   ToC   RFC5066 - Page 79
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[802.3ah] 45.2.1.23, 30.11.2.1.9"
        ::= { efmCuPme10PStatusEntry 2 }

     --
     -- Conformance Statements
     --

      efmCuGroups      OBJECT IDENTIFIER ::= { efmCuConformance 1 }

      efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 }

      -- Object Groups

      efmCuBasicGroup OBJECT-GROUP
        OBJECTS {
          efmCuPAFSupported,
          efmCuAdminProfile,
          efmCuTargetDataRate,
          efmCuTargetSnrMgn,
          efmCuAdaptiveSpectra,
          efmCuPortSide,
          efmCuFltStatus
        }
        STATUS      current
        DESCRIPTION
          "A collection of objects representing management information
          common for all types of EFMCu ports."
        ::= { efmCuGroups 1 }

      efmCuPAFGroup OBJECT-GROUP
        OBJECTS {
          efmCuPeerPAFSupported,
          efmCuPAFCapacity,
          efmCuPeerPAFCapacity,
          efmCuPAFAdminState,
          efmCuPAFDiscoveryCode,
          efmCuPAFRemoteDiscoveryCode,
          efmCuNumPMEs
        }
        STATUS      current
        DESCRIPTION
          "A collection of objects supporting OPTIONAL PME
          Aggregation Function (PAF) and PAF discovery in EFMCu ports."
        ::= { efmCuGroups 2 }
Top   ToC   RFC5066 - Page 80
      efmCuPAFErrorsGroup OBJECT-GROUP
        OBJECTS {
          efmCuPAFInErrors,
          efmCuPAFInSmallFragments,
          efmCuPAFInLargeFragments,
          efmCuPAFInBadFragments,
          efmCuPAFInLostFragments,
          efmCuPAFInLostStarts,
          efmCuPAFInLostEnds,
          efmCuPAFInOverflows
        }
        STATUS      current
        DESCRIPTION
          "A collection of objects supporting OPTIONAL error counters
          of PAF on EFMCu ports."
        ::= { efmCuGroups 3 }

      efmCuPmeGroup OBJECT-GROUP
        OBJECTS {
          efmCuPmeAdminProfile,
          efmCuPmeOperStatus,
          efmCuPmeFltStatus,
          efmCuPmeSubTypesSupported,
          efmCuPmeAdminSubType,
          efmCuPmeOperSubType,
          efmCuPAFRemoteDiscoveryCode,
          efmCuPmeOperProfile,
          efmCuPmeSnrMgn,
          efmCuPmePeerSnrMgn,
          efmCuPmeLineAtn,
          efmCuPmePeerLineAtn,
          efmCuPmeEquivalentLength,
          efmCuPmeTCCodingErrors,
          efmCuPmeTCCrcErrors,
          efmCuPmeThreshLineAtn,
          efmCuPmeThreshSnrMgn
        }
        STATUS      current
        DESCRIPTION
          "A collection of objects providing information about
          a 2BASE-TL/10PASS-TS PME."
        ::= { efmCuGroups 4 }

      efmCuAlarmConfGroup OBJECT-GROUP
        OBJECTS {
          efmCuThreshLowRate,
          efmCuLowRateCrossingEnable,
          efmCuPmeThreshLineAtn,
Top   ToC   RFC5066 - Page 81
          efmCuPmeLineAtnCrossingEnable,
          efmCuPmeThreshSnrMgn,
          efmCuPmeSnrMgnCrossingEnable,
          efmCuPmeDeviceFaultEnable,
          efmCuPmeConfigInitFailEnable,
          efmCuPmeProtocolInitFailEnable
        }
        STATUS      current
        DESCRIPTION
          "A collection of objects supporting configuration of alarm
          thresholds and notifications in EFMCu ports."
        ::= { efmCuGroups 5 }

      efmCuNotificationGroup NOTIFICATION-GROUP
        NOTIFICATIONS {
          efmCuLowRateCrossing,
          efmCuPmeLineAtnCrossing,
          efmCuPmeSnrMgnCrossing,
          efmCuPmeDeviceFault,
          efmCuPmeConfigInitFailure,
          efmCuPmeProtocolInitFailure
        }
        STATUS      current
        DESCRIPTION
          "This group supports notifications of significant conditions
          associated with EFMCu ports."
        ::= { efmCuGroups 6 }

      efmCuPme2BProfileGroup OBJECT-GROUP
        OBJECTS {
          efmCuPme2BProfileDescr,
          efmCuPme2BRegion,
          efmCuPme2BsMode,
          efmCuPme2BMinDataRate,
          efmCuPme2BMaxDataRate,
          efmCuPme2BPower,
          efmCuPme2BConstellation,
          efmCuPme2BProfileRowStatus,
          efmCuPme2BsModeDescr,
          efmCuPme2BsModeRowStatus,
          efmCuPme2BEquivalentLength,
          efmCuPme2BMaxDataRatePam16,
          efmCuPme2BMaxDataRatePam32,
          efmCuPme2BReachRateRowStatus
        }
        STATUS      current
        DESCRIPTION
          "A collection of objects that constitute a configuration
Top   ToC   RFC5066 - Page 82
          profile for configuration of 2BASE-TL ports."
        ::= { efmCuGroups 7}

      efmCuPme10PProfileGroup OBJECT-GROUP
        OBJECTS {
          efmCuPme10PProfileDescr,
          efmCuPme10PBandplanPSDMskProfile,
          efmCuPme10PUPBOReferenceProfile,
          efmCuPme10PBandNotchProfiles,
          efmCuPme10PPayloadDRateProfile,
          efmCuPme10PPayloadURateProfile,
          efmCuPme10PProfileRowStatus
        }
        STATUS  current
        DESCRIPTION
          "A collection of objects that constitute a configuration
          profile for configuration of 10PASS-TS ports."
        ::= { efmCuGroups 8 }

      efmCuPme10PStatusGroup OBJECT-GROUP
        OBJECTS {
          efmCuPme10PFECCorrectedBlocks,
          efmCuPme10PFECUncorrectedBlocks
        }
        STATUS  current
        DESCRIPTION
          "A collection of objects providing status information
          specific to 10PASS-TS PMEs."
        ::= { efmCuGroups 9 }

     -- Compliance Statements

      efmCuCompliance MODULE-COMPLIANCE
        STATUS      current
        DESCRIPTION
          "The compliance statement for 2BASE-TL/10PASS-TS interfaces.
          Compliance with the following external compliance statements
          is REQUIRED:

          MIB Module             Compliance Statement
          ----------             --------------------
          IF-MIB                 ifCompliance3
          EtherLike-MIB          dot3Compliance2
          MAU-MIB                mauModIfCompl3

          Compliance with the following external compliance statements
          is OPTIONAL for implementations supporting PME Aggregation
          Function (PAF) with flexible cross-connect between the PCS
Top   ToC   RFC5066 - Page 83
          and PME ports:

          MIB Module             Compliance Statement
          ----------             --------------------
          IF-INVERTED-STACK-MIB  ifInvCompliance
          IF-CAP-STACK-MIB       ifCapStackCompliance"

        MODULE  -- this module
          MANDATORY-GROUPS {
            efmCuBasicGroup,
            efmCuPmeGroup,
            efmCuAlarmConfGroup,
            efmCuNotificationGroup
          }

          GROUP       efmCuPme2BProfileGroup
          DESCRIPTION
            "Support for this group is only required for implementations
            supporting 2BASE-TL PHY."

          GROUP       efmCuPme10PProfileGroup
          DESCRIPTION
            "Support for this group is only required for implementations
            supporting 10PASS-TS PHY."

          GROUP       efmCuPAFGroup
          DESCRIPTION
            "Support for this group is only required for
            implementations supporting PME Aggregation Function (PAF)."

          GROUP       efmCuPAFErrorsGroup
          DESCRIPTION
            "Support for this group is OPTIONAL for implementations
            supporting PME Aggregation Function (PAF)."

          GROUP       efmCuPme10PStatusGroup
          DESCRIPTION
            "Support for this group is OPTIONAL for implementations
            supporting 10PASS-TS PHY."

          OBJECT      efmCuPmeSubTypesSupported
          SYNTAX      BITS {
            ieee2BaseTLO(0),
            ieee2BaseTLR(1),
            ieee10PassTSO(2),
            ieee10PassTSR(3)
          }
          DESCRIPTION
Top   ToC   RFC5066 - Page 84
            "Support for all subtypes is not required.  However, at
            least one value SHALL be supported."

          OBJECT      efmCuPmeAdminSubType
          MIN-ACCESS  read-only
          DESCRIPTION
            "Write access is not required (needed only for PMEs
            supporting more than a single subtype, e.g.,
            ieee2BaseTLO and ieee2BaseTLR or ieee10PassTSO and
            ieee10PassTSR)."

          OBJECT      efmCuTargetSnrMgn
          MIN-ACCESS  read-only
          DESCRIPTION
            "Write access is OPTIONAL.  For PHYs without write access,
            the target SNR margin SHALL be fixed at 5dB for 2BASE-TL
            and 6dB for 10PASS-TS."

          OBJECT      efmCuAdaptiveSpectra
          MIN-ACCESS  read-only
          DESCRIPTION
            "Write access is OPTIONAL.  For PHYs without write access,
            the default value SHOULD be false."

        ::= { efmCuCompliances 1 }
   END



(page 84 continued on part 4)

Next Section