Foundry Networks Switch and Router Installation And Configuration Manual page 415

Ones mean any value matches. For example, the <source-ip> and <wildcard> values 209.157.22.26 0.0.0.255
mean that all hosts in the Class C sub-net 209.157.22.x match the policy.
If you prefer to specify the wildcard (mask value) in CIDR format, you can enter a forward slash after the IP
address, then enter the number of significant bits in the mask. For example, you can enter the CIDR equivalent of
"209.157.22.26 0.0.0.255" as "209.157.22.26/24". The CLI automatically converts the CIDR number into the
appropriate ACL mask (where zeros instead of ones are the significant bits) and changes the non-significant
portion of the IP address into zeros. For example, if you specify 209.157.22.26/24 or 209.157.22.26 0.0.0.255,
then save the changes to the startup-config file, the value appears as 209.157.22.0/24 (if you have enabled
display of sub-net lengths) or 209.157.22.0 0.0.0.255 in the startup-config file.
If you enable the software to display IP sub-net masks in CIDR format, the mask is saved in the file in
"/<mask-bits>" format. To enable the software to display the CIDR masks, enter the ip show-subnet-length
command at the global CONFIG level of the CLI. You can use the CIDR format to configure the ACL entry
regardless of whether the software is configured to display the masks in CIDR format.
NOTE: If you use the CIDR format, the ACL entries appear in this format in the running-config and startup-config
files, but are shown with sub-net mask in the display produced by the show access-list and show ip access-list
commands.
The host <source-ip> | <hostname> parameter lets you specify a host IP address or name. When you use this
parameter, you do not need to specify the mask. A mask of all zeros (0.0.0.0) is implied.
The any parameter configures the policy to match on all host addresses.
The log argument configures the device to generate Syslog entries and SNMP traps for packets that are permitted
or denied by the access policy.
NOTE: You can enable logging on ACLs and filters that support logging even when the ACLs and filters are
already in use. To do so, re-enter the ACL or filter command and add the log parameter to the end of the ACL or
filter. The software replaces the ACL or filter command with the new one. The new ACL or filter, with logging
enabled, takes effect immediately.
Configure the Route Map
After you configure the ACLs, you can configure a PBR route map that matches based on the ACLs and sets
routing information in the IP traffic.
To configure a PBR route map, enter commands such as the following:
BigIron(config)# route-map test-route permit 1
BigIron(config-routemap test-route)# match ip address 1
BigIron(config-routemap test-route)# set ip next-hop 192.168.2.1
BigIron(config-routemap test-route)# exit
The commands in this example configure an entry in a route map named "test-route". The match statement
matches on IP information in ACL 1. The set statement changes the next-hop IP address for packets that match
to 192.168.2.1.
Syntax: route-map <map-name> permit | deny <num>
The <map-name> is a string of characters that names the map. Map names can be up to 32 characters in length.
You can define up 50 route maps on the Layer 3 Switch.
The permit | deny parameter specifies the action the Layer 3 Switch will take if a route matches a match
statement.
• If you specify deny, the Layer 3 Switch does not advertise or learn the route.
• If you specify permit, the Layer 3 Switch applies the match and set statements associated with this route map
instance.
December 2000
Using Access Control Lists (ACLs)
13 - 27