Setup Guide

FEFD Q6 CP 150 150 1000 1000
TRACEFLOW Q16 LP 200 200 500 500
FCoE Q12 RP 300 300 2000 2000
L3 LOCAL TERMINATED Q3 CP 400 400 5000 5000
L3 UNKNOWN/UNRESOLVED ARP Q7 RP 200 200 3000 3000
L2 DST HIT/BROADCAST Q1/Q8 CP/RP 200 200 500 500
MULTICAST CATCH ALL Q7 RP 200 200 500 500
ACL LOGGING Q17 LP 200 200 1000 1000
L3 HEADER ERROR/TTL0 Q0 CP 200 200 500 500
IP OPTION/TTL1 Q0 CP 100 100 500 500
VLAN L3 MTU FAIL Q0 CP 200 200 500 500
Physical L3 MTU FAIL Q0 CP 200 200 500 500
SOURCE MISS Q16 LP 200 200 500 500
STATION MOVE Q16 LP 200 200 500 500
SFLOW_EGRESS Q20 LP 5000 5000 3000 3000
SFLOW_INGRESS Q20 LP 5000 5000 3000 3000
Troubleshooting CoPP Operation
To troubleshoot CoPP operation, use the debug commands described in this section.
Enabling CPU Trac Statistics
During high-trac network conditions, you may want to manually enable the collection of CPU trac statistics by entering the debug
cpu-traffic-stats command. Statistic collection begins as soon as you enter the command, not when the system boots up.
The following message is displayed when the collection of CPU trac statistics is enabled. Use the show cpu-traffic-stats
command to view the statistics.
Excessive traffic is received by CPU and traffic will be rate controlled.
NOTE
: You must manually enable the collection of CPU trac statistics with the debug cpu-traffic-stats command
before the statistics display in show cpu-traffic-stats output. It is recommended that when you nish CoPP
troubleshooting, you disable the collection of CPU trac statistics by entering the
no debug cpu-traffic-stats
command.
Viewing CPU
Trac Statistics
To view the statistics collected on CPU trac, use the show cpu-traffic-stats [cp | rp |all] command.
Trac statistics are sorted on a per-interface basis; the interface receiving the most trac is displayed rst. All CPU and port information is
displayed unless you specify a port or CPU queue. Trac information is displayed for router ports only, not for management interfaces. CPU
trac statistics are collected only after you enter the debug cpu-traffic-stats command, not from when the system boots up.
Dell#show cpu-traffic-stats
Processor : CP
--------------
Received 100% traffic on fortyGigE 2/12 Total packets:8
LLC:0, SNAP:0, IP:5, ARP:0, other:3
Unicast:5, Multicast:3, Broadcast:0
Processor : RP
---------------
Received 100% traffic on fortyGigE 2/12 Total packets:168
LLC:0, SNAP:0, IP:165, ARP:0, other:3
Unicast:42, Multicast:126, Broadcast:0
Control Plane Policing (CoPP)
259