Configuration Guide User guide

FastIron Configuration Guide 1753
53-1002494-02
Policy-based routing (PBR)
Alternatively, you can enable PBR on specific interfaces, as shown in the following example. The
commands in this example configure IP addresses in the three source subnets identified in ACLs
50, 51, and 52, then apply route map test-route to the interface.
Brocade(config)#interface ve 1
Brocade(config-vif-1)#ip address 209.157.23.1/24
Brocade(config-vif-1)#ip address 209.157.24.1/24
Brocade(config-vif-1)#ip address 209.157.25.1/24
Brocade(config-vif-1)#ip policy route-map test-route
Setting the output interface to the null interface
The following commands configure a PBR policy to send all traffic from 192.168.1.204/32 to the
null interface, thus dropping the traffic instead of forwarding it.
Brocade(config)#access-list 56 permit 209.168.1.204 0.0.0.0
The following commands configure an entry in a route map called “file-13”. The first entry (permit
56) matches on the IP address information in ACL 56 above. For IP traffic from the host
209.168.1.204/32, this route map entry sends the traffic to the null interface instead of
forwarding it, thus sparing the rest of the network the unwanted traffic.
Brocade(config)#route-map file-13 permit 56
Brocade(config-routemap file-13)#match ip address 56
Brocade(config-routemap file-13)#set interface null0
Brocade(config-routemap file-13)#exit
The following command enables PBR by globally applying the route map to all interfaces.
Brocade(config)#ip policy route-map file-13
Alternatively, you can enable PBR on specific interfaces, as shown in the following example. The
commands in this example configure IP addresses in the source subnet identified in ACL 56, then
apply route map file-13 to the interface.
Brocade(config)#interface ethernet 3/11
Brocade(config-if-e10000-3/11)#ip address 192.168.1.204/32
Brocade(config-if-e10000-3/11)#ip policy route-map file-13
Trunk formation with PBR policy
When a trunk is formed, the PBR policy on the primary port applies to all the secondary ports. If a
different PBR policy exists on a secondary port at the time of a trunk formation, that policy is
overridden by the PBR policy on the primary port. If the primary port does not have a PBR policy,
then the secondary ports will not have a PBR policy.
When a trunk is removed, the PBR policy that was applied to the trunk interface is unbound
(removed) from former secondary ports. If global PBR is configured, the secondary ports adhere to
the global PBR; otherwise, no PBR policy is bound to former secondary ports.