Cisco Cisco Access Registrar 5.0 Fiche De Données
© 2005 Cisco Systems, Inc. All rights reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com.
Page 4 of 8
Request Processing Decisions
•
Process requests using different methods; for example, use LDAP for some access requests, the internal database for others
•
Process requests using a combination of these methods; for example, store an accounting request to a local file and proxy it to a number of remote
RADIUS servers, in serial or parallel
•
Split authentication and authorization by selecting one method for authentication and another for authorization (One-Time Password [OTP] server
and Oracle database, for example)
•
Decide which method to use based on attributes in the request or on Cisco Access Registrar’s ‘environment’ variables, such as source or
destination IP address or UDP port
•
Easy method selection based on DNS domain, username prefix, dialed number, calling number, or network access server (NAS), using the Cisco
Access Registrar Policy Engine
Session/Identity Tracking and Caching
•
Built-in feature to track user sessions and allocate resources
•
Enforcement of session limits per user and per group
•
Allocation of addresses from IP pools
•
Allocation of home agents and on-demand address pools
•
Real-time query of the session table using the command-line interface (CLI), XML over UDP, or RADIUS
•
Add custom information to the session table
•
Configure which attributes to store in the session table
•
Manual release of sessions and resources
•
Query and release sessions based on session age, username, NAS, and other criteria
•
Release sessions and generate PoD
•
Automatic session release when accounting stop is lost (inactivity timeout)
•
Automatic session release when accounting on/off is detected (system accounting)
•
In an environment with multiple Cisco Access Registrars, designate one Cisco Access Registrar to manage all sessions to avoid bypass of session
limits and to allocate IP addresses and other resources centrally
•
Session information is not lost even if Cisco Access Registrar or the system is restarted
•
Session tracking for accounting-only servers
•
Configure session key on calling number or other attributes
•
Send CoA request
System Tuning and System Configuration
•
Configure Cisco Access Registrar to listen on multiple UDP ports
•
Specify which network interfaces to use
•
Set the number of simultaneous requests to be processed
•
Enable access accept logging
•
Regular and advanced duplicate detection features
•
Extensible attribute dictionary
–
Populated with latest attribute definitions, including third-party, vendor-specific attributes
–
Easy addition of new attributes
–
Variable-length vendor type in vendor-specific attributes
•
Specify log file rollover rules