Policy-Based Routing with differing next hops

In this example, traffic is routed from different sources to different places (next hops). Packets arriving from source 192.168.0.0 are sent to the VRF vroutefwd‘s next hop at 3.3.3.3; packets arriving from source 192.168.1.1 are sent to the VRF vroutefwd‘s next hop at 3.3.3.5.

1. Configure the ACLs.
   

   device(config)# ip access-list standard Jules
   device(conf-ipacl-std)# permit 192.168.0.0 255.255.255.0
   device(conf-ipacl-std)# exit
   device(config)# ip access-list standard Vincent
   device(conf-ipacl-std)# permit 192.168.1.1 255.255.255.0
   device(conf-ipacl-std)# exit
   

2. Create the first stanza of the route map. (The example is using a route-map named pulp_fiction.)
   

   device(config)# route-map pulp_fiction permit 10
   device(config-routemap-pulp_fiction/permit/10)# match ip address acl Jules
   device(config-routemap-pulp_fiction/permit/10)# set ip vrf vroutefwd next-hop 3.3.3.3
   device(config-routemap-pulp_fiction/permit/10)# exit

3. Create the second stanza of the route-map (The example is using a route-map named pulp_fiction.)
   

   device(config)# route-map pulp_fiction permit 20
   device(config-routemap-pulp_fiction/permit/20)# match ip address acl Vincent
   device(config-routemap-pulp_fiction/permit/20)# set ip vrf vroutefwd next-hop 3.3.3.5
   device(config-routemap-pulp_fiction/permit/20)# set ip next-hop 6.6.6.7
   device(config-routemap-pulp_fiction/permit/20)# exit

4. Bind the route map to the desired interface.
   

   device(config)# interface ethernet 1/1
   device(conf-if-eth-1/1)# ip policy route-map pulp_fiction