- Overview
- Configuring Cisco Prime Access Registrar
- Customizing Your Configuration
- Setting the Cisco Prime Access Registrar Configurable Option
- Configuring and Monitoring the RADIUS Server
- Configuring Local Authentication and Authorization
- Using Extension Points
- Testing the RADIUS Server
- Using Trusted ID Authorization with SESM
- Using the REX Accounting Script
- Enhanced IP Allocation in Cisco Prime Access Registrar
Configuring and Monitoring the RADIUS Server
This chapter describes the objects you use to configure and operate your Cisco Prime Access Registrar (Prime Access Registrar) RADIUS server.
Prime Access Registrar is configured and operated through a set of objects. These objects are arranged in a hierarchy, with some of the objects containing subobjects; just as in a UNIX file system, in which directories can contain subdirectories. All of the objects, except those that are merely lists, contain properties that define the attributes or behavior of the object.
This chapter describes the following Prime Access Registrar objects:
- Radius— root of the configuration hierarchy
- UserLists—contains individual UserLists, which in turn contain users
- UserGroups—contains individual UserGroups
- Policies—contains individual Policies
- Clients—contains individual Clients
- Vendors—contains individual Vendors
- Scripts—contains individual Scripts
- Services—contains individual Services
- Session Managers—contains individual Session Managers
- Resource Managers—contains individual Resource Managers
- Profiles—contains individual Profiles
- Rules—contains individual Rules
- Fast Rules—contains attributes to add, modify, and delete in the request, response, and environment dictionaries.
- Translations—contains individual Translations
- TranslationGroups—contains individual Translation Groups
- Remote Servers—contains individual RemoteServers
- Advanced—contains advanced properties, Ports, Interfaces, Reply Messages, and the Attribute dictionary
Radius
The Radius object is the root of the hierarchy. For each installation of the Cisco Prime Access Registrar server, there is one instance of the Radius object. You reach all other objects in the hierarchy from the Radius.
The following is a listing of the RADIUS server object:
Table 5-1 lists the Radius properties. You you can set or change Radius properties using the Cisco Prime Access Registrar aregcmd commands.
Note
When a field is listed as required, it means a value must be supplied; that is, the value must be set. You can use the default (if it is supplied) or you can change it to something else, but you cannot unset it. You must supply values for the required fields and for which no defaults exist.
The remaining Cisco Prime Access Registrar objects are sub-objects of the Radius object.
UserLists
The UserLists object contains all of the individual UserLists, which in turn, contain the specific users stored within Cisco Prime Access Registrar. Cisco Prime Access Registrar references each specific UserList by name from a Service whose type is set to local . When Cisco Prime Access Registrar receives a request, it directs it to a Service. When the Service has its type property set to local, the Service looks up the user’s entry in the specific UserList and authenticates and/or authorizes the user against that entry.
Note Usernames might not include the forward slash (/) character. If the Cisco Prime Access Registrar server receives an access request packet with a User-Name attribute containing a forward slash character and the Prime Access Registrar server uses an internal UserList to look up users, the server produces an error (AX_EINVAL) and might fail. If usernames require a forward slash, use a script to translate the slash to an acceptable, unused character.
You can have more than one UserList in the UserLists object. Therefore, use the UserLists object to divide your user community by organization. For example, you might have separate UserLists objects for Company A and B, or you might have separate UserLists objects for different departments within a company.
Using separate UserLists objects allows you to have the same name in different lists. For example, if your company has three people named Bob and they work in different departments, you could create a UserList for each department, and each Bob could use his own name. Using UserLists lets you avoid the problem of Bob1, Bob2, and so on.
If you have more than one UserList, you can have a script Cisco Prime Access Registrar can run in response to requests. The script chooses the Service, and the Service specifies the actual UserList which contains the user. The alternative is dynamic properties.
The subobjects are the Users listed by name. Table 5-2 lists the UserLists object properties.
|
|
|
|---|---|
Users
The Users object contains all of the information necessary to authenticate a user or authorize a user. Users in local UserLists can have multiple profiles. Table 5-3 lists the Users object properties.
HiddenAttributes Property
The HiddenAttributes property in the user object provides a concatenation of all user-level reply attributes. The Prime Access Registrar server uses the HiddenAttributes property to construct and populate a virtual attributes directory.
The HiddenAttributes property is, in fact, hidden. It is not displayed and cannot be set or modified using aregcmd, but when an administrator issues a save, all values from the user’s Attributes directory go into the HiddenAttributes property and the persistent storage.
The attributes are added in a replace-if-present-add-if-not manner as used in the UserGroup-Base-Profile and User-Base-Profile.
UserGroups
The UserGroups objects allow you to maintain common authentication and authorization attributes in one location, and then have many users reference them. By having a central location for attributes, you can make modifications in one place instead of having to make individual changes throughout your user community.
For example, you can use several UserGroups to separate users by the services they use, such as a group specifying PPP and another for Telnet.
Table 5-4 lists the UserGroups properties.
Policies
A Policy is a set of rules applied to an Access-Request. If you are using Policies, the first one that must be created is SelectPolicy.
Table 5-5 lists the properties required for a given Policy.
|
|
|
|---|---|
Clients
All NASs and proxy clients that communicate directly with Cisco Prime Access Registrar must have an entry in the Clients list. This is required because NAS and proxy clients share a secret with the RADIUS server which is used to encrypt passwords and to sign responses. Table 5-6 lists the Client object properties.
Table 5-7 describes the Diameter client properties.
|
|
|
|---|---|
Required; specifies the client protocol which can be Radius or Diameter. |
|
Optional; you can use this property when you need special processing for a specific vendor’s peer. |
|
Optional; specifies a script that you can use to make client-specific modifications when a request is received from a client. |
|
Optional; specifies a script that you can use to make any client-specific modifications when responding to a particular client. |
|
Required; port on which the client connects with Prime Access Registrar server. |
|
Required, default value is False. If set to TRUE, SCTP will be used to establish the connection with the peer else TCP will be used. If SCTP is enabled, you can configure SCTP parameters for the Diameter client. For details, see the “Diameter” chapter of the Cisco Prime Access Registrar 9.1 User Guide. |
Prime Access Registrar supports configuring clients with type as Radius-TLS (Radius over TLS). This will enable the client to send the radius request using TLS connection.
Table 5-8 describes the RADIUS-TLS client properties.
Following is a sample CLI configuration of a RADIUS-TLS client:
Vendors
The Vendor object provides a central location for specifying all of the request and response processing a particular NAS or Proxy vendor requires. Depending on the vendor, it might be necessary to map attributes in the request from one set to another, or to filter out certain attributes before sending the response to the client. For more information about standard RADIUS attributes, see the “RADIUS Attributes” chapter of the Cisco Prime Access Registrar 9.1 Reference Guide.
Note When you have also set /Radius/IncomingScript, Cisco Prime Access Registrar runs that script before the vendor’s script. Conversely, when you have set a /Radius/Outgoing script, Cisco Prime Access Registrar runs the vendor’s script before that script.
Table 5-9 lists the Vendor object properties.
Scripts
The Script objects define the function Cisco Prime Access Registrar invokes whenever the Script is referenced by name from other objects in the configuration.
You can write three types of scripts:
- REX (RADIUS EXtension) scripts are written in C or C++, and thus are compiled functions that reside in shared libraries
- Tcl scripts are written in Tcl, and are interpreted functions defined in source files.
- Java scripts
Note For more information about how to write scripts and how to incorporate them into Cisco Prime Access Registrar, see Chapter7, “Using Extension Points”
Note Cisco is not liable for scripts developed by clients. See Client scripting in user guide chapter 1 overview chapter.
Table 5-10 lists the Script object properties.
The InitEntryPoint properties allow you to perform initialization before processing and then cleanup before stopping the server. For example, when Prime Access Registrar unloads the script (when it stops the RADIUS server) it calls the InitEntryPoint again to allow it to perform any clean-up operations as a result of its initialization. One use of the function might be to allow the script to close an open Accounting log file before stopping the RADIUS server.
Note When you use a Prime Access Registrar file service, Prime Access Registrar automatically closes any opened files. However, if you write scripts that manipulate files, you are responsible for closing them.
Note If you have more than one extension point script (defined under /Radius/Scripts) using the same Java class, only one instance of the class is created and used for all the extension point scripts.
Services
Cisco Prime Access Registrar supports authentication, authorization, and accounting (AAA) services. In addition to the variety of built-in AAA services (specified in the Type property), Cisco Prime Access Registrar also enables you to add new AAA services through custom shared libraries.
Table 5-11 lists the common Services properties. There are additional properties depending on the type of service.
Note OutagePolicy also applies to Accounting-Requests. If an Accounting-Request is directed to an unavailable Service, then the values in Table 5-12 apply.
Types of Services
This section lists the types of services available in Prime Access Registrar with their required and optional properties. The service you specify determines what additional information you must provide.
EAP Services
Prime Access Registrar supports Extensible Authentication Protocol (EAP) and Protected EAP (PEAP) to provide a common protocol for differing authentication mechanisms. EAP enables the dynamic selection of the authentication mechanism at authentication time based on information transmitted in the Access-Request. Prime Access Registrar provides the following EAP services:
- EAP-AKA
- EAP-AKA-PRIME (EAP-AKA’)
- EAP-FAST
- EAP-GTC
- EAP-LEAP
- EAP-MD5
- EAP-MSChapV2
- EAP-Negotiate
- EAP-SIM
- EAP-Transport Level Security (TLS)
- EAP-Tunneled TLS (TTLS)
- PEAP Version 0 (Microsoft PEAP)
- PEAP Version 1 (Cisco PEAP)
See the “Extensible Authentication Protocols” chapter of the Cisco Prime Access Registrar 9.1 User Guide for detailed information about properties used in EAP-type services.
Extended-EAP
Extended EAP is used as an authorization service to retrieve authorization information from a remote web server using the REST interface. Prime Access Registrar processes all EAP requests, and extends the process through extended EAP service. Extended EAP is supported for the following EAP services:
You can configure an extended-EAP service under /Radius/Services. When you define an extended-EAP service under /Radius/Services, you must set its type to extended-eap. Refer to the sample configuration given below:
To configure a REST remote server for the extended-EAP service, see REST.
File
Specify the file service when you want Cisco Prime Access Registrar’s RADIUS Server to perform local accounting using a specific file. Every file Service in your configuration will cause a file with the configured name to be created when the server is started, even if the service is not being invoked by any request packets. Table 5-13 lists the properties used for a file service.
|
|
|
|---|---|
Required; the default is DropPacket. This property defines how Cisco Prime Access Registrar handles requests if all servers listed in the RemoteServers properties are unavailable (that is, all remote RADIUS servers are not available). You must set it to one of the following: AcceptAll , DropPacket , or RejectAll. |
|
Optional; if you set this property to the name of a script, Cisco Prime Access Registrar runs it when an outage occurs. This property allows you to create a script that notifies you when the RADIUS server detects a failure. |
|
Required; a string that specifies where Cisco Prime Access Registrar writes the account records. It must be either a relative or absolute path. When you specify a relative path, it must be relative to the $INSTALL/logs directory. When you specify an absolute path, the server must be able to reach it. The default is Accounting. |
|
Optional; stored as a string, but is composed of two parts, a number and a units indicator (<n> <units>) in which the unit is one of: K, Kilobyte, Kilobytes, M, Megabyte, Megabytes, G, Gigabyte, Gigabytes. The default is ten megabytes. |
|
Optional; stored as a string, but is composed of two parts, a number and a units indicator ( <n> <units>) in which the unit is one of: H, Hour, Hours, D, Day, Days, W, Week, Weeks. The default is one day. |
|
Indicates the exact time including the day of the month or day of the week, hour and minute to roll over the accounting log file. |
|
When set to TRUE, indicates the accounting records' TimeStamp is in local time. When set to FALSE, the default, accounting records' TimeStamp is in GMT. |
|
Indicates the file type to export the accounting records to. Could be one of the following: |
|
Set to TRUE to enable rollover of the accounting records based on the accounting service properties. For more information on rollover of accounting logs, see the “RADIUS Accounting” chapter of the Cisco Prime Access Registrar 9.1 User Guide. |
|
The delimiter to use in the accounting file, if the file type is csv. |
Cisco Prime Access Registrar opens the file when it starts the RADIUS server and closes the file when you stop the server. Prime Access Registrar flushes the accounting record to disk before it acknowledges the request.
Based on the maximum file size and age you have specified, Prime Access Registrar closes the accounting file, moves it to a new name, and reopens the file as a new file. The name Prime Access Registrar gives this accounting file depends on its creation and modification dates.
- If the file was created and modified on the same date, the filename is
FileNamePrefix- <yyyymmdd> - <n> .log. The date is displayed as year, month, day, number. - If the file was created on one day and modified on another, the filename is FileNamePrefix- <yyyymmdd> - <yyyymmdd> - <n> .log. The dates are creation, modification, and number.
Group
A group service contains a list of references to other services and specifies whether the responses from each of the services should be handled as a logical AND or a logical OR function. You specify AND or OR in the Result-Rule attribute of Group Services. The default value is AND.
Table 5-14 lists the properties used to configure a group service.
If Result-Rule is set to AND, the response from the Group Service is positive if each of the services referenced return a positive result. The response is negative if any of the services reference return a negative result. If Result-Rule is set to OR, the response from the Group Service is positive if any of the services referenced return a positive result. The response is negative if all the referenced services return a negative result.
When the Result-Rule attribute is set to AND or OR, each referenced service is accessed sequentially, and the Group Service waits for a response from the first referenced service before moving on to the next service (if necessary). If a service takes a long time to respond, that causes a delay in sending the request to the next referenced server.
The ResultRule settings parallel-and and parallel-or are similar to the AND and OR settings except that they ask each referenced service to process the request simultaneously instead of asking each referenced server sequentially, thereby saving processing time.
A parallel-and setting might respond with its own reply as soon as it receives a negative response, but otherwise must wait for all responses before it can respond with a positive reply. Likewise, a parallel-or might respond as soon as it receives a positive response, but otherwise must wait for all responses before it can reply with a negative response.
If a service referenced from a Group Service is of type RADIUS and if Accounting-Requests are being processed by the Group Service, setting the AckAccounting property in the remote server will affect the behavior of the parallel-or Group Service. This is because if AckAccounting is set to FALSE, the RADIUS Remote Server will not wait for the response from the remote server but returns a response immediately. Since the Group Service is set to parallel-or, after it receives the response from the RADIUS service, it is free to send a response itself. This will have the effect that a response is sent very quickly from the Group Service acknowledging the Accounting-Request and responses from the other referenced services are handled as the arrive.
Note that since AckAccounting was set to FALSE, there is no guarantee that the Remote Server successfully processed the request. Since it is a RADIUS Remote Server, the Prime Access Registrar server attempts for MaxTries to send the request to the server and to get back an acknowledgment, but if that fails, there will be no indication to the client about that event. The acknowledgment to the client has been sent long before.
Java
Specify the java service type when you want to create a custom service and use a script for authentication, authorization, or accounting. Table 5-15 lists the properties required to configure a java service.
A java service uses an extension point script to provide the service’s functionality and handles both RADIUS and TACACS requests for authentication, authorization, and accounting.
LDAP
Specify the ldap service type when you want to use a particular LDAP remote server for authentication and/or authorization. Table 5-16 lists the properties used to configure an LDAP service.
When using LDAP for authentication and a local database for authorization, ensure that the usernames in both locations are identical with regard to case sensitivity.
Local
Specify local when you want the Cisco Prime Access Registrar server to perform the authentication and authorization using a specific UserList. For more information, see the “UserLists” section. Table 5-17 lists the properties used to configure a local service.
ODBC
Specify odbc when you want to use an ODBC service for authentication, authorization and accounting through an ODBC data store. Use an ODBC service to authenticate and authorize an access requests by querying user information through ODBC and to insert accounting records into a data store through ODBC. Table 5-18 lists the properties used to configure an ODBC service.
ODBC-Accounting
If you use the Oracle Accounting feature, you must configure an ODBC-Accounting RemoteServer object. See the “Configuring an ODBC/OCI RemoteServer” section in the “Using Open Database Connectivity” chapter of the Cisco Prime Access Registrar 9.1 User Guide, for more information on ODBC-Accounting RemoteServer.
Prepaid Services
Cisco Prime Access Registrar (Prime Access Registrar) supports two types of prepaid billing, IS835C and Cisco Real-time Billing (CRB), a Cisco proprietary solution. See “Using Prepaid Billing” chapter of the Cisco Prime Access Registrar 9.1 User Guide for more information on Prepaid -IS835C and Prepaid-CRB.
RADIUS
Specify the radius service type when you want to use a particular RADIUS remote server for authentication and authorization. Table 5-19 lists the properties used to configure a RADIUS service.
Radius Query
Prime Access Registrar supports a new service type called radius-query that can be used to query cached data through RADIUS packets. This radius-query service contains a list of session managers to be queried from and a list of (cached) attributes to be returned in the Access-Accept packet in response to a RADIUS Query request. Prime Access Registrar also supports caching and querying of multivalued attributes.
The RADIUS Query service should be selected through an extension point script or through the Rule and Policy Engine by setting it to a new environment variable named Query-Service. The reason for this is that the RADIUS Query request comes in as an Access-Request and the server has no way of knowing whether it is a RADIUS Query request or normal authentication request. Setting the Query-Service environment variable tells the Prime Access Registrar server that the request is a RADIUS Query request so the Prime Access Registrar server can process the request with the radius-query service set in the Query-Service environment variable.
When a RADIUS Query service is selected to process an Access-Request, it queries the configured list of Session Managers for a matching record using the QueryKey value configured in the session-cache Resource Manager referenced under these Session Managers as key. If a matching record is found, an Access-Accept containing a list of cached attributes present (based on the configuration) in the matched record is sent back to the client. If the session cache contains a multivalued attribute, all values of that attribute are returned in the response as a multivalued attribute. If there is no matching record, an Access-Reject packet is sent to the client.
Prime Access Registrar introduces scripting points at the Session Manager level along with automated programmable interfaces (APIs) to access cached information present in the session record. You can use these scripting points and APIs to write extension point scrips to modify the cached information.
The following example shows the default configuration of a radius-query service:
Table 5-20 lists the properties used to configure a RADIUS Query service.
When an Access-Request packet is received by the Prime Access Registrar server, the session-cache Resource Manager caches the configured attributes in the session with the configured QueryKey as the key to the cached data. In the TAL solution, the QueryKey will usually be Framed-IP-Address. If an Accounting-Requestor Accounting-Start packet is received for the same session, the cached data is updated if necessary. If there is a multivalued attribute in the Access-Request packet or Accounting-Request packet, the Prime Access Registrar server caches all the values of that attributes.
In TAL, when the SSG receives an IP packet originating from a user unknown to the SSG, it sends an Access-Request packet to the Prime Access Registrar server in which the User-Name and Framed-IP-Address attributes both contain the user’s source IP address, and the Service-Type is set to Outbound, among other attributes. These attributes and their values distinguish RADIUS Query requests from normal authentication requests in TAL.
Note In solutions other than TAL, the criterion that distinguishes RADIUS Query requests from normal authentication requests might be different.
A new environment variable, Query-Service, can be set to the name of a radius-query service, in an extension point script, or through the Rule and Policy engine so the Prime Access Registrar server knows the current request is a RADIUS Query request and processes it with the radius-query service value set in the Query-Service environment variable.
API Calls
Prime Access Registrar provides several new API calls you can use to get, put, and delete the cached attributes present in the session record.
The entry point function changes slightly to take a fifth argument which is a pointer to a structure containing the new API calls:
(
rex_AttributeDictionary_t* pRequest,
rex_AttributeDictionary_t* pResponse,
rex_EnvironmentDictionary_t* pRadius,
rex_SessionRecord_t* pSession
However, you can continue to write extension point scripts with four arguments as well, for example without the pSession argument.
The following are API calls and their functionality. All these API calls fail gracefully when they are invoked from any scripting point other than the Session Manager scripting points.
This API returns the value of the <iIndex>'d instance of the attribute cached in the session, represented as a string. When the session does not contain the attribute, an empty string is returned. When <pbMore> is non-zero, this method sets <pbMore> to TRUE when more instances of the same attribute exist after the one returned and to FALSE otherwise. This can be used to determine whether another call to get() method should be made to retrieve other instances of the same attribute.
When <iIndex> equals the special value REX_REPLACE, this method replaces any existing instances of <pszAttribute> with a single value in the session. When <iIndex> equals the special value REX_APPEND, it appends a new instance of <pszAttribute> to the end of the list of existing instances of <pszAttribute>. When <iIndex> equals the special value REX_AUGMENT, this method only puts <pszAttribute> when it does not already exist. Otherwise, a new instance of <pszAttribute> is inserted/replaced at the position indicated. This method returns TRUE if it is able to cache the attribute successfully and FALSE otherwise.
This method removes the <pszAttribute> from the session. When <iIndex> equals the special value REX_REMOVE_ALL, this method removes any existing instances of <pszAttribute>. Otherwise, it removes the instance of <pszAttribute> at the position indicated. It returns FALSE when <pszAttribute> is not present at any index in the session record and returns TRUE otherwise.
rex_SessionInfo_t* getSessionInfo(rex_SessionRecord_t* pSession)
This method returns the pointer to a structure that contains the other session-related information, like Session Id, Session Start time, Session Last Accessed Time, present in the session record. The structure that holds this information will appear as follows:
Tcl API calls
To use the extension point scripts written in Tcl, define the procedure at the session manager level as shown below:
There is a fourth argument session that needs to be passed to the Tcl procedure and the API calls that are intended to operate on the session record need to use this session dictionary.
API calls in Tcl have the same meaning with same number arguments and return values as described in Rex. The only difference is that the API getSessionInfo will not return a structure as in Rex but it will return the info as a string, as in the following example:
Java API calls
There are two new interfaces ExtensionForSession and ExtensionForSessionWithInitialization and the customers whishing to use the extension point scripts written in Java at the session manager level needs to implement one of these interfaces.
The runExtension method of these interfaces will look as below:
API calls that are intended to operate on session record needs to use this ‘session’ dictionary.
API calls in Java have the same meaning with same number arguments and return values as described in Rex. The only difference is that the API getSessionInfo will not return a structure as in Rex but it will return the info as a string. For example:
Session-ID=1, Session-Start-Time=1102099334, Session-Last-Accessed-Time=1102099334
Existing scripts written in any of these three languages will not be affected with the introduction of the new ‘session dictionary’ argument. And the customers can use a script with any number of arguments (i.e with or without the last ‘session dictionary’ argument) at any extension point script. If there is no session to operate on, for example when the customer is trying to use session dictionary argument at an extension point other than session manager’s, the Prime Access Registrar gracefully returns an error logging the appropriate message.
The simple replace or add if it does not exist model can still be used for simple modifications as before without the need to write a script. If the cached attributes are updated in the IncomingScript and if customers do not want them to be touched or updated again when the processing reaches session-cache resource manager, they can set the OverwriteAttributes property of the session-cache resource manager to FALSE so that the session-cache resource manager will not operate on this packet.
Diameter-RADIUS
This service helps to translate incoming Diameter request to a RADIUS equivalent and then the RADIUS response to Diameter equivalent. Prime Access Registrar provides scripting points, which operate on the original packet and on the newly translated packet based on request and response mapping.
RADIUS-Diameter
This service helps to translate incoming RADIUS request to a Diameter equivalent and then the Diameter response to RADIUS equivalent. Prime Access Registrar provides scripting points, which operate on the original packet and on the newly translated packet based on request and response mapping.
The following example shows a sample configuration of translation service in Diameter:
RADIUS-Session
A new Service step has been added in the processing of Access-Request and Accounting packets. This is an additional step after the AA processing for Access packet or Accounting processing for Accounting packet, but before the local session management processing. The Session-Service should have a service type of radius-session.
An environment variable Session-Service is introduced to determine the Session-Service dynamically. You can use a script or the rule engine to set the Session-Service environment variable. See Cross Server Session and Resource Management for more information on RADIUS-Session.
Rex
Specify the rex service type when you want to create a custom service and use a script for authentication, authorization, or accounting. Table 5-22 lists the properties required to configure a rex service.
For more information about scripting, see Chapter7, “Using Extension Points” For more information about using the REX Attribute dictionary, see “Cisco Prime Access Registrar Tcl, REX, and Java Dictionaries” chapter of the Cisco Prime Access Registrar 9.1 Reference Guide.
WiMAX
Prime Access Registrar uses the Extensible Authentication Protocol (EAP) to enable the WiMAX feature. It also caches the IP attributes and Mobility Keys that are generated during network access authentication. To enable caching of the WiMAX attributes, you must configure the respective resource managers. For more information, see the “Using WiMAX in Cisco Prime Access Registrar” chapter of the Cisco Prime Access Registrar 9.1 Reference Guide.
Diameter
Diameter works with the rule policy engine to perform the routing for multiple peers. The following are the multiple peer policies supported with the proxy service to route the traffic:
The following configuration is used to add Diameter proxy without Sticky session configuration:
The following configuration is used to add Diameter proxy with Sticky session configuration:
The following configuration is used to add Diameter proxy with IMSI range based load balancing configuration:
The following configuration is used to add Diameter local:
The following configuration is used to add Diameter relay:
The following configuration is used to add Diameter redirect:
M3UA
Prime Access Registrar supports the M3UA service, which is used to fetch MSISDN from IMSI through RADIUS Packets. The M3UA service sends a SendRoutingInfoForLCS(SRIForLCS) request that contains the IMSI information to the remote HLR. The HLR sends the MSISDN in response. To fetch the MSISDN information from IMSI, you need to configure the SIGTRAN-M3UA remote server where Prime Access Registrar is installed. See “SIGTRAN-M3UA” chapter of the Cisco Prime Access Registrar 9.1 User Guide for more information.
The M3UA service checks for IMSI environment variable to fetch the MSISDN information. If there is no IMSI environment variable set, then the User-Name in the Radius Access-Request is used as IMSI to fetch the MSISDN information. The fetched MSISDN is copied to the AuthorizationInfo environment variable where you can write a script to copy the environment variable to any attribute of your choice. For the list of environment variables, see the “Environment Dictionary” chapter of the Cisco Prime Access Registrar 9.1 Reference Guide.
Note M3UA service supports fetching the MSISDN only through SIGTRAN-M3UA interface.
The following shows an example configuration of M3UA service:
Session Managers
You can use Session Managers to track user sessions. The Session Managers monitor the flow of requests from each NAS and detect the session state. When requests come through to the Session Manager, it creates sessions, allocates resources from appropriate Resource Managers, and frees and deletes sessions when users log out.
The Session Manager enables you to allocate dynamic resources to users for the lifetime of their session. You can define one or more Session Managers and have each one manage the sessions for a particular group or company.
Note Session record size is limited by the operating system (OS) paging size (4 KB in Linux). If a request triggers creation of a session that exceeds the OS paging size, the request will be dropped and the session will not be created.
Note In this release of Prime Access Registrar, the memory capacity is enhanced to store more than 4 million active sessions by storing the active session records in database server instead of storing it in the main memory. The capacity is dependent on the number of attributes that are being captured for each session.
Note If the disk partition where Prime Access Registrar stores session backing store data (usually the disk partition where Prime Access Registrar is installed, such as /opt/CSCOar) is full, the subsequent packets that try to create sessions will be dropped and no sessions will be created due to lack of disk space.
Session Managers use Resource Managers, which in turn, manage a pool of resources of a particular type. Table 5-25 lists the Session Manager properties.
Prime Access Registrar adds IncomingScript, OutgoingScript, and SessionKey properties. The IncomingScript is run as soon as the session is acquired. The OutgoingScript is run just before the session is written to backing store. The SessionKey property sets the session key value for the Session Manager.
You can manage sessions with the two aregcmd session management commands: query-sessions and release-sessions . For more information about these two commands, see the query-sessions and the release-sessions.
This section contains the following topics:
- Session Creation
- Session Notes
- Soft Group Session Limit
- Session Correlation Based on User-Defined Attributes
Session Creation
Cisco Prime Access Registrar Sessions can be created by two types of RADIUS packets:
This allows Cisco Prime Access Registrar to monitor Sessions even when it is not allocating resources. For example, when Cisco Prime Access Registrar is being used as an “Accounting-Only” server (only receiving Accounting requests), it can create a Session for each Accounting “Start” packet it successfully processes. The corresponding Accounting “Stop” request will clean up the Session. Note, if a Session already exists for that NAS/NAS-Port/User (created by an Access-Request), Cisco Prime Access Registrar will not create a new one.
When you do not want Cisco Prime Access Registrar to create Sessions for Accounting “Start” requests, simply set the AllowAccountingStartToCreateSession property on the SessionManager to FALSE.
Session Notes
Session Notes are named text messages attached to a Session and are stored with the Session data, including resources allocated for a specific user session. This data, including Session Notes, can be retrieved and viewed using the aregcmd command query-sessions.
--> query-sessions /Radius/SessionManagers/session-mgr-2
sessions for /Radius/SessionManagers/session-mgr-2:
S257 NAS: localhost, NAS-Port:1, User-Name: user1, Time: 00:00:08,
IPX 0x1, GSL 1, USL 1, NOTES: "Date" "Today is 12/14/98.", "Requested
IP Address" "1.2.3.4", "Framed-IP-Address" "11.21.31.4"
Session Notes can be created by Scripts using the Environment dictionary passed into each or by the Cisco Prime Access Registrar server. When more than one Session Note is added, the Session-Notes entry should be a comma-separated list of entry names.
Step 1 The Script should create an Environment dictionary entry using the Session Note name as the entry name, and the Session Note text as the entry value. For example:
Step 2 The Script should create or set an Environment dictionary entry with the name Session-Notes with a value that contains the name of the entries created. For example:
Step 1 The Script should create an Environment dictionary entry using the Session Note name as the entry name, and the Session Note text as the entry value. For example:
Step 2 The Script should create/set an Environment dictionary entry with the name Session-Notes with a value that contains the name of the first entry created. For example:
Note Scripts creating Session Notes must be executed before the Session Management step takes place while processing a packet.
Cisco Prime Access Registrar will automatically create a Session Note if a packet is passed to a SessionManager and it already contains a Framed-IP-Address attribute in the packet’s Response dictionary. This IP address could come from a Profile, RemoteServer response, or from a previously executed script. For example, a Session output containing Session Notes when using the aregcmd command query-session would be as follows:
IPX 0x1, GSL 1, USL 1, NOTES: "Date" "Today is 12/14/08.", "Requested
IP Address" "1.2.3.4", "Framed-IP-Address" "11.21.31.4"
Session Notes are also copied into the Environment dictionary after Session Management. The Session-Notes Environment dictionary entry will contain the names of all the Environment dictionary entries containing Session Notes.
In Prime Access Registrar, a major command is introduced—count-sessions. The count-sessions /radius all command helps to count the total sessions in Prime Access Registrar. The options are similar to the query-session command options. The query-session command displays cached attributes in addition to session details.
Soft Group Session Limit
Two new environment variables, Group-Session-Limit and Current-Group-Count (see rex.h), are set if the group session limit resource is allocated for a packet. These variables allow a script to see how close the group is to its session limit; one way to use this information is to implement a script-based soft limit. For example, you could use the Class attribute to mark sessions that have exceeded a soft limit of 80% -- as hard coded in the script (in a Tcl script called from /Radius/):
set softlimit [ expr 0.8 * [ $environ get Group-Session-Limit ] ]
if { [ $environ get Current-Group-Count ] < $softlimit } {
Note The soft limit itself is hard coded in the script; soft limits are not directly supported in the server. The action to be taken when the soft limit is exceeded (for example, Class = 1, and then the accounting software branches on the value of Class) is also the responsibility of the script and/or external software.
Session Correlation Based on User-Defined Attributes
All the session objects are maintained in one dictionary keyed by a string. You can define the keying material to the session dictionary through a newly introduced environment variable, Session-Key.
If the Session-Key is presented at the time of session manager process, it will be used as the key to the session object for this session. The Session-Key is of type string. By default, the Session-Key is not set. Its value should come from attributes in the incoming packet and is typically set by scripts. For example, CLID can be used to set the value of Session-Key.
Use the function UseCLIDAsSessionKey as defined in the script rexscript.c to specify that the Calling-Station-Id attribute that should be used as the session key to correlate requests for the same session. This is a typical case for 3G mobile user session correlation. You can provide your own script to define other attributes as the session key.
In the absence of the Session-Key variable, the key to the session will be created based on the string concatenated by the value of the NAS-Identifier and the NAS-Port.
There is a new option with-key available in aregcmd for query-sessions and release-sessions to access sessions by Session-Key.
Resource Managers
Resource Managers allow you to allocate dynamic resources to user sessions. The following lists the different types of Resource Managers.
- IP-Dynamic —manages a pool of IP addresses that allows you to dynamically allocate IP addresses from a pool of addresses
- IP-Per-NAS-Port —allows you to associate ports to specific IP addresses, and thus ensure each NAS port always gets the same IP address
- IPX-Dynamic —manages a pool of IPX network addresses
- Subnet-Dynamic—manages a pool of subnet addresses
- Group-Session-Limit —manages concurrent sessions for a group of users; that is, it keeps track of how many sessions are active and denies new sessions after the configured limit has been reached
- User-Session-Limit —manages per-user concurrent sessions; that is, it keeps track of how many sessions each user has and denies the user a new session after the configured limit has been reached
- Home-Agent—manages a pool of on-demand IP addresses
- USR-VPN —manages Virtual Private Networks (VPNs) that use USR NAS Clients.
- Home-Agent-IPv6—manages a pool of on-demand IPv6 addresses
- Remote-IP-Dynamic—manages a pool of IP addresses that allows you to dynamically allocate IP addresses from a pool of addresses. It internally works with a remote ODBC database.
- Remote-User-Session-Limit—manages per-user concurrent sessions; that is, it keeps track of how many sessions each user has and denies the user a new session after the configured limit has been reached. It internally works with a remote ODBC database.
- Remote-Group-Session-Limit—manages concurrent sessions for a group of users; that is, it keeps track of how many sessions are active and denies new sessions after the configured limit has been reached. It internally works with a remote ODBC database.
- 3GPP—allows you to define the attribute for 3GPP authorization.
Each Resource Manager is responsible for examining the request and deciding whether to allocate a resource for the user, do nothing, or cause Cisco Prime Access Registrar to reject the request.
Table 5-26 lists the Resource Manager properties.
Types of Resource Managers
A number of different types of Resource Managers exist that allow you to manage IP addresses dynamically or statically, limit sessions on a per group or per user basis, or manage a Virtual Private Network. See the “Cisco Prime Access Registrar Tcl, REX, and Java Dictionaries” chapter of the Cisco Prime Access Registrar 9.1 Reference Guide for information on how to override these individual Resource Managers.
Note Resource Manager supports the following remote type session managers: remote-ip-dynamic, remote-session-cache, home-agent, remote-user-session-limit, home-agent-ipv6 and remote-group-session-limit.
Group-Session-Limit
Group-Session-Limit allows you to manage concurrent sessions for a group of users; that is, it keeps track of how many sessions are active and denies new sessions after the configured limit has been reached.
When you use this Resource Manager, you must set the GroupSessionLimit property to the maximum number of concurrent sessions for all users.
Home-Agent
Home-Agent is a resource manager that supports dynamic HA assignment. You configure the home-agent resource manager with a list of IP addresses. The Prime Access Registrar server assigns those addresses to clients whose request dictionary has the right attributes to indicate that an assignment should be done. This is similar to the ip-dynamic resource manager.
Unlike the ip-dynamic resource manager, HAs are not exclusively allocated to an individual session but are shared among a set of sessions.
Detailed configuration information for the Home-Agent resource manager is found in the “Wireless” chapter of the Cisco Prime Access Registrar 9.1 Reference Guide. When you use this Resource Manager, you must set the Home-Agent-IPAddresses property to a single IP address or a range of IP addresses.
Home-Agent-IPv6
Home-Agent-Ipv6 is a new resource manager used to configure IPv6 address.
IP-Dynamic
IP-Dynamic allows you to manage a pool of IP addresses from which you dynamically allocate IP addresses.
When you use the IP-Dynamic Resource Manager, provide values for the properties listed in Table 5-27 .
IP-Per-NAS-Port
IP-Per-NAS-Port allows you to associate specific IP addresses with specific NAS ports and thus ensures each NAS port always gets the same IP address.
When you use this Resource Manager, provide values for the properties listed in Table 5-28 .
Note You must have the same number of IP addresses and ports.
|
|
|
|---|---|
Required; must be the name of a known Client.This value must be the same as the NAS-Identifier attribute in the Access-Request packet. |
|
IPX-Dynamic
An IPX-Dynamic Resource Manager allows you to dynamically manage a pool of IPX networks. When you use the IPX-Dynamic Resource Manager, you must set the Networks property to a valid set of numbers which correspond to your networks.
Note You cannot use IPX network number 0x0. If you attempt to configure a Resource Manager with an IPX network number of 0x0, validation will fail.
Session-Cache
The session-cache Resource Manager supports the Identity Cache feature. You use session-cache Resource Managers to define the RADIUS attributes to store in cache. Set the QueryKey property to the XML attribute you want to key on such as XML-Address-format-IPv4 and list all attributes to be cached in the AttributesToBeCached subdirectory. Use the QueryMappings subdirectory to map XML attributes to RADIUS attributes.
Note Session record size is limited by the operating system (OS) paging size (4 KB in Linux). If a request triggers creation of a session that exceeds the OS paging size, the request will be dropped and the session will not be created.
If the disk partition where Prime Access Registrar stores session backing store data (usually the disk partition where Prime Access Registrar is installed, such as /opt/CSCOar) is full, the subsequent packets that try to create sessions will be dropped and no sessions will be created due to lack of disk space.
Subnet-Dynamic
The subnet-dynamic Resource Manager supports the On Demand Address Pool feature. You use subnet-dynamic resource managers to provide pools of subnet addresses. Following is an example of the configuration of a subnet dynamic resource manager:
When you use the subnet-dynamic Resource Manager, provide values for the properties listed in Table 5-30 .
|
|
|
|---|---|
User-Session-Limit
User-Session-Limit allows you to manage per-user concurrent sessions; that is, it keeps track of how many sessions each user has and denies the user a new session after the configured limit has been reached.
When you use the user-session-limit Resource Manager, set the user-session-limit property to the maximum number of concurrent sessions for a particular user.
USR-VPN
USR-VPN allows you to set up a Virtual Private Network (VPN) using a US Robotics NAS.
When you use this Resource Manager, provide values for the properties listed in Table 5-31 .
Dynamic-DNS
Prime Access Registrar supports the Dynamic DNS protocol providing the ability to update DNS servers.
When you use this Resource Manager, provide values for the properties listed in Table 5-32 .
Remote-IP-Dynamic
The configuration is same as IP-Dynamic but internally it works with a remote ODBC database.
Remote-User-Session-Limit
The configuration is same as User-Session-Limit but internally it works with a remote ODBC database.
Remote-Group-Session-Limit
The configuration is same as Group-Session-Limit but internally it works with a remote ODBC database.
Remote-Session-Cache
The configuration is same as Session-Cache but it should be used with session manager of type remote.
3GPP
Prime Access Registrar provides a resource manager for 3GPP authorization. When you use this Resource Manager, provide values for the properties listed in Table 5-33 .
Profiles
You use Profiles to group RADIUS attributes that belong together, such as attributes that are appropriate for a particular class of PPP or Telnet user. You can reference profiles by name from either the UserGroup or the User properties. Thus, if the specifications of a particular profile change, you can make the change in a single place and have it propagated throughout your user community.
Although you can use UserGroups or Profiles in a similar manner, choosing whether to use one rather than the other depends on your site. When you require some choice in determining how to authorize or authenticate a user session, then creating specific profiles, and creating a group that uses a script to choose among them is more flexible.
In such a situation, you might create a default group, and then write a script that selects the appropriate profile based on the specific request. The benefit to this technique is each user can have a single entry, and use the appropriate profile depending on the way they log in.
Table 5-34 lists the Profile properties.
|
|
|
|---|---|
Profiles include specific RADIUS attributes that Cisco Prime Access Registrar returns in the Access-Accept response. |
Attributes
Attributes are specific RADIUS components of requests and responses defined in the Request and Response Attribute dictionaries. Use the aregcmd command set to assign values to attributes.
For a complete list of the attributes, see the “RADIUS Attributes” chapter of the Cisco Prime Access Registrar 9.1 Reference Guide.
When setting a value for a STRING-type attribute such as Connect-Info (which starts with an integer), you must use the hexadecimal representation of the integer. For example, to set the attribute Connect-Info to a value of 7:7, use a set command like the following:
Translations
Translations add new attributes to a packet or change an existing attribute from one value to another. The Translations subdirectory lists all definitions of Translations the RADIUS server can apply to certain packets.
Under the /Radius/Translations directory, any translation to insert, substitute, or translate attributes can be added. The following is a sample configuration under the /Radius/Translations directory:
Add T1
cd T1
Set DeleAttrs Session-Timeout,Called-Station-Id
cd Attributes
Set Calling-Station-Id 18009998888
DeleAttrs is the set of attributes to be deleted from the packet. Each attribute is comma separated and no spaces are allowed between attributes. All attribute value pairs under the attributes subdirectory are the attributes and values that are going to be added or translated to the packet.
Under the /Radius/Translations/T1/Attributes directory, inserted or translated attribute value pairs can be set. These attribute value pairs are either added to the packet or replaced with the new value.
If a translation applies to an Access-Request packet, by referencing the definition of that translation, the Prime Access Registrar server modifies the Request dictionary and inserts, filters and substitutes the attributes accordingly. You can set many translations for one packet and the Prime Access Registrar server applies these translations sequentially.
Note Later translations can overwrite previous translations.
Table 5-35 lists the Translation properties.
|
|
|
|---|---|
TranslationGroups
You can add translation groups for different user groups under TranslationGroups. All Translations under the Translations subdirectory are applied to those packets that fall into the groups. The groups are integrated with the Prime Access Registrar Rule engine.
The Prime Access Registrar Administrator can use any RADIUS attribute to determine the Translation Group. The incoming and outgoing translation group can be different translation groups. For example, you can set one translation group for incoming translations and one for outgoing translations.
Under the /Radius/TranslationGroups directory, translations can be grouped and applied to certain sets of packets, which are referred to in a rule. The following is a sample configuration under the /Radius/TranslationGroups directory:
Add CiscoIncoming
cd CiscoIncoming
cd Translations
Set 1 T1
The translation group is referenced through the Prime Access Registrar Policy Engine in the /Radius/Rules/ <RuleName> /Attributes directory. Incoming-Translation-Groups are set to a translation group (for example CiscoIncoming) and Outgoing-Translation-Groups to another translation group (for example CiscoOutgoing). Table 5-36 lists the Translation Group properties.
|
|
|
|---|---|
Remote Servers
You can use the RemoteServers object to specify the properties of the remote servers to which Services proxy requests. RemoteServers are referenced by name from the RemoteServers list in either the radius, ldap or tacacs-udp Services.
Note You must not configure a remote server with an IP address, which is same as that of the client. This is applicable for all types of remote servers.
Table 5-37 lists the common RemoteServers properties.
Types of Protocols
The Remote Server protocol you specify determines what additional information you must provide. The following are the protocols available in Prime Access Registrar with their required and optional fields.
Prime Access Registrar provides the following RemoteServer protocol types:
Dynamic DNS
The dynamic-dns RemoteServer is used with the Dynamic DNS feature. The following is the default configuration of a dynamic-dns RemoteServer.
Table 5-38 lists and defines the dynamic-dns RemoteServer properties.
LDAP
ldap specifies an LDAP server. When you specify the ldap protocol, provide the information listed in Table 5-39 .
For any LDAP remote service, the server might perform the environment mappings at any time. This means that if the service is set to either authentication and authorization, authentication-only, or authorization-only, environment mappings will take place. RADIUS mappings will take place only if the service is set to perform authorization. Checkitem mappings will take place only if the service is set to perform authentication. Previously environment mappings only occurred when the service was set for both authentication and authorization. RADIUS mappings, environment mappings, and checkitem mappings will not take place, if bind-based authentication is enabled.
Map-Gateway
The following is the default configuration of a map gateway RemoteServer.
Sigtran
The following is the default configuration of a Sigtran RemoteServer.
Note The RPM packages such as lksctp-tools-1.0.10-1, lksctp-tools-doc-1.0.10-1 and lksctp-tools-devel-1.0.10-1 should be installed in Linux 5.3 before configuring sigtran remote server which eventually adds the sctp libs (libsctp.so.1.0.10).
The following files can be downloaded from http://lksctp.sourceforge.net/
- lksctp-tools-1.0.10-1.i386.rpm
- lksctp-tools-devel-1.0.10-1.i386.rpm
- lksctp-tools-doc-1.0.10-1.i386.rpm
Prime Access Registrar supports only:
- one object of Remoteserver with protocol type "sigtran"
- MAP version 3 (3GPP TS 29.002 V6.4.0 (2003-12)) and ITU Q.773 TCAP
Only one Quintets is fetched from HLR. The ITU TCAP continue message is not supported.
Table 5-40 lists and defines the Sigtran RemoteServer properties.
Note You should restart the Prime Access Registrar server, if you change any SIGTRAN related configuration.
ODBC
odbc specifies an ODBC server. Cisco Prime Access Registrar provides a RemoteServer object (and a service) to support Open Database Connectivity (ODBC), an open specification that provides application developers a vendor-independent API with which to access data sources. Table 5-41 lists the odbc server attributes.
For any ODBC remote service, the server might perform the environment mappings at any time. This means that if the service is set to either authentication and authorization, authentication-only, or authorization-only, environment mappings will take place. RADIUS mappings will take place only if the service is set to perform authorization. Checkitem mappings will take place only if the service is set to perform authentication. Previously environment mappings only occurred when the service was set for both authentication and authorization.
ODBC-Accounting
If you use the Oracle Accounting feature, you must configure an ODBC-Accounting RemoteServer object. Table 5-42 lists and defines the ODBC-Accounting RemoteServer properties.
|
|
|
|---|---|
Name of the remote server; this property is mandatory, and there is no default |
|
Mandatory time interval (in milliseconds) to activate an inactive server; defaults to 300000 ms. |
|
Mandatory time interval (in seconds) to wait for SQL operation to complete; defaults to 15 seconds |
|
Mandatory number of connections to be established; defaults to 8 |
|
Name of the ODBCDataSource to use and must refer to one entry in the list of ODBC datasources configured under /Radius/Advanced/ODBCDataSources. Mandatory; no default |
|
Mandatory time interval (in milliseconds) to send a keepalive to keep the idle connection active; defaults to zero (0) meaning the option is disabled |
|
Mandatory, TRUE or FALSE, determines whether to buffer the accounting packets to local file, defaults to TRUE which means that packet buffering is enabled. Note When set to TRUE, a constant flow of incoming accounting packets can fill the buffer backing store files in /cisco-ar/data/odbc beyond the size configured in MaximumBufferFileSize. Configure BackingStoreDiscThreshold in /Radius/Advanced when using ODBC accounting. See Advanced for information about how to configure BackingStoreDiscThreshold. |
|
Mandatory if BufferAccountingPackets is set to TRUE, determines the maximum buffer file size, defaults to 10 Megabyte) |
|
Mandatory if BufferAccountingPackets is set to TRUE. A number greater than zero determines the number of attempts to be made to insert the buffered packet into Oracle. Defaults to 3. |
OCI
OCI service can be used to authenticate and authorize an access request by querying user information through OCI and to insert accounting records into a data store through OCI. For more information on OCI server properties, see the “Using the Graphical User Interface” chapter of the Cisco Prime Access Registrar 9.1 User Guide.
OCI-Accounting
If you use the Oracle Accounting feature, you must configure an OCI-Accounting RemoteServer object. For more information on OCI accounting server properties, see the “Using the Graphical User Interface” chapter of the Cisco Prime Access Registrar 9.1 User Guide.
Prepaid-CRB
The following is the default configuration of a prepaid-crb RemoteServer. The Filename property is the name of the required shared library provided by the billing vendor. See the “Using Prepaid Billing” chapter of the Cisco Prime Access Registrar 9.1 User Guide for more information on Prepaid -CRB.
Prepaid-IS835C
The following is the default configuration of a prepaid-is835c RemoteServer. The Filename property is the name of the required shared library provided by the billing vendor. See the “Using Prepaid Billing” chapter of the Cisco Prime Access Registrar 9.1 User Guide for more information on Prepaid -IS835C.
RADIUS
radius specifies a RADIUS server. When you specify the radius protocol, supply the information in Table 5-43 .
Diameter
Diameter is a networking protocol which is derived from RADIUS protocol. You can configure a Diameter remote server using a set of parameters.
The following is a sample CLI configuration of a Diameter remote server. For details about these parameters, refer to the “Using the Graphical User Interface” chapter of the Cisco Prime Access Registrar 9.1 User Guide.
REST
Prime Access Registrar allows you to configure a REST remote server for extended-EAP service. Extended-EAP is used as an authorization service to retrieve authorization information from the remote web server using the REST interface. Prime Access Registrar processes all EAP requests and extends through extended EAP service. Extended-EAP is supported for the following EAP protocols:
To configure an extended-EAP service, see Extended-EAP.
Table 5-44 lists and describes the REST remote server properties.
The following is a sample CLI configuration of REST remote server for extended-EAP service:
SIGTRAN-M3UA
Prime Access Registrar supports SIGTRAN-M3UA to fetch the authentication vectors from HLR, which is required for EAP-AKA/EAP-SIM authentication. For more information on SIGTRAN-M3UA protocol, see the “SIGTRAN-M3UA” chapter of the Cisco Prime Access Registrar 9.1 User Guide.
Rules
A Rule is a function that selects services based on all input information used by the function.
Fast Rules
FastRules provides a mechanism to easily choose the right authentication, authorization, accounting, and query service(s), drop, reject, or break flows, run a script, choose a session manager and/or a chain of fast rules required for processing a packet. For more information, see the “Using FastRules to Process Packet Flow” chapter of the Cisco Prime Access Registrar 9.1 User Guide.
Advanced
Advanced objects let you configure system-level properties and the Attribute dictionary. Under normal system operation, you should not need to change the system-level properties.
Note The notation required means Cisco Prime Access Registrar needs a value for this property. For most of these properties, you can use system defaults.
Table 5-45 lists the Advanced properties.
|
|
|
|---|---|
Required; the default is FALSE, which means Cisco Prime Access Registrar logs all responses except Access-Accepts and Access-Challenges. Accepting the default reduces the load on the server by reducing that amount of information it must log. Note, the client is probably sending accounting requests to an accounting server, so the Access-Accept requests are being indirectly logged. When you set it to TRUE, Cisco Prime Access Registrar logs all responses to the server log file. |
|
Applicable only for Diameter; Set to TRUE to use TLS version 1.0 and above for Diameter connection. Set to FALSE to use TLS version greater than 1.0 for Diameter connection. |
|
Required; the default is 8192. This is a critical property you should set high enough to allow for the maximum number of simultaneous requests. When more requests come in than there are packets allocated, Cisco Prime Access Registrar will drop those additional requests. |
|
Required; the default is 4096. RFC 2138 specifies the maximum packet length can be 4096 bytes. Do not change this value. |
|
Required; the default value for this property is 4. The NumberOfRemoteUDPServerSockets property allows you to configure the number of source ports used while proxying requests to a remote radius server. If the NumberOfRemoteUDPServerSockets property is set to a value n, all remote servers share and use n sockets. The NumberOfRemoteUDPServerSockets value comprises a number, as in n, where n should be less than or equal to the current process file descriptor limit divided by 4.
Note |
|
This represents the number of RADIUS Identifiers that Prime Access Registrar can use per source port, while proxying requests to remote servers. To use a different source port for every request that is proxied, you need to set the value of this property to one. |
|
This property is used to avoid crashing of the radius process. The default value is 3500 Megabytes. This property is under /radius/advanced. When the radius process uses memory more than the configured limit, further sessions are not created and Prime Access Registrar rejects further incoming requests. |
|
This property is used to avoid crashing of the radius process. This is used in conjunction with MemoryLimitForRadiusProcess. The default value is 5 minutes. MemorySizeCheckInterval is a hidden parameter in mcd database. To modify the default value, you need to export the mcd database. Typically, a separate thread is created to monitor the radius process memory usage for every 5 minutes. |
|
Required; the default is 6500. This property sets the size of the initial heap for each packet. The heap is the dynamic memory a request can use during its lifetime. By preallocating the heap size at the beginning of request processing, we can minimize the cost of memory allocations. If PerPacketHeapSize is too low, Prime Access Registrar will ask the system for memory more often. If PerPacketHeapSize is too high, Prime Access Registrar will allocate too much memory for the request causing the system to use more memory than required. |
|
Required; the default is FALSE. If you accept the default, Cisco Prime Access Registrar only uses the source IP address to identify the immediate client that sent the request. Leaving it FALSE is useful when this RADIUS Server should only know about the proxy server and should treat requests as if they came from the proxy server. This might be the case with some environments that buy bulk dial service from a third party and thus do not need to, or are unable to, list all of the NASs behind the third party’s proxy server. When you set it to TRUE, you must list all of the NASs behind the Proxy in the Clients list. For more information about this property, see Using the RequireNASsBehindProxyBeInClientList Property. |
|
Required; specified in milliseconds, the default is 75. This property governs how often the file AAA service processes accounting requests and writes the accounting records to the file. You can lower the number to reduce the delay in acknowledging the Account-Request at the expense of more frequent flushing of the accounting file to disk. You can raise the number to reduce the cost of flushing to disk, at the expense of increasing the delays in acknowledging the Accounting-Requests. The default value was determined to provide a reasonable compromise between the two alternatives. |
|
Required; specified in milliseconds, the default is 100. If you change this value it must be a number greater than zero. This property governs how often the Session Manager backing store writes updated session information to disk. You can lower the number to reduce the delay in acknowledging requests at the expense of more frequent flushing of the file containing the session data to disk. You can raise the number to reduce the cost of flushing to disk at the expense of increasing delays in acknowledging requests. The default value was determined to provide a reasonable compromise between the two alternatives. |
|
Required; the default is 10 gigabytes. The value of BackingStoreDisc- BackingStoreDiscThreshold is used with session management and ODBC accounting and ensures that any data log files generated will not cross the BackingStoreDiscThreshold. |
|
Required; specifies the sleep time interval of the session backing store pruning thread. The recommended and default value is 6 hours, but you can modify this based on the traffic patterns you experience. With SessionBackingStorePruneInterval set to 6 hours, pruning will occur 6 hours after you restart or reload the Prime Access Registrar server and recur every 6 hours. You can set a very low value for this property to make pruning continuous, but there might not be enough data accumulated for the pruning to occur and pruning might be less effective compared to the default setting. |
|
Required; specifies the sleep time interval of the packet backing store pruning thread. The recommended value is 6 hours, but you can modify this based on the traffic patterns you experience. When PacketBackingStorePruneInterval is set to 6 hours, pruning will occur 6 hours after you restart or reload the Prime Access Registrar server and recur every 6 hours. You can set a very low value for this property to make pruning continuous, but there might not be enough data accumulated for the pruning to occur and pruning might be less effective compared to the default setting. |
|
Required; specified in milliseconds, the default is 10. This property governs how often the ldap RemoteServer thread checks to see if any results have arrived from the remote LDAP server. You can modify it to improve the throughput of the server when it proxies requests to a remote LDAP server. |
|
Required; specified in milliseconds, the default is 10. This property governs how often the sigtran RemoteServer thread checks to see if any results have arrived from the remote HLR/AuC server. You can modify it to improve the throughput of the server when it proxies requests to a remote sigtran server. |
|
Required; the default is 5. This property specifies the amount of time the time queue should initially sleep before beginning processing. This property is only used for initial synchronization and should not be changed. |
|
Required; the default is 65536 (64 K). This property governs how deep the system’s buffer size is for queueing UDP datagrams until Cisco Prime Access Registrar can read and process them. The default is probably sufficient for most sites. You can, however, raise or lower it as necessary. |
|
Required if you are using an LDAP RemoteServer and you want Prime Access Registrar to use SSL when communicating with that LDAP RemoteServer. This property specifies the path to the directory containing the client certificates to be used when establishing an SSL connection to an LDAP RemoteServer. This directory must contain the cert7.db and cert5.db certificates and the key3.db and key.db files database used by Netscape Navigator 3.x (and above) or the ServerCert.db certificate database used by Netscape 2.x servers. |
|
Required; the default is 1 Megabyte. This property specifies the maximum size of the RADIUS server log file. The value for the LogFileSize field is a string composed of two parts; a number, and a units indicator (<n> <units>) in which the unit is one of: K, kilobyte, kilobytes, M, megabyte, megabytes, G, gigabyte, or gigabytes. The LogFileSize property does not apply to the config_mcd_1_log or agent_server_1_log files. See Cisco Prime Access Registrar 9.1 Reference Guide to configure these files. |
|
Required; the default is 2. This property specifies the number of log files to be kept on the system. A new log file is created when the log file size reaches LogFileCount. The LogFileCount property does not apply to the config_mcd_1_log or agent_server_1_log files. See Cisco Prime Access Registrar 9.1 Reference Guide to configure these files. |
|
Required; the default is 1 GB. This property specifies the size of the trace files to be kept on the system. A new trace file is created when the trace file size reaches Trace FileSize. The value for the Trace FileSize field is a string composed of two parts; a number, and a units indicator (<n> <units>) in which the unit is one of: K, kilobyte, kilobytes, M, megabyte, megabytes, G, gigabyte, or gigabytes. |
|
Required; this value can be set from 1-100, and the default is 2. This property specifies the number of trace files to maintain. A value of 1 indicates that no file rolling occurs. |
|
Required; the default is FALSE. Set this property to TRUE when you want Cisco Prime Access Registrar to use a more robust duplicate request filtering algorithm. For more information on this property, see Advance Duplicate Detection Feature. |
|
Required when the Advanced Duplicate Detection feature is enabled. This property specifies how long (in milliseconds) Cisco Prime Access Registrar should remember a request. You must specify a number greater than zero. The default is 10,000. |
|
Optional; used to detect accounting packets that arrive out of sequential order. The default is FALSE. This property is useful when using accounting and session management in a RADIUS proxy service. When the DetectOutOfOrderAccountingPacket property is enabled (set to TRUE), a new Class attribute is included in all outgoing Accept packets. The value for this Class attribute will contain the session magic number. The client will echo this value in the accounting packets, and this will be used for comparison. The session magic number is a unique number created for all sessions when the session is created or reused and the DetectOutOfOrderAccountingPacket property is set to TRUE. The DetectOutOfOrderAccountingPacket property is used to detect out-of-order Accounting-Stop packets in roaming scenarios by comparing the session magic number value in the session with the session magic number value contained in the Accounting packet. The value of 0xffffffff is considered by the Prime Access Registrar server to be a wild card magic number. If any accounting stop packets contain the value of 0xffffffff, it will pass the session magic validation even if the session’s magic number is some thing else. The format of the class attribute is as follows: <4-byte Magic Prefix><4-byte server IP address><4-byte Magic value> |
|
Optional; used with the ODAP feature and reflects the returned size of the subnet if no matched subnet is found. There are three options to select if an exactly matched subnet does not exist: Bigger, Smaller, and Exact. The default is Bigger. |
|
A string which is the classpath to be used to locate Java classes and jar files containing the classes required for loading the Java extensions, either Java extension points or services. Note The classpath will always contain the directory $INSTALLDIR/scripts/radius/java and all of the jar files in that directory. |
|
A string that can contain options to be passed to the JRE upon startup. JavaVMOptions should be used only when requested by Cisco TAC. |
|
Specifies maximum size in bytes for an ODBC mapping. This parameter affects both ODBC result sizes and the trace log buffer for tracing script calls that access any of the dictionaries. (Default value is 256.) |
|
When set to FALSE, requires that you provide exact pathnames with regard to upper and lower case for all objects, subobjects, and properties. The default setting, TRUE, allows you to enter paths such as /rad/serv instead of /Rad/Serv. Note Prime Access Registrar always authenticates the RADIUS attribute User-Name with regard to upper and lower case, regardless of the setting of this flag. |
|
When set, specifies the local interface to bind to when creating the RemoteRadiusServer socket. If not set, the Prime Access Registrar binds to IPADDR_ANY. |
|
Optional; allows you to specify a character that separates multivalued attributes in the marker list when using ODBC accounting |
|
The minimum value is 1 and the maximum is a 32-bit unsigned integer. The default is 75. |
|
Must be set to TRUE when using the Change of Authorization (CoA) feature or Packet of Disconnect (POD) feature. Default is FALSE. |
|
Required when using identity caching. Indicates the maximum number of XML packets to be sent or received. The minimum value is 1 and the maximum is a 32-bit unsigned integer. The default is 1024. |
|
Required when using identity caching. Indicates the maximum size of XML packets to be sent or received. The minimum value is 1 and the maximum is a 32-bit unsigned integer. The default is 4096. |
|
Used in conjunction with the session-cache ResourceManager, this property specifies the length of time a given EncryptionKey will be used before a new one is created. When the session-cache ResourceManager caches User-Password attributes, Prime Access Registrar encrypts the User-Password so it is not stored in memory or persisted on disk in clear text. Prime Access Registrar uses up to 255 encryption keys, using a new one after each RollingEncryptionKeyChangePeriod expires. If RollingEncryptionKeyChangePeriod is set to 2 days, Prime Access Registrar will create and begin using a new EncryptionKey every two days. The oldest key will be retired, and Prime Access Registrar will re-encrypt any User-Passwords that used the old key with the new key. This way, if the RollingEncryptionKeyChangePeriod is set to 1 day, no key will be older than 255 days. |
|
Optional; the SessionPurgeInterval property determines the time interval at which to check for timed-out sessions. If no value is set, the session timeout feature is disabled. The checks are performed in the background when system resources are available, so checks might not always occur at the exact time set. The minimum recommended value for SessionPurgeInterval is 60 minutes. The SessionPurgeInterval value is comprised of a number and a units indicator, as in n units, where a unit is one of minutes, hours, days, or weeks. |
|
Set to one of two values: SilentDiscard (the default) or RejectFailure. When set to SilentDiscard, the Prime Access Registrar server silently discards and ignores bad EAP messages unless the protocol specification explicitly requires a failure message. When set to RejectFailure, the Prime Access Registrar server sends RADIUS Access-Rejects messages with embedded EAP-Failure in response to bad EAP messages as described in Internet RFC 3579. |
|
Required; the default value is “1 hour.” Specifies the time interval to maintain a session when a client does not respond to Accounting-Stop notification. When the Prime Access Registrar server does not receive an Accounting-Response from a client after sending an Accounting-Stop packet, Prime Access Registrar maintains the session for the time interval configured in this property before releasing the session. This property is stored as a string composed of two parts: a number and a unit indicator (<n> <units>) similar to the MaxFileAge property where the unit is one of: M, Minute, Minutes, H, Hour, Hours, D, Day, Days, W, Week, or Weeks. |
|
Optional; allows you to use ports other than the default, 1812 and 1813. You can use this option to configure Prime Access Registrar to use other ports,. If you add additional ports, however, Prime Access Registrar will use the added ports and no longer use ports 1812 and 1813. These ports can still be used by adding them to the list of ports to use. For more information, see Ports. |
|
Optional; see Interfaces |
|
Optional; see Reply Messages. |
|
Optional; see Attribute Dictionary. |
|
Optional; see SNMP. |
|
Optional; enables you to modify the Prime Access Registrar server to behave in a way that might deviate from RFC compliance in a special use case scenario. When AllowRejectAttrs is set to FALSE, Reply-Message attributes will not be passed in an Access Reject packet. When AllowRejectAttrs is set to TRUE, attributes will be allowed to pass in an Access Reject packet. When AllowEAPRejectAttrs is set to FALSE, Reply-Message attributes will not be passed in an Access Reject packet if the packet contains EAP-Message attribute. When AllowEAPRejectAttrs is set to TRUE, attributes will be allowed to pass in an Access Reject packet even if the packet contains EAP-Message attribute. Note Changing the state of either of these properties requires you to reload the Prime Access Registrar server. |
|
This subdirectory holds the SynthesizeReverseZone property and a list of Transaction Signatures (TSIG) keys. |
|
This property exists under DDNS and controls whether Prime Access Registrar automatically generates the name of the reverse zone (in-addr.arpa) that is updated with PTR records. If this attribute is enabled and the resource manager does not have an explicit ReverseZoneName property configured, the server uses the IP address and DNSHostBytes property to generate the reverse zone name. The default value is TRUE. |
|
A list of ODBC data sets and their associated environments including operating system, DBMS, and network platform used to access the DBMS an application wants to access. Required when using or ODBC accounting. |
|
Includes a Default subdirectory with an Attributes subdirectory that contains commonly-used attributes for Change of Authorization (CoA) and Packet of Disconnect (POD). You can add new attributes to the default group or create a new group as necessary. |
|
Used to protect the security and integrity of the PACs it issues. |
|
Optional; the default value for this property is 0. The MaximumIncomingRequestRate property is used to limit the incoming traffic in terms of “allowed requests per second”. Serves as a soft limit. The MaximumIncomingRequestRate property comprises a number n, where n can be any nonzero value. |
|
Required; the default value is TRUE. The HideSharedSecretAndPrivateKeys property hides:
When this property is set to TRUE, the following properties are displayed as <encrypted>: – – –
When the value for this property is set to FALSE, all the above properties are displayed in clear text. |
|
Optional; the default value for this property is 0. The MaximumOutstandingRequests property is used to limit the incoming traffic in terms of “requests processed”. Serves as a hard limit. The MaximumOutstandingRequests property comprises a number n, where n can be any nonzero value. |
|
Required; See Diameter |
|
This represents the sampling period in seconds. The minimum sampling period is set to 5. The default is 30. |
|
When set to true this property enables to log in the TPS usage in a CSV file.The TPS is logged in the following format: <mm-dd-yyyy>, <hh:mm:ss>, <tps-value>, <sigtran-m3ua traffic value> |
|
This represents the prefix of the CSV file which will be available in the logs directory of Prime Access Registrar. The following represents the CSV filename format: |
|
Configures the number of TPS Sampling log files to be maintained in the repository. The default value is 2. |
|
When set to TRUE, this property enables Prime Access Registrar to log the session count in the server. |
|
Required only if you set LogSessionActivity to TRUE; the number of session log files to maintain in the repository. The default value is 2. |
|
Required only if you set LogSessionActivity to TRUE; this represents the prefix of the session log file which will be available in the logs directory of Prime Access Registrar. |
|
Required only if you set LogSessionActivity to TRUE; this represents the session sampling period in seconds. The minimum sampling period is set to 5. The default is 30. |
|
Set to TRUE to allow Prime Access Registrar to flush the accounting record to disk before it acknowledges the request packets. |
|
Optional; used to disconnect ODBC Remote Servers when configured native Oracle Error has occurred (which are not considered as connection errors). You must specify Native Errors as comma (,) separated integer values. 04/14/2013 11:06:43.692: Log: ODBC client (DataSource 'CVOracleAcctDb', Connection 6): SQLExecute failed: SQLState:HY000 NativeError:12152 ErrorText:[Easysoft][Oracle]ORA-12152: TNS:unable to send break message 04/14/2013 10:44:59.388: Log: ODBC client (DataSource 'CVOracleAcctDb', Connection 3): SQLExecute failed: SQLState:HY000 NativeError:3114 ErrorText:[Easysoft][Oracle]ORA-03114: not connected to ORACLE For the above examples, the Native Errors need to be configured as follows: --> set AdditionalNativeOracleErrors 12152,3114 When any one of the Native Errors 12152 or 3114 occurs, Prime Access Registrar disconnects the ODBC Remote Server. |
|
When set to TRUE, this property enables to log the SIGTRAN stack logs in stack.log file. |
|
Required if you set EnableSIGTRANStackLogs to TRUE. This property specifies the maximum size (in megabyte) of the SIGTRAN stack log file. |
|
Required if you set EnableSIGTRANStackLogs to TRUE. This value can be set from 1–100, and the default is 10. This property specifies the number of SIGTRAN log files to maintain in the repository. |
|
Required; either True or False and the default value is True. When set to True, Prime Access Registrar displays the peer specific stats showing the number of sticky sessions associated with a peer for Diameter proxy service in name_radius_log file. |
|
Required; specified in milliseconds and the default is 60000. When the EnableStickySessionCount is set to True, this field specifies how often the Diameter proxy service will display the number of sticky sessions associated with a peer. |
|
Required; specified in milliseconds and the default value is 500. Specifies how often the Diameter proxy service will write the sticky sessions to a file located in /cisco-ar/temp/__sticky_sessions_store location. |
|
Percentage of the RADIUS packet pool to reserve for the RADIUS remote server responses. |
|
Check the box to enable location-based attributes within RADIUS and Diameter that can be used to convey location-related information for authentication and accounting exchanges. If this parameter is set to TRUE, Prime Access Registrar retrieves the location information from the client and processes the incoming packet for AA services. For more information on location information delivery flows, refer to RFC 5580. For information on location-based attributes in Prime Access Registrar, see the “Environment Dictionary” chapter of the Cisco Prime Access Registrar 9.1 Reference Guide. |
|
The time at which Prime Access Registrar must run the Diameter session restoration process. Format is HH:MM:SS (24 hrs format) and default value is 02:00:00. Recommended time is when the incoming traffic is minimal. Note This time should always be two hours behind the Diameter stale session purge time. |
|
The time at which Prime Access Registrar must check for Diameter stale sessions. Format is HH:MM:SS (24 hrs format) and default value is 00:00:00. |
The following CLI shows an example configuration of Advanced properties:
This section contains the following topics:
- RemoteODBCSessionServer
- Using the RequireNASsBehindProxyBeInClientList Property
- Advance Duplicate Detection Feature
- Invalid EAP Packet Processing
- Ports
- Interfaces
- Reply Messages
- Attribute Dictionary
- SNMP
- Diameter
RemoteODBCSessionServer
The following is an example of theRemoteODBCSessionServer configuration:
--> cd /Radius/Advanced/RemoteODBCSessionServer/
Table 5-46 lists and defines the RemoteODBCSessionServer properties.
|
|
|
|---|---|
Mandatory time interval (in milliseconds) to activate an inactive server; defaults to 300000 ms |
|
Mandatory time interval (in seconds) to wait for SQL operation to complete; defaults to 15 seconds |
|
Mandatory number of connections to be established; defaults to 8 |
|
Name of the ODBCDataSource to use and must refer to one entry in the list of ODBC datasources configured under /Radius/Advanced/ODBCDataSources. Mandatory; no default |
|
Mandatory time interval (in milliseconds) to send a keepalive to keep the idle connection active; defaults to zero (0) meaning the option is disabled |
|
Mandatory, TRUE or FALSE, determines whether to buffer the accounting packets to local file, defaults to TRUE which means that packet buffering is enabled. Note When set to TRUE, a constant flow of incoming accounting packets can fill the buffer backing store files in /cisco-ar/data/odbc beyond the size configured in MaximumBufferFileSize. Configure BackingStoreDiscThreshold in /Radius/Advanced when using ODBC accounting. See Advanced for information about how to configure BackingStoreDiscThreshold. |
|
Mandatory if BufferAccountingPackets is set to TRUE, determines the maximum buffer file size, defaults to 10 Megabyte) |
|
Default is 250000; This represents the overall limit on cache of all 'remote' session managers. This value is interpreted as the maximum number of packets that can be present in cache. When the number of sessions hits this limit, sessions will be 'cached out'. This cache out operation will continue, until the cache is at least 20% free. |
|
If set to 1, it enables a fast cache based lookup index for the items in the database. This optimizes the number of queries to the database hence will improve performance, but limits the number of sessions that can be scaled. |
Note Remote session manager will work only with Oracle database.
Using the RequireNASsBehindProxyBeInClientList Property
You can use the property RequireNASsBehindProxyBeInClientList to require NASs that send requests indirectly through a proxy to be listed in the Clients list or to allow the proxy to represent them all.
- When you want to ensure the proxy is only sending requests from NASs known to this server, set the property to TRUE, and list all of the NASs using this proxy. This increases memory usage.
- When it is impossible to know all of the NASs using this proxy or when you do not care, set the property to FALSE. Cisco Prime Access Registrar will use the proxy’s IP address to identify the origin of the request.
Advance Duplicate Detection Feature
Prime Access Registrar automatically detects and handles duplicate requests it is currently working on. It also provides an optional, more complex mechanism to handle duplicate requests that can be received by the server after it has completed processing the original request. These duplicate requests can consume extra processing power, and, if received out of order (as RADIUS is a UDP-based protocol) might cause Session Management problems.
One solution is the Advanced Duplicate Detection feature which causes Prime Access Registrar to remember requests it has seen, as well as the response sent to that request, for a configurable amount of time.
To enable this feature, perform the following:
- Set the UseAdvancedDuplicateDetection property in the /Radius/Advanced section of the configuration to TRUE.
- Set the AdvancedDuplicateDetectionMemoryInterval in the /Radius/Advanced section to specify how long (in milliseconds) Prime Access Registrar should remember a request.
Note Enabling this feature causes Cisco Prime Access Registrar to keep more of its preallocated packet buffers in use for a longer period of time. The number of preallocated buffers is controlled by the MaximumNumberOfRadiusPackets property in the /Radius/Advanced section of the configuration. This property might need to be increased (which will increase the amount of memory used by Cisco Prime Access Registrar) when the Advanced Duplicate Detection feature is enabled.
Invalid EAP Packet Processing
Prime Access Registrar has been enhanced to implement fatal error packet handling for Extensible Authentication Protocol (EAP) messages as described in section 2.2 of Internet RFC 3579 which states the following:
A RADIUS server determining that a fatal error has occurred must send an Access-Reject containing an EAP-Message attribute encapsulating EAP-Failure.
Because this enhancement is a deviation from various EAP specifications, you must explicitly enable this feature through a new configuration property in /Radius/Advanced named EapBadMessagePolicy .
You can set the EapBadMessagePolicy property to one of two values: SilentDiscard (the default) or RejectFailure. When set to SilentDiscard, the Prime Access Registrar server silently discards and ignores bad EAP messages unless the protocol specification explicitly requires a failure message. When set to RejectFailure, the Prime Access Registrar server sends RADIUS Access-Rejects messages with embedded EAP-Failure in response to bad EAP messages as described in Internet RFC 3579.
The implementation of EAP authentication methods in Prime Access Registrar behaves as described in Internet RFC 2284 (EAP) and related EAP method specifications. These specify silent discard as the standard way to handle all EAP error conditions. Any EAP response message from the client that contains an error or is received in an invalid authenticator state is discarded and there is no error response.
In a configuration where EAP requests are proxied between RADIUS servers using RADIUS messages (EAP over RADIUS), the silent discard of an EAP message means that no RADIUS response message is sent back to the originating RADIUS server. Because of this, the RADIUS server originating the request eventually declares the destination RADIUS server dead and fails over to a backup server (if so configured).
Ports
The Ports list specifies which ports to listen to for requests. When you specify a port, Cisco Prime Access Registrar makes no distinction between the port used to receive Access-Requests and the port used to receive Accounting-Requests. Either request can come in on either port.
Most NASs send Access-Requests to port 1812 and Accounting-Requests to 1813, however, Cisco Prime Access Registrar does not check.
When you do not specify any ports, Cisco Prime Access Registrar reads the /etc/services file for the ports to use for access and accounting requests. If none are defined, Prime Access Registrar uses the standard ports (1812 and 1813).
Interfaces
The Interfaces list specifies the interfaces on which the RADIUS server receives and sends requests. You specify an interface by its IP address.
- When you list an IP address, Cisco Prime Access Registrar uses that interface to send and receive Access-Requests.
- When no interfaces are listed, the server performs an interface discover and uses all interfaces of the server, physical and logical (virtual).
Note The IP address format is enhanced to support both IPv4 and IPv6.
Reply Messages
The Reply Messages list allows you to choose the reply message based on the reason the request was rejected. Each of the following properties (except Default) corresponds to a reason why the packet was rejected. The Reply Message properties allows you to substitute your own text string for the defined errors. After you set the property (with the set command) and the reason occurs, Cisco Prime Access Registrar sends the NAS that message in the Access-Reject packet as a Reply-Message attribute.
You might want to substitute your own messages to prevent users from getting too much information about why their requests failed. For example, you might not want users to know the password was invalid to prevent hackers from accessing your system. In such a case, you might specify the text string “ unauthorized access ” for the property UserPasswordInvalid.
Table 5-47 lists the Reply Message properties.
Attribute Dictionary
The Attribute dictionary allows you to specify the attributes to the RADIUS server. Cisco Prime Access Registrar comes with the standard RADIUS attributes (as defined by the RFC 2865) as well as the attributes required to support the major NASs. For more information about the standard attributes, see “RADIUS Attributes” chapter of the Cisco Prime Access Registrar 9.1 Reference Guide.
All RADIUS requests and responses consist of one or more attributes, such as the user’s name, the user’s password, the type of service the NAS should provide to the user, or the IP address the user should use for the session.
In the request and response packets, an attribute is composed of a number (between 1-255) that specifies the type of attribute to use, a length that specifies the entire attribute length, and a value. How the value is interpreted depends on its type. When it is a username, the value is a string. When it is the NAS’s IP address, the value is an IP address, and so on.
Table 5-48 lists the Attribute dictionary properties.
|
|
|
|---|---|
Required; must be unique in the Attribute dictionary list within the same context. Although it should be an attribute defined in the RFC, the name can be any attribute defined by your client. The NAS typically comes with a list of attributes it uses. Attributes are referenced in the Profile and by Scripts by this name. The accounting file service also uses this name when printing the attribute. |
|
Required; must be a number between 1-255. It must be unique within the Attribute dictionary list. |
|
Required; must be set to one of the types listed in Table 5-49 . The type governs how the value is interpreted and printed. |
Types
Types are required and must be one of the following listed in Table 5-49 .
Vendor Attributes
Table 5-50 lists the Vendor properties.
SNMP
Table 5-51 lists the five properties of the SNMP directory.
|
|
|
|---|---|
If Enabled and MasterAgentEnabled are both TRUE, arservagt will start and stop the SNMP daemon (snmpd). If either of these properties is FALSE, if the Prime Access Registrar server is not using SNMP or if your site uses a different master agent, arservagt will not start your master agent.
Diameter
This section explains how to configure Diameter general configuration and transport management.
Change the directory to /Radius/Advanced/Diameter.
The following configuration is used to configure Diameter general configuration like Product name and Version.
Table 5-52 describes the Diameter general properties.
Configuring Diameter Transport Management Properties
The following example shows the Diameter transport management configuration:
Table 5-53 describes the Diameter transport management properties.
Configuring Diameter Session Management
The following example shows the Diameter session management configuration:
Table 5-54 describes the Diameter Session Management properties.
Configuring Diameter Application
Table 5-55 describes the Diameter Application properties.
Configuring the Diameter Application
To configure the Diameter application:
Step 1 Move to //localhost/Radius/Advanced/Diameter/Applications directory:
Step 2 Add the application you want to add ( eg: NASREQ).
Step 3 Set the ApplicationId and ApplicationURI.
set ApplicationURL "ftp://ftp.ietf.org/internet-drafts/draft-ietf-aaa-diameter-nasreq-12.txt"
Step 4 Add the list of commands for this application.
Configuring Diameter Commands
Table 5-56 describes the Diameter command properties.
Configuring the Diameter Commands
To configure the Diameter commands:
Step 1 Change to /Radius/Advanced/Diameter/Commands.
Step 3 Set the properties for AA command.
Step 4 Configure the RequestMsgAVP's for the command.
Add Fixed AVP's for the request message.
Maximum and Minimum property specifies the multiplicity of the AVP Inside a request (or response). Similarly add the required and Optional AVP's.
Step 5 Configure AnswerMsgAVP's similar to step 3.
The following shows an example of NASREQ application configuration:
The following shows an example of the AA command configuration:
Configuring Diameter Dictionary
The Diameter dictionary contains a list of application specific AVPs.
Table 5-57 describes the Diameter BaseProtocol AVP Properties.
|
|
|
|---|---|
Required; default is FALSE. If set to FALSE, the application is ordinary application and user is prompted to enter ApplicationID. If set to TRUE, the application is a VendorSpecific Application. User is prompted to enter VendorSpecificApplicationID and VendorID. |
|
Required; specifies the unique integer value for the application. Note The Application ID must be set to 0 for BaseProtocol AVPs. |
|
Required, Specifies the integer value for the vendor specific application. |
|
Specifies the list of application specific avps. Refer to Table 5-58 for the description of AVP properties. |
Table 5-58 lists the application specific AVP properties.
Configure the Diameter Dictionary
To configure the Diameter Dictionary:
Step 1 Change to /Radius/Advanced/Diameter/Diameter Dictionary.
Step 3 Set the properties for BaseProtocolAVPs.
Step 4 Configure the application specific AVPs.
Step 5 Configure User-Name AVP type and number
The following is an example of Diameter BaseProtocol AVPs:
Feedback