OID reference

xdsl2LineSegmentBitsAlloc

1.3.6.1.2.1.10.251.1.2.1.1.3

Description

The bits allocation per subcarrier. An array of 256 octets (512 nibbles), designed for supporting up to 512 (downstream) subcarriers. When more than 512 subcarriers are supported, the status information is reported through multiple (up to 8) segments. The first segment is then used for the first 512 subcarriers. The s…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.2.1.10.251.1.2.1.1 (xdsl2LineSegmentEntry)
Node code
3
Node name
xdsl2LineSegmentBitsAlloc
Category
SNMP management object
Numeric OID
1.3.6.1.2.1.10.251.1.2.1.1.3
URN notation
urn:oid:1.3.6.1.2.1.10.251.1.2.1.1.3
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 2 1 10 251 1 2 1 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) stdmib-2(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) transmission(10) vdsl2MIB(251) xdsl2Objects(1) xdsl2Status(2) xdsl2LineSegmentTable(1) xdsl2LineSegmentEntry(1) xdsl2LineSegmentBitsAlloc(3)}
OID-IRI notation
  • /1/3/6/1/2/1/10/251/1/2/1/1/3
  • /ISO/Identified-Organization/6/1/2/1/10/251/1/2/1/1/3
  • /ISO/3/6/1/2/1/10/251/1/2/1/1/3
Named path variants
  • /iso/identified-organization/dod/internet/mgmt/mib-2/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/identified-organization/dod/internet/mgmt/mib/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/org/dod/internet/mgmt/mib-2/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/org/dod/internet/mgmt/mib/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/org/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/org/dod/internet/mgmt/stdmib-2/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/iso-identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/iso-identified-organization/dod/internet/mgmt/stdmib-2/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/iso-organization/dod/internet/mgmt/mib-2/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/iso-organization/dod/internet/mgmt/mib/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/iso-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc
  • /iso/iso-organization/dod/internet/mgmt/stdmib-2/transmission/vdsl2MIB/xdsl2Objects/xdsl2Status/xdsl2LineSegmentTable/xdsl2LineSegmentEntry/xdsl2LineSegmentBitsAlloc

SNMP properties

Value type
Xdsl2BitsAlloc
Units
bits
Maximum access defined by MIB
read-only
Status in MIB
current, mandatory

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — Cisco, MIBdepot, and others

Value type
Xdsl2BitsAlloc
Units
bits
Maximum access defined by MIB
read-only
Status in MIB
current

Variant 2 — Cisco SMIv1

Value type
Xdsl2BitsAlloc
Maximum access defined by MIB
read-only
Status in MIB
mandatory

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The bits allocation per subcarrier. An array of 256 octets (512 nibbles), designed for supporting up to 512 (downstream) subcarriers. When more than 512 subcarriers are supported, the status information is reported through multiple (up to 8) segments. The first segment is then used for the first 512 subcarriers. The second segment is used for the subcarriers 512 to 1023 and so on. The aggregate number of utilized nibbles in the downstream direction (in all segments) depends on NSds; in the upstream direction, it depends on NSus. This value is referred to here as NS. The segment number is in xdsl2SCStatusSegment. Nibble i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each segment is set to a value in the range 0 to 15 to indicate that the respective downstream or upstream subcarrier j (j=(segement-1)*512+i) has the same amount of bits allocation.
Original text from OID Repository
xdsl2LineSegmentBitsAlloc OBJECT-TYPE
SYNTAX Xdsl2BitsAlloc
UNITS "bits"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The bits allocation per subcarrier. An array of 256 octets
(512 nibbles), designed for supporting up to 512 (downstream)
subcarriers. When more than 512 subcarriers are supported, the
status information is reported through multiple (up to 8)
segments. The first segment is then used for the first 512
subcarriers. The second segment is used for the subcarriers
512 to 1023 and so on.
The aggregate number of utilized nibbles in the downstream
direction (in all segments) depends on NSds; in the
upstream direction, it depends on NSus.
This value is referred to here as NS. The segment number is in
xdsl2SCStatusSegment.
Nibble i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each
segment is set to a value in the range 0 to 15 to indicate that
the respective downstream or upstream subcarrier j
(j=(segement-1)*512+i) has the same amount of bits
allocation."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.1 (BITSpsds)
and paragraph #7.5.1.29.2 (BITSpsus)"
Sources for this description

OID Repository

View at oid-base.com
Automatically extracted from RFC5650

Circitor

Parsed from VDSL2-LINE-MIB.mib · VDSL2-LINE-MIB

Source file: Download VDSL2-LINE-MIB.mib

Browse all files from Circitor

Cisco

Source file: Download VDSL2-LINE-MIB.txt · Publisher's file

Vendor MIB copy from the Netdisco archive.

Source file: Download VDSL2-LINE-MIB · Publisher's file

Vendor MIB copy from the LibreNMS archive.

Source file: Download VDSL2-LINE-MIB · Publisher's file

Vendor MIB copy from the Observium Community archive.

Related source files and packages:

Source file: Download VDSL2-LINE-MIB.my · Publisher's file

Source file: Download RFC 5650 · Publisher's file · RFC errata

Browse all files from Cisco

Historical records

Additional source information

