Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vlanPrioToRxPriorityMappingTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"VlanPrioToRxPriorityMappingEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\" Different operators uses different VLAN p-bit classification of services. In addition to voice, video and best effort data services, it may also be required to distinguish between various data services, and to classify traffic based on other criteria's than just service. As a consequence, utilization of the entire range of VLAN p-bit values from 0 to 7 is needed. More incoming traffic may arrive from the uplink Ethernet interface, than it is possible to forward on the downlink interface. In this case it is important to forward traffic with highest priority first and drop low priority traffic if necessary. With this table it is possible to configure which receive priority (rxPriority) is used for incoming downstream traffic carrying specific VLAN p-bit values. It is possible to specify, per VLAN p-bit value, which receive priority incoming downstream traffic is allocated to. If more than one VLAN tag is included in the received packets, only the first VLAN tags priority is taken into account when mapping to receive priority. Any packets received without VLAN tag are mapped to the highest receive priority (rxPriority=1). Below is an illustration of how the VLAN priority could be mapped to the receive priorities. The illustration is just and example, any combinations of mappings are valid. Note that the number of receive priorities may vary from one product to another. ___________________________________ | | | | | -- p-bit 7 ----> rxPriority 1 | | / | Incoming traffic from | / | the aggregation network | /---- p-bit 6 ----> rxPriority 2 | (VLAN p-bit 0-7) |/ | ----------------------->|\\ | | \\---- p-bit 5 ----> rxPriority 3 | | \\ | | \\ | | -- p-bit 0-4 --> rxPriority 4 | | | |___________________________________| \"",
"::=",
"{",
"uplinkEthernetRxScheduling",
"15",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"VlanPrioToRxPriorityMappingEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Different operators uses different VLAN p-bit classification of services. In addition to voice, video and best effort data services, it may also be required to distinguish between various data services, and to classify traffic based on other criteria's than just service. As a consequence, utilization of the entire range of VLAN p-bit values from 0 to 7 is needed. More incoming traffic may arrive from the uplink Ethernet interface, than it is possible to forward on the downlink interface. In this case it is important to forward traffic with highest priority first and drop low priority traffic if necessary. With this table it is possible to configure which receive priority (rxPriority) is used for incoming downstream traffic carrying specific VLAN p-bit values. It is possible to specify, per VLAN p-bit value, which receive priority incoming downstream traffic is allocated to. If more than one VLAN tag is included in the received packets, only the first VLAN tags priority is taken into account when mapping to receive priority. Any packets received without VLAN tag are mapped to the highest receive priority (rxPriority=1). Below is an illustration of how the VLAN priority could be mapped to the receive priorities. The illustration is just and example, any combinations of mappings are valid. Note that the number of receive priorities may vary from one product to another. ___________________________________ | | | | | -- p-bit 7 ----> rxPriority 1 | | / | Incoming traffic from | / | the aggregation network | /---- p-bit 6 ----> rxPriority 2 | (VLAN p-bit 0-7) |/ | ----------------------->|\\ | | \\---- p-bit 5 ----> rxPriority 3 | | \\ | | \\ | | -- p-bit 0-4 --> rxPriority 4 | | | |___________________________________|"
],
null,
null,
null,
null
]
}