Prerequisites for the iWAG
•
Enable mobile client service abstraction (MCSA).
•
Enable the
ipv6 unicast-routing
command.
Restrictions for the iWAG
•
Roaming from a 3G mobility network to a WLAN is not supported for the GTP and Cisco ISG sessions.
•
IP subscriber-routed (L3) sessions are not supported.
•
IPv6 and quality of service (QoS) are not supported in a 3G mobility network.
•
Only newly established calls are offloaded to the WLAN Third-Generation Partnership Project (3GPP)
IP access.
•
The iWAG solution for WLAN offload is currently available only for the 3G Universal Mobile
Telecommunications System (UMTS).
Information About the iWAG
The iWAG deployment includes a combination of simple IP users (traditional ISG and WiFi) and mobile IP
users (PMIPv6 or GTP tunneling). The term
mobility service
is used to refer to either the GTP service or the
PMIPv6 service applied to user traffic. The iWAG provides mobility services to mobile IP users, and as a
result, a mobile client can seamlessly access a 3G or 4G mobility network. However, the iWAG does not
provide mobility services to simple IP users. Therefore, simple IP users can access the Public Wireless LAN
(PWLAN) network through the Cisco ISG. Clients are devices that access WiFi Internet (public wireless),
where possible. However, if WiFi is not available, the same clients can
connect to the Internet service using a 3G or 4G mobility network.
The iWAG has a transport or switching element with Cisco ISG subscriber awareness. The iWAG also has
RADIUS-based authentication and accounting, and policy-based subscriber routing for the WiFi wholesale
model.
For more information about the iWAG, see the
Overview of iWAG
video.
Intelligent Wireless Access Gateway Configuration Guide
2
OL-30226-03
Overview of the Intelligent Wireless Access Gateway
Prerequisites for the iWAG
