By default the total available buffer for PFC is 6.6 MB and when you configure dynamic ingress buffering, a minimum of least 52 KB per
queue is used when all ports are congested.
This default behavior is impacted if you modify the total buffer available for PFC or assign static buffer configurations to the individual PFC
queues.
Behavior of Tagged Packets
The below is example for enabling PFC for priority 2 for tagged packets. Priority (Packet Dot1p) 2 will be mapped to PG6 on PRIO2PG
setting. All other Priorities for which PFC is not enabled are mapped to default PG – PG7.
Classification rules on ingress (Ingress FP CAM region) matches incoming packet-dot1p and assigns an internal priority (to select queue as
per Table 1 and Table 2).
The internal Priority assigned for the packet by Ingress FP is used by the memory management unit (MMU) to assign the packet to right
queue by indexing the internal-priority to queue map table (TABLE 1) in hardware.
PRIO2COS setting for honoring the PFC protocol packets from the Peer switches is as per above Packet-Dot1p->queue table (Table 2).
The packets come in with packet-dot1p 2 alone are assign to PG6 on ingress.
The packets come in with packet-dot1p 2 alone use Q1 (as per dot1p to Queue classification – Table 2) on the egress port.
•
When Peer sends a PFC message for Priority 2, based on above PRIO2COS table (TABLE 2), Queue 1 is halted.
•
Queue 1 starts buffering the packets with Dot1p 2. This causes PG6 buffer counter to increase on the ingress, since P-dot1p 2 is
mapped to PG6.
•
As the PG6 watermark threshold is reached, PFC generats for dot1p 2.
Configuration Example for DSCP and PFC Priorities
Consider a scenario in which the following DSCP and PFC priorities are necessary:
DSCP
0 – 5, 10 - 15 20 – 25, 30 – 35
Expected PFC
Priority
1 2
To configure the aforementioned DSCP and PFC priority values, perform the following tasks:
1
Create class-maps to group the DSCP subsets
class-map match-any dscp-pfc-1
match ip dscp 0-5,10-15
!
class-map match-any dscp-pfc-2
match ip dscp 20-25,30-35
2
Associate above class-maps to Queues Queue assignment as below.
NOTE:
Although, each port on the S4810, S4820T, and S5000 devices support 8 QoS queues, you can configure only 4
QoS queues (0-3)to manage data traffic. The remaining 4 queues (4-7) are reserved for control traffic.
Table 19. Queue Assignments
Internal-
priority
0
1
2
3
4
5
6
7
Queue
0
0
0
1
2
3
3
3
Data Center Bridging (DCB)
265
Содержание S4048T-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 11 2 1 ...
Страница 148: ...Figure 10 BFD Three Way Handshake State Changes 148 Bidirectional Forwarding Detection BFD ...
Страница 251: ...Dell Control Plane Policing CoPP 251 ...
Страница 363: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 363 ...
Страница 511: ...Figure 64 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 511 ...
Страница 512: ...Figure 65 Inspecting Configuration of LAG 10 on ALPHA 512 Link Aggregation Control Protocol LACP ...
Страница 515: ...Figure 67 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 515 ...
Страница 516: ...Figure 68 Inspecting LAG 10 Using the show interfaces port channel Command 516 Link Aggregation Control Protocol LACP ...
Страница 558: ...Figure 84 Configuring Interfaces for MSDP 558 Multicast Source Discovery Protocol MSDP ...
Страница 559: ...Figure 85 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 559 ...
Страница 560: ...Figure 86 Configuring PIM in Multiple Routing Domains 560 Multicast Source Discovery Protocol MSDP ...
Страница 564: ...Figure 88 MSDP Default Peer Scenario 2 564 Multicast Source Discovery Protocol MSDP ...
Страница 565: ...Figure 89 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 565 ...
Страница 729: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 Per VLAN Spanning Tree Plus PVST 729 ...
Страница 841: ...Figure 115 Single and Double Tag TPID Match Service Provider Bridging 841 ...
Страница 842: ...Figure 116 Single and Double Tag First byte TPID Match 842 Service Provider Bridging ...