Access Control Lists (ACLs)
This chapter describes access control lists (ACLs), prefix lists, and route-maps.
At their simplest, access control lists (ACLs), prefix lists, and route-maps permit or deny traffic based on MAC and/or IP addresses. This
chapter describes implementing IP ACLs, IP prefix lists and route-maps. For MAC ACLS, refer to
An ACL is essentially a filter containing some criteria to match (examine IP, transmission control protocol [TCP], or user datagram protocol
[UDP] packets) and an action to take (permit or deny). ACLs are processed in sequence so that if a packet does not match the criterion in
the first filter, the second filter (if configured) is applied. When a packet matches a filter, the switch drops or forwards the packet based on
the filter’s specified action. If the packet does not match any of the filters in the ACL, the packet is dropped (implicit deny).
The number of ACLs supported on a system depends on your content addressable memory (CAM) size. For more information, refer to
. For complete CAM profiling information, refer to
You can configure ACLs on VRF instances. In addition to the existing qualifying parameters, Layer 3 ACLs also incorporate VRF ID as one of
the parameters. Using this new capability, you can also configure VRF based ACLs on interfaces.
NOTE:
You can apply Layer 3 VRF-aware ACLs only at the ingress level.
You can apply VRF-aware ACLs on:
•
VRF Instances
•
Interfaces
In order to configure VRF-aware ACLs on VRF instances, you must carve out a separate CAM region. You can use the
cam-acl
command
for allocating CAM regions. As part of the enhancements to support VRF-aware ACLs, the
cam-acl
command now includes the following
new parameter that enables you to allocate a CAM region:
vrfv4acl
.
The order of priority for configuring user-defined ACL CAM regions is as follows:
•
V4 ACL CAM
•
VRF V4 ACL CAM
•
L2 ACL CAM
With the inclusion of VRF based ACLs, the order of precedence of Layer 3 ACL rules is as follows:
•
Port/VLAN based PERMIT/DENY Rules
•
Port/VLAN based IMPLICIT DENY Rules
•
VRF based PERMIT/DENY Rules
•
VRF based IMPLICIT DENY Rules
NOTE:
In order for the VRF ACLs to take effect, ACLs configured in the Layer 3 CAM region must have an implicit-permit
option.
You can use the
ip access-group
command to configure VRF-aware ACLs on interfaces. Using the
ip access-group
command, in
addition to a range of VLANs, you can also specify a range of VRFs as input for configuring ACLs on interfaces. The VRF range is from 1 to
63. These ACLs use the existing V4 ACL CAM region to populate the entries in the hardware and do not require you to carve out a separate
CAM region.
NOTE:
You can configure VRF-aware ACLs on interfaces either using a range of VLANs or a range of VRFs but not both.
7
Access Control Lists (ACLs)
107
Summary of Contents for S3048-ON
Page 1: ...Dell Configuration Guide for the S3048 ON System 9 11 2 5 ...
Page 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 ...
Page 142: ...Figure 10 BFD Three Way Handshake State Changes 142 Bidirectional Forwarding Detection BFD ...
Page 241: ...Dell Control Plane Policing CoPP 241 ...
Page 287: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 287 ...
Page 428: ...Figure 53 Inspecting the LAG Configuration 428 Link Aggregation Control Protocol LACP ...
Page 477: ...Figure 73 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 477 ...
Page 478: ...Figure 74 Configuring OSPF and BGP for MSDP 478 Multicast Source Discovery Protocol MSDP ...
Page 483: ...Figure 77 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 483 ...
Page 484: ...Figure 78 MSDP Default Peer Scenario 3 484 Multicast Source Discovery Protocol MSDP ...
Page 745: ...Figure 104 Single and Double Tag TPID Match Service Provider Bridging 745 ...
Page 746: ...Figure 105 Single and Double Tag First byte TPID Match 746 Service Provider Bridging ...