OID Repository
OID Repository
https://oid-base.com
Display OID:

Action itemiso(1) Action itemidentified-organization(3) Action itemdod(6) Action iteminternet(1) Action itemmgmt(2) Action itemmib-2(1) Action itemtransmission(10) Action itemvdsl2MIB(251) Action itemxdsl2Objects(1) Action itemxdsl2Status(2) Action itemxdsl2LineSegmentTable(1) Action itemxdsl2LineSegmentEntry(1)

xdsl2LineSegmentBitsAlloc(3)


Navigating the OID tree
Separation line
OID description

 
Action itemFormat of this page
Action itemModify this OID
Action itemCreate child OID
Action itemCreate sibling OID
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

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)"



Classification:

MIB object for network management

See classes of OIDs

Information:

Automatically extracted from IETF RFC 5650.

Separation line
Short URL for this page:
Separation line

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved © 2007-2025
Parent OID: xdsl2LineSegmentEntry(1) First sibling OID: xdsl2LineSegmentDirection(1) Previous sibling OID: xdsl2LineSegment(2) Next sibling OID: xdsl2LineSegmentRowStatus(4) Last sibling OID: xdsl2LineSegmentRowStatus(4) Separation line
Chatbot helper Webmaster Bullet 22 Apr 2020 Bullet Page top