
CPU Queue
Weights
Rate (pps)
Protocol
2
2
300
TTL0, TTL1, IP with options, Mac limit violation,
Hyper pull, L3 with Bcast MacDA, Unknown L3,
ARP unresolved, ACL Logging
3
4
400
sFlow, L3 MTU Fail frames
4
127
2000
IPC/IRC, VLT Control frames
5
16
300
ARP Request, NS, RS, iSCSI OPT Snooping
6
16
400
ICMP, ARP Reply, NTP, Local terminated L3, NA,
RA,ICMPv6 (other Than NDP and MLD)
7
64
400
xSTP, FRRP, LACP, 802.1x,ECFM,L2PT,TRILL, Open
flow
8
32
400
PVST, LLDP, GVRP, FCOE, FEFD, Trace flow
9
64
600
OSPF, ISIS, RIPv2, BGP
10
32
300
DHCP, VRRP
11
32
300
PIM, IGMP, MSDP, MLD
Catch-All Entry for IPv6 Packets
Dell Networking OS currently supports configuration of IPv6 subnets greater than /64 mask length, but the agent writes it to the
default LPM table where the key length is 64 bits. The device supports table to store up to 256 subnets of maximum of /128 mask
lengths. This can be enabled and agent can be modified to update the /128 table for mask lengths greater than /64. This will restrict
the subnet sizes to required optimal level which would avoid these NDP attacks. The IPv6 stack already supports handling of >/64
subnets and doesn’t require any additional work. The default catch-all entry is put in the LPM table for IPv4 and IPv6. If this is
included for IPv6, you can disable this capability by using the
no ipv6 unknown-unicast
command. Typically, the catch-all
entry in LPM table is used for soft forwarding and generating ICMP unreachable messages to the source. If this is in place then
irrespective of whether it is </64 subnet or >/64 subnet, it doesn’t have any effect as there would always be LPM hit and traffic are
sent to CPU.
Unknown unicast L3 packets are terminated to the CPU CoS queue which is also shared for other types of control-plane packets like
ARP Request, Multicast traffic, L3 packets with Broadcast MAC address. The catch-all route poses a risk of overloading the CPU
with unknown unicast packets. This CLI knob to turn off the catch-all route is of use in networks where the user does not want to
generate Destination Unreachable messages and have the CPU queue’s bandwidth available for higher priority control-plane traffic.
Configuring CoPP for OSPFv3
You can create an IPv6 ACL for control-plane traffic policing for OSPFv3, in addition to the CoPP support for VRRPv3, BGPv6, and
ICMPv6. This functionality is supported on the S4810, S4820T, S6000, MXL, and Z9000 platforms. You can use the
ipv6
access-list
name
cpu-qos permit ospfv3
or the
ipv6 access-list
name
cpu-qos ospfv3
command to allow
CoPP traffic for OSPFv3. The control plane management support for IPv6 ICMPv6 packets is enhanced to enable more number of
CPU queues on port to be available and other COPP improvements have been implemented.
To configure control-plane policing, perform the following:
1.
Create an IPv6 ACL for control-plane traffic policing for ospfv3.
CONFIGURATION mode
Dell(conf)#ipv6 access-list ospfv3 cpu-qos
238
Control Plane Policing (CoPP)
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...