Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-30226-03
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
Overview of the Intelligent Wireless Access
Gateway
Service providers use a combination of WiFi and mobility offerings to offload their mobility networks in
the area of high-concentration service usage. This led to the evolution of the Intelligent Wireless Access
Gateway (iWAG).
The iWAG provides a WiFi offload option to 4G and 3G service providers by enabling a single-box solution
that provides the combined functionality of Proxy Mobile IPv6 (PMIPv6) and GPRS Tunneling Protocol
(GTP) on the Cisco Intelligent Services Gateway (Cisco ISG) framework. This document provides information
about the iWAG and how to configure it, and contains the following sections:
Finding Feature Information, page 1
•
Prerequisites for the iWAG, page 2
•
Restrictions for the iWAG, page 2
•
Information About the iWAG, page 2
•
How to Configure the iWAG, page 8
•
Additional References, page 22
•
Feature Information for the Intelligent Wireless Access Gateway, page 23
•
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
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.
Overview of the Intelligent Wireless Access Gateway
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.
For information about the field-replaceable units (FRUs) of the Cisco ASR 1000 Series Aggregation Services
Routers supported by each ROMmon release, see the "ROMmon Release Requirements" section in the Cisco
ASR 1000 Series Aggregation Services Routers Release Notes.
How to Configure the iWAG
Configuring the iWAG for Simple IP Users
You must configure the Cisco Intelligent Services Gateway (ISG) for the iWAG to enable simple IP users to
access Internet services.
The tasks listed below enable IP sessions and indicate how these sessions are identified. For detailed steps,
see the "Creating ISG Sessions for IP Subscribers" section in the Intelligent Services Gateway Configuration
Guide.
Creating ISG IP interface sessions
•
Overview of the Intelligent Wireless Access Gateway
Creating ISG Static Sessions
•
Creating ISG IP Subnet Sessions
•
Configuring IP Session Recovery for DHCP-Initiated IP Sessions
•
Verifying ISG IP Subscriber Sessions
•
Clearing ISG IP Subscriber Sessions
•
Troubleshooting ISG IP Subscriber Sessions
•
You must configure DHCP support in your network before performing the tasks listed below. For detailed
steps on assigning IP addresses using DHCP, see the "Assigning ISG Subscriber IP Addresses by Using
DHCP" section in the Intelligent Services Gateway Configuration Guide.
Configuring an ISG Interface for Dynamic DHCP Class Association
•
Configuring DHCP Server User Authentication
•
Configuring a DHCP Class in a Service Policy Map
•
Configuring a DHCP Class in a Service Profile or User Profile on the AAA Server
•
Configuring a DHCP Server IP Address
•
Configuring the iWAG for 3G Mobile IP Users
You must configure GTP for the iWAG to allow access to 3G mobile IP users. The various tasks described
in the following sections are mandatory for configuring the iWAG for 3G mobile IP users.
Configuring Authentication, Authorization, and Accounting for the iWAG
This section describes how to configure authentication, authorization, and accounting (AAA) for the iWAG
on the Cisco ASR 1000 Series Aggregation Services Routers.
Overview of the Intelligent Wireless Access Gateway
PurposeCommand or Action
Step 7
Step 8
domain-name domain
Example:
Router(dhcp-config)# domain-name example.com
lease {days [hours [ minutes ]] | infinite}
Specifies the domain name for a DHCP client.
Configures the duration of the lease for an IP address that is
assigned from a Cisco IOS DHCP server to a DHCP client.
Example:
Note
The DHCP pool lease time is applicable only to simple
sessions. For mobile GTP sessions, lease time from the
Router(dhcp-config)# lease 1 2 2
GTP configuration will be used. Under the GTP
configuration, lease duration should be configured the
same way as the address hold timer in the GGSN or
PGW.
Configuring the Cisco ISG Class Map and Policy Map for the iWAG
This section describes how to configure the Cisco ISG class map and policy map for the iWAG.
SUMMARY STEPS
enable
1.
configure terminal
2.
class-map type traffic match-any class-map-name
3.
match access-group output {access-group | name access-group-name}
4.
match access-group input {access-group | name access-group-name}
5.
policy-map type service policy-map-name
6.
[ priority ] class type traffic {class-map-name | default {in-out | input | output } }
7.
accounting aaa list aaa-method-list
8.
[ priority ] class type traffic { class-map-name | default {in-out | input | output}}
9.
drop
10.
policy-map type control policy-map-name
11.
class type control control-class-name | always} [event{access-reject | account-logoff | account-logon |
Overview of the Intelligent Wireless Access Gateway
Configuring a Session Initiator for the iWAG
This section describes how to configure a session initiator for the iWAG solution. A session can be created
using different triggers, such as an unknown MAC address, an unclassified MAC address, a RADIUS message
with the Cisco ASR 1000 Series Aggregation Services Router acting as RADIUS proxy or a DHCP DISCOVER
message with the Cisco ASR 1000 Series Aggregation Services Router acting as DHCP proxy.
To enable roaming, one initiator is required for DHCP sessions and another for the unclassified MAC.Note
SUMMARY STEPS
enable
1.
configure terminal
2.
interface GigabitEthernet slot/subslot/port
3.
description string
4.
ip address ip-address mask [secondary [vrf vrf-name]]
5.
negotiation auto
6.
service-policy type control policy-map-name
7.
ip subscriber {l2-connected}
8.
initiator {dhcp | radius-proxy | static ip subscriber list listname | unclassified ip | unclassified
9.
mac-address}
initiator {dhcp | radius-proxy | static ip subscriber list listname | unclassified ip | unclassified
10.
mac-address}
Configuring the iWAG for 3G Mobile IP Users
DETAILED STEPS
Step 1
Step 2
Step 3
Example:
Router> enable
Example:
Router# configure terminal
interface GigabitEthernet slot/subslot/port
Example:
Router(config)# interface GigabitEthernet 1/3/3
PurposeCommand or Action
Enables the privileged EXEC mode.enable
Enter your password, if prompted.
Enters the global configuration mode.configure terminal
Enters the interface configuration mode for Gigabit
Ethernet.
Overview of the Intelligent Wireless Access Gateway
PurposeCommand or Action
Step 4
Step 5
Step 6
Step 7
Step 8
description string
Example:
Router(config-if)# description access interface
connected to subscriber
ip address ip-address mask [secondary [vrf vrf-name]]
Example:
Router(config-if)# ip address 192.171.10.1
255.255.0.0
Example:
Router(config-if)# negotiation auto
service-policy type control policy-map-name
Example:
Router(config-if)# service-policy type control
BB_Profile
ip subscriber {l2-connected}
Example:
Router(config-if)# ip subscriber l2-connected
Adds a description to an interface configuration.
Sets a primary IP address or secondary IP address for
an interface.
Enables auto negotiation on a Gigabit Ethernet interface.negotiation auto
Applies a control policy to a context.
Enables Cisco ISG IP subscriber support on an interface
and specifies the access method that IP subscribers use
for connecting to the Cisco ISG on an interface.
Note
The iWAG does not support the routed access
method.
Step 9
initiator {dhcp | radius-proxy | static ip subscriber list
listname | unclassified ip | unclassified mac-address}
Example:
Router(config-subscriber)# initiator unclassified
mac-address
Step 10
initiator {dhcp | radius-proxy | static ip subscriber list
listname | unclassified ip | unclassified mac-address}
Example:
Router(config-subscriber)# initiator dhcp
Configuring a Tunnel Interface for the iWAG
This section describes how to configure a tunnel interface between the iWAG solution and the GGSN.
Enables the Cisco ISG to create an IP subscriber session
upon receipt of a specified type of packet.
Enables the Cisco ISG to create an IP subscriber session
upon receipt of a specified type of packet.
Overview of the Intelligent Wireless Access Gateway
PurposeCommand or Action
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
interval echo-request request-number
Example:
Router(config-gtp)# interval echo-request
60
interface local GigabitEthernet slot/subslot/port
Example:
Router(config-gtp)# interface local
GigabitEthernet 0/0/3
apn apn-name
Example:
Router(config-gtp)# apn example.com
ip address ggsn ip-address
Example:
Router(config-gtp-apn)# ip address ggsn
192.170.10.2
default-gw address prefix-len value
Example:
Router(config-gtp-apn)# default-gw
192.171.10.1 prefix-len 16
dns-server ip-address
Example:
Specifies the time interval, in seconds, for which the SGSN of the
iWAG waits for before sending an echo request message. The range
is from 60 to 65535. The default value is 60. The value of 0 disables
the Echo Request feature.
Configures the transport interface to communicate with the GGSN.
Configures an ASCII regular expression string to be matched against
the Access Point Name (APN) for GPRS load balancing.
Sets the IP address for the GGSN.
Specifies the default gateway address of the subscriber.
Note
This is the default gateway address of the IP provided by
the GGSN using GTP, and not the default gateway address
on the physical local interface that the subscriber is
connected to. They can be the same, but we recommend
that they be two different subnets.
Specifies the Domain Name System (DNS) IP servers that are
available for a DHCP client.
Specifies the primary and backup DHCP servers that are used to
allocate IP addresses to mobile station users entering a particular
public data network (PDN) access point.
Configures the duration (in seconds) of the lease for an IP address
that is assigned from a Cisco IOS DHCP Server to a DHCP client.
Overview of the Intelligent Wireless Access Gateway
Configuring the iWAG for 4G Mobile IP Users
Configuring PMIPv6 for the iWAG
You must configure PMIPv6 for the iWAG to allow access to mobile IP users.
The tasks listed below describe the procedures involved in configuring the Mobile Access Gateway. For
detailed steps, see the "How to Configure Proxy Mobile IPv6 Support for MAG Functionality" section in the
Configuring a Proxy Mobile IPv6 Domain by Using the Configuration from the AAA Server
•
Configuring the Minimum Configuration for a MAG to Function
•
Configuring a Detailed Configuration for a MAG when an AAA Server is not Available
•
Configuring a Minimum Configuration for a MAG
•
Configuring a Detailed Configuration for a MAG
•
Configuring the iWAG for 4G Mobile IP Users
The tasks listed below describe the procedures involved in configuring Local Mobility Anchor. For detailed
steps, see the "How to Configure Proxy Mobile IPv6 Support for LMA Functionality" section in the IP