Dell Force10 S55T S55 Configuration Guide FTOS 8.3.5.3 - Page 99

7 Access Control Lists (ACL), Prefix Lists, and Route-maps c e s Access Control Lists, Prefix Lists, and Route-maps are supported on platforms: c e s Ingress IP and MAC ACLs are supported on platforms: e Egress IP and MAC ACLs are supported on platforms: Overview 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 discusses implementing IP ACLs, IP Prefix lists and Route-maps. For MAC ACLS, refer to Chapter 10, Layer 2, on page 47. An ACL is essentially a filter containing some criteria to match (examine IP, TCP, or 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 CAM size. See CAM Profiling, CAM Allocation, and CAM Optimization in this chapter for more information. Refer to Chapter 10, Content Addressable Memory, on page 219 for complete CAM profiling information. This chapter covers the following topics: • IP Access Control Lists (ACLs) on page 100 • CAM Profiling, CAM Allocation, and CAM Optimization on page 100 • Implementing ACLs on FTOS on page 103 • IP Fragment Handling on page 104 • Configure a standard IP ACL on page 106 • Configure an extended IP ACL on page 109 • Configuring Layer 2 and Layer 3 ACLs on an Interface on page 112 • Assign an IP ACL to an Interface on page 112 • Configuring Ingress ACLs on page 114 • Configuring Egress ACLs on page 115 Access Control Lists (ACL), Prefix Lists, and Route-maps | 99