Troubleshooting guide

1-38
Cisco Wide Area Application Services Configuration Guide
OL-26579-01
Chapter 1 Configuring Traffic Interception
Using Policy-Based Routing Interception
Note The ip address command option matches the source or destination IP address that is
permitted by one or more standard or extended access lists.
d. Specify how the matched traffic should be handled.
In the following example, Edge-Router1 is configured to send the packets that match the specified
criteria to the next hop, which is Edge-WAE1 that has an IP address of 1.1.1.100:
Edge-Router1(config-route-map)# set ip next-hop 1.1.1.100
Note If you have more than one branch WAE, you can specify the IP address of a second branch
WAE for failover purposes (for example, enter the set ip next-hop 1.1.1.101 command on
Edge-Router1) to specify a next-hop address of 1.1.1.101 (the IP address of Edge-WAE2)
for failover purposes. The next-hop command is used for failover purposes and not for
load-balancing purposes.
Step 6 In the data center, create route maps on Core-Router1:
a. Define a route map on the LAN interface (ingress interface).
In the following example, the WAAS-CORE-LAN route map is created:
Core-Router1(config)# route-map WAAS-CORE-LAN permit
b. Define a route map on the WAN interface (egress interface).
In the following example, the WAAS-CORE-WAN route map is created:
Core-Router1(config)# route-map WAAS-CORE-WAN permit
c. Specify the match criteria.
Use the match command to specify the extended IP access list that Core-Router 1 should use to
determine which traffic is of interest to its WAN interface. If you do not enter a match command,
the route map applies to all packets. In the following example, Core-Router1 is configured to use
the access list 103 as the criteria for determining which traffic is of interest to its WAN interface:
Core-Router1(config-route-map)# match ip address 103
d. Specify how the matched traffic is to be handled.
In the following example, Core-Router1 is configured to send packets that match the specified
criteria to the next hop, which is Core-WAE1 that has an IP address of 2.2.2.100:
Core-Router1(config-route-map)# set ip next-hop 2.2.2.100
Note If you have more than one data center WAE, you can specify the IP address of a second data
center WAE for failover purposes (for example, enter the set ip next-hop 2.2.2.101
command on Core-Router1) to specify a next-hop address of 2.2.2.101 (the IP address of
Core-WAE2) for failover purposes. The next-hop command is used for failover purposes
and not for load-balancing purposes.
Step 7 In the branch office, apply the route maps to the LAN interface (ingress interface) and the WAN interface
(egress interface) on Edge-Router1:
a. On Edge-Router1, enter interface configuration mode: