reach slave unit’s CMIC via queues 0 – 7 will take same queues 0 – 7 on the back-plane ports while
traversing across units and finally on the master CMIC, they are queued on the same queues 0 – 7. In this
case, the queue (4 – 7) taken by the well-known protocol streams are uniform across different queuing
points, and the queue (0 – 3) taken by the CPU bound data streams are uniform. In back-plane ports,
queue 0 – 3 will carry both the front-end bound data streams as well as the CPU bound data streams
which is acceptable but the well-known protocol streams must not be mixed with the data streams on
queues 0 – 3 in back-plane ports.
Increased CPU Queues for CoPP
FTOS classifies every packet ingress from the front end port to system as control traffic or data traffic by
having the pre-defined rules based on protocol type or packets types like ttl, slow path etc. FP is used to
classify the traffic to transmit the control traffic to CMIC port. Other major function performed by the FP
rule is to decide to which CPU queue the packet must be sent. All other packets will be forwarded or
dropped at the ingress.
All packet transmitted to CPU will transmit to local CPU by using the CPU queues and processed. But in
stacked system only mater CPU is responsible for the control plane actions. So control packets received
in master or slave units will be tunneled to master CPU to process.
As part of enhancements, CPU queues are increased from 8 to 12 on CPU port. However, the front-end
port and the backplane ports support only 8 queues. As a result, when packets are transmitted to the
local CPU, the CPU uses Q0-Q11 queues. The control packets that are tunneled to the master unit are
isolated from the data queues and the control queues in the backplane links. Control traffic must be sent
over the control queues Q4-Q7 on higig links. After reaching the master unit tunneled packets must be
transmitted to the CPU using the Q0-Q11 queues.
The backplane ports can have a maximum of 4 control queues. So, when we have more than ‘n’ CMIC
queues for well-known protocols and n > 4, then streams on ‘n’ CMIC queues must be multiplexed on 4
control queues on back-plane ports and on the Master unit, these streams must be de-multiplexed to ‘n’
CMIC queues on the Master CPU.
After control packets reach the CPU through the CMIC port, the software schedules to process traffic on
each 12 CPU queues. This aspect must be ensured even in case of stand-alone systems and there is no
dependency with stacking.
Policing provides a method for protecting CPU bound control plane packets by policing packets
transmited to CPU with a specified rate and from undesired or malicious traffic. This is done at each CPU
queue on each unit.
FP Entries for Distribution of NDP Packets to Various CPU Queues
• At present generic mac based entries in system flow region will take IPv6 packets to CPU.
– OSPFv3 – 33:33:0:0:0:5 – Q7
– - 33:33:0:0:0:6 – Q7
– IPv6 Multicast – 33:33:0:0:0:0 – Q1
• Add/remove specific ICMPv6 NDP protocol entry when user configures the first ipv6 address in the
front panel port
– Distribute ICMPv6 NS/RS packets to Q5.
Control Plane Policing (CoPP)
277
Содержание S4820T
Страница 1: ...Dell Configuration Guide for the S4820T System 9 8 0 0 ...
Страница 282: ...Dell 282 Control Plane Policing CoPP ...
Страница 569: ...Figure 62 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 569 ...
Страница 572: ...Figure 64 Inspecting a LAG Port on BRAVO Using the show interface Command 572 Link Aggregation Control Protocol LACP ...
Страница 573: ...Figure 65 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 573 ...
Страница 617: ...mac address table static multicast mac address vlan vlan id output range interface Microsoft Network Load Balancing 617 ...
Страница 622: ...Figure 81 Configuring Interfaces for MSDP 622 Multicast Source Discovery Protocol MSDP ...
Страница 623: ...Figure 82 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 623 ...
Страница 624: ...Figure 83 Configuring PIM in Multiple Routing Domains 624 Multicast Source Discovery Protocol MSDP ...
Страница 629: ...Figure 86 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 629 ...
Страница 630: ...Figure 87 MSDP Default Peer Scenario 3 630 Multicast Source Discovery Protocol MSDP ...
Страница 751: ...10 11 5 2 00 00 05 00 02 04 Member Ports Te 1 2 1 PIM Source Specific Mode PIM SSM 751 ...
Страница 905: ...Figure 112 Single and Double Tag First byte TPID Match Service Provider Bridging 905 ...
Страница 979: ...6 Member not present 7 Member not present Stacking 979 ...
Страница 981: ...storm control Storm Control 981 ...
Страница 999: ... Te 1 1 0 INCON Root Rootguard Te 1 2 0 LIS Loopguard Te 1 3 0 EDS Shut Bpduguard Spanning Tree Protocol STP 999 ...
Страница 1103: ...Figure 134 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 1103 ...