Dell Force10 E600i FTOS Version 8.4.1.5 Configuration Guide for ExaScale - Page 131

10 IP Access Control Lists (ACL), Prefix Lists, and Route-maps c e s IP Access Control Lists, Prefix Lists, and Route-maps are supported on platforms: c e s Ingress IP ACLs are supported on platforms: e s Egress IP ACLs are supported on platform: 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 the Access Control Lists (ACLs) chapter in the FTOS Command Line Reference Guide. 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. Refer to CAM Profiling, CAM Allocation, and CAM Optimization in this chapter for more information. Refer to Chapter 13, Content Addressable Memory for complete CAM profiling information. This chapter covers the following topics: • IP Access Control Lists (ACLs) • CAM Profiling, CAM Allocation, and CAM Optimization • Implementing ACLs on FTOS • IP Fragment Handling • Configure a standard IP ACL • Configure an extended IP ACL • Configuring Layer 2 and Layer 3 ACLs on an Interface • Assign an IP ACL to an Interface • Configuring Ingress ACLs • Configuring Egress ACLs • Configuring ACLs to Loopback • Applying an ACL on Loopback Interfaces • IP Prefix Lists • ACL Resequencing • Route Maps IP Access Control Lists (ACL), Prefix Lists, and Route-maps | 131