Flow-Based Redirect for Selective IP Traffic Offload
Mobile IP sessions are provisioned with a traffic class service in the Cisco Intelligent Wireless Access Gateway
(iWAG) for routing web traffic to a next hop device, depending on the local policies or the policies that are
downloaded from the Cisco IOS authentication, authorization, and accounting (AAA) network security services.
The traffic class service can be configured for routing traffic to the next hop along with the other supported
features such as policing and Dynamic Rate Limit (DRL) accounting. You can configure multiple TC services
with different next hop addresses with the Flow-Based Redirect feature. However, only 16 traffic class services
can be applied to a session.
Network Address Translation (NAT) with Selective IP Traffic Offload (SIPTO) is required only for IPv4 and
Dual Stack IPv4 traffic sessions. NAT is enabled at the outgoing interface level so NAT does not need to be
IPoE session aware when used with Flow Based Redirect for Selective IP Traffic Offload.
In existing deployment, a NAT or Carrier Grade Network Address Translation (CGN) device may exist
upstream of the Intelligent Wireless Access Gateway (iWAG) device. In such a scenario, it is possible to
keep the architecture in place without enabling NAT on the Cisco ASR 1000 Series Aggregation Services
Router acting as iWAG, if and only if, there is a simple way for the return traffic to go from the NAT or
CGN device back to the iWAG. This needs to be verified prior to deployment to guarantee return paths.
Note
The following figure shows a typical deployment scenario where internet traffic is offloaded from the access
network, and is routed directly through the nearest IP gateway.
Figure 9: Flow-Based Redirect for Selective IP Traffic Offload
Intelligent Wireless Access Gateway Configuration Guide
OL-30226-03 81
Flow-Based Redirect
Flow-Based Redirect for Selective IP Traffic Offload
To Next Page
Loading...
Need help?
General
