DC-679
Cisco IOS Dial Technologies Configuration Guide
Configuring per-User Configuration
This chapter describes per-user configuration, a large-scale dial solution. It includes the following main
sections:
• Per-User Configuration Overview
• How to Configure a AAA Server for Per-User Configuration
• Monitoring and Debugging Per-User Configuration Settings
• Configuration Examples for Per-User Configuration
This set of features is supported on all platforms that support Multilink PPP (MLP).
A virtual access interface created dynamically for any user dial-in session is deleted when the session
ends. The resources used during the session are returned for other dial-in uses.
When a specific user dials in to a router, the use of a per-user configuration from an authentication,
authorization, and accounting (AAA) server requires that AAA is configured on the router and that a
configuration for that user exists on the AAA server.
To identify the hardware platform or software image information associated with a feature, use the
Feature Navigator on Cisco.com to search for information about the feature or refer to the software
release notes for a specific release. For more information, see the “Identifying Supported Platforms”
section in the “Using Cisco IOS Software” chapter.
For a complete description of the commands mentioned in this chapter, refer to the Cisco IOS Dial
Technologies Command Reference, Release 12.2 and the Cisco IOS Security Command Reference,
Release 12.2. To locate documentation of other commands that appear in this chapter, use the command
reference master index or search online.
Per-User Configuration Overview
Per-user configuration provides a flexible, scalable, easily maintained solution for customers with a
large number of dial-in users. This solution can tie together the following dial-in features:
• Virtual template interfaces, generic interface configuration and router-specific configuration
information stored in the form of a virtual template interface that can be applied (cloned) to a virtual
access interface each time any user dials in. This configuration is described in the chapter
“Configuring Virtual Template Interfaces” in this publication.
• AAA per-user security and interface configuration information stored on a separate AAA server and
sent by the AAA server to the access server or router in response to authorization requests during
the PPP authentication phase. The per-user configuration information can add to or override the
generic configuration on a virtual interface.
Comments to this Manuals