•
NDP Packets in VLT peer routing enable
•
VLT peer routing enable cases each VLT node will have route entry for link local address of both self and peer VLT node. Peer VLT
link local entry will have egress port as ICL link. And Actual link local address will have entry to CopyToCpu. But NDP packets
destined to peer VLT node needs to be taken to CPU and tunneled to the peer VLT node..
•
NDP packets in VLT peer routing disable case
•
NDP packets intended to peer VLT chassis taken to CPU and tunnel to peer.
The following table describes the protocol to queue mapping with the CPU queues increased to be 12.
Table 13. Redirecting Control Traffic to 12 CPU queues
CPU Queue
Weights
Rate (pps)
Protocol
0
100
1300
BFD
1
1
300
MC
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
238
Control Plane Policing (CoPP)
Содержание S3048-ON
Страница 1: ...Dell Configuration Guide for the S3048 ON System 9 11 2 5 ...
Страница 137: ...0 Gi 1 1 Gi 1 2 rx Flow N A N A 0 0 No N A N A yes Access Control Lists ACLs 137 ...
Страница 142: ...Figure 10 BFD Three Way Handshake State Changes 142 Bidirectional Forwarding Detection BFD ...
Страница 241: ...Dell Control Plane Policing CoPP 241 ...
Страница 287: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 287 ...
Страница 428: ...Figure 53 Inspecting the LAG Configuration 428 Link Aggregation Control Protocol LACP ...
Страница 429: ...Figure 54 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 429 ...
Страница 432: ...Figure 56 Inspecting a LAG Port on BRAVO Using the show interface Command 432 Link Aggregation Control Protocol LACP ...
Страница 433: ...Figure 57 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 433 ...
Страница 477: ...Figure 73 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 477 ...
Страница 478: ...Figure 74 Configuring OSPF and BGP for MSDP 478 Multicast Source Discovery Protocol MSDP ...
Страница 479: ...Figure 75 Configuring PIM in Multiple Routing Domains Multicast Source Discovery Protocol MSDP 479 ...
Страница 483: ...Figure 77 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 483 ...
Страница 484: ...Figure 78 MSDP Default Peer Scenario 3 484 Multicast Source Discovery Protocol MSDP ...
Страница 634: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 634 Per VLAN Spanning Tree Plus PVST ...
Страница 745: ...Figure 104 Single and Double Tag TPID Match Service Provider Bridging 745 ...
Страница 746: ...Figure 105 Single and Double Tag First byte TPID Match 746 Service Provider Bridging ...