Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) - Manual (Page 360)

332 Multi-Service IronWare Routing Configuration Guide
53-1003033-02
Configuring a PBR policy
NOTE
If none of the clauses of an IPv4 PBR routemap definition contains both 'match' and 'set' statements
together, PBR doesn't work and normal routing takes place.
To configure a PBR route map, enter commands such as the following:
Brocade(config)# route-map test-route permit 99
Brocade(config-routemap test-route)# match ip address 99
Brocade(config-routemap test-route)# set ip next-hop 192.168.2.1
Brocade(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 99. The set statement changes the next-hop IP
address for packets that match to 192.168.2.1.
Syntax: [no] 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 an unlimited number of route maps on the Brocade device, as
long as system memory is available.
The permit | deny parameter specifies the action the Brocade device will take if a route matches a
match statement:
• If you specify a deny routemap instance, it is ignored and not programmed in Layer- 4 CAM.
• If you specify permit, the Brocade device applies the match and set statements associated
with this route map instance.
The num parameter specifies the instance of the route map you are defining. Routes are compared
to the instances in ascending numerical order. For example, a route is compared to instance 1,
then instance 2, and so on.
PBR uses up to 200 Layer 3 route map instances for comparison and ignores the rest.
Syntax: [no] match ip address ACL-num-or-name
The ACL-num-or-name parameter specifies a standard or extended ACL number or name. Multiple
ACLs may be added when separated by spaces.
Setting the next hop
Traffic that matches a match statement in the route map is forwarded as defined by set
commands. Multiple set commands can be configured and when a match condition is met, the
device works sequentially through the list of set commands until it finds the first “next hop” that is
operational and uses it. If that “next hop” goes down, the next hop as defined in a set command is
chosen and if all next hop interfaces in the list are down, the packet is routed as determined in the
IP Route Table. If a next hop interface that was down comes back up, the next hop selection
process begins again and restarts its selection process from the top of the list.
Options for setting the next hop are described in the following:
• Setting the Next Hop to an IP Address
• Setting the Next Hop to a GRE Tunnel
• Setting the Next Hop to a GRE Interface
• Setting the Next Hop to a Null Interface
• Setting the Next Hop to an LSP