|
Table Of Contents
Configuring the Physical Subscriber Line for RADIUS Access and Accounting
Prerequisites for Configuring the Physical Subscriber Line for RADIUS Access and Accounting
Information About Configuring the Physical Subscriber Line for RADIUS Access and Accounting
PPP over ATM and PPPoE over ATM NAS-Port Attribute Field Format
PPPoE over IEEE 802.1Q VLANs Format
How to Configure the Physical Subscriber Line for RADIUS Access and Accounting
Configuring the LAC for RADIUS Port Identification for PPP
Configuring the LNS for RADIUS Port Identification for PPP
Configuration Examples for Identifying the Physical Subscriber Line
RADIUS Port Identification for PPPoE over ATM: Example
RADIUS Port Identification for PPPoE over an 802.1Q VLAN: Example
LNS Configuration for RADIUS Port Identification for PPP: Example
Feature Information for Identifying the Physical Subscriber Line for RADIUS Access and Accounting
Configuring the Physical Subscriber Line for RADIUS Access and Accounting
First Published: May 2, 2005Last Updated: November 20, 2009Configuring a physical subscriber line for RADIUS Access and Accounting enables an L2TP access concentrator (LAC) and an L2TP network server (LNS) to forward RADIUS NAS-Port and NAS-Port-Type attribute values for PPP over ATM, PPPoE over ATM, and PPPoE over IEEE 802.1Q VLANs.
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 Identifying the Physical Subscriber Line for RADIUS Access and Accounting" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS 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 Configuring the Physical Subscriber Line for RADIUS Access and Accounting
•Information About Configuring the Physical Subscriber Line for RADIUS Access and Accounting
•How to Configure the Physical Subscriber Line for RADIUS Access and Accounting
•Configuration Examples for Identifying the Physical Subscriber Line
•Feature Information for Identifying the Physical Subscriber Line for RADIUS Access and Accounting
Prerequisites for Configuring the Physical Subscriber Line for RADIUS Access and Accounting
•RADIUS port identification for PPP requires the PPP extended NAS-Port format.
•You must perform the configuration procedures in the "Configuring RADIUS" chapter in the Cisco IOS Security Configuration Guide.
•You must perform the PPP over ATM configuration procedures in the "Providing Protocol Support for Broadband Access Aggregation of PPP over ATM Sessions" module.
•You must perform the PPPoE configuration procedures in the "Providing Protocol Support for Broadband Access Aggregation of PPPoE Sessions" module.
Note The PPP extended NAS-Port format increases the size of the NAS-Port attribute field to 32 bits and changes the NAS-Port attribute format to provide the RADIUS server with details about the ATM port, the virtual path identifier (VPI), the virtual channel identifier (VCI), and, for IEEE 802.1Q VLANs, the VLAN ID.
Information About Configuring the Physical Subscriber Line for RADIUS Access and Accounting
To configure the physical subscriber line for communication to the RADIUS server, you should understand the following concepts:
•PPP over ATM and PPPoE over ATM NAS-Port Attribute Field Format
•PPPoE over IEEE 802.1Q VLANs Format
PPP over ATM and PPPoE over ATM NAS-Port Attribute Field Format
For PPP over ATM and PPP over ATM, the PPP extended format enables the NAS-Port attribute field to provide details about the ATM interface, VPI, and VCI. Figure 1 shows the format of the NAS-Port attribute field when the PPP extended NAS-Port format is configured and PPPoA over ATM or PPPoE over ATM is being used.
Figure 1 Format of the NAS-Port Attribute Field for PPP over ATM and PPPoE over ATM
The interfaces, VPI, and VCI correspond to the interface and virtual circuit (VC) on which the ppp session entered the router.
Note For Cisco 6400 series routers, the interface, VPI, and VCI correspond to the interface and VC on which the session entered the Cisco 6400 node switch processor (NSP).
Figure 2 shows the format of the 8-bit interface field. For platforms that do not have slots or modules, the slot and module fields is 0.
Figure 2 Format of the Interface Field for PPP over ATM and PPPoE over ATM
The NAS-Port-Type value for PPP over ATM and PPPoE over ATM is 5, which is the value for virtual port types.
PPPoE over IEEE 802.1Q VLANs Format
For PPPoE over 802.1Q VLANs, the PPP extended format provides details about the interface and the VLAN ID. Figure 3 shows the format of the NAS-Port attribute field when the PPP extended NAS-Port format is configured and PPPoE over an IEEE 802.1Q VLAN is being used.
Figure 3 Format of the NAS-Port Attribute Field for PPPoE over 802.1Q VLANs
Figure 4 shows the format of the 8-bit interface field. For platforms that do not have slots or modules, the slot and module fields will be 0.
Figure 4 Format of the Interface Field for PPPoE over 802.1Q VLANs
The NAS-Port-Type value for PPPoE over 802.1Q VLANs is 15.
How to Configure the Physical Subscriber Line for RADIUS Access and Accounting
This section contains the following procedures:
•Configuring the LAC for RADIUS Port Identification for PPP (required)
•Configuring the LNS for RADIUS Port Identification for PPP (required)
Configuring the LAC for RADIUS Port Identification for PPP
Perform this task to configure the LAC for RADIUS port identification for PPP.
SUMMARY STEPS
1. enable
2. configure terminal
3. radius-server attribute nas-port format d
4. end
DETAILED STEPS
Configuring the LNS for RADIUS Port Identification for PPP
Perform this task to configure the LNS for RADIUS port identification for PPP.
Note In order for the LNS to forward PPP extended NAS-Port format values to the RADIUS server, both the LAC and the LNS must be Cisco routers running a Cisco IOS image that supports RADIUS port identification for PPP.
SUMMARY STEPS
1. enable
2. configure terminal
3. radius-server attribute nas-port format d
4. vpdn aaa attribute nas-port vpdn-nas
5. end
DETAILED STEPS
Configuration Examples for Identifying the Physical Subscriber Line
This section provides the following configuration examples:
•RADIUS Port Identification for PPPoE over ATM: Example
•RADIUS Port Identification for PPPoE over an 802.1Q VLAN: Example
•LNS Configuration for RADIUS Port Identification for PPP: Example
RADIUS Port Identification for PPPoE over ATM: Example
The following example shows the configuration of the PPP extended NAS-Port format on an LAC using PPPoE over ATM:
vpdn enable!vpdn-group 1request-dialinprotocol l2tpdomain vpn1
initiate-to ip 10.12.1.64 priority 1local name NAS1-1!virtual-template 1 pre-clone 20virtual-template 2 pre-clone 20!!bba-group pppoe vpn1virtual-template 1sessions per-vc limit 2sessions per-mac limit 1!!
interface ATM4/0.1 multipointpvc 1/33encapsulation aal5snapprotocol pppoe group vpn1!!aaa new-modelaaa authentication ppp default local group radiusaaa authorization network default local group radiusaaa accounting network default start-stop group radiusradius-server host 172.69.69.66 auth-port 1645 acct-port 1646radius-server retransmit 3radius-server attribute nas-port format dradius-server key rad123!
RADIUS Port Identification for PPPoE over an 802.1Q VLAN: Example
The following example shows the configuration of the PPP extended NAS-Port format on an LAC running PPPoE over an 802.1Q VLAN:
bba-group pppoe globalvirtual-template 1sessions max limit 8000sessions per-vc limit 8sessions per-mac limit 2
!bba-group pppoe vpn1virtual-template 1sessions per-vc limit 2sessions per-mac limit 1!bba-group pppoe vpn2virtual-template 2sessions per-vc limit 2sessions per-mac limit 1 !vc-class atm class-pppoe-globalprotocol pppoe! !interface FastEthernet2/0.2encapsulation dot1Q 2pppoe enable group vpn1!interface FastEthernet2/0.3encapsulation dot1Q 3pppoe enable group vpn2!aaa new-model
aaa authentication ppp default local group radiusaaa authorization network default local group radiusaaa accounting network default start-stop group radiusradius-server host 172.69.69.66 auth-port 1645 acct-port 1646radius-server retransmit 3radius-server attribute nas-port format dradius-server key rad123
LNS Configuration for RADIUS Port Identification for PPP: Example
In the following example, the LNS is configured to recognize and forward PPP extended NAS-Port format values to the RADIUS server. The PPP extended NAS-Port format must also be configured on the LAC for this configuration to be effective.
vpdn enableno vpdn logging!vpdn-group L2TP-tunnelaccept-dialinprotocol l2tpvirtual-template 1terminate-from hostname lac1local name lns1!!aaa new-modelaaa authentication ppp default local group radiusaaa authorization network default local group radiusaaa accounting network default start-stop group radiusradius-server host 172.79.79.76 auth-port 1645 acct-port 1646radius-server retransmit 3radius-server attribute nas-port format dradius-server key lns123!vpdn aaa attribute nas-port vpdn-nas
Additional References
The following sections provide references related to the Identifying the Physical Subscriber Line for RADIUS Access and Accounting feature.
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for Identifying the Physical Subscriber Line for RADIUS Access and Accounting
Table 1 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(1) or later releases appear in the table.
Not all commands may be available in your Cisco IOS software release. For details on when support for specific commands was introduced, see the command reference documents.
For information on a feature in this technology that is not documented here, see the "Configuring Broadband Access Aggregation Features Roadmap."
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS 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 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Table 1 Feature Information for Identifying the Physical Subscriber Line for RADIUS Access and Accounting
Feature Name Releases Feature InformationRADIUS Port Identification
12.2(1)
12.2(33)SRCConfiguring RADIUS port identification for PPP enables an L2TP access concentrator (LAC) and an L2TP network server (LNS) to identify and forward RADIUS NAS-Port and NAS-Port-type attribute values for PPP over ATM, PPPoE over ATM, and PPPoE over IEEE 802.1Q VLANs.
The following sections provide information about this feature:
"How to Configure the Physical Subscriber Line for RADIUS Access and Accounting" section on page 3
In 12.2(1), this feature was introduced.
In 12.2(33)SRC, this feature was integrated into the SRC release.
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 used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2005-2009 Cisco Systems, Inc. All rights reserved.