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
Page 2
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.
Page 29
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
Overview of the Intelligent Wireless Access Gateway
Standards and RFCs
Feature Information for the Intelligent Wireless Access Gateway
TitleStandard/RFC
Mobility Support in IPv6RFC 3775
Proxy Mobile IPv6RFC 5213
RFC 5844
RFC 5845
MIBs
No new or modified MIBs are supported by this
feature.
Technical Assistance
The Cisco Support and Documentation website
provides online resources to download documentation,
software, and tools. Use these resources to install and
configure the software and to troubleshoot and resolve
technical issues with Cisco products and technologies.
Access to most tools on the Cisco Support and
Documentation website requires a Cisco.com user ID
and password.
IPv4 Support for Proxy Mobile
IPv6
Generic Routing Encapsulation
(GRE) Key Option for Proxy
Mobile IPv6
MIBs LinkMIB
To locate and download MIBs for selected platforms,
Cisco software releases, and feature sets, use Cisco
MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
LinkDescription
http://www.cisco.com/cisco/web/support/index.html
Feature Information for the Intelligent Wireless Access Gateway
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Overview of the Intelligent Wireless Access Gateway
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.
Table 2: Feature Information for the Intelligent Wireless Access Gateway
The iWAG solution offers the
following tunneling
technologies to integrate WiFi
access with the Evolved
Packet Core (EPC):
GPRS Tunnel Protocol
•
version 1 (GTPv1)
allows integration of a
3G environment, where
iWAG behaves in a way
that is similar to a
Serving GPRS Support
Node (SGSN)
connecting to a Gateway
GPRS Support Node
(GGSN).
Proxy Mobile IPv6
•
(PMIPv6) allows the
integration of a 4G
environment where
iWAG behaves as a
PMIPv6 Mobile Access
Gateway (MAG)
connecting to an Local
Mobility Anchor (LMA)
that is co-located with a
Packet Gateway (PGW),
which acts as PMIPv6
LMA.
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)
3.8S, this feature was
implemented on the Cisco
ASR 1000 Series Aggregation
Services Routers.
Page 33
CHAPTER 2
IP Sessions Over Gigabit EtherChannel
The IP Sessions over Gigabit EtherChannel (IPoGEC) feature enables you to add the Link Aggregation
Control Protocol (LACP) functionality for IP sessions. The LACP defines a virtual interface for a port channel
or a port bundle, and adds physical member links to the port channel. This section provides information
about the IPoGEC and how to configure it.
Finding Feature Information, page 25
•
Restrictions for IPoGEC, page 25
•
Information About IP Sessions over Gigabit EtherChannel, page 26
•
Configuring IP Sessions over Gigabit EtherChannel, page 26
•
Configuring Member Links for IP Sessions over Gigabit EtherChannel, page 28
•
Configuration Examples for IP Sessions Over Gigabit EtherChannel, page 29
•
Additional References, page 29
•
Feature Information for IP Sessions over Gigabit EtherChannel, page 30
•
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.
Restrictions for IPoGEC
IP Sessions over Gigabit EtherChannel (IPoGEC) currently supports the 1:1 model, where only one member
link is active while the second member link is passive and does not carry traffic.
Information About IP Sessions over Gigabit EtherChannel
Information About IP Sessions over Gigabit EtherChannel
The IP sessions over Gigabit EtherChannel (IPoGEC) feature ensures consistency between systems by adding
redundancy and allows dynamic link management during local and remote system failures. LACP fast
switchover enables the standby member link to take over instantly (in milliseconds) when the active member
link goes down. As a result, the port channel remains up. The carrier-delay {delay-seconds | msecmilliseconds} command used in the configuration of the IPoGEC ensures fast switchover, with the delay in
switchover being in milliseconds rather than seconds.
Supported Features for IPoGEC
IPoGEC supports both simple IP sessions and mobile IP sessions.
•
IPoGEC is supported over virtual local area network (VLAN) and subinterfaces.
•
IPoGEC is supported on all Ethernet SPAs, including 10-Gigabit Ethernet ports and 1-Gigabit Ethernet
•
ports.
Configuring IP Sessions over Gigabit EtherChannel
SUMMARY STEPS
configure terminal
1.
interface port-channel channel-number
2.
description string
3.
ip address ip-address mask [secondary [vrf vrf-name] ]
4.
load-interval seconds
5.
lacp fast-switchover
6.
lacp max-bundle max-bundle-number
7.
service-policy type control policy-map-name
8.
ip subscriber {l2-connected}
9.
initiator {dhcp | radius-proxy | static ip subscriber list listname | unclassified ip | unclassified
10.
mac-address}
initiator {dhcp | radius-proxy | static ip subscriber list listname | unclassified ip | unclassified
Enters the global configuration mode.configure terminal
Page 35
IP Sessions Over Gigabit EtherChannel
Configuring IP Sessions over Gigabit EtherChannel
PurposeCommand or Action
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
interface port-channel channel-number
Example:
Router(config)#interface port-channel 1
description string
Example:
Router(config-if)#description GEC:1 interface
towards switch
ip address ip-address mask [secondary [vrf vrf-name] ]
Example:
Router(config-if)#ip address 21.0.0.1 255.255.0.0
load-interval seconds
Example:
Router(config-if)#load-interval 30
Example:
Router(config-if)#lacp fast-switchover
lacp max-bundle max-bundle-number
Example:
Router(config-if)#lacp max-bundle 1
service-policy type control policy-map-name
Creates a port-channel virtual interface.
Adds a description to an interface configuration.
Removes an IP address from an interface.
Changes the length of time for which data is used to
compute load statistics.
Enables the LACP 1:1 link redundancy.lacp fast-switchover
Defines the maximum number of active, bundled LACP
ports allowed in a port channel.
Applies a control policy to a context.
Example:
Router(config-if)#service-policy type control
BB_PMAP
Step 9
ip subscriber {l2-connected}
Example:
Router(config-if)#ip subscriber l2-connected
Step 10
initiator {dhcp | radius-proxy | static ip subscriber list
listname | unclassified ip | unclassified mac-address}
Example:
Router(config-subscriber)# initiator unclassified
mac-address
OL-30226-0327
Enables Cisco Intelligent Services Gateway (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.
Enables the Cisco ISG to create an IP subscriber session
upon receipt of a specified type of packet.
no ip address ip-address mask [secondary [vrf
vrf-name] ]
Example:
Router(config-if)#no ip address
carrier-delay {delay-seconds | msec milliseconds}
Example:
Router(config-if)# carrier-delay msec 50
lacp port-priority priority
Example:
Router(config-if)#lacp port-priority 4000
PurposeCommand or Action
Enters the interface configuration mode for Gigabit Ethernet
interface.
Removes an IP address from an interface.
Sets the carrier delay on a serial interface. To achieve faster
switchover from active to standby member link, the carrier delay
value can be set to 0 ms.
Sets the LACP priority for a physical interface. IPoGEC currently
supports 1:1 model, that is one active member link and one
standby member link, which only requires choosing two different
values for priority field to make sure one interface is active while
the other is standby. The value set for the priority field shall
match the value configured on the switch.
Configures the interface in a channel group and sets the LACP
mode.
Configuration Examples for IP Sessions Over Gigabit
EtherChannel
Example: Configuring IPoGEC
interface Port-channel1
description GEC:1 interface towards switch
ip address 21.0.0.1 255.255.0.0
load-interval 30
lacp fast-switchover
lacp max-bundle 1
service-policy type control BB_PMAP
ip subscriber l2-connected
Feature Information for IP Sessions over Gigabit EtherChannel
MIBs
IP Sessions Over Gigabit EtherChannel
MIBs LinkMIB
No new or modified MIBs are supported by this
feature.
Technical Assistance
The Cisco Support website provides extensive online
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a Cisco.com user ID and password.
To locate and download MIBs for selected platforms,
Cisco software releases, and feature sets, use Cisco
MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
LinkDescription
http://www.cisco.com/cisco/web/support/index.html
Feature Information for IP Sessions over Gigabit EtherChannel
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
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.
Table 3: Feature Information for IP Sessions over Gigabit EtherChannel
Feature InformationReleasesFeature Name
Cisco IOS XE Release 3.9IP Sessions over Gigabit
EtherChannel
The IP sessions over Gigabit
EtherChannel (IPoGEC) feature
enables you to add the Link
Aggregation Control Protocol
(LACP) functionality for IP
sessions.
In Cisco IOS XE Release 3.9S, this
feature was implemented on the
Cisco ASR 1000 Series
Aggregation Services Routers.
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)
A tunnel facilitates bidirectional transport or acts as a conduit for forwarding subscriber traffic. In PMIPv6,
subscriber traffic is transported between the MAG and the Local Mobility Anchor (LMA) through the Generic
Routing Encapsulation (GRE) tunnel. In the GTP, subscriber traffic is transported between the iWAG and
the GGSN through the GTP tunnel. The tunnel information structure is associated with each tunnel and
specifies common tunnel attributes, such as source address, destination address, protocol, port, key, tunnel
transport VRF, and tunnel mode.
Finding Feature Information, page 33
•
Information About Multiple-Flow Tunnel, page 33
•
Additional References, page 34
•
Feature Information for Multiple-Flow Tunnel, page 35
•
Finding Feature Information
CHAPTER 3
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.
Information About Multiple-Flow Tunnel
Both the GTP and PMIPv6 support multiple flows per tunnel. A multiple-flow tunnel mechanism configures
and manages multiple flows of traffic within the same tunnel. Each flow is identified by a flow key. A flow
identifier or flow key is a 32-bit integer. The key is globally unique per system for the GTP. However, the
key can be unique per tunnel for PMIPv6. The flow key for the GTP is the Tunnel Endpoint Identifier (TEID),
and for PMIPv6, it is the GRE key. Each flow has parameters to describe the per-flow attributes.
PMIPv6 uses a multipoint GRE tunnel per LMA, and creates one adjacency per flow. An LMA can support
scaling numbers up to 128,000 MAG. From the LMA perspective, only one multipoint GRE tunnel interface
is created and 128,000 tunnel endpoints are populated. This scaling level supports the MAG functionality that
is implemented on access points or hotspots, from which only one or few PMIPv6 subscribers can be attached.
Cisco high-end routing platforms, such as the Cisco ASR 1000 Series Route Processor 2, the Cisco ASR 1000
Series 40-Gbps ESP, and the Cisco ASR 1000 Series 100-Gbps ESP support 128,000 scaling for the LMA.
To support 128,000 scaling, configure the following on the LMA:
ipv6 mobile pmipv6-lma LMA1 domain D1
bce maximum 128000
Additional References
Related Documents
Multiple-Flow Tunnel
Document TitleRelated Topic
Cisco IOS Master Commands List, All ReleasesCisco IOS commands
iWAG commands
MIBs
No new or modified MIBs are supported by this
feature.
Technical Assistance
The Cisco Support website provides extensive online
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a Cisco.com user ID and password.
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
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.
Table 4: Feature Information for Multiple-Flow Tunnel
Feature InformationReleasesFeature Name
Cisco IOS XE Release 3.9SMultiple-Flow Tunnel
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)
Service Provider WiFi: Support for Integrated
Ethernet Over GRE
Generic Routing Encapsulation (GRE) is a tunneling protocol that encapsulates a wide variety of network
layer protocols inside virtual point-to-point links over a Layer 3 IPv4 or Layer 3 IPv6 access network.
Finding Feature Information, page 37
•
Information About Ethernet Over GRE, page 38
•
Restrictions for Configuring Ethernet Over GRE, page 38
•
Prerequisites for Configuring Ethernet Over GRE, page 39
•
Information About Configuring Ethernet Over GRE, page 39
•
Supported Features, page 44
•
How to Configure the EoGRE Feature, page 45
•
Example: Configuring the EoGRE Feature, page 46
•
Additional References, page 48
•
Feature Information for Configuring Ethernet Over GRE, page 49
•
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.
Ethernet over GRE (EoGRE) is a new aggregation solution for aggregating WiFi traffic from hotspots. This
solution enables customer premises equipment (CPE) devices to bridge the Ethernet traffic coming from an
end host, and encapsulate the traffic in Ethernet packets over an IP GRE tunnel. When the IP GRE tunnels
are terminated on a service provider broadband network gateway, the end host’s traffic is terminated and
subscriber sessions are initiated for the end host.
The following figure shows the structure of the Ethernet over GRE.
Figure 2: Ethernet Over GRE Structure
Service Provider WiFi: Support for Integrated Ethernet Over GRE
Restrictions for Configuring Ethernet Over GRE
The following features are not supported on the Cisco ASR 1000 Series Aggregation Services Routers:
IPsec tunnel between the Cisco ASR 1000 Series Aggregation Services Routers and the CPE devices
•
Native multicast coexistence for subscribers
•
Per-CPE QoS
•
IPv6 subscriber
•
The Cisco Intelligent Services Gateway (ISG) RADIUS proxy initiator
Service Provider WiFi: Support for Integrated Ethernet Over GRE
Prerequisites for Configuring Ethernet Over GRE
Prerequisites for Configuring Ethernet Over GRE
Before you configure the Ethernet over GRE feature on the Cisco ASR 1000 Series Aggregation Services
Routers, ensure that the following prerequisites are met:
A physical interface or dot1Q interface should be configured.
•
The ISG policy should not be applied to the physical interface.
•
Information About Configuring Ethernet Over GRE
The Cisco ASR 1000 Series Aggregation Services Routers serve as a service provider broadband network
gateway that:
Terminates IPv4 or IPv6 GRE tunnels.
•
Manages the subscriber session for end-host clients.
•
The EoGRE feature works with legacy residential gateways and CPE devices to terminate the Ethernet L2
traffic in the Cisco ASR 1000 Series Aggregation Services Routers. When configured as an intelligent Wireless
Access Gateway (iWAG) with EoGRE access tunneling support, the Cisco ASR 1000 Series Aggregation
Services Routers can extend mobility and the ISG services in support of these legacy devices.
Service Provider WiFi: Support for Integrated Ethernet Over GRE
EoGRE Deployment with PMIPv6 Integrated for Mobility Service
EoGRE Deployment with PMIPv6 Integrated for Mobility Service
Proxy Mobile IPv6 (PMIPv6) provides mobility service to the mobile nodes that are connected to the Mobile
Access Gateway (MAG) via an EoGRE tunnel. The following figure shows the structure of the EoGRE
deployment with PMIPv6 integrated for mobility service.
Figure 5: Structure of the EoGRE Deployment with PMIPv6 Integrated for Mobility Service
Note
Mobile nodes access the mobile internet service over Wi-Fi access points. The access points are either
autonomous access points or are connected to the Cisco Wireless LAN Controller (WLC). These access points
and WLCs are used as residential gateways or CPE devices. CPEs are preconfigured with a point-to-multipoint
GRE IP tunnel to the Cisco ASR 1000 Series Aggregation Services Routers as the MAG. The tunnel from
the CPE device can be configured with a static GRE key. The CPEs are provisioned to forward the Ethernet
traffic from both public and private customers to the GRE tunnel, and to add a VLAN tag on the Ethernet
frame before forwarding the traffic.
As with regular PMIPv6 deployments, the Cisco ASR 1000 Series Aggregation Services Routers can create
IP sessions on EoGRE access tunnels similar to the regular IP sessions on the physical Ethernet interfaces,
and allocate IP addresses for mobile nodes, either locally or in the proxy mode. Mobility service is provided
to the mobile nodes and the tunneled Ethernet traffic is forwarded via IP tunnels to the Local Mobility Anchor
(LMA).
When you ping a mobile node from the MAG with a packet size that is larger than that of the path maximum
transmission unit (PMTU) that is configured with the DF bit set, the packet will be dropped. However,
you will not get the return type as M.M.M (could not fragment). This is reflected in the log messages or
error messages.
For more information about PMIPv6 and the ISG configurations for the iWAG, see the Intelligent WirelessGateway Configuration Guide.
Service Provider WiFi: Support for Integrated Ethernet Over GRE
EoGRE Deployment with GTP Integrated for Mobility Service
EoGRE Deployment with GTP Integrated for Mobility Service
GPRS Tunneling Protocol (GTP) provides mobility service to the mobile nodes that are connected to the
iWAG via an EoGRE tunnel, as shown in the following figure.
Figure 6: Structure of the EoGRE Deployment with GTP Integrated for Mobility Service
For more information about the GTP and ISG configurations for the iWAG, see the Intelligent Wireless
Gateway Configuration Guide.
EoGRE Deployment with ISG Integrated for Simple IP Service
The ISG provides simple IP service to mobile nodes that are connected to ISG via the EoGRE tunnel, as
shown in the following figure. The Cisco ASR 1000 Series Aggregation Services Routers use the ISG
Service Provider WiFi: Support for Integrated Ethernet Over GRE
framework to allocate IP sessions for authenticated subscribers. Simple IP subscribers are provided ISG
services, including Internet access, but are not provided access to mobility services via GTP or PMIPv6.
Figure 7: Structure of the EoGRE Deployment with ISG Integrated for Simple IP Service
Supported Features
The following features are supported as part of the EoGRE feature on the Cisco ASR 1000 Series Aggregation
Services Routers:
Ethernet over GRE traffic termination on the routers
•
Frames can have up to one dot1Q VLAN tag
•
L2-connected IPv4 mobile nodes
•
GRE tunnel for IPv4 or IPv6
•
ISG and PMIPv6 or GTP integrated with the EoGRE tunnel
Service Provider WiFi: Support for Integrated Ethernet Over GRE
How to Configure the EoGRE Feature
SUMMARY STEPS
enable
1.
configure terminal
2.
interface interface-name
3.
ip unnumbered loopback interface-name or ip address ip-address
4.
tunnel source interface-type interface-number
5.
(For simple IP mode) mac-address H.H.H
6.
tunnel mode ethernet gre ipv4 or tunnel mode ethernet gre ipv6
7.
(Optional) tunnel vlan vlan-id
8.
end
9.
How to Configure the EoGRE Feature
DETAILED STEPS
Step 1
Example:
Router> enable
Step 2
Example:
Router# configure terminal
Step 3
Step 4
interface interface-name
Example:
Router(config)# interface Tunnel 0
ip unnumbered loopback interface-name or ip
address ip-address
Example:
Router(config-if)# ip unnumbered loopback 0
or
Router(config-if)# ip address 20.1.1.2
255.255.255.0
PurposeCommand or Action
Enables the privileged EXEC mode.enable
Enter your password, if prompted.
Enters the global configuration mode.configure terminal
Specifies the logical interface for the EoGRE tunnel.
For PMIPv6 and GTP scenarios, an unnumbered address or
a specified IP address can be configured on the tunnel
interface.
For a simple IP scenario, only a specified IP address can be
configured on the tunnel interface. This IP address can be used
as a default gateway IP address.
Service Provider WiFi: Support for Integrated Ethernet Over GRE
PurposeCommand or Action
Step 5
Step 6
Step 7
Step 8
Step 9
tunnel source interface-type interface-number
Example:
Router(config-if)# tunnel source Loopback 0
(For simple IP mode) mac-address H.H.H
Example:
Router(config-if)# mac-address 0000.5e00.5213
tunnel mode ethernet gre ipv4 or tunnel mode
ethernet gre ipv6
Example:
Router(config-if)# tunnel mode ethernet gre
ipv4
or
Router(config-if)# tunnel mode ethernet gre
ipv6
(Optional) tunnel vlan vlan-id
Example:
Router(config-if)# tunnel vlan 1000
Sets the source interface for the EoGRE tunnel interface.
Sets the source MAC address for the EoGRE tunnel interface.
The MAC address is mandatory for simple IP deployment.
For PMIPv6/GTP, the default MAC address associated with
EoGRE Tunnel is 0000.5e00.5213.
Sets the EoGRE encapsulation mode for the tunnel interface
for IPv4.
or
Sets the EoGRE encapsulation mode for the tunnel interface
for IPv6.
(Optional) Sets the VLAN ID of the EoGRE tunnel.
Ends the current configuration session.end
Example:
Router(config-if)# end
Example: Configuring the EoGRE Feature
aaa new-model
!
aaa group server radius AAA_SERVER_CAR
server-private 5.3.1.76 auth-port 2145 acct-port 2146 key cisco
!
aaa authentication login default none
aaa authentication login ISG_PROXY_LIST group AAA_SERVER_CAR
aaa authorization network ISG_PROXY_LIST group AAA_SERVER_CAR
aaa authorization subscriber-service default local group AAA_SERVER_CAR
aaa accounting network PROXY_TO_CAR
action-type start-stop
group AAA_SERVER_CAR
!
aaa accounting network ISG_PROXY_LIST start-stop group AAA_SERVER_CAR
!
Service Provider WiFi: Support for Integrated Ethernet Over GRE
aaa server radius dynamic-author
client 5.3.1.76 server-key cisco
auth-type any
ignore server-key
!
!
ip dhcp excluded-address 172.16.254.254
!
ip dhcp pool ISG_SIMPLE_IP
domain-name cisco.com
!
policy-map type control EOGRE_L2_ISG
class type control always event session-start
2 authorize aaa list ISG_PROXY_LIST password cisco identifier mac-address
4 set-timer IP_UNAUTH_TIMER 5
!
class type control always event service-start
1 service-policy type service identifier service-name
2 collect identifier nas-port
!
!
interface Loopback0
ip address 9.9.9.9 255.255.255.255
interface GigabitEthernet1/0/0
ip address 192.168.0.9 255.255.255.0
negotiation auto
!
interface GigabitEthernet1/0/0.778
description "to ASR5K GGSN"
encapsulation dot1Q 778
ip address 172.16.199.9 255.255.255.0
!
interface Tunnel10
description "EoGRE Tunnel for Simple IP subscribers"
mac-address 0000.5e00.5213
ip address 172.16.254.254 255.255.0.0
no ip redirects
tunnel source 172.16.199.9
tunnel mode ethernet gre ipv4
service-policy type control EOGRE_L2_ISG
ip subscriber l2-connected
initiator unclassified mac-address
initiator dhcp
interface Tunnel100
description "IPv4 EoGRE Tunnel for PMIP/GTP subscribers"
ip unnumbered Loopback0
tunnel source GigabitEthernet1/0/0
tunnel mode ethernet gre ipv4
tunnel vlan 100
service-policy type control EOGRE_L2_ISG
ip subscriber l2-connected
initiator unclassified mac-address
initiator dhcp
!
interface Tunnel200
description "IPv6 EoGRE Tunnel for PMIP/GTP subscribers"
ip unnumbered Loopback0
tunnel source 2001:161::9
tunnel mode ethernet gre ipv6
tunnel vlan 200
Service Provider WiFi: Support for Integrated Ethernet Over GRE
ipv4-address 192.168.199.1
!
ipv6 mobile pmipv6-mag M1 domain D1
sessionmgr
role 3GPP
address ipv4 9.9.9.9
interface Tunnel100
interface Tunnel200
lma LMA_5K D1
ipv4-address 192.168.199.1
encap gre-ipv4
!
ntp master
!
gtp
information-element rat-type wlan
interface local GigabitEthernet1/0/0.778
apn 1
apn-name gtp.com
ip address ggsn 172.16.199.1
fixed link-layer address 00ab.00cd.00ef
default-gw 20.100.254.254 prefix-len 16
dns-server 20.100.254.254
dhcp-server 20.100.254.254
!
end
You can use the following commands to check and show subscriber session information:
show ip dhcp sip statistics
show subscriber statistics
show subscriber session
show ipv6 mobile pmipv6 mag binding
show gtp pdp-context all
show interface tunnel-name
Additional References
Related Documents
iWAG commands
MIBs
No new or modified MIBs are supported by this
feature.
Document TitleRelated Topic
Cisco IOS Master Commands List, All ReleasesCisco IOS commands
Service Provider WiFi: Support for Integrated Ethernet Over GRE
Technical Assistance
Feature Information for Configuring Ethernet Over GRE
LinkDescription
The Cisco Support website provides extensive online
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a Cisco.com user ID and password.
http://www.cisco.com/cisco/web/support/index.html
Feature Information for Configuring Ethernet Over GRE
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
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.
Feature Information for Configuring Ethernet Over GRE
Table 5: Feature Information for Configuring the Ethernet Over GRE Feature
Service Provider WiFi: Support for Integrated Ethernet Over GRE
Feature InformationReleasesFeature Name
Integrated Ethernet Over
GRE
3.9.1SService Provider WiFi:
This feature enables the
Ethernet over Generic
Routing Encapsulation
(EoGRE) tunnel to be
used as a service provider
WiFi access interface
from CPE devices. A
Cisco ASR 1000 Series
Aggregation Services
Router is used as an L2
aggregator to terminate
L2 traffic at the GRE
tunnel interface and
provide L3 services.
In Cisco IOS XE Release
3.9.1S, this feature is
implemented on the Cisco
ASR 1000 Series
Aggregation Services
Routers.
The following sections
provide information about
this feature:
Effective from Cisco IOS XE Release 3.10S, the support for GPRS Tunneling Protocol Version 2 (GTPv2)
is offered on the Cisco ASR 1000 Series Aggregation Services Routers as an enhancement to the GTPv1
offering in the iWAG solution that was introduced in Cisco IOS XE Release 3.8S. GTPv2 provides support
for both the 4G and 3G mobile users, whereas GTPv1 provides support only for 3G mobile users.
Finding Feature Information, page 51
•
Restrictions for GTPv2 of the iWAG, page 51
•
Information About GTPv2 in the iWAG, page 52
•
GTPv2 Configuration, page 52
•
Intra-iWAG Roaming, page 53
•
Additional References, page 54
•
Feature Information for GTPv2 Support in the iWAG, page 55
•
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.
Restrictions for GTPv2 of the iWAG
The same domain name cannot be configured in different APNs, for example:
ip address ggsn 98.0.7.14
default-gw 192.168.0.1 prefix-len 16 #different domain name but same pool ip;
dns-server 10.254.255.253
dhcp-lease 3000
Information About GTPv2 in the iWAG
A GTP session with GTPv2 support uses more memory than a GTP session with GTPv1 support. GTPv2
support does not require any new AAA attributes. However, the new gtpv2 enum value for the
Cisco-MPC-Protocol-Interface attribute is necessary to specify the use of GTPv2. The AAA server identifies
a subscriber depending upon whether the subscriber profile is sent over GTPv1 tunnel or GTPv2 tunnel from
the iWAG back to the Evolved Packet Core (EPC). The GTPv1 and GTPv2 sessions can exist simultaneously
on the iWAG.
GTPv2 Configuration
All the configurations required for GTPv1 support are also needed for GTPv2 support.
Effective from Cisco IOS XE Release 3.10S, both GTPv1 and GTPv2 support connected subscriber roaming
across different access interfaces of the iWAG. GTPv1 and GTPv2 preserve and update their existing sessions
to allow their data traffic to flow through the new ingress interfaces from the access network.
Configuration for the GTPv1 and GTPv2 Roaming Scenario
The initiator unclassified mac-address command must be configured on every iWAG access interface to
support subscriber roaming between these interfaces. As shown in the following configuration, all the access
interfaces must be specified under the GTP configuration before bringing up the IP subscriber sessions. If the
access interface is not specified under the GTP, a subscriber’s roaming option is not enabled for that interface.
Also, adding interfaces under the GTP after the sessions bring up fails subscriber roaming.
The following example shows the configuration for GTPv1 and GTPv2 roaming scenario:
interface GigabitEthernet0/0/2
description To client facing interface
ip address 192.1.1.1 255.255.0.0
negotiation auto
service-policy type control ISG_GTP_CONTROL
ip subscriber l2-connected
initiator unclassified mac-address # must for roaming config
initiator dhcp
!
interface GigabitEthernet0/0/3
description To client facing interface
ip address 192.2.1.1 255.255.0.0
negotiation auto
service-policy type control ISG_GTP_CONTROL
ip subscriber l2-connected
initiator unclassified mac-address # must for roaming config
initiator dhcp
!
gtp
The Cisco Support website provides extensive online
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a Cisco.com user ID and password.
http://www.cisco.com/cisco/web/support/index.html
Feature Information for GTPv2 Support in the iWAG
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
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.
Table 6: Feature Information for GTPv2 Support in the iWAG
Feature InformationReleasesFeature Name
Cisco IOS XE Release 3.10GTPv2 Support in the iWAG
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)
In Cisco IOS XE Release 3.10S,
this feature was implemented on
the Cisco ASR 1000 Series
Aggregation Services Routers.
Effective from Cisco IOS XE Release 3.10S, the per-session Stateful Switchover (SSO)/In Service Software
Upgrade (ISSU) feature supports iWAG mobility sessions that are tunneled to MNO using GTP. The SSO
feature takes advantage of Route Processor (RP) redundancy by establishing one of the RPs as the active
processor, while the other RP is designated as the standby processor, and then synchronizing the critical
state information between them. When a failover occurs, the standby device seamlessly takes over, starts
performing traffic-forwarding services, and maintains a dynamic routing table.
Finding Feature Information, page 57
•
Information About iWAG SSO Support for GTP, page 57
•
Enabling SSO Support for the GTP, page 58
•
Additional References, page 59
•
Feature Information for iWAG SSO Support for GTP, page 60
•
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.
Information About iWAG SSO Support for GTP
The SSO/ISSU feature supports only the Cisco ASR 1000 Series Aggregation Services Routers intrachassis
(RP-to-RP) SSO, but not the interchassis (Cisco ASR1K-to-Cisco ASR1K) SSO. The First Sign Of Life
(FSOL) triggers that are supported on SSO include DHCP proxy (where the iWAG acts as the DHCP proxy
server) and DHCP proxy plus unclassified MAC.
For more information about ISSU, see the “Overview of ISSU on the Cisco ASR 1000 Series Routers” section
of the Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide.
The process as part of iWAG SSO handling GTP checkpoints to the standby RP the information that is
necessary to create a copy of the session on the standby RP. Such an inactive copy of the session becomes
active when the standby RP becomes active.
When an iWAG mobility session with GTP tunneling is enabled using the SSO/ISSU feature, the Cluster
Control Manager on the active RP needs to wait for a few more components, including the GTP, to become
ready before checkpoint data collection, and polls these additional components for checkpoint data during
data collection. A very similar operation is performed on the standby RP as well. Although such additional
CPU consumption is per session, it is not expected to be too heavy since processing in each of these components
should include the time spent on a few data structure lookups and memory-copying operations.
During ISSU SIP and SPA upgrade, there is traffic interruption. To avoid session disconnect because of
dropped echo messages during such traffic interruption, a user has the following options:
Option 1 (preferred):
•
1
Disable the echo messages on the iWAG and GGSN for the duration of the ISSU.
2
Re-enable the echo messages after ISSU is completed on the iWAG and GGSN.
Option 2: Extend the t3 and n3 configurations to exceed the expected traffic interruption. The traffic
•
interruption characterized in the Cisco IOS XE Release 3.10S is 127 seconds. Hence, we recommend
the following t3 and n3 settings (t3_response: 1 and n3_request: 7, resulting in 127 seconds on both the
iWAG and GGSN) but the duration of the traffic interruption may depend on the types of SIPs and SPAs
and how loaded the router is. If traffic interruption exceeds the configured t3 and n3 limits, the session
is disconnected.
iWAG SSO Support for GTP
Enabling SSO Support for the GTP
This section describes how to enable SSO support for the GTP on the Cisco ASR 1000 Series Aggregation
Services Routers.
The Cisco Support website provides extensive online
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a Cisco.com user ID and password.
http://www.cisco.com/cisco/web/support/index.html
Feature Information for iWAG SSO Support for GTP
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
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.
Table 7: Feature Information for iWAG SSO Support for GTP
Feature InformationReleasesFeature Name
Cisco IOS XE Release 3.10iWAG SSO Support for GTP
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)
In Cisco IOS XE Release 3.10S,
this feature was implemented on
the Cisco ASR 1000 Series
Aggregation Services Routers.
In Cisco IOS XE Release 3.10S, the Configuring Intelligent Services Gateway (ISG) Policy Templates
feature optimizes the provisioning of ISG policies on IPv4 and IPv6 subscriber sessions. It enables support
of up to 128,000 IP subscriber sessions with more complex ISG policies at a higher churn rate on the Cisco
ASR 1000 Series Aggregation Services Routers.
Finding Feature Information, page 61
•
Restrictions for Configuring ISG Policy Templates, page 61
•
Information About Configuring ISG Policy Templates, page 61
•
Additional References, page 62
•
Feature Information for Configuring ISG Policy Templates, page 63
•
Finding Feature Information
CHAPTER 7
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.
Restrictions for Configuring ISG Policy Templates
Enabling policy templates in the ISG is not supported for any type of PPP sessions and IP interface sessions.
Information About Configuring ISG Policy Templates
A typical ISG configuration has very few distinct policies and many sessions that use these policies. ISG
policy templates take advantage of this to optimize resource consumption and enable support for higher scale.
Instead of provisioning an ISG policy with all its individual services and features on each target IP subscriber
session, it provisions a template of the policy through the system only once and references the template after
that to apply the policy on each target session. Enabling policy templates in the ISG does not impact session
SSO.
How to Configure ISG Policy Templates
By default, the ISG policy templates are disabled. The platform subscriber template command enables the
ISG policy templates.
Configuring ISG Policy Templates
Note
The platform subscriber template command does not take effect until the router is reloaded. For example,
if this command is entered at the configuration prompt, policy templating remains disabled until the router
is reloaded. Similarly, if templating is enabled, the router has to be reloaded after the no subscriber template
command is entered to disable ISG policy templating.
Additional References
Related Documents
iWAG commands
MIBs
No new or modified MIBs are supported by this
feature.
Document TitleRelated Topic
Cisco IOS Master Commands List, All ReleasesCisco IOS commands
Feature Information for Configuring ISG Policy Templates
LinkDescription
The Cisco Support website provides extensive online
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a Cisco.com user ID and password.
http://www.cisco.com/cisco/web/support/index.html
Feature Information for Configuring ISG Policy Templates
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
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.
Table 8: Feature Information for Configuring ISG Policy Templates
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)
In Cisco IOS XE Release 3.10S,
this feature was implemented on
the Cisco ASR 1000 Series
Aggregation Services Routers.
The ISG Accounting Accuracy for LNS Sessions feature improves the accuracy of reported statistics for the
LNS sessions and traffic classes in the Stop Accounting messages. Because of the distributed nature of the
Cisco ASR 1000 Series Aggregation Services Routers, subscriber statistics are collected periodically every
10 seconds to balance the impact to statistics accuracy, and call setup and teardown rates. Statistics reports
that are generated using this collection are therefore up to 10 seconds old. When the Accounting Accuracy
feature is enabled, the most recent statistics are retrieved for particular subscribers in specific conditions,
such as when a session is torn down or stopped.
Finding Feature Information, page 65
•
Information About Cisco ISG Accounting Accuracy for LNS Sessions, page 65
•
Additional References, page 66
•
Feature Information for Cisco ISG Accounting Accuracy for LNS Sessions, page 67
•
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.
Information About Cisco ISG Accounting Accuracy for LNS
Sessions
You can enable or disable the ISG Accounting Accuracy for LNS Sessions feature using the subscriber
accounting accuracy timeout value command.
When the ISG Accounting Accuracy for LNS Sessions feature is enabled, the LNS sessions that are getting
disconnected are held off until the timeout value configured in the subscriber accounting accuracy timeoutvalue command is reached. The sessions are torn down when their most recent statistics have been collected,
or when the timeout period expires, whichever is sooner. The minimum timeout that can be configured is 1
second, and the maximum timeout that can be configured is 10 seconds.
Additional References
Related Documents
Cisco ISG Accounting Accuracy for LNS Sessions
Document TitleRelated Topic
Cisco IOS Master Commands List, All ReleasesCisco IOS commands
iWAG commands
MIBs
No new or modified MIBs are supported by this
feature.
Technical Assistance
The Cisco Support website provides extensive online
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a Cisco.com user ID and password.
Feature Information for Cisco ISG Accounting Accuracy for LNS Sessions
Feature Information for Cisco ISG Accounting Accuracy for LNS
Sessions
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
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.
Table 9: Feature Information for Cisco ISG Accounting Accuracy for LNS Sessions
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)
The ISG Accounting Accuracy for
Sessions feature improves the
accuracy of reported statistics for
L2TP Network Server (LNS)
sessions and traffic classes in the
Stop Accounting messages.
In Cisco IOS XE Release 3.11S,
this feature was implemented on
the Cisco ASR 1000 Series
Aggregation Services Routers.
Effective from Cisco IOS XE Release 3.11S, the Intelligent Wireless Access Gateway (iWAG) supports
dual-stack session for Proxy Mobile IPv6 (PMIPv6) and GPRS Tunneling Protocol (GTP) sessions.
This chapter contains the following sections:
Finding Feature Information, page 69
•
Information About Dual-Stack Support for PMIPv6, page 69
•
Information About Dual-Stack Support for GTP, page 70
•
AAA Attributes for Dual Stack, page 70
•
Configuration Examples for Dual-Stack PMIPv6, page 71
•
Configuration Examples for Dual-Stack GTP, page 75
•
Additional References, page 76
•
Feature Information for Dual-Stack Support for PMIPv6 and GTP, page 77
•
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.
Information About Dual-Stack Support for PMIPv6
The Dual Stack Support for PMIPv6 feature allows both IPv4 and IPv6 traffic streams to flow through a single
PMIPv6 session. The IPv4 and IPv6 traffic streams from a subscriber are identified using the Subscriber MAC
address. The iWAG supports following functionalities:
Dual-stack L2-connected Internet Protocol Over Ethernet (IPoE) subscriber sessions
•
Features Supported for Dual-Stack PMIPv6 Sessions
IPv4 address allocation method using Dynamic Host Configuration Protocol (DHCP)
•
IPv6 address allocation method using Stateless Address Auto Configuration (SLAAC)
•
Idle timeout for per-user accounting and per-flow accounting
•
Absolute timeout for per-user accounting and per-flow accounting
•
Postpaid for per-user accounting and per-flow accounting
•
QoS policy for per-user accounting and per-flow accounting
•
Information About Dual-Stack Support for GTP
The Dual Stack Support for GTP feature allows both IPv4 and IPv6 traffic streams to flow through a single
GTP session. The IPv4 and IPv6 traffic streams from a subscriber are identified using the Subscriber MAC
address. This feature enables the assignment of both an IPv4 address and an IPv6 address to a client. Therefore,
the overall number of supported subscribers on the Cisco ASR 1000 Series Aggregation Services Routers are
not affected by a mix of IPv4 and IPv6 traffic.
Prior to the introduction of the Dual-Stack feature, GTP supported only IPv4 sessions.Note
Dual-Stack GTP sessions support the following session initiators:
Unclassified MAC
•
IPv6 Neighbor Discovery
•
DHCPv4
•
Restrictions for Dual-Stack GTP
The connection between the iWAG and GGSN or PGW can only be IPv4 even though the sessions can
•
be IPv4, IPv6, or dual stack.
The DNS server (under the gtp or apn configuration submode) can be configured only for IPv4.
•
AAA Attributes for Dual Stack
After the AAA server authenticates a subscriber, an AAA attribute is returned in the Access Accept message
sent to the iWAG to indicate the session type.
The AAA attribute for the Dual Stack configuration can have the following values:
Example: Configuring an Access Interface for Dual-Stack PMIPv6
stack
15 service-policy type service name ACC_V4#applying services during dual
stack
16 service-policy type service name ACC_V6#applying services during dual
stack
20 service-policy type service name TO_V4#applying services during dual
stack
21 service-policy type service name TO_V6#applying services during dual
stack
25 service-policy type service name SESSION_TIMEOUT_SERVICE #applying services during
dual stack
30 authorize aaa list default identifier mac-address#performs MAC TAL authorization
Example: Configuring an Access Interface for Dual-Stack PMIPv6
interface GigabitEthernet0/0/2
description manthiya connected to MN1
ip address 11.1.1.2 255.255.255.0
negotiation auto
ipv6 address FE80::200:5EFF:FE00:5213 link-local
service-policy type control PMIP_DUAL_STACK#subscriber services are applied based on
ip subscriber l2-connected#invokes iWAG functionality
initiator unclassified mac-address#unclassified MAC address with IPv4 and IPv6
packets,
are treated as FSOL to create a session
initiator dhcp#DHCP control packets are used as FSOL
to create DHCPv4 only session
end
the control policy definition
Example: Configuring the Local Mobility Anchor for Cisco ASR 5000 Routers
context pgw
ip pool PMIP_POOL 70.70.0.1 255.255.0.0 public 0 subscriber-gw-address 70.70.70.1
ip pool v4_staticpool 9.9.9.1 255.255.0.0 static
ipv6 pool v6_pool prefix eeee::1/48 public 0 policy allow-static-allocation
router rip
network ip 70.70.0.0/16
network name lma2
redistribute connected
interface GigabitEthernet0/1/3
description SGSN to GGSN port
ip address 10.201.31.1 255.255.255.0
negotiation auto
ipv6 address 2007::2/64
end
Example: Configuring a Control Policy for Dual-Stack GTP
policy-map type control BB_PMAP
class type control always event session-start
10 authorize aaa list BB_1 password cisco identifier mac-address
Example: Configuring an Access Interface for Dual-Stack GTP
interface GigabitEthernet0/0/3
ip address 21.0.0.1 255.255.0.0
ipv6 address 8001::1/16
ipv6 enable
ipv6 nd ra interval 600
service-policy type control BB_PMAP
ip subscriber l2-connected
Cisco IOS Master Commands List, All ReleasesCisco IOS commands
iWAG commands
MIBs
No new or modified MIBs are supported by this
feature.
Technical Assistance
The Cisco Support website provides extensive online
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a Cisco.com user ID and password.
Feature Information for Dual-Stack Support for PMIPv6 and GTP
Feature Information for Dual-Stack Support for PMIPv6 and GTP
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
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.
Table 10: Feature Information for Dual-Stack Support for PMIPv6 and GTP
Feature InformationReleasesFeature Name
Cisco IOS XE Release 3.11Dual-Stack Support for PMIPv6
Cisco IOS XE Release 3.11Dual-Stack Support for GTP
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)
The Dual-Stack Support for
PMIPv6 feature allows both IPv4
and IPv6 traffic streams to flow
through a single PMIPv6 session.
In Cisco IOS XE Release 3.11S,
this feature was implemented on
the Cisco ASR 1000 Series
Aggregation Services Routers.
The Dual-Stack Support for GTP
feature allows both IPv4 and IPv6
traffic streams to flow through a
single GTP session.
In Cisco IOS XE Release 3.11S,
this feature was implemented on
the Cisco ASR 1000 Series
Aggregation Services Routers.
The traffic from an IP session is redirected based on the destination address (for a simple IP session), and
to a tunnel (for a mobile IP session). However, in some application scenarios, some of the traffic is routed
to a specific system or a specific interface for additional service or processing. Through the Adult Content
Filtering (ACF) capability, web traffic of some sessions can be routed to an ACF appliance that filters the
traffic based on the URL or content. The Flow-Based Redirect (FBR) feature enables applications such as
the ACF to route matching traffic to a specified next hop device.
The FBR feature is Virtual Routing and Forwarding (VRF)-aware. You can map an interface to a VRF or
transfer a VRF as long as the session and the interface connecting the next hop device are within the same
VRF network.
Finding Feature Information, page 79
•
Flow-Based Redirect for Adult Content Filtering, page 80
•
Flow-Based Redirect for Selective IP Traffic Offload, page 81
•
Activating and Deactivating the Flow-Based Redirect Feature Through Vendor-Specific Attributes,
•
page 82
Configuring Flow-Based Redirect for a Traffic Class Service, page 82
•
Examples, page 85
•
Best Practices for Configuring the NAT on the Cisco ASR 1000 Series Routers, page 87
•
NAT Overloading and Port Parity, page 88
•
NAT Interface Overloading with VRF, page 88
•
Additional References, page 89
•
Feature Information for Flow-Based Redirect, page 89
•
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.
Flow-Based Redirect for Adult Content Filtering
In a typical WiFi hotspot deployment, all subscriber traffic goes through Cisco ISG (Intelligent Service
Gateway) after successful authentication. For unauthenticated traffic, L4R feature offers a logic to redirect
traffic based on a pre-defined access-list (ACL). This L4R feature acts as a way to redirect some traffic to a
web portal or opengarden environment using a translation logic. In order to implement a similar redirection
logic after successful authentication without the need for translating the traffic, the flow based redirect has
been implemented in ISG to allow traffic to be redirected/rerouted. A typical use case is Adult Content Filtering
(ACF) where web traffic needs to be redirected to a Web Filtering Appliance.
You can apply the ACF policy to subscriber traffic in the following ways:
If the Wi-Fi hotspot provider allows individual subscribers to opt out of the ACF, the ACF policy is not
•
applied on their personal profile. For those subscribers who do not opt out of the ACF, the ACF policy
is applied on their personal profile through the RADIUS vendor-specific attribute (VSA) when they log
in to their account. For more information about RADIUS VSA attributes, see Activating and Deactivating
the Flow-Based Redirect Feature Through Vendor-Specific Attributes .
Flow-Based Redirect
If the Wi-Fi hotspot provider enforces ACF on all the subscribers accessing the internet from their site,
•
the ACF policy is configured in the local policy of the Cisco ISG.
The following figure shows a typical scenario where ACF is applied on Wi-Fi hotspots.
Figure 8: Adult Content Filtering on Wi-Fi Hotspots
Flow-Based Redirect for Selective IP Traffic Offload
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.
Note
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.
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
Activating and Deactivating the Flow-Based Redirect Feature Through Vendor-Specific Attributes
Activating and Deactivating the Flow-Based Redirect Feature
Through Vendor-Specific Attributes
You can provision or activate a traffic class service with the Flow-Based Redirect feature by adding the
following vendor-specific attribute (VSA) in the user profile of the RADIUS server:
vsa cisco 250 ACF_SERVICE
You can activate a traffic class service with the Flow-Based Redirect feature for an established session through
the RADIUS Change of Authorization (CoA) feature, using the following VSAs:
vsa cisco 250 S<sessionID>
vsa cisco generic 1 string "subscriber:command=activate-service"
vsa cisco generic 1 string "subscriber:service-name=ACF_SERVICE”
You can deactivate a traffic class service with the Flow-Based Redirect feature for an established session
through the RADIUS CoA feature, using the following VSAs:
vsa cisco 250 S<sessionID>
vsa cisco generic 1 string "subscriber:command=deactivate-service"
vsa cisco generic 1 string "subscriber:service-name=ACF_SERVICE”
Configuring Flow-Based Redirect for a Traffic Class Service
The following steps show how to configure the Flow-Based Redirect feature for a traffic class service.
SUMMARY STEPS
enable
1.
configure terminal
2.
ip access-list extended traffic class
3.
permit tcp source_IP destination_IP eq port
4.
class-map type traffic match-any traffic class map
5.
match access-group input name traffic class
6.
policy-map type service policy-map name
7.
class type traffic traffic class map
8.
reroute to next-hop ip IP address
9.
policy-map type control policy-map name
10.
class type control always event account-logon
11.
20 service-policy type service name service-policy name
12.
class type control always event service-stop
13.
1 service-policy type service unapply identifier service-name
14.
class type control always event service-start
15.
10 service-policy type service identifier service-name
Configuring Flow-Based Redirect for a Traffic Class Service
The following sample output shows how a traffic class service with the Flow-Based Redirect feature is
configured to redirect all HTTP traffic to a different next hop device upon logging in to the account:
Router# configure terminal
Router (config)# ip access-list extended WEB_ACL_IN
Router (config-ext-nacl)# permit tcp any any eq www
Router (config-ext-nacl)# permit tcp any any eq www
Router (config-ext-nacl)# class-map type traffic match-any ACF_ACL
Router (config-traffic-classmap)# match access-group input name WEB_ACL_IN
Router (config-traffic-classmap)# policy-map type service ACF_SERVICE
Router (config-service-policymap)# class type traffic ACF_ACL
Router (config-service-policymap-class-traffic)# reroute to next-hop ip 44.0.0.22
Router (config-control-policymap-class-control)# policy-map type control INTERNET_SERVICE_RULE
Router (config-control-policymap)# class type control always event account-logon
Router (config-control-policymap-class-control)# 20 service-policy type service name
ACF_SERVICE
Router (config-control-policymap-class-control)# class type control always event service-stop
Router (config-control-policymap-class-control)# 1 service-policy type service unapply
identifier service-name
Router (config-control-policymap)# class type control always event service-start
Router (config-control-policymap-class-control)# 10 service-policy type service identifier
service-name
Router (config-control-policymap)# class type control always event account-logoff
Router (config-control-policymap-class-control)# 10 service disconnect delay 5
Viewing the FBR Policy that is Attached to a Session
To view the FBR policy that is attached to a session at session start, use the show subscriber session uid uid
command:
Authentication status: authen
Active services associated with session:
name "ACF_SERVICE", applied before account logon
Rules, actions and conditions executed:
subscriber rule-map INTERNET_SERVICE_RULE
condition always event session-start
80 authorize identifier source-ip-address
subscriber rule-map default-internal-rule
condition always event service-start
1 service-policy type service identifier service-name
Classifiers:
Class-idDirPacketsBytesPri. Definition
0In499319360Match Any
1Out000Match Any
56In499319360Match ACL WEB_ACL_IN
57Out000Match ACL WEB_ACL_OUT
Configuration Sources:
Type Active Time AAA Service ID Name
SVC00:01:43-ACF_SERVICE
USR00:01:43-Peruser
INT00:01:43-GigabitEthernet0/0/4
Verifying the Packet Count Status
To verify whether the packet count on the interface that is connected to the next hop device is increasing, use
the show interface interface connected to the next hop device command:
Router(config)# show interface GigabitEthernet0/0/5
GigabitEthernet0/0/5 is up, line protocol is up
Hardware is SPA-8X1GE-V2, address is 0021.d81a.d305 (bia 0021.d81a.d305)
Description: IXIA_Client_Facing
Internet address is 44.0.0.1/24
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not supported
Full Duplex, 1000Mbps, link type is auto, media type is SX
output flow-control is on, input flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:05:03, output 00:05:03, output hang never
Last clearing of "show interface" counters 00:06:48
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 12000 bits/sec, 20 packets/sec
0 output buffer failures, 0 output buffers swapped out
Viewing Statistics of Dropped Packets
To display the statistics of all the dropped packets on the Embedded Services Processor (ESP), use the show
platform hardware qfp active statistics drop command.
Note
As per FBR behavior, the ISG drops packets if next hop is unreachable. The show platform hardware
qfp active statistics drop command output shows counters for the dropped packets.
Router# Show platform hardware qfp active statistics drop
------------------------------------------------------------------------Global Drop StatsPacketsOctets
Best Practices for Configuring the NAT on the Cisco ASR 1000 Series Routers
Configuring NAT Access Interface for Ingress Traffic
interface GigabitEthernet0/0/4
ip address 36.0.0.1 255.255.255.0
ip nat inside
negotiation auto
ipv6 address FE80::200:5EFF:FE00:5213 link-local
service-policy type control PREMS
ip subscriber l2-connected
initiator unclassified mac-address
initiator dhcp
!
Configuring NAT Network Interface for Egress Traffic
interface GigabitEthernet1/2/4
description IXIA_port_for_offload
ip address 44.0.0.1 255.255.255.0
ip nat outside
load-interval 30
negotiation auto
ipv6 address 44::1/60
!
Enabling Carrier Grade NAT
ip nat settings mode cgn
no ip nat settings support mapping outside
ip nat pool natpool 55.0.0.3 55.0.255.250 netmask 255.255.0.0
ip nat inside source list 100 pool natpool overload
Best Practices for Configuring the NAT on the Cisco ASR 1000
Series Routers
The following are the recommended best practices to configure the NAT on the Cisco ASR 1000 Series
Aggregation Services Routers:
Restriction on the total QFP DRAM usage
•
At 97 percent DRAM utilization, depletion messages are displayed in the syslog as a warning message
to make the operator aware of low QFP DRAM availability. We recommend that you configure QFP
DRAM CAC in the system to avoid any unexpected behavior. The Call Admission Control (CAC)
functionality ensures that new subscriber sessions cannot be established when QFP DRAM utilization
exceeds the configured threshold.
The configuration example below demonstrates configuration of a QFP DRAM threshold set to 95
percent:
platform subscriber cac mem qfp 95.
Set the maximum limit for total number of NAT translations:
The ip nat translation max-entries all-host command can be used in scenarios where the Cisco ASR
•
1000 Series Router acting as ISG, performs NAT on all or most of the subscriber traffic. This helps the
operator to prevent a single host from occupying the entire translation table, while allowing a reasonable
upper limit to each host.
The maximum number of translations per host can be configured using either of these ways:
•
Ensure that you keep the translations timeout low, around 2 minutes for TCP, and 1 minute for UDP
•
translations:
Flow-Based Redirect
Configuring the same number of maximum translation entries for all the subscribers using the
◦
following command:
ip nat translation max-entries all-host maximum number of NAT entries for each host
Configuring the maximum translation entries for a given subscriber using the following command:
◦
ip nat translation max-entries host ip-address [per-host NAT entry limit]
ip nat translation timeout 120
◦
ip nat translation tcp-timeout 120
◦
ip nat translation udp-timeout 60
◦
NAT Overloading and Port Parity
You can preserve the addresses in the global address pool by allowing a device to use one global address for
many local addresses. This type of NAT configuration is called overloading.
When an Interface IP is overloaded for the translations and a single IP address is used for all the expected
translations, a maximum of 60,000 translations can be achieved with this configuration depending on the
traffic ports and the port parity involved. You can use the NAT Pool Overload configuration to achieve
maximum translations.
There is a concept of port parity (even/odd) in NAT and NAT64. If a source port is in the port range of 0 to
1023, it is translated between ports 512 to 1023. If a source port range is more than 1023, it takes ports from
1024 onwards.
NAT Interface Overloading with VRF
The NAT Interface Overloading with VRF scenario assumes that the service provider is only interested in
performing application-specific NAT, for example, the service provider perform NAT only on the DNS
requests from clients and the rest of the traffic will proceed as it is. Therefore, we can use Interface Overloading
instead of a pool. With this, we can have a maximum of 60000 translations per interface, which is deemed
good for the application-specific NAT. Also, the IP sessions and NAT are in a VRF (named
PROVIDER_WIFI_01, in the example below).
Cisco IOS Master Commands List, All ReleasesCisco IOS commands
iWAG commands
MIBs
No new or modified MIBs are supported by this
feature.
Technical Assistance
The Cisco Support website provides extensive online
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a Cisco.com user ID and password.
To locate and download MIBs for selected platforms,
Cisco software releases, and feature sets, use Cisco
MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
LinkDescription
http://www.cisco.com/cisco/web/support/index.html
Feature Information for Flow-Based Redirect
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
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.
Table 11: Feature Information for Flow-Based Redirect
Feature InformationReleasesFeature Name
Cisco IOS XE Release 3.11Flow-Based Redirect
Flow-Based Redirect (FBR) feature
enables Adult Content Filtering
(ACF) to route matching traffic to
a specified next hop device.
Cisco IOS XE Release 3.12Flow-Based Redirect for Selective
IP Traffic Offload
Flow-Based Redirect (FBR) feature
enables Selective IP Traffic
Offload (SIPTO) to route matching
traffic to a specified next hop
device.
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)
This chapter provides various call flows for simple IP users.
Finding Feature Information, page 91
•
Simple IP Unclassified MAC Authentication (MAC TAL and Web Login) Call Flows, page 91
•
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.
CHAPTER 11
Simple IP Unclassified MAC Authentication (MAC TAL and Web
Login) Call Flows
The MAC Transparent Auto Login (TAL) authentication method is associated with the web authentication
method and is prevalent in public access control as used in public wireless LAN (PWLAN) applications or
in limited usage as in broadband residential access. Here, many sessions are aggregated on a single VLAN
or interface at the broadband remote access server (BRAS), and individual sessions are identified based on
the source MAC address for the Layer 2 access subscriber.
MAC TAL enables the iWAG to authorize a subscriber on the basis of the subscriber’s source MAC address.
After authentication, the iWAG applies the auto-login services on the session and the subscriber will be able
to access the service. If the initial authorization based on the MAC address fails, then the iWAG subscriber
is redirected to the ISP’s web portal, where the subscriber enters the ISP-assigned credentials (username and
password) to complete the authentication in order to avail the ISP’s services. The iWAG then applies the
services that the subscriber selected from the portal, and provides the subscriber full access to those services.