RFC-2867 RADIUS Tunnel Accounting
First Published: November 3, 2003
Last Updated: October 19, 2009
The RFC-2867 RADIUS Tunnel Accounting introduces six new RADIUS accounting types that are used with the RADIUS accounting attribute Acct-Status-Type (attribute 40), which indicates whether an accounting request marks the beginning of user service (start) or the end (stop).
This feature also introduces two virtual private virtual private dialup network (VPDN) commands that help users better troubleshoot VPDN session events.
Without RADIUS tunnel accounting support, VPDN with network accounting, which allows users to determine tunnel-link status changes, did not report all possible attributes to the accounting record file. Now that all possible attributes can be displayed, users can better verify accounting records with their Internet Service Providers (ISPs).
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 RFC-2867 RADIUS Tunnel 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://tools.cisco.com/ITDIT/CFN/jsp/index.jsp. An account on Cisco.com is not required.
Contents
•
Restrictions for RFC-2867 RADIUS Tunnel Accounting
•
Information About RFC-2867 RADIUS Tunnel Accounting
•
How to Configure RADIUS Tunnel Accounting
•
Configuration Examples for RADIUS Tunnel Accounting
•
Additional References
Restrictions for RFC-2867 RADIUS Tunnel Accounting
RADIUS tunnel accounting works only with L2TP tunnel support.
Information About RFC-2867 RADIUS Tunnel Accounting
To use RADIUS tunnel attributes and commands, you should understand the following concepts:
•
RADIUS Attributes Support for RADIUS Tunnel Accounting
RADIUS Attributes Support for RADIUS Tunnel Accounting
Table 1 outlines the new RADIUS accounting types that are designed to support the provision of compulsory tunneling in dialup networks; that is, these attribute types allow you to better track tunnel status changes.
Note
The accounting types are divided into two separate tunnel types so users can decide if they want tunnel type, tunnel-link type, or both types of accounting.
Table 1 RADIUS Accounting Types for the Acct-Status-Type Attribute
|
|
|
|
Tunnel-Start |
9 |
Marks the beginning of a tunnel setup with another node. |
• User-Name (1)—from client • NAS-IP-Address (4)—from AAA • Acct-Delay-Time (41)—from AAA • Event-Timestamp (55)—from AAA • Tunnel-Type (64)—from client • Tunnel-Medium-Type (65)—from client • Tunnel-Client-Endpoint (66)—from client • Tunnel-Server-Endpoint (67)—from client • Acct-Tunnel-Connection (68)—from client |
Tunnel-Stop |
10 |
Marks the end of a tunnel connection to or from another node. |
• User-Name (1)—from client • NAS-IP-Address (4)—from AAA • Acct-Delay-Time (41)—from AAA • Acct-Input-Octets (42)—from AAA • Acct-Output-Octets (43)—from AAA • Acct-Session-Id (44)—from AAA • Acct-Session-Time (46)—from AAA • Acct-Input-Packets (47)—from AAA • Acct-Output-Packets (48)—from AAA • Acct-Terminate-Cause (49)—from AAA • Acct-Multi-Session-Id (51)—from AAA • Event-Timestamp (55)—from AAA • Tunnel-Type (64)—from client • Tunnel-Medium-Type (65)—from client • Tunnel-Client-Endpoint (66)—from client • Tunnel-Server-Endpoint (67)—from client • Acct-Tunnel-Connection (68)—from client • Acct-Tunnel-Packets-Lost (86)—from client |
Tunnel-Reject |
11 |
Marks the rejection of a tunnel setup with another node. |
• User-Name (1)—from client • NAS-IP-Address (4)—from AAA • Acct-Delay-Time (41)—from AAA • Acct-Terminate-Cause (49)—from client • Event-Timestamp (55)—from AAA • Tunnel-Type (64)—from client • Tunnel-Medium-Type (65)—from client • Tunnel-Client-Endpoint (66)—from client • Tunnel-Server-Endpoint (67)—from client • Acct-Tunnel-Connection (68)—from client |
Tunnel-Link-Start |
12 |
Marks the creation of a tunnel link. Only some tunnel types (Layer 2 Transport Protocol [L2TP]) support the multiple links per tunnel; this value should be included only in accounting packets for tunnel types that support multiple links per tunnel. |
• User-Name (1)—from client • NAS-IP-Address (4)—from AAA • NAS-Port (5)—from AAA • Acct-Delay-Time (41)—from AAA • Event-Timestamp (55)—from AAA • Tunnel-Type (64)—from client • Tunnel-Medium-Type (65)—from client • Tunnel-Client-Endpoint (66)—from client • Tunnel-Server-Endpoint (67)—from client • Acct-Tunnel-Connection (68)—from client |
Tunnel-Link-Stop |
13 |
Marks the end of a tunnel link. Only some tunnel types (L2TP) support the multiple links per tunnel; this value should be included only in accounting packets for tunnel types that support multiple links per tunnel. |
• User-Name (1)—from client • NAS-IP-Address (4)—from AAA • NAS-Port (5)—from AAA • Acct-Delay-Time (41)—from AAA • Acct-Input-Octets (42)—from AAA • Acct-Output-Octets (43)—from AAA • Acct-Session-Id (44)—from AAA • Acct-Session-Time (46)—from AAA • Acct-Input-Packets (47)—from AAA • Acct-Output-Packets (48)—from AAA • Acct-Terminate-Cause (49)—from AAA • Acct-Multi-Session-Id (51)—from AAA • Event-Timestamp (55)—from AAA • NAS-Port-Type (61)—from AAA • Tunnel-Type (64)—from client • Tunnel-Medium-Type (65)—from client • Tunnel-Client-Endpoint (66)—from client • Tunnel-Server-Endpoint (67)—from client • Acct-Tunnel-Connection (68)—from client • Acct-Tunnel-Packets-Lost (86)—from client |
Tunnel-Link-Reject |
14 |
Marks the rejection of a tunnel setup for a new link in an existing tunnel. Only some tunnel types (L2TP) support the multiple links per tunnel; this value should be included only in accounting packets for tunnel types that support multiple links per tunnel. |
• User-Name (1)—from client • NAS-IP-Address (4)—from AAA • Acct-Delay-Time (41)—from AAA • Acct-Terminate-Cause (49)—from AAA • Event-Timestamp (55)—from AAA • Tunnel-Type (64)—from client • Tunnel-Medium-Type (65)—from client • Tunnel-Client-Endpoint (66)—from client • Tunnel-Server-Endpoint (67)—from client • Acct-Tunnel-Connection (68)—from client |
How to Configure RADIUS Tunnel Accounting
This section contains the following procedures:
•
Enabling Tunnel Type Accounting Records
•
Verifying RADIUS Tunnel Accounting
Enabling Tunnel Type Accounting Records
Use this task to configure your LAC to send tunnel and tunnel-link accounting records to be sent to the RADIUS server.
Two new command line interfaces (CLIs)—vpdn session accounting network (tunnel-link-type records) and vpdn tunnel accounting network (tunnel-type records)—are supported to help identify the following events:
•
A VPDN tunnel is brought up or destroyed
•
A request to create a VPDN tunnel is rejected
•
A user session within a VPDN tunnel is brought up or brought down
•
A user session create request is rejected
Note
The first two events are tunnel-type accounting records: authentication, authorization, and accounting (AAA) sends Tunnel-Start, Tunnel-Stop, or Tunnel-Reject accounting records to the RADIUS server. The next two events are tunnel-link-type accounting records: AAA sends Tunnel-Link-Start, Tunnel-Link-Stop, or Tunnel-Link-Reject accounting records to the RADIUS server.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
aaa accounting network {default | list-name} {start-stop | stop-only | wait-start | none} group groupname
4.
vpdn enable
5.
vpdn tunnel accounting network list-name
6.
vpdn session accounting network list-name
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. • Enter your password if prompted. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
Router(config)# aaa accounting network {default | list-name} {start-stop | stop-only | wait-start | none} group groupname |
Enables network accounting. • default—If the default network accounting method-list is configured and no additional accounting configurations are enabled on the interface, network accounting is enabled by default. If either the vpdn session accounting network command or the vpdn tunnel accounting network command is linked to the default method-list, all tunnel and tunnel-link accounting records are enabled for those sessions. • list-name—The list-name defined in the aaa accounting command must be the same as the list-name defined in the VPDN command; otherwise, accounting will not occur. |
Step 4 |
Router(config)# vpdn enable |
Enables virtual private dialup networking on the router and informs the router to look for tunnel definitions in a local database and on a remote authorization server (if applicable). |
Step 5 |
Router(config)# vpdn tunnel accounting network list-name |
Enables Tunnel-Start, Tunnel-Stop, and Tunnel-Reject accounting records. • list-name—The list-name must match the list-name defined in the aaa accounting command; otherwise, network accounting will not occur. |
Step 6 |
Router(config)# vpdn session accounting network list-name |
Enables Tunnel-Link-Start, Tunnel-Link-Stop, and Tunnel-Link-Reject accounting records. • list-name—The list-name must match the list-name defined in the aaa accounting command; otherwise, network accounting will not occur. |
What To Do Next
After you have enabled RADIUS tunnel accounting, you can verify your configuration via the following optional task ""Verifying RADIUS Tunnel Accounting" section."
Verifying RADIUS Tunnel Accounting
Use either one or both of the following optional steps to verify your RADIUS tunnel accounting configuration.
SUMMARY STEPS
1.
enable
2.
show accounting
3.
show vpdn [session | tunnel]
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. • Enter your password if prompted. |
Step 2 |
Router# show accounting |
Displays the active accountable events on the network and helps collect information in the event of a data loss on the accounting server. |
Step 3 |
Router# show vpdn [session] [tunnel] |
Displays information about active L2TP tunnel and message identifiers in a VPDN. • session—Displays a summary of the status of all active tunnels. • tunnel—Displays information about all active L2TP tunnels in summary-style format. |
Configuration Examples for RADIUS Tunnel Accounting
This section provides the following configuration examples:
•
Configuring RADIUS Tunnel Accounting on LAC: Example
•
Configuring RADIUS Tunnel Accounting on LNS: Example
Configuring RADIUS Tunnel Accounting on LAC: Example
The following example shows how to configure your L2TP access concentrator (LAC) to send tunnel and tunnel-link accounting records to the RADIUS server:
aaa authentication ppp default group radius
aaa authorization network default local
aaa accounting network m1 start-stop group radius
aaa accounting network m2 stop-only group radius
enable secret 5 $1$IDjH$iL7puCja1RMlyOM.JAeuf/
username ISP_LAC password 0 tunnelpass
ip host dirt 171.69.1.129
vpdn tunnel accounting network m1
vpdn session accounting network m1
vpdn search-order domain dnis
initiate-to ip 10.1.26.71
isdn switch-type primary-5ess
fax interface-type fax-mail
mta receive maximum-recipients 0
interface FastEthernet0/0
ip address 10.1.27.74 255.255.255.0
interface FastEthernet0/1
ip address 60.0.0.2 255.255.255.0
isdn switch-type primary-5ess
ip default-gateway 10.1.27.254
ip route 0.0.0.0 0.0.0.0 10.1.27.254
dialer-list 1 protocol ip permit
radius-server host 172.19.192.26 auth-port 1645 acct-port 1646 key rad123
radius-server retransmit 3
Configuring RADIUS Tunnel Accounting on LNS: Example
The following example shows how to configure your L2TP network server (LNS) to send tunnel and tunnel-link accounting records to the RADIUS server:
aaa accounting network m1 start-stop group radius
aaa accounting network m2 stop-only group radius
enable secret 5 $1$ftf.$wE6Q5Yv6hmQiwL9pizPCg1
username ENT_LNS password 0 tunnelpass
username user1@cisco.com password 0 lab
username user2@cisco.com password 0 lab
firmware location system:/ucode/mica_port_firmware
firmware location system:/ucode/mica_port_firmware
ip host CALLGEN-SECURITY-V2 64.24.80.28 3.47.0.0
ip host dirt 171.69.1.129
vpdn tunnel accounting network m1
vpdn session accounting network m1
terminate-from hostname ISP_LAC
isdn switch-type primary-5ess
mta receive maximum-recipients 0
ip address 70.0.0.101 255.255.255.0
ip address 80.0.0.101 255.255.255.0
ip address 10.1.26.71 255.255.255.0
interface Virtual-Template1
peer default ip address pool vpdn-pool1
interface Virtual-Template2
peer default ip address pool vpdn-pool2
ip local pool vpdn-pool1 70.0.0.1 70.0.0.100
ip local pool vpdn-pool2 80.0.0.1 80.0.0.100
ip default-gateway 10.1.26.254
ip route 0.0.0.0 0.0.0.0 10.1.26.254
ip route 90.1.1.2 255.255.255.255 10.1.26.254
dialer-list 1 protocol ip permit
radius-server host 172.19.192.80 auth-port 1645 acct-port 1646 key rad123
radius-server retransmit 3
Additional References
The following sections provide references related to RFC-2867 RADIUS Tunnel Accounting.
Related Documents
Standards
MIBs
|
|
None |
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs |
RFCs
|
|
RFC 2867 |
RADIUS Accounting Modifications for Tunnel Protocol Support |
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. |
http://www.cisco.com/techsupport |
Feature Information for RFC-2867 RADIUS Tunnel Accounting
Table 2 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
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://tools.cisco.com/ITDIT/CFN/jsp/index.jsp. An account on Cisco.com is not required.
Note
Table 2 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 2 Feature Information for RFC-2867 RADIUS Tunnel Accounting
|
|
|
RFC-2867 RADIUS Tunnel Accounting |
12.2(15)B 12.3(4)T |
The RFC-2867 RADIUS Tunnel Accounting introduces six new RADIUS accounting types that are used with the RADIUS accounting attribute Acct-Status-Type (attribute 40), which indicates whether an accounting request marks the beginning of user service (start) or the end (stop). This feature also introduces two virtual private virtual private dialup network (VPDN) commands that help users better troubleshoot VPDN session events. In 12.2(15)B, this feature was introduced on the Cisco 6400 series, Cisco 7200 series, and the Cisco 7400 series routers. This feature was integrated into Cisco IOS Release 12.3(4)T. The following commands were introduced or modified: aaa accounting, vpdn session accounting network, vpdn tunnel accounting network. |
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.
© 2003-2009 Cisco Systems, Inc. All rights reserved.