15-4
Catalyst 6500 Series Switch Software Configuration Guide—Release 8.7
OL-8978-04
Chapter 15 Configuring Access Control
Supported ACLs
After the packets are routed and before they are forwarded out to the next hop, Cisco IOS software
examines all ACLs that are associated with the outbound features configured on the egress interface for
the following:
•
Outbound ACLs (standard, extended, and/or reflexive)
•
Encryption ACLs (not supported on the MSFC)
•
NAT ACLs (for inside-to-outside translation)
•
WCCP ACL
•
TCP intercept ACL
VACLs
The following sections describe the VACLs:
•
VACL Overview, page 15-4
•
ACEs Supported in VACLs, page 15-5
•
Handling Fragmented and Unfragmented Traffic, page 15-6
VACL Overview
The VACLs can access control
all
traffic. You can configure the VACLs on the switch to apply to all
packets that are routed into or out of a VLAN or are bridged within a VLAN. The VACLs are strictly for
security packet filtering and redirecting traffic to specific physical switch ports. Unlike the Cisco IOS
ACLs, the VACLs are not defined by direction (input or output).
You can configure the VACLs on the Layer 3 addresses for IP and IPX. All other protocols are access
controlled through the MAC addresses and EtherType using the MAC VACLs.
Caution
The IP traffic and IPX traffic are not access controlled by the MAC VACLs. All other traffic types
(AppleTalk, DECnet, and so on) are classified as MAC traffic; the MAC VACLs are used to access
control this traffic.
Note
With Supervisor Engine 720 (PFC3A/PFC3B/PFC3BXL) and Supervisor Engine 32
(PFC3B/PFC3BXL), the IPX routing is done through the software and the IPX Cisco IOS ACLs and IPX
VACLs are not supported. You can match the IPX packets using the MAC VACLs. You can enter the
ipx-arpa
keyword to match the IPX ARPA frames. Use 0xffff EtherType to match on the IPX non-ARPA
frames and the frames with an EtherType of 0xffff. For information on configuring the MAC VACLs, see
the
“Creating a Non-IP Version 4/Non-IPX VACL (MAC VACL) and Adding ACEs” section on
page 15-52
.
You can enforce the VACLs only on the packets going through the Catalyst 6500 series switch; you
cannot enforce the VACLs on the traffic between the hosts on a hub or another switch that is connected
to the Catalyst 6500 series switch.