Table Of Contents
Implementing ADSL for IPv6
Finding Feature Information
Contents
Prerequisites for Implementing ADSL for IPv6
Restrictions for Implementing ADSL for IPv6
Information About Implementing ADSL for IPv6
Address Assignment for IPv6
Stateless Address Autoconfiguration
Prefix Delegation
AAA over IPv6
RADIUS over IPv6
TACACS+ Over an IPv6 Transport
IPv6 Prefix Pools
Broadband IPv6 Counter Support at LNS
How to Configure ADSL in IPv6
Configuring the NAS
What to Do Next
Enabling the Sending of Accounting Start and Stop Messages
Forcing Release of Prefix Bindings
Configuring DHCP for IPv6 AAA Options
Configuring PPP IPv6 Accounting Delay Enhancements
Configuring TACACS+ over IPv6
Configuring the TACACS+ Server over IPv6
Specifying the Source Address in TACACS+ Packets
Configuring TACACS+ Server Group Options
Verifying Broadband IPv6 Counter Support at the LNS
Configuration Examples for Implementing ADSL for IPv6
Example: NAS Configuration
Example: RADIUS Configuration
Examples: Verifying Broadband IPv6 Counter Support at the LNS
Example: show l2tp session Command
Example: show l2tp tunnel Command
Example: show l2tun session Command
Example: show vpdn session Command
Example: show vpdn tunnel Command
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for Implementing ADSL for IPv6
Implementing ADSL for IPv6
First Published: November 25, 2009
Last Updated: March 30, 2011
This module describes the implementation of prefix pools, the authorization, authentication, and accounting (AAA) server, and per-user Remote Access Dial-In User Service (RADIUS) attributes in IPv6. It also describes the deployment of IPv6 in Digital Subscriber Line (DSL) and dial-access environments. Asymmetric Digital Subscriber Line (ADSL) provides the extensions that make large-scale access possible for IPv6 environments, including IPv6 RADIUS attributes, stateless address configuration on Point-to-Point Protocol (PPP) links, per-user static routes, and access control lists (ACLs).
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see 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 for Implementing ADSL for IPv6" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Implementing ADSL for IPv6
•
Restrictions for Implementing ADSL for IPv6
•
Information About Implementing ADSL for IPv6
•
How to Configure ADSL in IPv6
•
Configuration Examples for Implementing ADSL for IPv6
•
Additional References
•
Feature Information for Implementing ADSL for IPv6
Prerequisites for Implementing ADSL for IPv6
This document assumes that you are familiar with IPv4. Refer to the publications referenced in the "Additional References" section for IPv4 configuration and command reference information.
Restrictions for Implementing ADSL for IPv6
ADSL deployment is available for interfaces with PPP encapsulation enabled, including PPP over ATM (PPPoA), PPP over Ethernet (PPPoE, PPPoEoVLAN, PPPoEoQinQ) and PPPoEoA.
Information About Implementing ADSL for IPv6
•
Address Assignment for IPv6
•
AAA over IPv6
Address Assignment for IPv6
A Cisco router configured with IPv6 will advertise its IPv6 prefixes on one or more interfaces, allowing IPv6 clients to automatically configure their addresses. In IPv6, address assignment is performed at the network layer, in contrast to IPv4 where a number of functions are handled in the PPP layer. The only function handled in IPv6 Control Protocol is the negotiation of a unique interface identifier. Everything else, including DNS server discovery, is done within the IPv6 protocol itself.
In IPv6, ISPs assign long-lived prefixes to users, which has some impact on the routing system. In typical IPv4 environments, each network access server (NAS) has a pool of 24-bit addresses and users get addresses from this pool when dialing in. If a user dials another POP or is connected to another NAS at the same POP, a different IPv4 address is assigned.
Addresses for IPv6 are assigned by the following methods.
•
Stateless Address Autoconfiguration
•
Prefix Delegation
Stateless Address Autoconfiguration
Assigning addresses using the stateless address autoconfiguration method can only be used to assign 64-bit prefixes. Each user is assigned a 64-bit prefix, which is advertised to the user in a router advertisement (RA). All addresses are automatically configured based on the assigned prefix.
A typical scenario is to assign a separate 64-bit prefix per user; however, users can also be assigned a prefix from a shared pool of addresses. Using the shared limits addresses to only one address per user.
This solution works best for the cases where the customer provider edge router (CPE) is a single PC or is limited to only one subnet. If the user has multiple subnets, Layer 2 (L2) bridging, multilink subnets or proxy RA can be used. The prefix advertised in the RA can come from an authorization, authentication, and accounting (AAA) server, which also provides the prefix attribute, can be manually configured, or can be allocated from a prefix pool.
The Framed-Interface-Id AAA attribute influences the choice of interface identifier for peers and, in combination with the prefix, the complete IPv6 address can be determined.
Prefix Delegation
Prefix delegation uses Dynamic Host Configuration Protocol (DHCP). When the user requests a prefix from the prefix delegator, typically the NAS, the prefix is allocated as described in the "Stateless Address Autoconfiguration" section.
An IPv6 prefix delegating router selects IPv6 prefixes to be assigned to a requesting router upon receiving a request from the client. The delegating router might select prefixes for a requesting router in the following ways:
•
Static assignment based on subscription to an ISP
•
Dynamic assignment from a pool of available prefixes
•
Selection based on an external authority such as a RADIUS server using the Delegated-IPv6-Prefix attribute (see the "Delegated-IPv6-Prefix" section).
Contrary to IPv4 address assignment, an IPv6 user will be assigned a prefix, not a single address. Typically the Internet service provider (ISP) assigns a 64- or 48-bit prefix.
Accounting Start and Stop Messages
PPP calls a registry to allow DHCPv6 to append the delegated prefix information to accounting start and stop messages.
Forced Release of a Binding
The DHCPv6 server maintains an automatic binding table in memory to track the assignment of some configuration parameters, such as prefixes between the server and its clients. The automatic bindings can be stored permanently in the database agent, which can be, for example, a remote TFTP server or local NVRAM file system.
DHCPv6 invokes a routine when the virtual interface used by PPP terminates. This routine automatically releases any delegated prefix bindings associated with the PPP virtual interface that is being terminated.
When a PPP virtual interface terminates, the routine runs through the full table of DHCPv6 bindings checking for the matching interface. Because PPP uses a virtual interface, this subroutine clears any related lease information when the PPP connection terminates.
For further information about DHCPv6 bindings, see "Implementing DHCP for IPv6" in the Cisco IOS XE IPv6 Configuration Guide.
DHCP SIP Server Options
Two DHCP for IPv6 Session Initiation Protocol (SIP) server options describe a local outbound SIP proxy: one carries a list of domain names, the other a list of IPv6 addresses. These two options can be configured in a DHCPv6 configuration pool.
AAA over IPv6
Vendor-specific attributes (VSAs) have been developed to support AAA for IPv6. The Cisco VSAs are inacl, outacl, route, and prefix.
Prefix pools and pool names are configurable through AAA. Customers can deploy IPv6 RADIUS or the TACACS+ server to communicate with Cisco IOS routers.
AAA over IPv6 is described in the following sections:
•
RADIUS over IPv6
•
TACACS+ Over an IPv6 Transport
•
IPv6 Prefix Pools
RADIUS over IPv6
The following RADIUS attributes as described in RFC 3162 are supported for IPv6:
•
Framed-Interface-Id
•
Framed-IPv6-Prefix
•
Login-IPv6-Host
•
Framed-IPv6-Route
•
Framed-IPv6-Pool
These attributes can be configured on a RADIUS server and downloaded to access servers where they can be applied to access connections.
Prerequisites for Using AAA Attributes for IPv6
The AAA attributes for IPv6 are compliant with RFC 3162 and require a RADIUS server capable of supporting RFC 3162.
RADIUS Per-User Attributes for Virtual Access in IPv6 Environments
The following IPv6 attributes for RADIUS attribute-value (AV) pairs are supported for virtual access:
•
Delegated-IPv6-Prefix
•
Framed-Interface-Id
•
Framed-IPv6-Prefix
•
Login-IPv6-Host
•
Framed-IPv6-Route
•
Framed-IPv6-Pool
•
IPv6 Route
•
IPv6 ACL
•
IPv6 Prefix#
•
IPv6 Pool
Delegated-IPv6-Prefix
The Delegated-IPv6-Prefix attribute calls DHCPv6 to parse and store AAA attribute information. PPP sends the accounting start and stop messages for PPP sessions.
The following is an example of a Delegated-IPv6-Prefix attribute:
cisco-avpair = ipv6:delegated-prefix=2001:DB8::/64
Note
For Delegated-IPv6-Prefix attribute, Cisco VSA format is not supported. If you try add this attribute in the cisco-vsa format in the profile, the RADIUS server response fails. Use only the IETF attribute for Delegated-IPv6-Prefix.
Framed-Interface-Id
The Framed-Interface-Id attribute indicates the IPv6 interface identifier to be configured. This per-user attribute is used during the IPv6CP negotiations and may be used in access-accept packets. If the Interface-Identifier IPv6CP option has been successfully negotiated, this attribute must be included in an Acc-0Request packet as a hint by the NAS to the server that it would prefer that value.
Framed-IPv6-Prefix
The Framed-IPv6-Prefix attribute performs the same function as the Cisco VSA: It is used for virtual access only and indicates an IPv6 prefix (and corresponding route) to be configured. This attribute is a per-user attribute and lets the user specify which prefixes to advertise in Neighbor Discovery Router Advertisement messages. The Framed-IPv6-Prefix attribute may be used in access-accept packets and can appear multiple times. The NAS will create a corresponding route for the prefix.
To use this attribute for DHCP for IPv6 prefix delegation, create a profile for the same user on the RADIUS server. The user name associated with the second profile has the suffix "-dhcpv6."
The Framed-IPv6-Prefix attribute in the two profiles is treated differently. If a NAS needs both to send a prefix in router advertisements (RAs) and delegate a prefix to a remote user's network, the prefix for RA is placed in the Framed-IPv6-Prefix attribute in the user's regular profile, and the prefix used for prefix delegation is placed in the attribute in the user's separate profile.
Note
For Framed-IPv6-Prefix attribute, RADIUS IETF attribute and RADIUS Cisco VSA format are supported.
Login-IPv6-Host
The Login-IPv6-Host attribute is a per-user attribute that indicates the IPv6 system with which to connect the user when the Login-Service attribute is included.
Framed-IPv6-Route
The Framed-IPv6-Route attribute performs the same function as the Cisco VSA: It is a per-user attribute that provides routing information to be configured for the user on the NAS. This attribute is a string attribute and is specified using the ipv6 route command.
Framed-IPv6-Pool
The Framed-IPv6-Pool attribute is a per-user attribute that contains the name of an assigned pool that should be used to assign an IPv6 prefix for the user. This pool should either be defined locally on the router or defined on a RADIUS server from which pools can be downloaded.
IPv6_DNS_Servers
The IPv6_DNS_Servers attribute saves one or two DNS server addresses in the interface DHCPv6 subblock, and this information is returned to the DHCPv6 if it was made available in the AAA attribute information. Any information provided in this way will override anything configured in the DHCPv6 pool. This attribute will also be included into the returned attributes for AAA start and stop notifications.
IPv6 Route
The IPv6 route attribute allows you to specify a per-user static route. A static route is appropriate when the Cisco IOS XE software cannot dynamically build a route to the destination. See the description of the ipv6 route command for more information about building static routes.
The following example shows the IPv6 route attribute used to define a static route:
cisco-avpair = "ipv6:route#1=2001:DB8:cc00:1::/48",
cisco-avpair = "ipv6:route#2=2001:DB8:cc00:2::/48",
IPv6 ACL
You can specify a complete IPv6 access list. The unique name of the access list is generated automatically. The access list is removed when its user logs out. The previous access list on the interface is reapplied.
The inacl and outacl attributes allow you to a specific existing access list configured on the router. The following example shows ACL number 1 specified as the access list:
cisco-avpair = "ipv6:inacl#1=permit 2001:DB8:cc00:1::/48",
cisco-avpair = "ipv6:outacl#1=deny 2001:DB8::/10",
IPv6 Prefix#
The IPv6 prefix# attribute lets you indicate which prefixes to advertise in Neighbor Discovery Router Advertisement messages. When the prefix# attribute is used, a corresponding route (marked as a per-user static route) is installed in the routing information base (RIB) tables for the given prefix.
cisco-avpair = "ipv6:prefix#1=2001:DB8::/64",
cisco-avpair = "ipv6:prefix#2=2001:DB8::/64",
IPv6 Pool
For RADIUS authentication, the IPv6 pool attribute extends the IPv4 address pool attributed to support the IPv6 protocol. It specifies the name of a local pool on the NAS from which to get the prefix and is used whenever the service is configured as PPP and whenever the protocol is specified as IPv6. Note that the address pool works in conjunction with local pooling. It specifies the name of the local pool that has been preconfigured on the NAS.
PPP IPv6 Accounting Delay Enhancements
This feature enhances accounting records for dual-stack networks. It ensures that a unique IPv6 address is assigned to PPP IPv6 and IPv4 sessions for IP addresses that are received from RADIUS.
When this feature is enabled, it automatically creates a database to hold new incoming access-accept responses from RADIUS. The access-accept responses in this database are then checked for duplicates of a specific set of attributes. If the attributes are already present in the database, then the RADIUS server has already offered them to an existing session; therefore, the new session is immediately removed and a stop-record message sent. If none of the specific set of attributes are in the database, they are immediately added to the database, and the session proceeds normally. When the session is removed, the entries in the database are also removed.
The following RADIUS attributes are tracked in the database and checked at access-accept time:
•
Framed-IPv6-Prefix
•
Delegated-IPv6-Prefix
The attributes are available as standard RFC-defined binary format, or as Cisco VSAs. (The Delegated-IPv6-Prefix attribute currently does not have a VSA definition in AAA.)
TACACS+ Over an IPv6 Transport
An IPv6 server can be configured to use TACACS+. Both IPv6 and IPv4 servers can be configured to use TACACS+ using a name instead of an IPv4 or IPv6 address.
IPv6 Prefix Pools
The function of prefix pools in IPv6 is similar to that of address pools in IPv4. The main difference is that IPv6 assigns prefixes rather than single addresses.
As for IPv4, a pool or a pool definition can be configured locally or it can be retrieved from an AAA server. Overlapping membership between pools is not permitted.
Once a pool is configured, it cannot be changed. If you change the configuration, the pool will be removed and re-created. All prefixes previously allocated will be freed.
Prefix pools can be defined so that each user is allocated a 64-bit prefix or so that a single prefix is shared among several users. In a shared prefix pool, each user may receive only one address from the pool.
Broadband IPv6 Counter Support at LNS
This feature provides support for broadband PPP IPv6 sessions at the layer 2 tunneling protocol (L2TP) network server (LNS). The sessions are forwarded by L2TP access concentrator (LAC) using layer 2 tunneling protocol L2TP over IPv6.
This feature is enabled automatically when the user configures LNS and enables IPv6.
How to Configure ADSL in IPv6
•
Configuring the NAS
•
Enabling the Sending of Accounting Start and Stop Messages
•
Forcing Release of Prefix Bindings
•
Configuring DHCP for IPv6 AAA Options
•
Configuring PPP IPv6 Accounting Delay Enhancements
•
Configuring TACACS+ over IPv6
•
Verifying Broadband IPv6 Counter Support at the LNS
Configuring the NAS
Perform this task to configure the NAS to implement ADSL for IPv6 environments.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
hostname name
4.
aaa new-model
5.
aaa authentication ppp {default | list-name} method1 [method2...]
6.
aaa authorization {auth-proxy | cache | commands level | config-commands | configuration | console | exec | ipmobile | multicast | network | policy-if | prepaid | radius-prox | reverse-access | subscriber-service | template} {default | list-name} [method1 [method2...]]
7.
aaa accounting {auth-proxy | system | network | exec | connection | commands level | dot1x} {default | list-name | guarantee-first} [vrf vrf-name] {start-stop | stop-only | none} [broadcast] {radius | group group-name}
8.
aaa accounting send counters ipv6
9.
interface virtual-template number [type virtual-template-type]
10.
ip unnumbered type number
11.
ipv6 address autoconfig [default]
12.
no ipv6 nd ra suppress
13.
ppp authentication {protocol1 [protocol2...]} [if-needed] [list-name | default] [callin] [one-time] [optional]
14.
ppp accounting {default | listname}
15.
no snmp trap link-status [permit duplicates]
16.
no logging event link-status
17.
exit
18.
aaa group server radius group-name
19.
server-private ip-address [auth-port port-number | acct-port port-number] [non-standard] [timeout seconds] [retransmit retries] [key string]
20.
radius-server host {hostname | ip-address} [test username user-name] [auth-port port-number] [ignore-auth-port] [acct-port port-number] [ignore-acct-port] [timeout seconds] [retransmit retries] [key string] [alias {hostname | ip-address}] [idle-time minutes] [backoff exponential {backoff-retry number-of-retransmits | max-delay minutes}] [key encryption-key]
21.
radius-server vsa send [accounting [3gpp2] | authentication [3gpp2] | cisco-nas-port [3gpp2]]
22.
radius-server vsa send [accounting [3gpp2] | authentication [3gpp2] | cisco-nas-port [3gpp2]]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
hostname name
Example:
Router(config)# hostname hostname1
|
Specifies the host name for the network server.
|
Step 4
|
aaa new-model
Example:
Router(config)# aaa new-model
|
Enables the AAA server.
|
Step 5
|
aaa authentication ppp {default | list-name}
method1 [method2...]
Example:
Router(config)# aaa authentication ppp default
if-needed group radius
|
Specifies one or more AAA authentication methods for use on serial interfaces that are running PPP.
|
Step 6
|
aaa authorization {auth-proxy | cache |
commands level | config-commands |
configuration | console | exec | ipmobile |
multicast | network | policy-if | prepaid |
radius-proxy | reverse-access |
subscriber-service | template} {default |
list-name} [method1 [method2...]]
Example:
Router(config)# aaa authorization network
{default | list-name} [method1 [method2...]]
|
Sets parameters that restrict user access to a network.
|
Step 7
|
aaa accounting {auth-proxy | system | network |
exec | connection | commands level | dot1x}
{default | list-name | guarantee-first} [vrf
vrf-name] {start-stop | stop-only | none}
[broadcast] {radius | group group-name}
Example:
Router(config)# aaa accounting network {default
| list-name} start-stop group {radius | group
group-name}
|
Enables AAA accounting of requested services for billing or security purposes when you use RADIUS.
|
Step 8
|
aaa accounting send counters ipv6
Example:
Router(config)# aaa accounting send counters
ipv6
|
Sends IPv6 counters in the stop record to the accounting server.
|
Step 9
|
interface virtual-template number [type
virtual-template-type]
Example:
Router(config)# interface virtual-template 1
|
Creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces.
|
Step 10
|
ip unnumbered type number
Example:
Router(config-if)# ip unnumbered loopback
interface1
|
Enables IP processing on an interface without assigning an explicit IP address to the interface.
|
Step 11
|
ipv6 address autoconfig [default]
Example:
Router(config-if)# ipv6 address autoconfig
|
Enables automatic configuration of IPv6 addresses using stateless autoconfiguration on an interface and enable IPv6 processing on the interface.
|
Step 12
|
no ipv6 nd ra suppress
Example:
Router(config-if)# no ipv6 nd ra suppress
|
Allows IPv6 router advertisement transmissions on a LAN interface.
|
Step 13
|
ppp authentication {protocol1 [protocol2...]}
[if-needed] [list-name | default] [callin]
[one-time] [optional]
Example:
Router(config-if)# ppp authentication chap
|
Enables at least one PPP authentication protocol and to specify the order in which the protocols are selected on the interface.
|
Step 14
|
ppp accounting {default | listname}
Example:
Router(config-if)# ppp accounting list1
|
Enables AAA services on the selected interface.
|
Step 15
|
no snmp trap link-status [permit duplicates]
Example:
Router(config-if)# no snmp trap link-status
|
Disables SNMP link traps.
|
Step 16
|
no logging event link-status
Example:
Router(config-if)# no logging event link-status
|
Disables link-status event messaging.
|
Step 17
|
exit
Example:
Router(config-if)# exit
|
Exits interface configuration mode, and places the router into global configuration mode.
|
Step 18
|
aaa group server radius group-name
Example:
Router(config)# aaa group service radius group1
|
Groups different RADIUS server hosts into distinct lists and distinct methods.
|
Step 19
|
server-private ip-address [auth-port
port-number | acct-port port-number]
[non-standard] [timeout seconds] [retransmit
retries] [key string]
Example:
Router(config)# server-private 10.1.1.1
timeout 5 retransmit 3 key xyz
|
Configures the IP address of the private RADIUS server for the group server.
|
Step 20
|
radius-server host {hostname | ip-address}
[test username user-name] [auth-port
port-number] [ignore-auth-port] [acct-port
port-number] [ignore-acct-port] [timeout
seconds] [retransmit retries] [key string]
[alias {hostname | ip-address}] [idle-time
minutes] [backoff exponential {backoff-retry
number-of-retransmits | max-delay minutes}]
[key encryption-key]
Example:
Router(config)# radius-server host 192.0.2.176
test username test1 auth-port 1645 acct-port
1646
|
Specifies a RADIUS server host.
|
Step 21
|
radius-server vsa send [accounting [3gpp2] |
authentication [3gpp2] | cisco-nas-port
[3gpp2]]
Example:
Router(config)# radius-server vsa send
accounting
|
Configures the NAS to recognize and use VSAs such as accounting.
|
Step 22
|
radius-server vsa send [accounting [3gpp2] |
authentication [3gpp2] | cisco-nas-port
[3gpp2]]
Example:
Router(config)# radius-server vsa send
authentication
|
Configures the NAS to recognize and use VSAs such as authentication.
|
What to Do Next
Once you have configured the NAS router, configure RADIUS to establish the AV pairs for callback. Callback allows remote network users to dial in to the NAS without being charged. When callback is required, the NAS hangs up the current call and dials the caller back. When the NAS performs the callback, only information for the outgoing connection is applied. The rest of the attributes from the preauthentication access-accept message are discarded.
The following example shows a RADIUS profile configuration for a local campus:
campus1 Auth-Type = Local, Password = "mypassword"
User-Service-Type = Framed-User,
cisco-avpair = "ipv6:inacl#1=permit dead::/64 any",
cisco-avpair = "ipv6:route=dead::/64",
cisco-avpair = "ipv6:route=cafe::/64",
cisco-avpair = "ipv6:prefix=dead::/64 0 0 onlink autoconfig",
cisco-avpair = "ipv6:prefix=cafe::/64 0 0 onlink autoconfig",
cisco-avpair = "ip:route=10.0.0.0 255.0.0.0",
The RADIUS AV pairs for IPv6 are described in RADIUS Per-User Attributes for Virtual Access in IPv6 Environments.
Enabling the Sending of Accounting Start and Stop Messages
Perform this task to allow the router to send accounting start and stop messages.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ipv6 dhcp pool poolname
4.
accounting mlist
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
ipv6 dhcp pool poolname
Example:
Router(config)# ipv6 dhcp pool pool1
|
Configures a DHCP for IPv6 configuration information pool and enters DHCP for IPv6 pool configuration mode.
|
Step 4
|
accounting mlist
Example:
Router(config-dhcp)# accounting list1
|
Enables accounting start and stop messages to be sent.
|
Forcing Release of Prefix Bindings
Perform this task to release any delegated prefix bindings associated with the PPP virtual interface that is being terminated.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
ipv6 dhcp bindings track ppp
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
interface type number
Example:
Router(config)# interface VirtualAccess2.2
|
Specifies an interface type and number, and places the router in interface configuration mode.
|
Step 4
|
ipv6 dhcp bindings track ppp
Example:
Router(config-if)# ipv6 dhcp bindings track ppp
|
Releases any delegated prefix leases associated with the PPP virtual interface that is being terminated.
|
Configuring DHCP for IPv6 AAA Options
Perform this task for configure DHCPv6 AAA options.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ipv6 dhcp pool poolname
4.
prefix-delegation aaa [method-list method-list] [lifetime]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
ipv6 dhcp pool poolname
Example:
Router(config)# ipv6 dhcp pool pool1
|
Configures a DHCP for IPv6 configuration information pool and enters DHCP for IPv6 pool configuration mode.
|
Step 4
|
prefix-delegation aaa [method-list method-list]
[lifetime]
Example:
Router(config-dhcp)# prefix-delegation aaa
method-list list1
|
Specifies that prefixes are to be acquired from AAA servers.
|
Configuring PPP IPv6 Accounting Delay Enhancements
Perform this task to configure PPP IPv6 accounting delay enhancements.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ppp unique address access-accept
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
ppp unique address access-accept
Example:
Router(config)# ppp unique address
access-accept
|
Tracks duplicate addresses received from RADIUS and creates a standalone database.
|
Configuring TACACS+ over IPv6
Perform these tasks to configure TACACS+ over IPv6:
•
Configuring the TACACS+ Server over IPv6
•
Specifying the Source Address in TACACS+ Packets
•
Configuring TACACS+ Server Group Options
Configuring the TACACS+ Server over IPv6
Perform this task to configure to TACACS+ server over IPv6.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
tacacs server name
4.
address ipv6 ipv6-address
5.
key [0 | 7] key-string
6.
port [number]
7.
send-nat-address
8.
single-connection
9.
timeout seconds
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
tacacs server name
Example:
Router(config)# tacacs server server1
|
Configures the TACACS+ server for IPv6 or IPv4 and enter TACACS+ server configuration mode.
|
Step 4
|
address ipv6 ipv6-address
Example:
Router(config-server-tacacs)# address ipv6
2001:DB8:3333:4::5
|
Configures the IPv6 address of the TACACS+ server.
|
Step 5
|
key [0 | 7] key-string
Example:
Router(config-server-tacacs)# key 0 key1
|
Configures the per-server encryption key on the TACACS+ server.
|
Step 6
|
port [number]
Example:
Router(config-server-tacacs)# port 12
|
Specifies the TCP port to be used for TACACS+ connections.
|
Step 7
|
send-nat-address
Example:
Router(config-server-tacacs)# send-nat-address
|
Sends a client's post-NAT address to the TACACS+ server.
|
Step 8
|
single-connection
Example:
Router(config-server-tacacs)# single-connection
|
Enables all TACACS packets to be sent to the same server using a single TCP connection.
|
Step 9
|
timeout seconds
Example:
Router(config-server-tacacs)# timeout 10
|
Configures the time to wait for a reply from the specified TACACS server.
|
Specifying the Source Address in TACACS+ Packets
Perform this task to specify the source address in TACACS+ packets.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ipv6 tacacs source-interface interface
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
ipv6 tacacs source-interface interface
Example:
Router(config)# ipv6 tacacs source-interface
GigabitEthernet 0/0/0
|
Specifies an interface to use for the source address in TACACS packets.
|
Configuring TACACS+ Server Group Options
Perform this task to configure TACACS+ server group options.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
aaa group server tacacs+ group-name
4.
server name server-name
5.
server-private {ip-address | name | ipv6-address} [nat] [single-connection] [port port-number] [timeout seconds] [key [0 | 7] string]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
aaa group server tacacs+ group-name
Example:
Router(config)# aaa group server tacacs+ group1
|
Groups different TACACS+ server hosts into distinct lists and distinct methods.
|
Step 4
|
server name server-name
Example:
Router(config-sg-tacacs+)# server name server1
|
Specifies an IPv6 TACACS+ server.
|
Step 5
|
server-private {ip-address | name |
ipv6-address} [nat] [single-connection] [port
port-number] [timeout seconds] [key [0 | 7]
string]
Example:
Router(config-sg-tacacs+)# server-private
2001:DB8:3333:4::5 port 19 key key1
|
Configures the IPv6 address of the private TACACS+ server for the group server.
|
Verifying Broadband IPv6 Counter Support at the LNS
This feature is enabled automatically when the user configures LNS and enables IPv6. To verify information about this feature, you can use any or all of the following optional commands as needed.
SUMMARY STEPS
1.
enable
2.
show l2tp session [all | packets [ipv6] | sequence | state | [brief | circuit | interworking] [hostname]] [ip-addr ip-addr [vcid vcid] | tunnel {id local-tunnel-id local-session-id | remote-name remote-tunnel-name local-tunnel-name} | username username | vcid vcid]
3.
show l2tp tunnel [all | packets [ipv6] | state | summary | transport] [id local-tunnel-id | local-name local-tunnel-name remote-tunnel-name | remote-name remote-tunnel-name local-tunnel-name]
4.
show l2tun session [l2tp | pptp] [all [filter] | brief [filter] [hostname] | circuit [filter] [hostname] | interworking [filter] [hostname] | packets [ipv6] [filter] | sequence [filter] | state [filter]]
5.
show vpdn session [l2f | l2tp | pptp] [all | packets [ipv6] | sequence | state [filter]]
6.
show vpdn tunnel [l2f | l2tp | pptp] [all [filter] | packets [ipv6] [filter] | state [filter] | summary [filter] | transport [filter]]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
show l2tp session [all | packets [ipv6] |
sequence | state | [brief | circuit |
interworking] [hostname]] [ip-addr ip-addr
[vcid vcid] | tunnel {id local-tunnel-id
local-session-id | remote-name
remote-tunnel-name local-tunnel-name} |
username username | vcid vcid]
Example:
Router# show l2tp session packets ipv6
|
Displays information about L2TP sessions.
|
Step 3
|
show l2tp tunnel [all | packets [ipv6] | state
| summary | transport] [id local-tunnel-id |
local-name local-tunnel-name remote-tunnel-name
| remote-name remote-tunnel-name
local-tunnel-name]
Example:
Router# show l2tp tunnel packets ipv6
|
Displays details about L2TP tunnels.
|
Step 4
|
show l2tun session [l2tp | pptp] [all [filter]
| brief [filter] [hostname] | circuit [filter]
[hostname] | interworking [filter] [hostname] |
packets [ipv6] [filter] | sequence [filter] |
state [filter]]
Example:
Router# show l2tun session packets ipv6
|
Displays the current state of Layer 2 sessions and protocol information about L2TP control channels.
|
Step 5
|
show vpdn session [l2f | l2tp | pptp] [all |
packets [ipv6] | sequence | state [filter]]
Example:
Router# show vpdn session packets ipv6
|
Displays session information about active Layer 2 sessions for a virtual private dialup network (VPDN).
|
Step 6
|
show vpdn tunnel [l2f | l2tp | pptp] [all
[filter] | packets [ipv6] [filter] | state
[filter] | summary [filter] | transport
[filter]]
Example:
Router# show vpdn tunnel packets ipv6
|
Displays information about active Layer 2 tunnels for a VPDN.
|
Configuration Examples for Implementing ADSL for IPv6
•
Example: NAS Configuration
•
Example: RADIUS Configuration
•
Examples: Verifying Broadband IPv6 Counter Support at the LNS
Example: NAS Configuration
This configuration for the ISP NAS shows the configuration that supports access from the remote CE router.
aaa authentication ppp default if-needed group radius
aaa authorization network default
aaa accounting network default start-stop group radius
aaa accounting send counters ipv6
interface virtual-template 1
ip unnumbered loopback interface1
ipv6 address autoconfig
ppp accounting list1
no snmp trap link-status
no logging event link-status
aaa group service radius group1
server-private 10.1.1.1 timeout 5 retransmit 3 key xyz
radius-server host 192.0.2.176 test username test1 auth-port 1645 acct-port 1646
radius-server vsa send accounting
radius-server vsa send authentication
Example: RADIUS Configuration
This RADIUS configuration shows the definition of AV pairs to establish the static routes.
campus1 Auth-Type = Local, Password = "mypassword"
User-Service-Type = Framed-User,
cisco-avpair = "ipv6:inacl#1=permit dead::/64 any",
cisco-avpair = "ipv6:route=library::/64",
cisco-avpair = "ipv6:route=cafe::/64",
cisco-avpair = "ipv6:prefix=library::/64 0 0 onlink autoconfig",
cisco-avpair = "ipv6:prefix=cafe::/64 0 0 onlink autoconfig",
cisco-avpair = "ip:route=10.0.0.0 255.0.0.0",
Examples: Verifying Broadband IPv6 Counter Support at the LNS
•
Example: show l2tp session Command
•
Example: show l2tp tunnel Command
•
Example: show l2tun session Command
•
Example: show vpdn session Command
•
Example: show vpdn tunnel Command
Example: show l2tp session Command
The show l2tp session command used with the packets and ipv6 keywords displays information about IPv6 packets and byte counts in an L2TP session.
Router# show l2tp session packets ipv6
L2TP Session Information Total tunnels 1 sessions 1
LocID RemID TunID Pkts-In Pkts-Out Bytes-In Bytes-Out
16791 53352 27723 30301740 30301742 20159754280 20523375360
Example: show l2tp tunnel Command
The show l2tp tunnel command used with the packets and ipv6 keywords displays information about IPv6 packet statistics and byte counts in L2TP tunnels.
Router# show l2tp tunnel packets ipv6
L2TP Tunnel Information Total tunnels 1 sessions 1
LocTunID Pkts-In Pkts-Out Bytes-In Bytes-Out
27723 63060379 63060383 39400320490 40157045438
Example: show l2tun session Command
The show l2tun session command used with the packets and ipv6 keywords displays information about IPv6 packet statistics and byte counts in an L2TUN session.
Router# show l2tun session packets ipv6
L2TP Session Information Total tunnels 1 sessions 1
LocID RemID TunID Pkts-In Pkts-Out Bytes-In Bytes-Out
16791 53352 27723 31120707 31120708 21285014938 21658462236
Example: show vpdn session Command
The show vpdn session command used with the l2tp, packets, and ipv6 keywords displays session information about IPv6 packet statistics and byte counts in an active layer 2 session for a VPDN.
Router# show vpdn session l2tp packets ipv6
L2TP Session Information Total tunnels 1 sessions 1
LocID RemID TunID Pkts-In Pkts-Out Bytes-In Bytes-Out
16791 53352 27723 35215536 35215538 22616342688 23038929320
Example: show vpdn tunnel Command
The show vpdn tunnel command used with the l2tp, packets, and ipv6 keywords displays session information about IPv6 packet statistics and byte counts in an active layer 2 tunnel for a VPDN.
Router# show vpdn tunnel l2tp packets ipv6
L2TP Tunnel Information Total tunnels 1 sessions 1
LocTunID Pkts-In Pkts-Out Bytes-In Bytes-Out
27723 61422447 61422451 37149801922 37886871686
Additional References
Related Documents
Standards
Standards
|
Title
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
|
—
|
MIBs
MIBs
|
MIBs Link
|
None
|
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
|
RFCs
RFCs
|
Title
|
RFC 3162
|
RADIUS and IPv6
|
RFC 3177
|
IAB/IESG Recommendations on IPv6 Address
|
RFC 3319
|
Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiated Protocol (SIP) Servers
|
Technical Assistance
Description
|
Link
|
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.
|
http://www.cisco.com/cisco/web/support/index.html
|
Feature Information for Implementing ADSL for IPv6
Table 15 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 15 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.
Table 15 Feature Information for Implementing ADSL for IPv6
Feature Name
|
Releases
|
Feature Information
|
Enhanced IPv6 Features for ADSL and Dial Deployment
|
Cisco IOS XE Release 2.5
|
Several features were enhanced to enable IPv6 to use ADSL and dial deployment.
The following sections provide information about these features:
• Address Assignment for IPv6
• Stateless Address Autoconfiguration
• Configuring the NAS
|
AAA Support for Cisco VSA IPv6 Attributes
|
Cisco IOS XE Release 2.5
|
Vendor-specific attributes (VSAs) were developed to support AAA for IPv6.
The following section provides information about this feature:
• AAA over IPv6
|
IPv6 Access Services: PPPoE
|
Cisco IOS XE Release 2.5
|
ADSL and dial deployment is available for interfaces with PPP encapsulation enabled, including PPPoE.
The following sections provide information about this feature:
• Address Assignment for IPv6
• Configuring the NAS
|
AAA Support for RFC 3162 IPv6 RADIUS Attributes
|
Cisco IOS XE Release 2.5
|
The AAA attributes for IPv6 are compliant with RFC 3162 and require a RADIUS server capable of supporting RFC 3162.
The following sections provide information about these features:
• AAA over IPv6
• Prerequisites for Using AAA Attributes for IPv6
• RADIUS Per-User Attributes for Virtual Access in IPv6 Environments
• Configuring DHCP for IPv6 AAA Options
The following commands were modified by this feature: ipv6 dhcp pool, prefix-delegation aaa
|
DHCP - DHCPv6 Prefix Delegation RADIUS VSA
|
Cisco IOS XE Release 2.5
|
When the user requests a prefix from the prefix delegator, typically the NAS, the prefix is allocated using DHCPv6.
The following sections provide information about this feature:
• Prefix Delegation
|
PPP Enhancement for Broadband IPv6
|
Cisco IOS XE Release 2.5
|
The following sections provide information about this feature.
• Accounting Start and Stop Messages
• Forced Release of a Binding
• Delegated-IPv6-Prefix
• Enabling the Sending of Accounting Start and Stop Messages
• Forcing Release of Prefix Bindings
|
AAA Improvements for Broadband IPv6
|
Cisco IOS XE Release 2.5
|
The following sections provide information about this feature.
• Accounting Start and Stop Messages
• Forced Release of a Binding
• Delegated-IPv6-Prefix
• Enabling the Sending of Accounting Start and Stop Messages
• Forcing Release of Prefix Bindings
|
DHCP Enhancements to Support IPv6 Broadband Deployments
|
Cisco IOS XE Release 2.5
|
The following sections provide information about this feature.
• Accounting Start and Stop Messages
• Forced Release of a Binding
• Delegated-IPv6-Prefix
• Enabling the Sending of Accounting Start and Stop Messages
• Forcing Release of Prefix Bindings
|
PPPoA
|
Cisco IOS XE Release 3.3S
|
ADSL and dial deployment is available for interfaces with PPP encapsulation enabled, including PPPoA.
|
SSO - PPPoE IPv6
|
Cisco IOS XE Release 2.5
|
This feature is supported in Cisco IOS XE Release 2.5.
|
Broadband IPv6 Counter Support at LNS
|
Cisco IOS XE Release 2.6
|
This feature provides support for broadband PPP IPv6 sessions at the L2TP LNS. The sessions are forwarded by LAC using layer 2 tunneling protocol L2TP over IPv4.
The following sections provide information about this feature.
• Broadband IPv6 Counter Support at LNS
• Verifying Broadband IPv6 Counter Support at the LNS
The following commands were modified by this feature: show l2tp session, show l2tp tunnel, show l2tun session, show vpdn session, show vpdn tunnel.
|
PPP IPv6 Accounting Delay Enhancements
|
Cisco IOS XE Release 3.2S
|
This feature enhances accounting records for dual-stack networks. It ensures that a unique IPv6 address is assigned to PPP IPv6 and IPv4 sessions for IP addresses that are received from RADIUS.
The following sections provide information about this feature.
• PPP IPv6 Accounting Delay Enhancements
• Configuring PPP IPv6 Accounting Delay Enhancements
The following command was introduced by this feature: debug ppp unique address, ppp unique address access-accept
|
RADIUS over IPv6
|
Cisco IOS XE Release 3.2S
|
RADIUS over IPv6 is supported.
The following section provides information about this feature.
• RADIUS over IPv6
|
TACACS+ over IPv6
|
Cisco IOS XE Release 3.2S
|
TACACS+ over IPv6 is supported.
The following section provides information about this feature.
• TACACS+ Over an IPv6 Transport
• Configuring TACACS+ over IPv6
The following commands were introduced or modified by this feature: aaa group server tacacs+, address ipv6 (TACACS+), ipv6 tacacs source-interface, key (TACACS+), port (TACACS+), send-nat-address, server name (IPv6 TACACS+), server-private (TACACS+), single-connection, tacacs server, timeout (TACACS+).
|
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
© 2009-2011 Cisco Systems, Inc. All rights reserved.