-----------------------------------------------------------------------
20416 1 18 IP 0x0 0 0 23.64.0.5/32 0.0.0.0/0 20 2
20417 1 18 IP 0x0 0 0 0.0.0.0/0 0.0.0.0/0 - 0
20418 1 0 IP 0x0 0 0 23.64.0.2/32 0.0.0.0/0 10 1
20419 1 0 IP 0x0 0 0 0.0.0.0/0 0.0.0.0/0 - 0
20420 1 0 IP 0x0 0 0 23.64.0.3/32 0.0.0.0/0 12 1
20421 1 0 IP 0x0 0 0 0.0.0.0/0 0.0.0.0/0 - 0
20422 1 10 0 0x0 0 0 0.0.0.0/0 0.0.0.0/0 14 1
24511 1 0 0 0x0 0 0 0.0.0.0/0 0.0.0.0/0 - 0
In the previous example, the ClassAF1 does not classify traffic as intended. Traffic matching the first
match criteria is classified to Queue 1, but all other traffic is classified to Queue 0 as a result of CAM entry
20419.
When you remove the explicit “deny any” rule from all three ACLs, the CAM reflects exactly the desired
classification.
The following example shows correct traffic classifications.
Dell#show cam layer3-qos interface tengigabitethernet 2/4/1
Cam Port Dscp Proto Tcp Src Dst SrcIp DstIp DSCP Queue
Index Flag Port Port Marking
-------------------------------------------------------------------------
20416 1 18 IP 0x0 0 0 23.64.0.5/32 0.0.0.0/0 20 2
20417 1 0 IP 0x0 0 0 23.64.0.2/32 0.0.0.0/0 10 1
20418 1 0 IP 0x0 0 0 23.64.0.3/32 0.0.0.0/0 12 1
20419 1 10 0 0x0 0 0 0.0.0.0/0 0.0.0.0/0 14 1
24511 1 0 0 0x0 0 0 0.0.0.0/0 0.0.0.0/0 - 0
Dot1p to Queue Mapping Requirement
The dot1p to queue mapping on the system is global and this is used to configure the PRIO2COS table
configuration. For DSCP based PFC feature on untagged packets, this mapping must be the same as the
default dot1p to queue mapping and should not be changed (as in TABLE 1). If a custom dot1p to queue
mapping is present it should be reconfigured to the default dot1p to queue mapping.
• Currently Dell Networking OS supports matching only the following TCP flags:
– ACK
– FIN
– SYN
– PSH
– RST
– URG
In the existing software, ECE/CWR TCP flag qualifiers are not supported.
• Because this functionality forcibly marks all the packets matching the specific match criteria as
‘yellow’, Dell Networking OS does not support Policer based coloring and this feature concurrently.
• If single rate two color policer is configured along with this feature, then by default all packets less
than PIR would be considered as “Green” But ‘Green’ packets matching the specific match criteria for
which ‘color-marking’ is configured will be over-written and marked as “Yellow”.
714
Quality of Service (QoS)
Содержание 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 ...