Cisco Cisco Access Registrar 5.0 Scheda Tecnica
Cisco Internal Use Only
Copyright © 2001 Cisco Systems, Inc. All rights reserved.
Page 3 of 9
•
Allows service providers to extend competitive advantages by rapidly deploying the latest wireless technologies.
PRODUCT ARCHITECTURE
Cisco Access Registrar is built on a multithreaded architecture to take advantage of multiprocessor systems and provide the highest AAA
performance. At the core of Cisco Access Registrar (Figure 1) is a “policy” engine that determines processing based on the contents of the
RADIUS request packet. The policy engine makes the following types of decisions:
•
Whether authentication against a Lightweight Directory Access Protocol (LDAP) directory or Oracle database is required
•
Whether a request should be forwarded to an external RADIUS server
•
What type of accounting is required
•
Whether session limits apply
•
Whether an IP address pool has been assigned
While the basic operation of the server is determined by configuration, multiple extension points within the server provide optional callouts to
custom code. Extension points can be used for several purposes, including influencing the processing of a request or modifying incoming or
outgoing packets to meet specialized requirements.
Cisco Access Registrar provides a rich set of processing methods, including local, LDAP, Open Database Connectivity (ODBC), proxy, and
prepaid, but Cisco Access Registrar also permits custom service code to be inserted into its architecture to allow service providers to support
special request processing and system integration.
Figure 1. Cisco Access Registrar Architecture