Filter
Top Products
2-9
Cisco Access Registrar 3.5 Concepts and Reference Guide
OL-2683-02
Chapter 2 Understanding Cisco Access Registrar
Cross Server Session and Resource Management
Table 2-8 Cisco Access Registrar Processing Hierarchy for Outgoing Scripts
Cross Server Session and Resource Management
Prior to Cisco AR1.6, sessions and resources were managed locally, meaning that in a multi-AR server
environment, resources such as IP addresses, user-based session limits, and group-based session limits
were divided between all the Cisco ARservers. It also meant that, to ensure accurate session tracking, all
packets relating to one user session were required to go to the same Cisco ARserver.
Overview
Cisco Access Registrar 1.6 and above can manage sessions and resources across AAA server boundaries.
A session can be created by an Access-Request sent to AR1, and it can be removed by an
Accounting-Stop request sent to AR2, as shown in Figure 2-1. This enables accurate tracking of User
and Group session L across multiple AAA servers, and IP addresses allocated to sessions are managed
in one place.
Figure 2-1 Multiple Cisco AR Servers
All resources that must be shared cross multiple front line Cisco AR servers are configured in the Central
Resource Cisco AR server. Resources that are not shared can still be configured at each front line Cisco
AR server as done prior to the Cisco AR 1.6 release.
10) User Authorization.
11) Session Management.
Overall Flow Sequence Outgoing Scripts
12) Service
13) Specific NAS.
14) Vendor of the specific NAS.
15) Immediate client.
16) Vendor of the immediate client.
17) Radius
Overall Flow Sequence Authentication/Authorization Scripts
AR1
AR2
AR3
Central Resource AR
45640