Information from Circitor
xdsl2LineSegmentBitsAlloc  OBJECT-TYPE
     SYNTAX      Xdsl2BitsAlloc
     UNITS       "bits"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION

     "The bits allocation per subcarrier.  An array of 256 octets
      (512 nibbles), designed for supporting up to 512 (downstream)
      subcarriers.  When more than 512 subcarriers are supported, the
      status information is reported through multiple (up to 8)
      segments.  The first segment is then used for the first 512
      subcarriers.  The second segment is used for the subcarriers
      512 to 1023 and so on.
      The aggregate number of utilized nibbles in the downstream
      direction (in all segments) depends on NSds; in the
      upstream direction, it depends on NSus.
      This value is referred to here as NS.  The segment number is in
      xdsl2SCStatusSegment.
      Nibble i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each
      segment is set to a value in the range 0 to 15 to indicate that
      the respective downstream or upstream subcarrier j
      (j=(segement-1)*512+i) has the same amount of bits
      allocation."
   REFERENCE    "ITU-T G.997.1, paragraph #7.5.1.29.1 (BITSpsds)
                 and paragraph #7.5.1.29.2 (BITSpsus)"
     ::= { xdsl2LineSegmentEntry 3 }
Information from Cisco SMIv1
xdsl2LineSegmentBitsAlloc OBJECT-TYPE
    SYNTAX Xdsl2BitsAlloc



    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "The bits allocation per subcarrier.  An array of 256 octets
         (512 nibbles), designed for supporting up to 512 (downstream)
         subcarriers.  When more than 512 subcarriers are supported, the
         status information is reported through multiple (up to 8)
         segments.  The first segment is then used for the first 512
         subcarriers.  The second segment is used for the subcarriers
         512 to 1023 and so on.
         The aggregate number of utilized nibbles in the downstream
         direction (in all segments) depends on NSds; in the
         upstream direction, it depends on NSus.
         This value is referred to here as NS.  The segment number is in
         xdsl2SCStatusSegment.
         Nibble i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each
         segment is set to a value in the range 0 to 15 to indicate that
         the respective downstream or upstream subcarrier j
         (j=(segement-1)*512+i) has the same amount of bits
         allocation."
    REFERENCE
        "ITU-T G.997.1, paragraph #7.5.1.29.1 (BITSpsds)
         and paragraph #7.5.1.29.2 (BITSpsus)"
    ::= { xdsl2LineSegmentEntry 3 }
Information from MIBdepot
xdsl2LineSegmentBitsAlloc  OBJECT-TYPE
     SYNTAX      Xdsl2BitsAlloc
     UNITS       "bits"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION

     "The bits allocation per subcarrier.  An array of 256 octets
      (512 nibbles), designed for supporting up to 512 (downstream)
      subcarriers.  When more than 512 subcarriers are supported, the
      status information is reported through multiple (up to 8)
      segments.  The first segment is then used for the first 512
      subcarriers.  The second segment is used for the subcarriers
      512 to 1023 and so on.
      The aggregate number of utilized nibbles in the downstream
      direction (in all segments) depends on NSds; in the
      upstream direction, it depends on NSus.
      This value is referred to here as NS.  The segment number is in
      xdsl2SCStatusSegment.
      Nibble i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each
      segment is set to a value in the range 0 to 15 to indicate that
      the respective downstream or upstream subcarrier j
      (j=(segement-1)*512+i) has the same amount of bits
      allocation."
   REFERENCE    "ITU-T G.997.1, paragraph #7.5.1.29.1 (BITSpsds)
                 and paragraph #7.5.1.29.2 (BITSpsus)"
     ::= { xdsl2LineSegmentEntry 3 }
Information from Cisco
xdsl2LineSegmentBitsAlloc  OBJECT-TYPE
     SYNTAX      Xdsl2BitsAlloc
     UNITS       "bits"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION

     "The bits allocation per subcarrier.  An array of 256 octets
      (512 nibbles), designed for supporting up to 512 (downstream)
      subcarriers.  When more than 512 subcarriers are supported, the
      status information is reported through multiple (up to 8)
      segments.  The first segment is then used for the first 512
      subcarriers.  The second segment is used for the subcarriers
      512 to 1023 and so on.
      The aggregate number of utilized nibbles in the downstream
      direction (in all segments) depends on NSds; in the
      upstream direction, it depends on NSus.
      This value is referred to here as NS.  The segment number is in
      xdsl2SCStatusSegment.
      Nibble i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each
      segment is set to a value in the range 0 to 15 to indicate that
      the respective downstream or upstream subcarrier j
      (j=(segement-1)*512+i) has the same amount of bits
      allocation."
   REFERENCE    "ITU-T G.997.1, paragraph #7.5.1.29.1 (BITSpsds)
                 and paragraph #7.5.1.29.2 (BITSpsus)"
     ::= { xdsl2LineSegmentEntry 3 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6.1.2)

Internet Assigned Numbers Authority

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.10.251.1.2.1.1.1 xdsl2LineSegmentDirection00 The direction of the subcarrier either
upstream or downstream.
1.3.6.1.2.1.10.251.1.2.1.1.2 xdsl2LineSegment00 The segment of the subcarriers status information
provided by this row.
Status parameters in this table are retrieved in segments…
1.3.6.1.2.1.10.251.1.2.1.1.4 xdsl2LineSegmentRowStatus00 Row Status. The SNMP agent will create a row in this table
for storing the results of a measurement performed on the
associated …