- Overview of ISG
- Configuring ISG Control Policies
- Configuring ISG Access for PPP Sessions
- Configuring ISG Access for IP Subscriber Sessions
- Configuring ISG IPv6 Support
- Configuring MQC Support for IP Sessions
- Configuring ISG Port-Bundle Host Key
- Configuring ISG as a RADIUS Proxy
- Configuring ISG as a RADIUS Proxy in Passthrough Mode
- ISG RADIUS Proxy Support for Mobile Users—Hotspot Roaming and Accounting Start Filtering
- Walk-By User Support in ISG
- ISG L2 Subscriber Roaming
- Configuring RADIUS-Based Policing
- ISG Dynamic VLAN Interface Provisioning
- Ambiguous VLAN Support for IP sessions over ISG
- Configuring ISG Policies for Automatic Subscriber Logon
- Configuring DHCP Option 60 and Option 82 with VPN-ID Support for Transparent Automatic Logon
- Enabling ISG to Interact with External Policy Servers
- Configuring ISG Subscriber Services
- Configuring ISG Network Forwarding Policies
- Configuring ISG Accounting
- Configuring ISG Support for Prepaid Billing
- Configuring ISG Policies for Session Maintenance
- Redirecting Subscriber Traffic Using ISG Layer 4 Redirect
- Configuring Layer 4 Redirect Logging
- Configuring ISG Policies for Regulating Network Access
- Configuring ISG Integration with SCE
- Service Gateway Interface
- ISG MIB
- ISG SSO and ISSU
- ISG Debuggability
- Troubleshooting ISG with Session Monitoring and Distributed Conditional Debugging
- Configuring ISG Troubleshooting Enhancements
- Index
- Finding Feature Information
- Prerequisites for Dual-Stack Support for Simple IP Subscriber Sessions
- Restrictions for Dual Stack Support for Simple IP Subscriber Sessions
- Information About Dual Stack Support for Simple IP Subscriber Sessions
- How to Configure Dual Stack Support for Simple IP Subscriber Sessions
- Configuration Examples for Dual Stack Support for Simple IP Subscriber Sessions
- Additional References
- Feature Information for Dual Stack Support for Simple IP Subscriber Sessions
Dual-Stack Support for Simple IP Subscriber Sessions
The Dual-Stack Support for Simple IP Subscriber Sessions feature enables L2-connected, dual-stack IP over Ethernet (IPoE) sessions to be provisioned on the Cisco Intelligent Services Gateway (ISG). This module describes how to configure ISG to support IPv6 L2-connected sessions and dual-stack IP sessions.
- Finding Feature Information
- Prerequisites for Dual-Stack Support for Simple IP Subscriber Sessions
- Restrictions for Dual Stack Support for Simple IP Subscriber Sessions
- Information About Dual Stack Support for Simple IP Subscriber Sessions
- How to Configure Dual Stack Support for Simple IP Subscriber Sessions
- Configuration Examples for Dual Stack Support for Simple IP Subscriber Sessions
- Additional References
- Feature Information for Dual Stack Support for Simple IP Subscriber Sessions
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.
Prerequisites for Dual-Stack Support for Simple IP Subscriber Sessions
- The subscriber must be Layer 2-connected.
- The web or portal server should be a dual-stack host.
- The ipv6 unicast-routing command needs to be enabled on the ISG to enable dual-stack sessions.
- Either the IPv6 pool has to be configured in the ISG or the framed IPv6 prefix needs to be downloaded from RADIUS.
- The ISG has to be configured with the respective TCs or services to ensure proper web or portal access.
- You should be familiar with the concepts and tasks described in the “Configuring ISG Control Policies” module.
Restrictions for Dual Stack Support for Simple IP Subscriber Sessions
- EoGRE or walkby is not supported for dual stack.
- WebAuth is supported only on IPv4.
- The IPv6 local pool cannot be associated to a VRF. So, the address space is defined globally. This requires that the IPv6 address is not defined under the multi-service interface associated to a VRF. Also, non-VRF subscribers get the IPv6 prefix from the IPv6 pool defined for VRF subscribers. So, an IPv6 pool name has to be specified as a mandatory parameter in the auth profile as well as for unauth clients and radius-timeout scenarios.
- IPv6 prefix assigned via an auth profile should not overlap with that of a locally defined IPv6 pool. If the IPv6 prefix from local pool is assigned via an auth profile, ISG does not consider it as assigned. This may lead to the same prefix being allocated to another subscriber.
- The VRF service has to be defined in AAA or RADIUS only as it cannot be defined locally in ISG and assigned via a service-policy map.
- PBHK is not supported for IPv6 traffic. So, the IPv6 VRF client cannot access the portal in the global domain.
- DNS info cannot be sent to a VRF client using the DHCPv6 server in ISG.
- Dual stack session information cannot be queried through SNMP.
- Overlapping address spaces are supported only for DHCP-initiated-VRF sessions and not for unclassified-MAC-VRF sessions.
- The DHCP session restart does not work for VRF sessions with DHCP RENEW.
- Data traffic is dropped when the access and service VRFs are different.
- Each dual stack session supports up to a maximum of 3 traffic classes.
Information About Dual Stack Support for Simple IP Subscriber Sessions
Features supporting Dual Stack simple IP sessions
The following ISG features support dual stack implementation:
How to Configure Dual Stack Support for Simple IP Subscriber Sessions
Configuring Dual Stack Support on ISG
Dual stack can be configured in ISG for both MAC TAL and WebAuth subscribers.
To configure dual stack for MAC TAL users, perform the following actions:
To configure dual stack for WebAuth users, perform the following actions:
Verifying Dual Stack Support on ISG
To verify the dual stack configuration on an ISG device, use any of the following show commands, in any order, in privileged EXEC mode.
1.
show subscriber session detail
2.
show ip subscriber detail
DETAILED STEPS
Verifying L2 Roaming on ISG
Use the show ip subscriber detail command to verify that the ISG subscriber has successfully roamed to a new interface. On comparing the outputs of this command before and after roaming, you will notice that UID and AAA UID remain the same even after the access interface is changed.
1. show ip subscriber detail (Before roaming)
2. show ip subscriber detail (After roaming)
DETAILED STEPS
Configuration Examples for Dual Stack Support for Simple IP Subscriber Sessions
Example: Configuring Simple IP Dual Stack with MAC TAL
#----------------------------- # Configure the IPv6 pool #----------------------------- ! access-list 101 permit ip host 22.22.22.1 any access-list 101 permit icmp host 22.22.22.1 any ipv6 route 2001:420:54FF:4::400:0/119 2001:420:54FF:4::400:1 ipv6 local pool FIRST 9999::/48 64 ---> To support ipv6 on the existing v4 box ipv6 local pool RED 6868::/48 64 ! ! ! #----------------------------- # Enable IPv6 on the interface #----------------------------- ! interface GigabitEthernet0/0/0 #Configuring the core interface ip address 9.27.52.4 255.255.0.0 ip portbundle outside negotiation auto ipv6 enable ! interface GigabitEthernet0/0/1 #Configuring the access interface ip unnumbered Loopback68 negotiation auto ipv6 enable service-policy type control START_WEB ip subscriber l2-connected initiator unclassified mac-address initiator dhcp !
Example: Configuring Simple IP Dual Stack with Web Auth
#----------------------------- # Configure the IPv6 pool #----------------------------- ! access-list 101 permit ip host 22.22.22.1 any access-list 101 permit icmp host 22.22.22.1 any ipv6 route 2001:420:54FF:4::400:0/119 2001:420:54FF:4::400:1 ipv6 local pool FIRST 9999::/48 64 ---> To support ipv6 on the existing v4 box ipv6 local pool RED 6868::/48 64 ! ! ! #----------------------------- # Enable IPv6 on the interface #----------------------------- ! interface GigabitEthernet0/0/0 #Configuring the core interface ip address 9.27.52.4 255.255.0.0 ip portbundle outside negotiation auto ipv6 enable ! interface GigabitEthernet0/0/1 #Configuring the access interface ip unnumbered Loopback68 negotiation auto ipv6 enable service-policy type control START_WEB ip subscriber l2-connected initiator unclassified mac-address initiator dhcp ! #----------------------------- # Configure policy #----------------------------- ! ipv6 access-list TCPv6 #Configuring IPv6 ACL permit tcp any any ! ipv6 access-list TCPv6_ALL permit tcp any any ! class-map type traffic match-any TCPv6 #Configuring the class map for IPv6 traffic match access-group input name TCPv6 match access-group output name TCPv6 ! class-map type traffic match-any TCPv4 match access-group input name TCPv4 match access-group output name TCPv4 ! policy-map type service L4Rv4 class type traffic TCPv4 redirect to ip 18.18.18.18 port 8080 ! ! policy-map type service L4Rv6 #Service definition for IPv6 class type traffic TCPv6 redirect to ip 1818::1818 port 80 ! ! policy-map type control START_WEB class type control UNAUTH_COND event timed-policy-expiry 10 service disconnect ! class type control always event session-start 8 service-policy type service name PBHK 9 authorize identifier mac-address 11 service-policy type service name L4Rv6 #Associating the service to the control policy 12 service-policy type service name L4Rv4 15 set-timer UNAUTH_TIMER 10 ! class type control always event session-restart 8 service-policy type service name PBHK 9 authorize identifier mac-address 11 service-policy type service name L4Rv6 12 service-policy type service name L4Rv4 15 set-timer UNAUTH_TIMER 10 ! class type control always event account-logon 2 authenticate aaa list List1 14 service-policy type service unapply name L4Rv6 15 service-policy type service unapply name L4Rv4 ! !
Additional References
Related Documents
|
Related Topic |
Document Title |
|---|---|
|
Cisco IOS commands |
|
|
ISG commands |
|
|
Dual stack for mobile IP subscriber sessions |
|
|
Call flows for dual stack mobile IP subscriber sessions |
|
|
ISG Access for IP Subscriber Sessions |
"Configuring ISG Access for IP Subscriber Sessions" module in the Intelligent Services Gateway Configuration Guide |
Standards and RFCs
| Standard/RFC | Title |
|---|---|
|
RFC 4241 |
A Model of IPv6/IPv4 Dual Stack |
Technical Assistance
| Description | Link |
|---|---|
|
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 Simple IP Subscriber 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.
|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
Dual Stack Support for Simple IP Subscriber Sessions |
Cisco IOS XE Release 3.11S |
The Dual Stack Support for Simple IP Subscriber Sessions enables L2-connected, dual-stack IP over Ethernet (IPoE) sessions to be provisioned on the Cisco Intelligent Services Gateway (ISG). The following command was modified: initiator unclassified mac-address. |
Feedback