Configure Priority Mapping
Priority mapping is the mapping among the 802.1p priority, DSCP value and local priority (LP) in the packet. Modify or distribute the priority field of the packet to serve for the congestion avoidance and congestion management.
Configuration Condition
None
Configure Priority Mapping
Priority mapping includes the ingress mapping and egress mapping. The ingress mapping maps to the local priority (LP) according to the 802.1p priority and DSCP value in the packet; the egress mapping maps to the 802.1p priority and DSCP value according to the local priority (LP).
Table1-2 Configure the priority mapping
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Configure the priority mapping profile
|
qos map-table { ingress | egress } template-name
|
Mandatory
Configure the egress and ingress priority profile.
|
Enter the profile view
|
{ dot1p-lp | dscp-lp | lp-dot1p | lp-dscp } index to value
|
Optional
By default, the priority mapping in the profile is the default mapping relation.
|
Bind the port with the priority mapping profile
|
map-table template-name { ingress | egress }
|
Mandatory
By default, do not bind the priority mapping profile.
|
- For the packet with the specified priority entering the queue, you'd better not let the packet enter queue 7, because the packets sent out from CPU all enter queue 7. If queue 7 has too many packets, the packets from CPU may be dropped.
- The dscp-Ip mapping and dotlp-lp are configured in the profile at the same time. The dscp-lp has higher priority and it takes effect first.
- After enabling the ingress dot1p-lp mapping, the 802.1p priority of the forwarded packet is not modified according to the local priority (LP) by default. For example, the dot1p-lp mapping relation is 1 to 5; after matching the 802.1p of the VLAN Tag in the ingress packet to 1, the 802.1p priority of the forwarded packet with VLAN Tag is still 1.
- The priority mapping does not take effect for the packet remarked by the action group. First, remark the local priority (LP) at the ingress action group, and then mapping to the 802.1p priority and DSCP value of the packet via the local priority (LP) at the egress takes effect. Remark the 802.1p priority at the ingress and then mapping the local priority and DSCP value via the 802.1p priority does not take effect, but remarking the 802.1p priority itself takes effect. Mapping according to the 802.1p priority of the original packet also takes effect, that is to say, remarking takes effect separately, the priority mapping takes effect separately, and the priority mapping according to the remarked value does not take effect.
- If the QINQ function is enabled on the port, and the bound profile of the port contains dot1p-lp and dscp-lp mappings, maybe you cannot get the desired mapping result. Therefore, it is recommended not to enable the port binding priority mapping function of QINQ on one port at the same time.
- After configuring the lp-dscp mapping, the default mapping of lp-dscp is 0 to 0, 1 to 8, 2 to 16, 3 to 24, 4 to 32, 5 to 40, 6 to 48, and 7 to 56.
Configure Default Priority Mapping
The default priority mapping, the same as the priority mapping, has the ingress and egress mapping. The difference lies in that the default priority mapping maps the entries not configured with priority mapping to the default value.
Table 1-3 Configure the default priority mapping
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Configure the priority mapping profile
|
qos map-table { ingress | egress } template-name
|
Mandatory
Configure the ingress and egress priority profile.
|
Configure the default priority mapping
|
{ dot1p-lp | dscp-lp | lp-dot1p | lp-dscp } default value
|
Mandatory
By default, do not configure the default priority mapping.
|