IP SLA tracks the Silver Peak appliance, and removes the policy route when the appliance becomes unreachable. This effectively prevents a routing “black hole” from occurring, where the router is sending traffic to an unreachable appliance.
The access list needs to match the traffic you wish to optimize with the Silver peak appliance. The route map creates the policy based routing feature, and uses the access list to define what traffic to route to the Silver Peak. Traffic passing through the router that does not match this access list will not be sent to the Silver Peak, and will not be optimized.
Apply the policy route-map named silverpeak-lan-to-wan to the LAN interface. For multiple LAN interfaces, apply the policy route-map to each LAN interface with traffic to be optimized, this includes physical interfaces, sub-interfaces, or BVI interfaces (Layer 3 VLAN interfaces).
Note 
Do not apply the policy route-map to the interface connected to the Silver Peak (in this example, GigabitEthernet0/0), or you will create a routing loop.
Do not apply the policy route-map to the interface connected to the Silver Peak (in this example, GigabitEthernet0/0), or you will create a routing loop.
In the preceding example, the Cisco router will only redirect outgoing traffic (from the LAN out to the WAN) to the Silver Peak. For Silver Peak’s Auto-Optimization feature to work in this Policy-Based Routing scenario, the router also must forward the return traffic to the Silver Peak appliance (from the WAN incoming to the LAN). To accomplish this, we need to configure a routing policy to match the incoming traffic from the WAN.
|
1
|
Configure the access list and route map for the incoming traffic. The incoming access list is the inverse of outgoing access list above.
|
|
2
|
Configure the WAN interface with the policy route-map named silverpeak-wan-to-lan.
|
