![Dell S6000-ON Скачать руководство пользователя страница 725](http://html.mh-extra.com/html/dell/s6000-on/s6000-on_configuration-manual_84557725.webp)
associate to queue 1 using the policy map. The same class map needs to be applied in switch B as well
and when queue 1 gets congested, PFC would be generated for priority 2. Switch A on receiving PFC
frames with priority 2 would stop scheduling queue 1.
If a tagged packet with VLAN dot1p as 5 ingresses on switch A. Consider that tagged packet also has
DSCP in range of 0-7.These packets will match the class map and get queued on queue 1 on both the
switches.
But when queue 1 gets congested on switch B, PFC frames for tagged packets will not be generated as
PFC is not enabled on dot1p priority 5.
Support for marking dot1p value in L3 Input Qos Policy
In case the incoming packet is untagged and the packet which goes out to the peer is tagged, then the
dot1p should be marked appropriately using L3 Input Qos Policy. This is required because in the peer
switch PFC will be generated based on the dot1p value. Currently if the ingress is untagged and egress is
tagged, then dot1p priority 0(default) will be added as part of the tag header and from the next hop PFC
will be based on that dot1p priority. Support is added to mark the dot1p value in the L3 Input Qos Policy
in this feature. Hence it is possible to mark both DSCP and Dot1p simultaneously in the L3 Input Qos
Policy. You are expected to mark the Dot1p priority when the ingress packets are untagged but go out to
the peer as tagged
NOTE: L2 qos-policy behavior will be retained and would not be changed, that is we would not
allow to set both DSCP and Dot1p in the L2 Input Qos Policy.
Example case:
Consider that two switches A and B are connected back to back via a tagged interface. Consider the case
where untagged packets arrive on switch A, if you want to generate PFC for priority 2 for DSCP range
0-7, then you must need to match the interested traffic using the class map. You should create an L3
Input Qos Policy and mark vlan dot1p as 2. You have to associate both the L3 class map and L3 Input Qos
Policy to queue 1 using the policy map.
In switch B, global dot1p honoring should be enabled, this will queue the packets on queue 1 as the dot1p
will be 2 and PFC should be enabled for priority 2. The policy map applied on switch A need not be
enabled in switch B. When queue 1 in switch B gets congested, PFC will be generated for priority 2 which
will be honored in switch A.
You will not get the below CLI errors after adding this support:
Dell(conf)#qos-policy-input qos-input
Dell(conf-qos-policy-in)#set mac-dot1p 5
% Error: Dot1p marking is not allowed on L3 Input Qos Policy.
Dell(conf-qos-policy-in)#
You will also be able to mark both DSCP and Dot1p in the L3 Input Qos Policy:
Dell(conf)#qos-policy-input qos-input
Dell(conf-qos-policy-in)#set mac-dot1p 2
Dell(conf-qos-policy-in)#set ip-dscp 5
Dell Dell(conf-qos-policy-in)#
Quality of Service (QoS)
725
Содержание S6000-ON
Страница 1: ...Dell Configuration Guide for the S6000 ON System 9 9 0 0 ...
Страница 505: ...Figure 60 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 505 ...
Страница 508: ...Figure 62 Inspecting a LAG Port on BRAVO Using the show interface Command 508 Link Aggregation Control Protocol LACP ...
Страница 509: ...Figure 63 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 509 ...
Страница 552: ...mac address table static multicast mac address vlan vlan id output range interface 552 Microsoft Network Load Balancing ...
Страница 557: ...Figure 80 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 557 ...
Страница 558: ...Figure 81 Configuring PIM in Multiple Routing Domains 558 Multicast Source Discovery Protocol MSDP ...
Страница 562: ...Figure 83 MSDP Default Peer Scenario 1 562 Multicast Source Discovery Protocol MSDP ...
Страница 563: ...Figure 84 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 563 ...
Страница 564: ...Figure 85 MSDP Default Peer Scenario 3 564 Multicast Source Discovery Protocol MSDP ...
Страница 665: ...Policy based Routing PBR 665 ...
Страница 672: ...ip pim bsr border Remove candidate RP advertisements clear ip pim rp mapping 672 PIM Sparse Mode PIM SM ...
Страница 818: ...Figure 110 Single and Double Tag TPID Match 818 Service Provider Bridging ...
Страница 819: ...Figure 111 Single and Double Tag First byte TPID Match Service Provider Bridging 819 ...
Страница 995: ...Figure 140 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 995 ...