- Preface
- Chapter 1 Overview
- Chapter 2 Using the aregcmd Commands
- Chapter 3 Using the Graphical User Interface
- Chapter 4 Cisco Prime Access Registrar Server Objects
- Chapter 5 Using the radclient Command
- Chapter 6 Configuring Local Authentication and Authorization
- Chapter 7 RADIUS Accounting
- Chapter 8 Diameter
- Chapter 9 Extensible Authentication Protocols
- Chapter 10 Using WiMAX in Cisco Prime Access Registrar
- Chapter 11 Using Extension Points
- Chapter 12 Using Replication
- Chapter 13 Using On-Demand Address Pools
- Chapter 14 Using Identity Caching
- Chapter 15 Using Trusted ID Authorization with SESM
- Chapter 16 Using Prepaid Billing
- Chapter 17 Using Cisco Prime Access Registrar Server Features
- Chapter 18 Directing RADIUS Requests
- Chapter 19 Wireless Support
- Chapter 20 Using LDAP
- Chapter 21 Using Open Database Connectivity
- Chapter 22 SIGTRAN-M3UA
- Chapter 23 Using SNMP
- Chapter 24 Enforcement of Licensing Models
- Chapter 25 Backing Up the Database
- Chapter 26 Using the REX Accounting Script
- Chapter 27 Logging Syslog Messages
- Chapter 28 Troubleshooting Cisco Prime Access Registrar
- Appendix A: Cisco Prime Access Registrar Tcl, REX and Java Dictionaries
- Appendix B: Environment Dictionary
- Appendix C: RADIUS Attributes
- Glossary
- Index
Using the Graphical User Interface
Cisco Prime Access Registrar (Cisco Prime AR) is a Remote Authentication Dial-In User Service (RADIUS) server that enables multiple dial-in Network Access Server (NAS) devices to share a common authentication, authorization, and accounting database.
This chapter describes how to use the standalone graphical user interface (GUI) of Cisco Prime AR to:
•
Configure Cisco Prime Access Registrar
•
Manage Network Resources managed by Cisco Prime AR
•
Administer Cisco Prime AR related activities
The following topics help you to work with and understand the Cisco Prime AR GUI:
•
Configuring Cisco Prime Access Registrar
Launching the GUI
Cisco Prime AR requires you to use Microsoft Internet Explorer 8.0 SP1 (Windows 2000 and Windows XP). You start the GUI by pointing your browser to the Cisco Prime AR server and port 8080, as in the following:
http://ar_server_name:8080
Note
You can also use Mozilla Firefox 16.0 and Google Chrome 22.0 browsers to launch the Cisco Prime AR GUI.
To start a secure socket layer (SSL) connection, use https to connect to the Cisco Prime AR server and port 8443, as in the following:
https://ar_servr_name:8443
By default, both HTTP and HTTPS are enabled. The following sections describe how to disable HTTP and HTTPS:
Note
For proper function of Cisco Prime AR GUI, the DNS name resolution for the server's hostname should be defined precisely.
Disabling HTTP
To disable HTTP access, you must edit the server.xml file in the /cisco-ar/apache-tomcat-5.5.27/conf directory. You must have root privileges to edit this file.
Use a text editor such as vi to open the server.xml file, and comment out lines 96-99. Use the <!-- character sequence to begin a comment. Use the --> character sequence to end a comment.
The following are lines 93-99 of the server.xml file:
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<!-- CHANGE MADE: Note: to disable HTTP, comment out this Connector -->
<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="150 minSpare/Threads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />
The following example shows these lines with beginning and ending comment sequences to disable HTTP:
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<!-- CHANGE MADE: Note: to disable HTTP, comment out this Connector -->
<!--
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="60000"/>
-->
After you modify the server.xml file, you must restart the Cisco Prime AR server for the changes to take effect. Use the following command line to restart the server:
/opt/CSCOar/bin/arserver restart
Disabling HTTPS
To disable HTTPS access, you must edit the server.xml file in the /cisco-ar/apache-tomcat-5.5.27/conf directory. You must have root privileges to edit this file.
Use a text editor such as vi to open the server.xml file, and comment out lines 116-121. Use the <!-- character sequence to begin a comment. Use the --> character sequence to end a comment.
The following are lines 111-121 of the server.xml file:
<!-- Define an SSL HTTP/1.1 Connector on port 8443 -->
<!-- CHANGE MADE: enabled HTTPS.
Note: to disable HTTPS, comment out this Connector -->
<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="true" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false"
keystoreFile="/cisco-ar/certs/tomcat/server-cert.p12"
keystorePass="cisco" keystoreType="PKCS12" sslProtocol="TLS" />
</Connector>
The following example shows these lines with beginning and ending comment sequences to disable HTTPS.
<!-- Define an SSL HTTP/1.1 Connector on port 8443 -->
<!-- CHANGE MADE: enabled HTTPS.
Note: to disable HTTPS, comment out this Connector -->
<!--
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8443" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="10" debug="0" scheme="https" secure="true">
<Factory className="org.apache.catalina.net.SSLServerSocketFactory"
keystoreFile="/cisco-ar/certs/tomcat/server-cert.p12"
keystorePass="cisco" keystoreType="PKCS12"
clientAuth="false" protocol="TLS"/>
</Connector>
-->
After you modify the server.xml file, you must restart the Cisco Prime AR server for the changes to take effect. Use the following command line to restart the server:
/opt/CSCOar/bin/arserver restart
Login Page
The login page has fields for a username and password. This page displays when you first attempt to log in to the system, if a session times out, or after you log out of the system.
Logging In
Users who are configured as Administrators can log into the Cisco Prime AR server.
Logging in
To log into the Cisco Prime AR GUI:
Step 1
Enter the relevant url in the browser. The Cisco Prime AR Login page is displayed.
Step 2
Enter the credentials in the provided fields.
Step 3
Click Login. The Cisco Prime AR main page is displayed.
Note
After installation of Cisco Prime AR server, when you log into the application for the first time, the application redirects to the change password page.
Refreshing the pages using the GUI
To stop the server (when it is running), and then immediately start the server, click the Reload link.
Restarting the GUI
To restart the Cisco Prime AR server, click the Restart link.
Applying different Themes for the GUI
To apply various themes for the Cisco Prime AR main page:
Step 1
Click the Themes link at the top right corner of the Cisco Prime AR main page.
Step 2
Choose a theme from the list that you want to apply for the main page. The selected theme will be applied for the Cisco Prime AR main page.
Note
If aregcmd interface is active, then it needs to be closed for restarting the Cisco Prime AR server.
Logging Out
To log out of the Cisco Prime AR GUI, click the Logout in the upper right portion of the Cisco Prime AR GUI window.
Common Methodologies
This section explains the operations that are common across the GUI interface of Cisco Prime AR. The functions explained in this section are referred throughout to this help system.
This section describes the following:
•
Setting Record Limits per Page
•
Performing Common Navigations
Filtering Records
To filter a record:
Step 1
Navigate to the required page. For example, select Configuration > Profile. The Profile page is displayed.
Step 2
Enter the known details of the record in the Filter text box.
Step 3
Click Go. The matching records are displayed in the search criteria below.
Step 4
Click Clear Filter to clear the performed filter.
You can also perform the following:
•
Setting Record Limits per Page
•
Performing Common Navigations
Editing Records
To edit the required records:
Step 1
Navigate to the required page.
Step 2
Search for a record using the filter option, if required.
Step 3
Choose the required record that you want to edit.
Step 4
Click Edit. The selected record details are displayed in the appropriate page.
Step 5
Make the necessary changes.
Step 6
Click Submit or Update to save the details. The page is displayed with the updated details and a message is prompted. Otherwise click Cancel to return to the page without saving the details.
You can also perform the following:
•
Setting Record Limits per Page
•
Performing Common Navigations
Deleting Records
To delete a record:
Step 1
Navigate to the required page. For example, choose Configuration > Profile. The Profile page is displayed.
Step 2
Search for a record using the filter option, if required.
Step 3
Choose the check box against the record that you want to delete.
Step 4
Click Delete. A message is displayed on successful deletion of the record.
You can also perform the following:
•
Setting Record Limits per Page
•
Performing Common Navigations
Setting Record Limits per Page
To set the numbers of records to be displayed per page, select the record limit from the list available and click the Go button. The available denominations are 10, 25, 50, 100, and All.
You can also perform the following:
•
Performing Common Navigations
Performing Common Navigations
On existence of more records that cannot be accommodated in a page, the records are displayed in multiple pages. Table 3-1 describes the icons used for page navigation.
.
|
|
|
|---|---|
|
To view the next page |
|
To return back to previous page |
|
To view the last page |
|
To return to the first page |
You can also perform the following:
•
Setting Record Limits per Page
Relocating Records
Table 3-2 describes the icons used for relocating records.
You can also perform the following:
•
Setting Record Limits per Page
•
Performing Common Navigations
Dashboard
The dashboard of the Cisco Prime AR GUI shows you the overview on the status on the server and user session details. It consists of the three tabs: Server Status, User Sessions, and System Information.
The Server Status provides the following details:
•
AAA Server status— includes the AAA Process, Process ID, and Status.
•
Health status of the AAA Server— the status of the AAA Server with respect to the performance condition is displayed.
The User Sessions consists of three graphs.
•
Number of Sessions versus Duration in Weeks
•
Number of Sessions versus Duration in Days
The Number of Sessions vs Duration in Weeks report provides the session details with respect to the number of weeks for which it is queried. The Number of Sessions vs Duration in Days report provides the session details with respect to the number of days for which it is queried. The Time(mins) vs Username report provides the accumulated time with respect to the selected username. This report can also be viewed in the form of chart and grid. Click the relevant icons below the graph to view the details in the respective formats.
The System Information tab consists of two graphs:
•
Disk Availability for Cisco Prime AR Directory
•
CPU Utilisation
The Disk Availability for Cisco Prime AR Directory report provides the details of the available disk space and used disk space in the Cisco Prime AR directory. When you hover the mouse on the pie chart, the details of the disk space are displayed. The CPU Utilisation report provides the utilization of the CPU for a specific time. The CPU usage is represented in kilobits per seconds.
Sessions
The Sessions feature of the dashboard helps you in viewing the records based on session id. Table 3-3 lists and describes the various session views in the page.
To view sessions details:
Step 1
Choose Dashboard > Sessions. The Sessions page appears.
Step 2
Choose the required session id to view Release, Release All, Send CoA, Send PoD, and Query All Session details. The session details are displayed as described in the above table.
Note
You can locate the session id using the filter option. See Filtering Records for more details.
Configuring Cisco Prime Access Registrar
Cisco Prime AR's operation and configuration are based on a set of objects. On configuring the Cisco Prime AR major components, the server objects can be created. These objects include the following:
•
RADIUS— the root of the configuration hierarchy
•
Profiles—contains individual Profiles
•
UserGroups—contains individual UserGroups
•
UserList—contains individual UserLists which in turn contain users
•
Users—contains individual authentication or authorization details of a user
•
Scripts—contains individual Scripts
•
Clients—contains individual Clients
•
Policies—contains a set of rules applied to an Access-Request
•
Services—contains individual Services
•
Replication—maintains identical configurations on multiple machines simultaneously
•
RADIUS Dictionary—passes information between a script and the RADIUS server, or between scripts running on a single packet
•
Vendor Dictionary—allows to maintain the attributes of the vendor with respect to vendor id, vendor type and the attributes required to support the major NAS
•
Vendor Attributes—communicates prepaid user balance information from the Cisco Prime AR server to the AAA client, and actual usage, either interim or total, between the NAS and the Cisco Prime AR server
•
Vendors—contains individual Vendors
•
Translations—adds new attributes to a packet or change an existing attribute from one value to another.
•
Translation Groups—add translation groups for different user groups
•
Session Managers—contains individual Session Managers
•
Resource Manager—contains individual Resource Managers
•
Remote Servers—contains individual Remote Servers
•
DIAMETER—contains SessionManagement, Applications, and Commands
•
Advanced—contains Ports, Interfaces, Reply Messages, and the Attribute dictionary
•
Rules—allows to set rules for service selection
RADIUS
The Radius object is the root of the hierarchy. For each installation of the Cisco Prime AR server, there is one instance of the Radius object. You reach all other objects in the hierarchy from the Radius.
Table 3-4 lists and describes the fields in the Radius Properties page.
Note
Fields which are represented with the term "required" in the windows of the Cisco Prime AR GUI, denote mandatory input.
Setting Up or Changing the Radius Properties
To set or change the Radius properties:
Step 1
Choose Configuration > Radius. The Radius Properties page appears.
Step 2
Specify the relevant details.
Step 3
Click Save to save the changes made to the Radius properties page.
On successful setting up of the radius, a message is displayed.
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 3-5 lists and describes the fields in the Add Profiles page.
|
|
|
|---|---|
Name |
Required; must be unique in the Profiles list. |
Description |
Optional; description of the profile. |
RADIUS |
Optional; set Radius, if the attribute and value needs to be defined for Radius. |
VENDOR |
Optional; set Vendor, if the attribute and value needs to be defined for Vendor. |
Attribute Name |
Optional; based on the Attribute Type selected, the attribute name is automated. Set the relevant name for the attribute type selected. |
Value Attribute |
Optional; set the value for the selected attribute. Click the Add button to save the details and list it in Radius and Value list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Use the Profiles page for the following:
Adding Profile Details
To add new profile details:
Step 1
Choose Configuration > Profiles. The Profiles page is displayed.
Step 2
Click Add. The Add Profile page is displayed.
Step 3
Specify the required details.
Step 4
Click Submit to save the specified details in the Profiles page. Otherwise click Cancel to return to the Profiles page without saving the details. On successful creation of the profiles, the Profiles page is displayed else a respective error message is displayed.
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 3-6 lists and describes the fields in the Add User Groups page.
|
|
|
|---|---|
General Properties tab |
|
Name |
Required; must be unique in the UserGroup list. |
Description |
Optional; description of the group. |
BaseProfile |
Optional; when you set this to the name of a profile, Cisco Prime AR adds the properties in the Profile to the response dictionary as part of the authorization. |
AuthenticationScript |
Optional; when you set this property to the name of a script, you can use the Script to perform additional authentication checks to determine whether to accept or reject the user. |
AuthorizationScript |
Optional; when you set this property to the name of a script, you can use the script to add, delete, or modify the attributes of the Response dictionary. |
Attribute List tab |
|
RADIUS |
Optional; set Radius, if the attribute and value needs to be defined for Radius. |
VENDOR |
Optional; set Vendor, if the attribute and value needs to be defined for Vendor. |
Attribute Name |
Optional; based on the Attribute Type selected, the attribute name is automated. Set the relevant name for the attribute type selected. |
Attribute Value |
Optional; set the value for the selected attribute. Click the Add button to save the details and list it in Name and Value list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
CheckItems List tab |
|
RADIUS |
Optional; set Radius, if the attribute and value needs to be defined for Radius. |
VENDOR |
Optional; set Vendor, if the attribute and value needs to be defined for Vendor. |
Attribute Name |
Optional; based on the Attribute Type selected, the attribute name is automated. Set the relevant name for the attribute type selected. |
Attribute Value |
Optional; set the value for the selected attribute. Click the Add button to save the details and list it in Check Name and Check Value list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Use the User Groups page for the following:
Adding UserGroup Details
To add new user groups details:
Step 1
Choose Configuration > UserGroups. The User Groups page is displayed.
Step 2
Click Add to add new user group details. The Add UserGroup page is displayed.
Step 3
Specify the required details.
Step 4
Click Submit to save the specified details in the User Groups page. Otherwise click Cancel to return to the User Groups page without saving the details.
On successful creation of the user groups, the User Groups page is displayed else a respective error message is displayed.
UserList
The UserLists object contains all of the individual UserLists, which in turn, contain the specific users stored within Cisco Prime AR. Cisco Prime AR references each specific UserList by name from a Service whose type is set to local. When Cisco Prime AR 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.
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, Cisco Prime AR can run a script 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.
Table 3-7 lists and describes the fields in the Add User List page.
|
|
|
|---|---|
UserList Name |
Required; must be unique. |
Description |
Optional; description of the user. |
Use the User List page for the following:
Adding UserList Details
To add new user list details:
Step 1
Choose Configuration > UserList. The User List page is displayed.
Step 2
Click Add to add new user list details. The Add UserList page is displayed.
Step 3
Enter the required details.
Step 4
Click Submit to save the specified details in the User List page. Otherwise click Cancel to return to the User List page without saving the details.
On successful creation of the user list, the User List page is displayed else a respective error message is displayed.
Note
After adding a new user list, you can add users to the user list. See Adding User Details for more information.
Users
The user objects are created to hold the necessary details to authenticate or authorize a user. These users form the component of User Lists, where their details are stored within Cisco Prime AR. The users in local Userlist can have multiple profiles.
Note
Usernames might not include the forward slash (/) character. If the Cisco Prime AR server receives an access request packet with a Username attribute containing a forward slash character and the Cisco Prime AR 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.
Table 3-8 lists and describes the fields in the Add Users page.
|
|
|
|---|---|
General Properties tab |
|
Name |
Required; must be unique. |
Enabled |
Required; must be checked to allow user access. If Enabled is not checked, user is denied access. |
Allow Null Pwd |
During authentication, if the Allow NULL Password environment variable is set to TRUE, user authentication is bypassed. By default, the Allow NULL Password environment variable is not set. |
UserGroup |
Use the drop-down list to select a UserGroup and use the properties specified in the UserGroup to authenticate and/or authorize the user. The default is none. |
Password |
Required; length must be between 0-253 characters. |
Base Profile |
Optional; use the drop-down list to select a Profile. If the service-type is not equal to Authenticate Only, Cisco Prime AR adds the properties in the Profile to the Response dictionary as part of the authorization. This field is optional for the CLI, but required for the GUI. Use the menu to select a profile other than the default None. |
Confirm Password |
Required; must match password. |
User Defined |
Optional; you can use this property to store notational information which you can then use to filter the UserList. This property also sets the environment variable for UserDefined. |
Authentication Script |
Optional; use the drop-down list to select the name of a script to perform additional authentication checks to determine whether to accept or reject the user. This field is optional for the CLI, but required for the GUI. Use the menu to select an Authentication Script other than the default None. |
Authorization Script |
Optional; use the drop-down list to select the name of a script to add, delete, or modify the attributes of the Response dictionary. This field is optional for the CLI, but required for the GUI. Use the menu to select an Authorization Script other than the default None. |
Description |
Optional; description of the user. |
Attribute List tab |
|
RADIUS |
Optional; set Radius, if the attribute and value needs to be defined for Radius. |
VENDOR |
Optional; set Vendor, if the attribute and value needs to be defined for Vendor. |
Attribute Name |
Optional; based on the Attribute Type selected, the attribute name is automated. Set the relevant name for the attribute type selected. |
Attribute Value |
Optional; set the value for the selected attribute. Click the Add button to save the details and list it in Name and Value list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
CheckItems List tab |
|
RADIUS |
Optional; set Radius, if the attribute and value needs to be defined for Radius. |
VENDOR |
Optional; set Vendor, if the attribute and value needs to be defined for Vendor. |
Attribute Name |
Optional; based on the Attribute Type selected, the attribute name is automated. Set the relevant name for the attribute type selected. |
Attribute Value |
Optional; set the value for the selected attribute. Click the Add button to save the details and list it in Check Name and Check Value list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Use the Users page for the following:
Adding User Details
To add new user details:
Step 1
Choose Configuration > UserList. The User List page is displayed.
Step 2
Click the user list name link. The Users page is displayed.
Step 3
Click Add to add new user details. The Add Users page is displayed.
Step 4
Specify the required details.
Step 5
Click Submit to save the specified details in the Users page. Otherwise click Cancel to return to the Users page without saving the details.
On successful creation of the user details, the Users page is displayed else a respective error message is displayed.
Scripts
The Script objects define the function Cisco Prime AR 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
For more information about scripts, see Chapter 12, "Using Extension Points." of the Cisco Prime Access Registrar 6.0 User Guide.
Table 3-9 lists and describes the fields in the Add Scripts page.
The InitEntryPoint properties allow you to perform initialization before processing and then cleanup before stopping the server. For example, when Cisco Prime AR 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 Cisco Prime AR file service, Cisco Prime AR 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.
Use the Scripts page for the following:
Adding Script Details
To add new script details:
Step 1
Choose Configuration > Scripts. The Scripts page is displayed.
Step 2
Click Add to add new scripts details. The Add Script page is displayed.
Step 3
Enter the required details.
Step 4
Click Save to save the specified details in the Scripts page. Otherwise click Cancel to return to the Scripts page without saving the details.
On successful creation of the scripts, the Scripts page is displayed else a respective error message is displayed.
Policies
A Policy is a set of rules applied to an Access-Request.
Table 3-10 lists and describes the fields in the Add Policies page.
Use the Policies page for the following:
Adding Policy Details
To add new policy details:
Step 1
Choose Configuration > Policies. The Policies page is displayed.
Step 2
Click Add to add new policy details. The Add Policy page is displayed.
Step 3
Specify the required details.
Step 4
Click Submit to save the specified details in the Policies page. Otherwise click Cancel to return to the Policies page without saving the details.
On successful creation of the policies, the Policies page is displayed else a respective error message is displayed.
Services
Cisco Prime AR supports authentication, authorization, and accounting (AAA) services. In addition to the variety of built-in AAA services (specified in the Type property), Cisco Prime AR also enables you to add new AAA services through custom shared libraries.
This section lists the types of services available in Cisco Prime AR with their required and optional properties. The service you specify determines what additional information you must provide. The various types of services are:
Simple Services
Cisco Prime AR provides the following simple services:
•
Rex
•
File
•
Java
Rex
Select rex service when a custom service needs to be created and a script for authentication, authorization, or accounting has to be used.
File
Select File type when local accounting is to be performed using a specific file. The files under the configuration will be saved in the configured name when the server is invoked even if the service is not being invoked by any request packets.
Cisco Prime AR flushes the accounting record to disk before it acknowledges the request packets. Based on the specified maximum file size and age, it closes the accounting file, moves it to a new name, and reopens the file as a new file. The file names are based on its creation and modification dates.
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 OR function, which is specified in the Result-Rule attribute of Group Services. The default value is AND.
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).
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.
Local
Select local services when authentication and authorization needs to be performed by Cisco Prime AR server using a specific UserList.
Java
Select Java service type when a custom service needs to be created and to use an extension point script to provide the service's functionality and handle both RADIUS and TACACS requests for authentication, authorization, or accounting.
WiMAX
Cisco Prime AR uses the Extensible Authentication Protocol (EAP) to enable the WiMAX feature. It captures the IP attributes and Mobility Keys that are generated during network access authentication.
Radius Query
Select this service type to query cached data through Radius Packets. It contains the 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. It is initiated through an extension point script or through the Rule and Policy Engine by setting it to a new environment variable named Query-Service.
Table 3-11 lists and describes the fields in the Add Simple Services List page. The fields listed below are the entire list of all the available types. The fields are displayed based on the type selected.
|
|
|
|---|---|
Service Name |
Required; must be unique in the Services list. |
Incoming Script |
Optional; name of script to run when the service starts. |
Type |
Required; must set it to a valid Cisco Prime AR service. |
Outgoing Script |
Name of script to run when the service ends. |
Description |
Optional; description of the service. |
Outage Script |
Optional; if you set this property to the name of a script, Cisco Prime AR runs it when an outage occurs. This property allows you to create a script that notifies you when the RADIUS server detects a failure. |
Outage Policy |
Required; the default is RejectAll. This property defines how Cisco Prime AR 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. |
Filename |
Required; must be either a relative or an absolute path to the shared library containing the Service. When the pathname is relative, it must be relative to $INSTALL/Scripts/Radius/rex. |
EntryPoint |
Required; must be set to the function's global symbol. |
InitEntryPoint |
Required; must be the name of the global symbol Cisco Prime AR should call when it initializes the shared library and just before it unloads the shared library. A rex service must have an InitEntryPoint even if the service only returns REX_OK. |
InitEntryPointArgs |
Optional; when set, it provides the arguments to be passed to the InitEntryPoint in the environmental variable Arguments. |
FilenamePrefix |
Required; a string that specifies where Cisco Prime AR 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. |
MaxFileAge |
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. |
RolloverSchedule |
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. |
MaxFileSize |
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, or kilobytes, M, megabyte, or megabytes, or G, gigabyte, or gigabytes. The default is ten megabytes. |
UseLocalTimeZone |
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. |
UserService |
Required; name of service that can be used to authenticate |
SessionManager |
Required; select the required session manager from the available list. |
Result Rule |
When set to AND (the default), the response from the GroupService 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. When set to OR, the response from the GroupService 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. The settings parallel-AND or parallel-OR are similar to AND and OR settings, except that each referenced service processes requests simultaneously instead of asking each reference service sequentially to save processing time. |
InitEntryPoint |
Required; must be the name of the global symbol Cisco Prime AR should call when it initializes the shared library and just before it unloads the shared library. A rex service must have an InitEntryPoint even if the service only returns REX_OK. |
GroupServices |
Optional; use the GroupServices subdirectory to specify the subservices in an indexed list to provide specific ordering control of which services to apply first. Each subservice listed must be defined in the Services section of the Radius configuration and cannot be a of type group, eap-leap, or eap-md5. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. |
UserList |
Required; this object contains all of the individual UserLists, which in turn, contain the specific users stored within Cisco Prime AR. Cisco Prime AR references each specific UserList by name from a Service whose type is set to local. When Cisco Prime AR 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. |
Class name |
Optional; set to the name of a class that implements the Extension interface. |
InitializeArg |
Optional; set to a string to be passed to the Initialize method if the class implements the optional ExtensionWithInitialization interface. |
HARKKey |
Required; used as the base key to generate random HARKKey for all the HAs that are configured in Cisco Prime AR. By default, the value is cisco112.You can change this value. |
WimaxAuthenticationService |
Required; a valid EAP service which can be used for WiMAX authentication. By default, this value is none. |
HARKLifeTime |
Required; used as time (in minutes) to regenerate the HARKKeys based on its lifetime. |
WimaxSessionManager |
Required; set a valid session manager which has HA and HA Cache as resource managers. By default, this value is none. |
WimaxQueryService |
Required; set a valid RADIUS query service which is configured with WiMAX session manager. By default, this value is none. |
WimaxPrepaidService |
Optional; set a valid prepaid service to carry out the prepaid functionality of WiMAX. Otherwise this value is set to none. |
AllowAAAToIncludeKeys |
Optional; If this is set, the HAAA will include the hHA-RK-Key, hHA-RK-SPI and hHA-RK-Lifetime in the Access-Accept. Otherwise, those attributes will not be in the Access-Accept. By default this value is True. |
RequiredMSK |
Optional; If this is set, the MSK will be provided by the AAA server as a result of successful EAP-Authentication. By default, this value is False. |
Attribute List tab |
|
Attribute type |
Select either RADIUS or VENDOR. If Vendor is selected, specify the vendor type from the drop-down list. Select the attributes from the available list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. |
Session Manager tab |
|
Session Manager |
Select the required session manager from the available list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. |
Use the Simple Services List page for the following:
•
Adding Simple Service Details
Adding Simple Service Details
To add new simple service details:
Step 1
Choose Configuration > Services > Simple. The Services List(REX, FILE, LOCAL, GROUP, JAVA...) page is displayed.
Step 2
Click Add to add new simple service details. The Add Service page is displayed.
Step 3
Enter the required details.
Step 4
Click Submit to save the specified details in the Services List(REX, FILE, LOCAL, GROUP, JAVA...) page. Otherwise click Cancel to return to the Services List(REX, FILE, LOCAL, GROUP, JAVA...) page without saving the details.
On successful creation of the simple service properties, the Services List(REX, FILE, LOCAL, GROUP, JAVA...) page is displayed else a respective error message is displayed.
ServiceWithRS
The RemoteServers directory lists one or more remote servers to process access requests. The servers must also be listed in order under /Radius/RemoteServers. The order of the RemoteServers list determines the sequence for directing access requests when MultipleServersPolicy is set to RoundRobin mode. The first server in the list receives all access requests when MultipleServersPolicy is set to Failover mode.
The RemoteServers object can be used 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.
Table 3-12 lists and describes the fields in the Add ServiceWithRS List page.
|
|
|
|---|---|
Service Name |
Required; name of the remote server service |
Incoming Script |
Optional; name of script to run when the service starts |
Type |
Required; Remote service Type must be set to one of the following: domain-auth, ldap, ldap-accounting, odbc-accounting, odbc, oci-accounting, oci, prepaid, radius, or radius-session. |
Outgoing Script |
Optional; name of script to run when the service ends. |
Outage Script |
Optional; if you set this property to the name of a script, Cisco Prime AR runs it when an outage occurs. This property allows you to create a script that notifies you when the RADIUS server detects a failure. |
Outage Policy |
The default is RejectAll. This property defines how Cisco Prime AR 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. |
Description (optional) |
Optional; description of the remote server service |
MultipleServersPolicy |
Required; must be set to either Failover or RoundRobin. When you set it to Failover, Cisco Prime AR directs requests to the first server in the list until it determines the server is offline. At which time, Cisco Prime AR redirects all requests to the next server in the list until it finds a server that is online. When you set it to RoundRobin, Cisco Prime AR directs each request to the next server in the RemoteServers list to share the resource load across all of the servers listed in the RemoteServers list. |
RemoteServers |
Select the required remote server from the available list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. |
Use the PEAP Services List page for the following:
•
Adding Remote Server Service Details
Adding Remote Server Service Details
To add new remote server service details:
Step 1
Choose Configuration > Services > ServiceWithRS. The Services List (..with Remote Servers) page is displayed.
Step 2
Click Add to add new remote server service details. The Add ServiceWithRS page is displayed.
Step 3
Enter the required details.
Step 4
Click Submit to save the specified details in the Services List (..with Remote Servers) page. Otherwise, click Cancel to return to the Services List (..with Remote Servers) List page without saving the details.
On successful creation of the properties, the Services List (..with Remote Servers) page is displayed else a respective error message is displayed.
•
PEAP Service
Protected EAP (PEAP) is an authentication method designed to mitigate several weaknesses of EAP. PEAP leverages Industry standard authentication of the server using certificates TLS (RFC 2246) and creation of a secure session that can then be used to authenticate the client.
The PEAP protocol consists of two phases, an authentication handshake phase and a tunnel phase where another complete EAP authentication exchange takes place protected by the session keys negotiated by phase one. Cisco Prime AR supports the tunneling of other EAP methods within the PEAP phase two exchange.
Cisco Prime AR supports the two major existing variants of PEAP,
•
PEAP Version 0 (Microsoft PEAP)
•
PEAP Version 1 (Cisco Prime PEAP)
PEAP Version 0
PEAP Version 0 also called as Microsoft PEAP is described in IETF drafts (draft-kamath-pppext-peapv0-00.txt and draft-josefsson-pppext-eap-tls-eap-02.txt). This version of PEAP uses either EAP-MSChapV2 or EAP-SIM as an authentication method. The testing method used for this version of PEAP is radclient.
PEAP Version 1
PEAP Version 1 also called as Cisco Prime PEAP is described by IETF draft (draft-zhou-pppext-peapv1-00.txt). This version can use either EAP-GTC or EAP-SIM as an authentication method. The testing method used for this version of PEAP is radclient.
Table 3-13 lists and describes the fields in the Add PEAP Services List page. The fields listed below are the entire list of all the available types. The fields are displayed based on the type selected.
Use the ServiceWithRS List page for the following:
Adding PEAP Service Details
To add new PEAP service details:
Step 1
Choose Configuration > Services > PEAP. The PEAP Services List page is displayed.
Step 2
Click Add to add new PEAP service details. The Add PEAP-Service page is displayed.
Step 3
Specify the relevant PEAP service details.
Step 4
Click Submit to save the specified details in the PEAP Services List page. Otherwise click Cancel to return to the PEAP Services List page without saving the details.
On successful creation of the PEAP service properties, the PEAP Services List page is displayed else a respective error message is displayed.
EAP Service
Cisco Prime Access Registrar (Cisco Prime AR) supports the Extensible Authentication Protocol (EAP) to provide a common protocol for differing authentication mechanisms. It provides dynamic selection of the authentication mechanism at the time of authentication based on information transmitted in the Access-Request.
Cisco Prime AR supports the following EAP authentication methods:
•
EAP-Transport Level Security (TLS)
EAP-AKA
Authentication and Key Agreement (AKA) is an EAP mechanism for authentication and session key distribution. It is used in the 3rd generation mobile networks Universal Mobile Telecommunications System (UMTS) and CDMA2000. AKA is based on symmetric keys, and typically runs in a UMTS Subscriber Identity Module (USIM), or a (Removable) User Identity Module ((R) UIM), similar to a smart card. EAP-AKA (Extensible Authentication Protocol Method for UMTS Authentication and Key Agreement) includes optional identity privacy support, optional result indications, and an optional fast reauthentication procedure. The EAP-AKA authentication service is extended to generate a Diameter message Multimedia-Authentication-Request (MAR), with the subscriber identity(IMSI), to the Home Subscriber Server (HSS) when it requires the authentication vectors. The HSS sends a Diameter Mutlimedia-Authentication-Answer (MAA) back containing the number of quintuplets.
EAP-FAST
EAP-FAST is an authentication method which uses the EAP-MSChapV2 method for credential provisioning and EAP-GTC for authentication. Credential provisioning typically occurs only during the client's initial EAP-FAST authentication. Subsequent authentications rely on the provisioned credential and will usually omit the provisioning step.
This authentication protocol is designed to address the performance shortcomings of prior TLS-based EAP methods while retaining features such as identity privacy and support for password-based protocols. The EAP-FAST protocol is described by the IETF draft (draft-cam-winget-eap-fast-00.txt).
EAP-GTC
This method defined in RFC 2284, is used for transmitting a username and password to an authentication server.
Note
It should not be used except as an authentication method for PEAP Version 1 because the password is not protected.
EAP-LEAP
The new AAA Cisco-proprietary protocol called Light Extensible Authentication Protocol (LEAP) supported by Cisco Prime AR, is a proprietary Cisco authentication protocol designed for use in IEEE 802.11 wireless local area network (WLAN) environments. Important features of LEAP include:
•
Mutual authentication between the network infrastructure and the user
•
Secure derivation of random, user-specific cryptographic session keys
•
Compatibility with existing and widespread network authentication mechanisms (e.g., RADIUS)
Note
Cisco Prime AR supports a subset of EAP to support LEAP. This is not a general implementation of EAP for Cisco Prime AR.
The Cisco-Wireless or LEAP is an EAP authentication mechanism where the user password is hashed based on an MD4 algorithm.
EAP-MD5
This is another EAP authentication exchange. In EAP-MD5 there is a CHAP-like exchange and the password is hashed by a challenge from both client and server to verify the password. On successful verification, the connection proceeds, although the connection is periodically rechallenged (per RFC 1994).
EAP-Negotiate
This is a special service used to select at runtime the EAP service to be used to authenticate the client. It is configured with a list of candidate EAP services that represent the allowable authentication methods in preference order.
EAP-Negotiate is useful when the client population has deployed a mix of different EAP methods that must be simultaneously supported by Cisco Prime AR. EAP-Negotiate solves the problem of distinguishing client requirement by using the method negotiation feature of the EAP protocol.
EAP-MSChapV2
EAP-MSChapv2 encapsulates the MSChapV2 protocol (specified by RFC 2759) and can be used either as an independent authentication mechanism or as an inner method for PEAP Version 0 (recommended). This is based on draft-kamath-pppext-eap-mschapv2-00.txt, an informational IETF draft document.
EAP-SIM
An access point uses the Cisco Prime AR RADIUS server to perform EAP-SIM authentication of mobile clients. Cisco Prime AR must obtain authentication information from the HLR. Cisco Prime AR contacts the MAP gateway that performs the MAP protocol over SS7 to the HLR. The EAP-SIM authentication service is extended to generate a Diameter message Multimedia-Authentication-Request (MAR), with the subscriber identity(IMSI), to the HSS when it requires the authentication vectors. The HSS sends a Diameter Mutlimedia-Authentication-Answer (MAA) back containing the number of triplets.
EAP-Transport Level Security (EAP-TLS)
This is an authentication method (described in RFC 2716) which leverages TLS, described in RFC 2246, to achieve certificate-based authentication of the server and the client (optionally). It provides many of the same benefits as PEAP but differs in the lack of support for legacy authentication methods.
EAP-Transport Level Security (TLS)
This is an authentication method (described in RFC 2716) which leverages TLS, described in RFC 2246, to achieve certificate-based authentication of the server and the client (optionally). It provides many of the same benefits as PEAP but differs in the lack of support for legacy authentication methods.
EAP-TTLS
The Extensible Authentication Protocol Tunneled TLS (EAP-TTLS) is an EAP protocol that extends EAP-TLS. EAP- TTLS extends the authentication negotiation EAP-TLS by using the secure connection established by the TLS handshake to exchange additional information between client and server. It leverages TLS (RFC 2246) to achieve certificate-based authentication of the server (and optionally the client) and creation of a secure session that can then be used to authenticate the client using a legacy mechanism.
EAP-TTLS is a two-phase protocol. Phase 1 conducts a complete TLS session and derives the session keys used in Phase 2 to securely tunnel attributes between the server and the client. The attributes tunneled during Phase 2 can be used to perform additional authentication(s) via a number of different mechanisms.
The authentication mechanisms used during Phase 2 include PAP, CHAP, MS-CHAP, MS-CHAPv2, and EAP. If the mechanism is EAP, then several different EAP methods are possible.
Table 3-14 lists and describes the fields in the Add EAP Services List page. The fields listed below are the entire list of all the available types. The fields are displayed based on the type selected.
|
|
|
|---|---|
Service Name |
Required; service name |
Incoming Script |
Optional script Cisco Prime AR server runs when it receives a request from a client. |
Type |
Required; must set it to a valid Cisco Prime AR service |
Outgoing Script |
Optional script Cisco Prime AR server runs before it sends a response to a client |
Description (optional) |
Optional; description of the PEAP service. |
Authentication Timeout |
Mandatory; specifies time (in seconds) to wait before an authentication request times out; defaults to 120. |
UserService |
Required; name of service that can be used to authenticate using cleartext passwords. |
ServiceList |
List of preconfigured EAP authentication services. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. |
Maximum Message Size |
Required; indicates the maximum length in bytes that a PEAP message can have before it is fragmented. |
Server Certificate File |
Required; the full pathname of the file containing the server's certificate or certificate chain used during the TLS exchange. The pathname can be optionally prefixed with a special string that indicates the type of encoding used for the certificate. The two valid encoding prefixes are PEM and DER. If an encoding prefix is not present, the file is assumed to be in PEM format. |
Private Key Password |
Required; the password used to protect the server's private key. |
Server RSA Key File |
Required; the full pathname of the file containing the server's RSA private key. The pathname can be optionally prefixed with a special string that indicates the type of encoding used for the certificate. The two valid encoding prefixes are "PEM" and "DER". If an encoding prefix is not present, the file is assumed to be in PEM format. The following example assumes that the subdirectory pki under /cisco-ar contains the server's certificate file. The file server-key.pem is assumed to be in PEM format. The file extension .pem is not significant. set ServerRSAKeyFile PEM:/cisco-ar/pki/server-key.pem |
CRL Distribution URL |
Optional; enter the URL that Cisco Prime AR should use to retrieve the CRL.You can specify a URL that uses HTTP or LDAP. The following is an example for an HTTP URL: The following is an example for an LDAP URL: |
CA Certificate File |
Optional; the full pathname of the file containing trusted CA certificates used for client verification. The file can contain more than one certificate, but all certificates must be in PEM format. DER encoding is not allowed. |
Certificate Verification Mode |
The value is set to optional by default. If set to RequireCertificate, the client certificate will always be verified. If set to optional, client certificate verification happens optionally. |
CA Certificate Path |
The name of a directory containing trusted CA certificates (in PEM format) used for client verification. This parameter is optional and if it is used there are some special preparations required for the directory it references. Each certificate file in this directory must contain exactly one certificate in PEM format. The server looks up the certificate files using the MD5 hash value of the certificate's subject name as a key. The directory must therefore also contain a set of symbolic links each of which points to an actual certificate file. The name of each symbolic link is the hash of the subject name of the certificate. For example, if a certificate file named ca-cert.pem is located in the CACertificatePath directory, and the MD5 hash of the subject name contained in ca-cert.path.pem is 1b96dd93, then a symbolic link named 1b96dd93 must point to ca-cert.pem. If there are subject name collisions such as multiple certificates with the same subject name, each link name must be indexed with a numeric extension as in 1b96dd93.0 and 1b96dd93.1. |
Verification Depth |
Optional; specifies the maximum length of the certificate chain used for client verification. |
Enable Session Cache |
Optional; specifies whether TLS session caching (fast reconnect) is enabled or not. Set to True to enable session caching; otherwise set to False. |
Session Timeout |
Required; if TLS session caching (fast reconnect) is enabled, SessionTimeout specifies the maximum lifetime of a TLS session. Expired sessions are removed from the cache and will require a subsequent full authentication. SessionTimeout is specified as a string consisting of pairs of numbers and units, where units might be one of the following: M, Minute, Minutes, H, Hour, Hours, D, Day, Days, W, Week, Weeks, as in the following: Set SessionTimeout "1 Hour 45 Minutes" |
UseECCCertificate |
Determines the applicability of the authentication mechanism in SmartGrid Solutions. When you select this check box, it can use the ECC, RSA, or combination of both certificate for certificate based verification. When you uncheck this check box, it can only use the RSA certificate for certificate based verification. The default location to fetch the certificate file is /cisco-ar/pki. |
Authentication Service |
Specifies the name of the EAP-GTC service used for authentication. The named service must have the UseLabels parameter set to True. |
User Prompt |
Optional string the client might display to the user; default is Enter password:" Use the set command to change the prompt, as in the following: set UserPrompt "Admin Password:" |
UseLabels |
Required; must be set to TRUE for EAP-FAST authentication and set to FALSE for PEAP authentication. Set to FALSE by default. |
SystemID |
Optional; string that identifies the sender of the MSChapV2 challenge message. |
IsWindows7Client |
Optional; must be set to TRUE for EAP-MSChapV2 authentication. Set to FALSE by default. |
Authority Identifier |
Required; a string that uniquely identifies the credential (PAC) issuer. The client uses this value to select the correct PAC to use with a particular server from the set of PACs it might have stored locally. |
Authority Information |
Required; a string that provides a descriptive text for this credential issuer. The value can be displayed to the client for identification purposes and might contain the enterprise or server names. |
Credential Life Time |
Optional; specifies the maximum lifetime of a Protected Access Credential (PAC). Clients that successfully authenticate with an expired PAC will be reprovisioned with a new PAC. CredentialLifetime is specified as a string consisting of pairs of numbers and units, where units might be one of the following: M, Minute, Minutes, H, Hour, Hours, D, Day, Days, W, Week, Weeks. Credentials that never expire should be specified as Forever. |
Provision Service |
Required; specifies the name of the EAP-MSChapV2 service used for provisioning. |
Provision Mode |
Required; specifies the TLS mode used for provisioning. Clients only support the default Anonymous mode. |
Always Authenticate |
Optional; indicates whether provisioning should always automatically rollover into authentication without relying on a separate session. Most environments, particularly wireless, will perform better when this parameter is set to True, the default value. |
SubscriberDBLookup |
Specifies the type of communication with the HLR/HSS server. Based on the type selected, the communication happens with the HLR/HSS server using the diameter Wx interface, MAP protocol, or SIGTRAN-M3UA protocol. This field is displayed when you select the eap-sim option in the Type field. |
Subscriber_DBLookup |
Specifies the type of communication with the HLR/HSS server. Based on the type selected, the communication happens with the HLR/HSS server using the diameter Wx interface, SIGTRAN protocol, or SIGTRAN-M3UA protocol. This field is displayed when you select the eap-aka option in the Type field. |
DestinationRealm |
Required. Need to configure the Diameter Remote Server for the Realm. The role of the remote server should be Relay. |
PreRequestTranslationScript |
Optional. Cisco Prime AR server runs before sending the request to the Diameter remote server. The script can modify the Radius packet dictionaries. |
PostRequestTranslationScript |
Optional. Cisco Prime AR server runs before sending the request to the Diameter remote server. The script can modify the Diameter packet dictionaries. |
PreResponseTranslationScript |
Optional. Cisco Prime AR server runs after receiving the response from the Diameter remote server. The script can modify the Diameter packet dictionaries. |
PostResponseTranslationScript |
Optional. Cisco Prime AR server runs after receiving the response from the Diameter remote server. The script can modify the Radius packet dictionaries. |
FetchAuthorizationInfo |
When you select this check box, it fetches MSISDN from HLR. |
General tab |
|
MultipleServersPolicy |
Required. Must be set to either Failover or RoundRobin. When set to Failover, Cisco Prime AR directs requests to the first server in the list until it determines the server is offline. At that time, Cisco Prime AR redirects all requests to the next server in the list until it finds a server that is online. When set to RoundRobin, Cisco Prime AR directs each request to the next server in the RemoteServers list to share the resource load across all of the servers listed in the RemoteServers list. |
NumberOfTriplets |
Required; number of triplets (1, 2, or 3) to use for authentication; default is 2. |
PseudonymSecret |
Required; the secret string that is used as the basis for protecting identities when identity privacy is enabled. This should be at least 16 characters long and have a value that is impossible for an outsider to guess. The default value is secret. Note |
PseudonymRenewtime |
Required; specifies the maximum age a pseudonym can have before it is renewed. When the server receives a valid pseudonym that is older than this, it generates a new pseudonym for that subscriber. The value is specified as a string consisting of pairs of numbers and units, where the units might be of the following: M, Minute, Minutes, H, Hour, Hours, D, Day, Days, W, Week, Weeks. The default value is "24 Hours". Examples are: "8 Hours", "10 Hours 30 Minutes", "5 D 6 H 10 M" |
PseudonymLifetime |
Required; specifies the maximum age a pseudonym can have before it is rejected by the server, forcing the subscriber to authenticate using it's permanent identity. The value is specified as a string consisting of pairs of numbers and units, where the units might be one of the following: M, Minute, Minutes, H, Hour, Hours, D, Day, Days, W, Week, Weeks. It can also be Forever, in which case, pseudonyms do not have a maximum age. The default value is "Forever". Examples are: "Forever", "3 Days 12 Hours 15 Minutes", "52 Weeks" |
ReauthenticationTimeout |
Required; specifies the time in seconds that reauthentication identities are cached by the server. Subscribers that attempt to reauthenticate using identities that are older than this value will be forced to use full authentication instead. The default value is 3600 (one hour). |
EnableReauthentication |
Optional; when True, the fast reauthentication option is enabled. The default value is False. |
UseProtectedResults |
Optional; enables or disables the use of protected results messages. Results messages indicate the state of the authentication but are cryptographically protected. |
ReauthenticationRealm |
Optional; this information will be supplied later. |
MaximumReauthentications |
Required; specifies the maximum number of times a reauthentication identity might be reused before it must be renewed. The default value is 16. |
TripletCacheTimeout |
Required; time in seconds an entry remains in the triplet cache. A zero (0) indicates that triplets are not cached. The maximum is 28 days; the default is 0 (no caching). |
Authentication Timeout |
Required; time in seconds to wait for authentication to complete. The default is 2 minutes; range is 10 seconds to 10 minutes. |
UseSimDemoTriplets |
Optional; set to TRUE to enable the use of demo triplets. This must be disabled for release builds. |
AlwaysRequestIdentity |
Optional; when True, enables the server to obtain the subscriber's identity via EAP/SIM messages instead of relying on the EAP messages alone. This might be useful in cases where intermediate software layers can modify the identity field of the EAP-Response/Identity message. The default value is False. |
EnableIdentityPrivacy |
Optional; when True, the identity privacy feature is enabled. The default value is False. |
Generate3GPPCompliantPseudonym |
Optional; the value is set to False by default. If set to TRUE then Cisco Prime AR generates a 12 octet 3GPP compliant pseudonym identity. The Pseudonym username identities are used to protect the privacy of subscriber identities. |
SendReAuthIDInAccept |
Optional; the value is set to False by default. When set to True, Cisco Prime AR sends SN-Fast-ReAuth-UserName (Starent VSA) in access-accept message. |
Outage Script |
Optional; if you set this property to the name of a script, Cisco Prime AR runs it when an outage occurs. This property allows you to create a script that notifies you when the RADIUS server detects a failure. |
Remote Servers tab |
|
Attribute |
Optional; list of remote RADIUS servers which are map gateways. The remote server type must be set to map-gateway. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. |
Use the EAP Services List page for the following:
Adding EAP Service Details
To add new EAP service details:
Step 1
Choose Configuration > Services > EAP. The EAP Services List page is displayed.
Step 2
Click Add to add new EAP service details. The Add EAP-Service page is displayed.
Step 3
Enter the relevant details.
Step 4
Click Submit to save the specified details in the EAP Services List page. Otherwise click Cancel to return to the EAP Services List page without saving the details.
On successful creation of the EAP Service properties, the EAP Services List page is displayed else a respective error message is displayed.
Diameter Service
Proxy agents assist in routing Diameter messages using the Diameter routing table. Diameter proxy service works in tandem with the rule policy engine to perform the routing for multiple realms or applications. The following are the multiple peer policies supported by the proxy service:
•
RoundRobin
•
FailOver
•
IMSI Range Based.
Table 3-15 lists and describes the fields in the Add Diameter Services List page. The fields listed below are the entire list of all the available roles. The fields are displayed based on the role selected.
Use the Diameter Services List page for the following:
•
Adding Diameter Service Details
Adding Diameter Service Details
To add a new Diameter Service details:
Step 1
Choose Configuration > Services > Diameter. The Diameter Services page is displayed.
Step 2
Click Add to add new Diameter service details. The Add DIAMETER- Services page is displayed.
Step 3
Specify the require details in the PEER Statements, Applications, and PEER Definitions Proxy specific sections.
Step 4
Click Save DIAMETER Service to save the specified details in the Diameter Services page. Otherwise click Cancel to return to the Diameter Services page without saving the details.
On successful creation of the Diameter Service properties, the Diameter Services page is displayed else a respective error message is displayed.
Note
You may need to enter PEER Statements, Applications, and PEER Definitions Proxy details based on the Role that you select in the DIAMETER-Services page.
Adding the PEER Statements Details
To add new PEER Statement details:
Step 1
Click Add to add new PEER Statements details section. The fields specific to PEER Statements are displayed.
Step 2
Specify the required details.
Step 3
Click Save to save the specified details in the PEER Statements section. Otherwise click Cancel to return to the PEER Statements section without saving the details.
On successful creation of the Diameter Service properties, the Diameter Services page is displayed else a respective error message is displayed.
Adding the Applications Details
To add new Application details:
Step 1
Click Add to add new Applications details in the Application List section. The fields specific to Applications are displayed.
Step 2
Specify the required details.
Step 3
Click Save Appln to save the specified details in the Application List section. Otherwise click Cancel Appln to return to the Application List section without saving the details.
Adding the PEER Definitions Proxy Details
To add PEER Definitions Proxy details:
Step 1
Click Add to add new Proxy PEER Statements in the PEER Definitions Proxy section. The fields specific to Proxy PEER Statements are displayed.
Step 2
Specify the required details.
Step 3
Click Save to save the specified details in the Proxy PEER Statements section. Otherwise click Cancel to return to the Proxy PEER Statements section without saving the details.
Replication
The replication feature of Cisco Prime AR allows you to maintain identical configurations on multiple machines simultaneously. It eliminates the need to have administrators with multiple Cisco Prime AR installations, make the same configuration changes at each of their installations. Instead, only the master's configuration must be changed and the slave is automatically configured eliminating the need to make repetitive, error-prone configuration changes for each individual installation. In addition to enhancing server configuration management, using replication eliminates the need for a hot-standby machine.
Employing Cisco Prime AR's replication feature, both servers can perform RADIUS request processing simultaneously, eliminating wasted resources. It focuses on configuration maintenance only, not session information or installation-specific information.
Table 3-16 lists and describes the fields in the Replication Details page.
Use the Replication Details page for the following:
•
Adding the Replication Member Details
Adding Replication Details
To add new replication details:
Step 1
Choose Configuration > Replication. The Replication Details page is displayed.
Step 2
Specify the replication details.
Step 3
Enter the Replication Member Details, if needed.
Step 4
Click Save to save the new replication details. Otherwise click Reset to restore the default values.
On successful creation of the replication details, a success message is displayed else a respective error message is displayed.
Adding the Replication Member Details
To add new replication member details:
Step 1
Click the Replication Members tab. The List of Replication Members section is displayed.
Step 2
Enter the required details.
Step 3
Click Submit to save the new replication member details.
•
RADIUS Dictionary
The RADIUS dictionary passes information between a script and the RADIUS server, or between scripts running on a single packet.
Table 3-17 lists and describes the fields in the Add Radius Attributes page. The fields listed below are the entire list of all the available types. The fields are displayed based on the type selected.
|
|
|
|---|---|
Name |
Required; must be unique in the Radius dictionary list |
Description |
Optional; description of the attribute |
Attribute |
Required; must be a number between 1-255. It must be unique within the Attribute dictionary list. |
Type |
Required; type governs how the value is interpreted and printed. |
Minimum |
Set to zero |
Maximum |
Set to 253 |
Enum Number |
Enums allow you to specify the mapping between the value and the strings. After you have established this mapping, Cisco Prime AR then replaces the number with the appropriate string. The min/max properties represent the lowest to highest values of the enumeration. |
Enum Equivalent |
The value can range from 1 through 255. Click the Add button to save the details and list it in the Enums list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Tag |
The tag number value can range from 0 through 31. The default value is zero. |
Use the Radius Attributes page for the following:
•
Adding Radius Dictionary Details
Adding Radius Dictionary Details
To add new Radius dictionary details:
Step 1
Choose Configuration > Radius Dictionary. The Radius Attributes page is displayed.
Step 2
Click Add to add new Radius dictionary details. The Add RADIUS Dictionary page is displayed.
Step 3
Enter the required details.
Step 4
Click Submit to save the specified details in the Radius Attributes page. Otherwise click Cancel to return to the Radius Attributes page without saving the details.
On successful creation of the Radius Attributes, the Radius Attributes page is displayed else a respective error message is displayed.
•
Vendor Dictionary
The vendor dictionary allows the user to maintain the attributes of the vendor with respect to vendor id, vendor type and the attributes required to support the major NAS.
Table 3-18 lists and describes the fields in the Add Vendor Dictionary page. The fields listed below are the entire list of all the available types. The fields are displayed based on the type selected.
|
|
|
|---|---|
Name |
Required; must be unique in the Vendor dictionary list |
Description |
Optional; description of the attribute |
Vendor ID |
Required; must be a valid number and unique within the entire attribute dictionary |
Type |
Required; type governs how the value is interpreted and printed. |
Minimum |
Optional; set to zero |
Maximum |
Optional; set to 253 |
Enum Number |
Optional; enums allow you to specify the mapping between the value and the strings. After you have established this mapping, Cisco Prime AR then replaces the number with the appropriate string. The min/max properties represent the lowest to highest values of the enumeration. |
Enum Equivalent |
Optional; the value can range from 1 through 255. Click the Add button to save the details and list it in the Enums list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Tag |
Optional; the tag number value can range from 0 through 31. The default value is zero. |
Vendor Size |
Optional; set the vendor size to 8, 16, or 32 bit |
HasSubAttributeLengthField |
Optional; indicates that the value field of the attribute has the length field for the sub attribute. |
Use the Vendor Dictionary page for the following:
•
Adding Vendor Dictionary Details
Adding Vendor Dictionary Details
To add new vendor dictionary details:
Step 1
Choose Configuration > Vendor Dictionary. The Vendor Attributes page is displayed.
Step 2
Click Add to add new Vendor dictionary details. The Add Vendor Dictionary page is displayed.
Step 3
Enter the required details.
Step 4
Click Submit to save the specified details in the Vendor Attributes page. Otherwise click Cancel to return to the Vendor Attributes page without saving the details.
On successful creation of the vendor dictionary details, the Vendor Attributes page is displayed else a respective error message is displayed.
Note
After adding new vendor dictionary details, you can add vendor attributes details. Or you can also add vendor attributes details by clicking the link in the vendor dictionary list, see Adding Vendor Attributes for details.
Vendor Attributes
Vendor-specific attributes are included in specific RADIUS packets to communicate prepaid user balance information from the Cisco Prime AR server to the AAA client, and actual usage, either interim or total, between the NAS and the Cisco Prime AR server.
Table 3-19 lists and describes the fields in the Add Vendor Attributes page.
|
|
|
|---|---|
Name |
Required; must be unique in the Vendor attribute list |
Description |
Optional; description of the attribute |
Attribute |
Required; must be a valid number and unique within the entire attribute dictionary |
Type |
Required; type governs how the value is interpreted and printed. |
Minimum |
Optional; set to zero |
Maximum |
Optional; set to 253 |
Enum Number |
Optional; enums allow you to specify the mapping between the value and the strings. After you have established this mapping, Cisco Prime AR then replaces the number with the appropriate string. The min/max properties represent the lowest to highest values of the enumeration. |
Enum Equivalent |
Optional; the value can range from 1 through 255. Click the Add button to save the details and list it in the Enums list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Tag |
Optional; the tag number value can range from 0 through 31. The default value is zero. |
Use the Vendor Attributes page for the following:
Adding Vendor Attributes
To add new Vendor attributes:
Step 1
Choose Configuration > Vendor Dictionary. The Vendor Attributes page is displayed.
Step 2
Click the Vendor name link. The Vendor Attributes page is displayed.
Step 3
Click Add to add new Vendor attributes. The Add Vendor Attributes page is displayed.
Step 4
Enter the required details.
Step 5
Click Submit to save the specified details in the Vendor Attributes page. Otherwise click Cancel to return to the Vendor Attributes page without saving the details.
On successful creation of the vendor attributes, the Vendor Attributes page is displayed else a respective error message is displayed.
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 Appendix C, "RADIUS Attributes." of Cisco Prime Access Registrar, 6.0 User Guide.
Note
When you have also set /Radius/IncomingScript, Cisco Prime AR runs that script before the vendor's script. Conversely, when you have set a /Radius/Outgoing script, Cisco Prime AR runs the vendor's script before that script.
Table 3-20 lists and describes the fields in the Add Vendor page.
Use the Vendors page for the following:
Adding Vendor Details
To add new Vendor details:
Step 1
Choose Configuration > Vendors. The Vendors page is displayed.
Step 2
Click Add to add new Vendor details. The Add Vendor page is displayed.
Step 3
Enter the required details.
Step 4
Click Submit to save the specified details in the Vendors page. Otherwise click Cancel to return to the Vendors page without saving the details.
On successful creation of the vendor details, the Vendors page is displayed else a respective error message is displayed.
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:
cd /Radius/Translations
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 Cisco Prime AR server modifies the Request dictionary and inserts, filters and substitutes the attributes accordingly. You can set many translations for one packet and the Cisco Prime AR server applies these translations sequentially.
Note
Later translations can overwrite previous translations.
Table 3-21 lists and describes the fields in the Add Translations page.
|
|
|
|---|---|
General Properties tab |
|
Name |
Required; must be unique in the Translations list. |
Description |
Optional; description of the Translation |
Attribute Type |
Optional; select either RADIUS or VENDOR. If Vendor is selected, specify the vendor type from the drop-down list. Select the attributes from the available list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. |
Attributes tab |
|
Attribute Type |
Optional; select either RADIUS or VENDOR. If Vendor is selected, specify the vendor type from the drop-down list. |
Attribute Name |
Optional; based on the Attribute Type selected, the attribute name is automated. Set the relevant name for the attribute type selected. |
Attribute Value |
Optional; set the value for the selected attribute. Click the Add button to save the details and list it in Radius and Value list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Use the Translations page for the following:
Adding Translation Details
To add new translation details:
Step 1
Choose Configuration > Translations. The Translations page is displayed.
Step 2
Click Add to add new translations details. The Add Translations page is displayed.
Step 3
Enter the required details.
Step 4
Click Add Translation to save the specified details in the Translations page. Otherwise click Cancel to return to the Translations page without saving the details.
On successful creation of the translation details, the Translations page is displayed else a respective error message is displayed.
Translation Groups
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 Cisco Prime AR Rule engine.
The Cisco Prime AR 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:
cd /Radius/TranslationGroups
Add CiscoIncoming
cd CiscoIncoming
cd Translations
Set 1 T1
The translation group is referenced through the Cisco Prime AR 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 3-22 lists and describes the fields in the Add Translation Groups page.
|
|
|
|---|---|
Name |
Required; must be unique in the Translations list. |
Description |
Optional; description of the Translation Group. |
Translations |
Optional; lists of translation. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. |
Use the Translation Groups page for the following:
•
Adding Translation Group Details
Adding Translation Group Details
To add new translation group details:
Step 1
Choose Configuration > TranslationGroups. The Translation Groups page is displayed.
Step 2
Click Add to add new translation group details. The Add TranslationGroup page is displayed.
Step 3
Enter the required details.
Step 4
Click Add TranslationGroup to save the specified details in the Translation Groups page. Otherwise click Cancel to return to the Translation Groups page without saving the details.
On successful creation of the translation group details, the Translation Groups page is displayed else a respective error message is displayed.
DIAMETER
Diameter is a computer networking protocol for Authentication, Authorization and Accounting (AAA). It is a successor to RADIUS or an enhanced version of the RADIUS protocol. It includes numerous enhancements in all aspects, such as error handling and message delivery reliability. It extracts the essence of the AAA protocol from RADIUS and defines a set of messages that are general enough to be the core of the Diameter Base protocol. The various applications that require AAA functions can define their own extensions on top of the Diameter base protocol, and can benefit from the general capabilities provided by the Diameter base protocol.
The following sections can be used to configure diameter transportmanagement properties, sessionmanagement properties, add new application, commands associated with it and application specific AVPs:
General
This section explains how to set Diameter general configuration such as product name, version, and transport management properties.
Setting General Diameter Parameters
Table 3-23 lists and describes the fields in the General Diameter page.
Setting Up the General Diameter Parameters
To set up the general diameter parameters:
Step 1
Choose Configuration > Diameter > General. The General Diameter page is displayed.
Step 2
Specify the required details.
Step 3
Click Set to save the specified details.
On successful creation of the general diameter parameters, a success message is displayed else a respective error message is displayed.
SessionManagement
Diameter Base protocol stack provides the functionality of SessionManagement. Base Stack maintains sessions separately for authentication and accounting messages. Session-Id AVP is used to identify the user session.
Table 3-24 lists and describes the fields in the Session Management page.
Setting Session Management Properties
To set up the session management properties:
Step 1
Choose Configuration > Diameter>SessionManagement. The Session Management page is displayed.
Step 2
Enter the required details and click Set.
On successful creation of the parameters, a success message is displayed else a respective error message is displayed.
Applications
A Diameter application is not a software application, but a protocol based on the Diameter base protocol (defined in RFC 6733). Each application is defined by an application identifier and can add new command codes and/or new mandatory AVPs.
When you click the Add button in the Applications page, the Application Details page is displayed. Table 3-25 lists and describes the fields in the Application Details page.
|
|
|
|---|---|
Name |
Required; name of the application. |
Description |
Optional; description of the application. |
VendorSpecific |
Required; the default is FALSE. If set to FALSE, the application is ordinary application and user is prompted to enter the ApplicationID. If set to TRUE, the application is a VendorSpecific Application. User is prompted to enter VendorSpecificApplicationID and VendorID. |
AuthApplication |
Required; if set to TRUE the application represents AuthApplication else it represents Accounting Application. |
Application ID |
Required; specifies the unique integer value for the application. The following are examples of Diameter application: NASREQ 1 Mobile-IP 2 Diameter Base Accounting 3 Note |
VendorSpecificApplicationID |
Required; specifies the integer value for the vendor specific application. |
VendorID |
Required; specifies the VendorID for the application. Example: DIAMETER 3GPP Cx APPLICATION VendorSpecificApplicationID 16777216 VendorID 10415 |
ApplicationURI |
Optional; specifies the URI of the Application. Eg: "ftp://ftp.ietf.org/internet-drafts/draft-ietf-aaa-diameter-nasreq- 12.txt" |
Commands |
Required; an indexed list from 1 to <n>. Each entry in the list is the name of the command. It specifies the list of commands associated with the application. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. |
Use the Applications page for the following:
•
Adding Diameter Application Details
Adding Diameter Application Details
To add new Diameter application details:
Step 1
Choose Configuration > Diameter > Applications. The Applications page is displayed.
Step 2
Click Add. The Application Details page is displayed.
Step 3
Enter the relevant details.
Step 4
Click Add Application to save the specified details in the Application Details page. Otherwise click Cancel to return to the Applications page without saving the details.
On successful creation of the Applications details, a success message is displayed else a respective error message is displayed.
Commands
Each command in Diameter is associated with a command code. The command can be a request command or an answer command which is identified by the 'R' bit in the Command Flags field of the Diameter header.
When you click the Add button in the commands page, the Command Details page is displayed. Table 3-26 lists and describes the fields in the Command Details page.
You can click the Add button in the Command Details page to add the AVP details. Table 3-27 lists and describes the fields displayed on clicking the Add button.
Adding Diameter Commands
To add the diameter commands:
Step 1
Choose Configuration > Diameter > Commands. The Commands page is displayed.
Step 2
Click Add. The Add Commands page is displayed.
Step 3
Enter the relevant details.
Step 4
Click the required tab and click Add to enter the AVP details.
Step 5
Click Save to save the AVP details or click Cancel to exit the page without saving the details.
Step 6
Click Add Command to save the specified details in the Add Commands page. Otherwise click Cancel to return to the Commands page without saving the details.
The Commands page is displayed with the newly added details or a respective error message is displayed.
Advanced
Advanced objects allow configuring system-level properties and the Attribute dictionary. Under normal system operation, the system-level properties should not be changed.
The following list helps you in defining the system-level properties and attribute dictionary:
•
SNMP
•
DDNS
•
Log
Default
This feature of GUI allows you in configuring the default values for other functionalities of GUI. The configurations set in this feature reflects on all the other features.
Table 3-28 lists and describes the fields in the Default Advanced Details page.
Setting Default Configuration
To set up the default configuration details:
Step 1
Choose Configuration > Advanced > Default. The Default Advanced Details page is displayed.
Step 2
Enter the relevant details.
Step 3
Click Set to save the specified details in the Default Advanced Details page. Otherwise, click Reset to restore the default values. On successful creation of the default configurations, a success message is displayed else a respective error message is displayed.
BackingStore/ServerParam
The Backing Store is a Parsing Tool which helps you in analyzing the session backing store files. It retrieves the information on Radius sessions, clears phantom sessions details manually and processes the binary log files information to user-readable format.
The Server parameters are set to configure objects to remote server using the relevant aregcmd commands.
Table 3-29 lists and describes the fields in the Backing/ServerParam Advanced Details page.
Setting Server Parameters
To set up new server parameters:
Step 1
Choose Configuration > Advanced > Backing/ServerParam. The Backing/ServerParam Advanced Details page is displayed.
Step 2
Specify the relevant details.
Step 3
Click Set to save the specified details in the Backing/ServerParamAdvanced Details page.
On successful creation of the server parameters, a success message is displayed else a respective error message is displayed.
RemoteSessionServer
Cisco Prime AR sessions can also be stored on a remote database. This improves the overall scalability of the number of sessions that Cisco Prime AR can simultaneously handle.
The remote session manager internally uses the following two ODBC remote servers:
•
Internal-ODBC-Read-Server
•
Internal-ODBC-Write-Server.
Configurations pertaining to these internal remoteservers can be done under the RemoteSessionServer section.
Note
Ensure that the length of fields such as Username, Session/Resource Manager name Session-Key, Query-Key and so on are limited to the value specified in the schema, while it is configured. Although the field length of entire session record is 3KB it is limited to 2KB. This is practically sufficient to hold all the session parameters as well as the cached attributes (if any). For more information about the schema, see section Remote Session Management of the Cisco Prime Access Registrar 6.0 User Guide: http://www.cisco.com/en/US/docs/net_mgmt/access_registrar/6.0/user/guide/features.html
Note
Remote session manager will work only with Oracle database.
Table 3-30 lists and describes the fields in the RemoteSessionServer Advanced Details page.
Setting RemoteSessionServer Details
To set a new RemoteSessionServer details:
Step 1
Choose Configuration > Advanced > RemoteSessionServer. The RemoteSessionServer Advanced Details page appears.
Step 2
Specify the relevant details.
Step 3
Click Set to save the specified details in the RemoteSessionServer Advanced Details page.
On successful creation of the RemoteSessionServer details, a success message is displayed else a respective error message is displayed.
SNMP
Cisco Prime AR provides SNMP MIB for users of network management systems. The supported MIBs enable the network management station to collect state and statistic information from a Cisco Prime AR server. It enables a standard SNMP management station to check the current state of the server as well as the statistics on each client or each proxy remote server. These messages contain information indicating that either the server was brought up or down or that the proxy remote server is down or has come back online.
Table 3-31 lists and describes the fields in the SNMP Advanced Details page.
Setting SNMP Details
To set up new SNMP details:
Step 1
Choose Configuration > Advanced > SNMP. The SNMP Advanced Details page is displayed.
Step 2
Specify the relevant details.
Step 3
Click Set to save the specified details in the SNMP Advanced Details page.
On successful creation of the SNMP details, a success message is displayed else a respective error message is displayed.
DDNS
Cisco Prime AR supports Dynamic DNS Remote server. It is a method, protocol, or network that notifies the server to change the active DNS configuration of its configured hostnames, addresses or other information stored in DNS.
You can click the Add button in the DDNS Details page to enter the TSIGKeys details in the TSIGKeys Details section.
Table 3-32 lists and describes the fields in the TSIGKeys Details section.
|
|
|
|---|---|
Name |
Name of the TSIG Key. |
Secret |
Set to the same base64-encoded string as defined in the DNS server. |
Description |
Description of the TSIG Key |
Use the DDNS Details page for the following:
Setting DDNS Details
To set up new DDNS details:
Step 1
Choose Configuration > Advanced > DDNS. The DDNS Details page is displayed.
Step 2
Check the SynthesizeReverseZone check box, and click Set DDNS.
Adding the TSIGKeys for DDNS
To add TSIGKeys details for DDNS:
Step 1
Choose Configuration > Advanced > DDNS. The DDNS Details page is displayed.
Step 2
Click Add. The TSIGKeys details section is displayed.
Step 3
Enter the relevant details.
Step 4
Click Add to save the specified details in the TSIGKeys Details section.
On successful creation of the TSIGKeys details, a success page is displayed else a respective error message is displayed.
ODBC DataSources
Cisco Prime AR uses ODBC as the datasource name to be used by the remote server. Multiple remote servers can use the same ODBCDataSource. Under the ODBCDataSource object definition, a list defines ODBC.ini filename/value pairs for a connection. The list includes a Type field and a Driver field, different for each Driver and Data Source, to indicate its Driver and Data Source. Cisco Prime AR supports only the Easysoft Open Source Oracle Driver.
Table 3-33 lists and describes the fields in the Add ODBC DataSources page.
Use the ODBC DataSources page for the following:
•
Log
Adding ODBC Data Source
To add new ODBC dta source details:
Step 1
Choose Configuration > Advanced > ODBC DataSources. The ODBC DataSources page is displayed.
Step 2
Click Add to add new ODBC data source details. The ODBC DataSources Details page is displayed.
Step 3
Entre the relevant details.
Step 4
Click Submit to save the specified details. Otherwise click Cancel to return to the ODBC DataSources page without saving the details.
The ODBC DataSources page is displayed with the newly added details and a success message is displayed else a respective error message is displayed.
Log
The log files defined in Cisco Prime AR assist you in identifying the issues related to it. Cisco Prime AR holds sets of log files to store information relevant to server agent processes, monitoring arserver utility, execution of aregcme commands, mcd internal database details, radius server processes and debug details of RADIUS request process.
Table 3-34 lists and describes the fields in the Log Files page.
Use the Log Files page for the following:
Viewing Log Details
To view the log files:
Step 1
Choose Configuration > Advanced > Log. The Log Files page is displayed.
Step 2
Choose the appropriate radio button and click View to view the file.
Downloading Log Details
To download the log files:
Step 1
Choose Configuration > Advanced > Log. The Log Files page is displayed.
Step 2
Choose the appropriate radio button and click Download to download the file.
Setting Log Details
To set the log details:
Step 1
Choose Configuration > Advanced > Log. The Log Files page is displayed.
Step 2
Enter the relevant details and click Set to save the specified details.
Ports
The Ports list specifies which ports to listen to for requests. When you specify a port, Cisco Prime AR 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 1645 and Accounting-Requests to 1646, however, Cisco Prime AR does not check.
When you do not specify any ports, Cisco Prime AR reads the /etc/services file for the ports to use for access and accounting requests. If none are defined, Cisco Prime AR uses the standard ports (1645 and 1646).
Table 3-35 lists and describes the fields in the Ports page.
Use the Ports page for the following:
Adding Port Details
To add new port details:
Step 1
Choose Configuration > Advanced > Port. The Ports page is displayed.
Step 2
Enter the relevant details and click Add. The new port details will be listed in the Ports page.
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 AR 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.
Use the interfaces page for the following:
•
Adding IP Addressing Interface
Adding IP Addressing Interface
To add a new IP address interface to define an interface:
Step 1
Choose Configuration > Advanced > Interfaces. The Interfaces page is displayed.
Step 2
Enter the IP Address and click Add.
The Interfaces page is displayed with the newly added details and a success message is displayed else a respective error message is displayed.
Attribute Groups
The Attributes can be grouped using Cisco Prime AR Profile object. The attributes for a particular user group can be grouped under a profile and the attributes contained in the profiles will be returned in their access-accepts.
Table 3-36 lists and describes the fields in the Attribute Groups Details page.
|
|
|
|---|---|
Name |
Name of the attribute group. |
Description |
Optional; description of the attribute group. |
Attribute type |
Select either RADIUS or VENDOR. If Vendor is selected, specify the vendor type from the drop-down list. |
Attribute Name |
Optional; based on the Attribute Type selected, the attribute name is automated. Set the relevant name for the attribute type selected. Click the Add button to save the details and list it in Attribute list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Use the Attribute Groups page for the following:
•
Adding Attribute Group Details
Adding Attribute Group Details
To add new attribute groups details:
Step 1
Choose Configuration > Advanced > Attributes Groups. The Attribute Groups page is displayed.
Step 2
Click Add to add new attribute group details. The Attribute Group Details page is displayed.
Step 3
Enter the relevant details.
Step 4
Click Submit to save the specified details in the Attribute Groups Details page. Otherwise click Cancel to return to the Attribute Groups page without saving the details.
The Attribute Groups page is displayed with the newly added details or a respective error message is displayed.
Rules
A Rule is a function that selects services based on all input information used by the function.
Table 3-37 lists and describes the fields in the Add Rules List page.
|
|
|
|---|---|
General Properties tab |
|
Name |
Required; must be unique in the Rule list. |
Description |
Optional; description of the rule. |
Type |
Required; specifies the type of the rule which can be Radius or Diameter. |
Script Name |
Name of the script. |
Attribute Details tab |
|
RADIUS |
Optional; set Radius, if the attribute and value needs to be defined for Radius. |
VENDOR |
Optional; set Vendor, if the attribute and value needs to be defined for Vendor. |
AttributeName |
Optional; based on the Attribute Type selected, the attribute name is automated. Set the relevant name for the attribute type selected. |
AttributeValue |
Optional; set the value for the selected attribute. Click the Add button to save the details and list it in Name and Value list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Use the Rules List page for the following:
Setting Rules
To set new rules:
Step 1
Choose Configuration > Rules. The List of Rules page is displayed.
Step 2
Click Add. The Rules Details page is displayed.
Step 3
Enter the relevant details.
Step 4
Click Submit to save the specified details in the Rules Details page. Otherwise click Cancel to return to the List of Rules page without saving the details.
The List of Rules page is displayed with the newly added details or a respective error message is displayed.
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 (8 KB in Solaris and 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 Cisco Prime AR, the memory capacity is enhanced to store more than 4 million active session's 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 Cisco Prime AR stores session backing store data (usually the disk partition where Cisco Prime AR 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 3-38 lists and describes the fields in the Session Manager Details page.
|
|
|
|---|---|
Name |
Required; must be unique in the Session Managers list. |
Description |
Optional description of the Session Manager. |
Type |
Required; set to local or remote. Local is the traditional session manager that maintains sessions in memory and has good performance. The remote session manager operates on a remote ODBC database, and its performance is highly dependent on the performance of the ODBC database. |
SessionKey |
SessionKey property is used to set the sessionkey value for the Session Manager. The SessionManager checks whether the environmental variable Session-Key is set or not. If the environmental variable is set, the server uses it as the sessionkey. If environmental variable Session-Key is not set then SessionManager gets the value configured in the SessionKey property under SessionManager. SessionKey can be a combination of attributes separated by colon. The values for those attributes are obtained from the RequestDictionary. If any one of the attribute that is configured for the sessionkey is not present in the RequestDictionary, Cisco Prime AR will drop the request. However, if Session-Key is not set, SessionManager uses NAS-Identifier and NAS-Port to create the sessionkey. An example configuration, --> set SessionKey "User-Name:NAS-Port" The following shows the sample configuration of sessionkey for Session Manager: [ //localhost/Radius/SessionManagers/session-mgr-1 ] Name = session-mgr-1 Description = IncomingScript = OutgoingScript = AllowAccountingStartToCreateSession = TRUE SessionTimeOut = PhantomSessionTimeOut = SessionKey = ResourceManagers/ |
AllowAccountingStartToCreateSession |
Set to TRUE by default; start the session when the Cisco Prime AR server receives an Access Accept or an Accounting-Start. When set to FALSE, start the session when the Cisco Prime AR server receives an Access Accept. |
IncomingScript |
Optional; name of script to run when the service starts. This script is run as soon as the session is acquired in Cisco Prime AR. |
OutgoingScript |
Optional; script to be run just before the session is written to backing store. |
SessionTimeOut |
The SessionTimeOut property is optional; no value for this property means the session timeout feature is disabled. Used in conjunction with /Radius/Advanced/SessionPurgeInterval for the session timeout feature. Enables the session timeout feature for a Session Manager. If the SessionTimeOut property is set to a value under a session manager, all sessions that belong to that session manager will be checked for timeouts at each SessionPurgeInterval. If any sessions have timed out, they will be released, and all resources associated with those sessions are also released. The SessionTimeOut property determines the timeout for a session. If the time difference between the current time and the last update time is greater than this property's value, the session is considered to be stale. The last update time of the session is the time at which the session was created or updated. The SessionTimeOut 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. The default unit is `days'. |
PhantomSessionTimeOut |
Optional; no value for this property means the phantom session timeout feature is disabled. The PhantomSessionTimeOut property is used in conjunction with /Radius/Advanced/SessionPurgeInterval to enable the phantom session timeout feature for Session Manager. If the PhantomSessionTimeOut property is set to a value under a session manager, all sessions that belong to that session manager will be checked for receipt of an Accounting-Start packet. Sessions that do not receive an Accounting-Start packet from creation until its timeout will be released. The PhantomSessionTimeOut value comprises a number and a units indicator, as in n units, where a unit is one of minutes, hours, days, or weeks. The default unit is `days' |
Resource Managers List |
Ordered list of Resource Managers. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. |
MemoryLimitForRadiusProcess |
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 Cisco Prime AR rejects further incoming requests. |
MemorySizeCheckInterval |
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. |
Use the Session Managers page for the following:
•
Adding Session Manager Details
Adding Session Manager Details
To add new session manager details:
Step 1
Choose Configuration > Session Managers. The Session Managers page is displayed.
Step 2
Click Add. The Session Manager Details page is displayed.
Step 3
Enter the required details.
Step 4
Click Add to save the specified details in the Session Manager Details page. Otherwise click Cancel to return to the Session Managers page without saving the details.
The Session Managers page is displayed with the newly added details or a respective error message is displayed.
Resource Manager
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.
•
Session Cache—allows you to define the RADIUS attributes to store in cache.
•
Dynamic-DNS—manages the DNS server.
•
Remote-Session-Cache—allows you to define the RADIUS attributes to store in cache. It should be used with session manager of type 'remote'.
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 AR to reject the request.
Table 3-39 lists and describes the fields in the Resource Manager Details page.
The fields displayed in the Resource Manager Details page changes based on the option selected in the Type field. The following tables describe the fields in the Resource Manager Details page.
DYNAMIC-DNS
Table 3-40 lists and describes the fields in the Resource Manager Details page.
GROUP-SESSION-LIMIT
Table 3-41 lists and describes the fields in the Resource Manager Details page.
|
|
|
|---|---|
Group Session Limit |
Set the GroupSessionLimit property to the maximum number of concurrent sessions for all users. |
REMOTE-GROUP-SESSION-LIMIT
Table 3-42 lists and describes the fields in the Resource Manager Details page.
|
|
|
|---|---|
Group Session Limit |
Set the GroupSessionLimit property to the maximum number of concurrent sessions for all users. |
HOME-AGENT
Table 3-43 lists and describes the fields in the Resource Manager Details page.
|
|
|
|---|---|
HomeAgentIPAddresses tab |
|
Start |
Required; must be an IP address. |
End |
Required; must be an IP address. |
Click the Add button to save the details and list it in Start and End IP list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below.
HOME-AGENT-IPv6
Table 3-44 lists and describes the fields in the Resource Manager Details page.
|
|
|
|---|---|
HomeAgentIPv6Addresses tab |
|
Start |
Required; must be an IPv6 address. |
End |
Required; must be an IPv6 address. |
Click the Add button to save the details and list it in Start and End IPv6 list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below.
IP-DYNAMIC
Table 3-45 lists and describes the fields in the Resource Manager Details page.
Click the Add button to save the details and list it in Start and End IP list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below.
REMOTE-IP-DYNAMIC
Table 3-46 lists and describes the fields in the Resource Manager Details page.
Click the Add button to save the details and list it in Start and End IP list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below.
IP-PER-NAS-PORT
Table 3-47 lists and describes the fields in the Resource Manager Details page.
Click the Add button to save the details and list it in Start and End IP list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below.
IPX-DYNAMIC
Table 3-48 lists and describes the fields in the Resource Manager Details page.
|
|
|
|---|---|
Networks tab |
|
Start |
Required; must be an IP address. |
End |
Required; must be an IP address. |
Click the Add button to save the details and list it in Start and End IP list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below.
SESSION-CACHE
Table 3-49 lists and describes the fields in the Resource Manager Details page.
Click the Add button to save the details and list it in Start and End IP list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below.
SUBNET-DYNAMIC
Table 3-50 lists and describes the fields in the Resource Manager Details page.
Click the Add button to save the details and list it in Start and End IP list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below.
USER-SESSION-LIMIT
Table 3-51 lists and describes the fields in the Resource Manager Details page.
|
|
|
|---|---|
User Session Limit |
Set the user session limit property to the maximum number of concurrent sessions for a particular user |
REMOTE-USER-SESSION-LIMIT
Table 3-52 lists and describes the fields in the Resource Manager Details page.
|
|
|
|---|---|
User Session Limit |
Set the user session limit property to the maximum number of concurrent sessions for a particular user |
USR-VPN
Table 3-53 lists and describes the fields in the Resource Manager Details page.
To edit the gateway details, check the appropriate check box and click the Edit button. Enter new information in the editable fields and click the Save button. You can also delete the record using Delete button.
REMOTE-SESSION-CACHE
Table 3-54 lists and describes the fields in the Resource Manager Details page.
Use the Resource Manager List page for the following:
•
Adding Resource Manager Details
Adding Resource Manager Details
To add new resource manager details:
Step 1
Choose Configuration > Resource Manager. The Resource Manager List page is displayed.
Step 2
Click Add. The Resource Manager Details page is displayed.
Step 3
Enter the required details.
Step 4
Click Submit to save the specified details in the Resource Manager Details page. Otherwise click Cancel to return to the Resource Manager List page without saving the details.
The Resource Manager List page is displayed with the newly added details or a respective error message is displayed.
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.
Network Resources
Network Resources constitutes the maintenance and management of the details of the clients and remote servers. The clients IP address and shared secret details are maintained under clients, The management of server directory with use of remote server protocols details are maintained in remote server.
This section describes the following:
Clients
All NASs and proxy clients that communicate directly with Cisco Prime AR 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 3-55 lists and describes the fields in the Client Details page.
Use the Clients page for the following:
Adding Client Details
To add new Client details:
Step 1
Choose Network Resources > Clients. The Clients page is displayed.
Step 2
Click Add to add new client details. The Client Details page is displayed.
Step 3
Enter the required details in the General Properties, Dynamic Authorization, and Notification Properties tabs.
Step 4
Click Save to save the specified details in the Client Details page. Otherwise click Cancel to return to the Client page without saving the details.
The Client page is displayed with the newly added details or a respective error message is displayed.
Remote Servers
You can use the RemoteServers object to specify the properties of the remote servers to which Services proxy requests.
Cisco Prime AR provides the following RemoteServer protocol types:
•
LDAP
LDAP
Specify the ldap service type when you want to use a particular LDAP remote server for authentication and/or authorization.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.
Table 3-56 lists and describes the fields in the Add LDAP-RemoteServers Details page.
|
|
|
|---|---|
LDAP Properties tab |
|
Name |
Required; name of the LDAP server |
Host Name |
Required; the LDAP server's hostname or IP address. |
Port |
Required; defaults to port 389. |
Description |
Description of the LDAP server. |
Timeout |
Required; the default is 15. The timeout property indicates how many seconds the RADIUS server will wait for a response from the LDAP server. Note |
Reactivate Time Interval |
Required; the amount of time (in milliseconds) to wait before retrying a remote server that was offline. You must specify a number greater than zero. The default is 300,000 (5 minutes). |
MaxReferrals |
Required; must be a number equal to or greater than zero. This property indicates how many referrals are allowed when looking up user information. When you set this property to zero, no referrals are allowed. Cisco Prime AR manages referrals by allowing the RADIUS server's administrator to indicate an LDAP "referral attribute," which might or might not appear in the user information returned from an LDAP query. When this information is returned from a query, Cisco Prime AR assumes it is a referral and initiates another query based on the referral. Referrals can also contain referrals. Note |
Referral Attribute |
Required when you have specified a MaxReferrals value. This property specifies which LDAP attribute, returned from an LDAP search, to check for referral information. Note |
Referral Filter |
Required when you have specified a MaxReferral value. This is the filter Cisco Prime AR uses when processing referrals. When checking referrals, the information Cisco Prime AR finds in the referral itself is considered to be the search path and this property provides the filter. The syntax is the same as that of the Filter property. Note |
Bind Name |
Optional; the distinguished name (dn) to use when establishing a connection between the LDAP and RADIUS servers. |
Bind Password |
Optional; the password associated with the BindName. |
Search Path |
Required; the path that indicates where in the LDAP database to start the search for user information. |
Limit Outstanding Requests |
Required; the default is FALSE. Cisco Prime AR uses this property in conjunction with the MaxOutstandingRequests property to tune the RADIUS server's use of the LDAP server. When you set this property to TRUE, the number of outstanding requests for this RemoteServer is limited to the value you specified in MaxOutstandingRequests. When the number of requests exceeds this number, Cisco Prime AR queues the remaining requests, and sends them as soon as the number of outstanding requests drops to this number. |
User Password Attribute |
Required; this specifies which LDAP field the RADIUS server should check for the user's password. |
Escape Spl.Character in UserName |
FALSE by default |
Datasource Connections |
Specifies the number of concurrent connections to the LDAP server. The default value is 8. |
Use SSL |
A boolean field indicating whether you want Cisco Prime AR to use SSL (Secure Socket Layer) when communicating with this RemoteServer. When you set it to TRUE, be sure to specify the CertificateDBPath field in the Advanced section, and be sure the port you specified for this RemoteServer is the SSL port used by the LDAP server. |
EnableKeepAlive |
Default is FALSE. This is enabled to send a TCP keepalive to keep the idle connection active. |
Filter |
Required; this specifies the search filter Cisco Prime AR uses when querying the LDAP server for user information. When you configure this property, use the notation "%s" to indicate where the user ID should be inserted. For example, a typical value for this property is "(uid=%s)," which means that when querying for information about user |
Max Outstanding Requests |
Required when you have set the LimitOutstandingRequests to TRUE. The number you specify, which must be greater than zero, determines the maximum number of outstanding requests allowed for this remote server. |
Password Encryption Style |
The default is None. You can also specify crypt, dynamic, SHA-1, and SSHA-1. |
DNSLookup and LDAP RebindInterval |
Specifies the timeout period after which the Cisco Prime AR server will attempt to resolve the LDAP hostname to IP address (DNS resolution); 0 by default |
Search Scope |
Specifies how deep to search within a search path; default is SubTree which indicates a search of the base object and the entire subtree of which the base object distinguished name is the highest object. Base indicates a search of the base object only. OneLevel indicates a search of objects immediately subordinate to the base object, but does not include the base object. |
Use Binary Password Comparison |
A boolean field that enables binary password comparison for authentication. This property when set to TRUE, enables binary password comparison. By default, this property is set to FALSE. |
Use Bind Based Authentication |
A boolean field that enables bind-based authentication with LDAP server. By default, this property is set to FALSE. When set to FALSE, it uses existing legacy authentication method. On setting this property to TRUE, the mappings LDAPToRadius, LDAPToEnvironment, and LDAPToCheckItem will not work. |
LDAPToRadiusMappings tab |
|
LDAPAttribute |
Set the value for the LDAP attribute |
RadiusAttribute |
A list of name/value pairs in which the name is the name of the ldap attribute to retrieve from the user record, and the value is the name of the RADIUS attribute to set to the value of the ldap attribute retrieved. For example, when the LDAPToRadiusMappings has the entry: FramedIPAddress = Framed-IP-Address, the RemoteServer retrieves the FramedIPAddress attribute from the ldap user entry for the specified user, uses the value returned, and sets the Response variable Framed-IP-Address to that value. Click the Add button to save the details and list it in the attribute list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
LDAPToCheckItems Mappings tab |
|
Attribute Type |
Select either RADIUS or VENDOR. If Vendor is selected, specify the vendor type from the drop-down list. |
LDAPAttribute |
Set the value for the LDAP attribute |
CheckedItems |
A list of LDAP attribute/value pairs which must be present in the RADIUS access request and must match, both name and value, for the check to pass. For example, when the LDAPToCheckItemMappings has the entry: group = User-Group, the Access Request must contain the attribute group, and it must be set to User-Group. Click the Add button to save the details and list it in the attribute list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
LDAPToEnvironmentalMappings tab |
|
LDAPAttribute |
Set the value for the LDAP attribute |
EnvironmentalAttribute |
A list of name/value pairs in which the name is the name of the ldap attribute to retrieve from the user record, and the value is the name of the Environment variable to set to the value of the ldap attribute retrieved. For example, when the LDAPToEnvironmentMappings has the entry: group = User-Group, the RemoteServer retrieves the group attribute from the ldap user entry for the specified user, uses the value returned, and sets the Environment variable User-Group to that value. Click the Add button to save the details and list it in the attribute list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Use the LDAP-RemoteServers page for the following:
Adding LDAP Details
To add new LDAP details:
Step 1
Choose Network Resources > RemoteServers > LDAP. The LDAP-RemoteServers page is displayed.
Step 2
Click Add to add LDAP details. The LDAP-RemoteServers Details page is displayed.
Step 3
Enter the required details in the tabs.
Step 4
Click Save LDAP Server to save the specified details in the LDAP-RemoteServers Details page. The LDAP-RemoteServers page is displayed with the newly added details or a respective error message is displayed. Otherwise click Cancel to return to the LDAP-RemoteServers page without saving the details.
LDAP Accounting
Previous releases of Cisco Prime AR supported accessing user data from an LDAP server, but this feature was limited to performing authentication and authorization (AA). You could only write the accounting records to local file or oracle database or proxy to another RADIUS server. Cisco Prime AR supports writing accounting records into LDAP server enabling integration between billing systems and LDAP.
Table 3-57 lists and describes the fields in the LDAPAcct RemoteServer Details page.
|
|
|
|---|---|
LDAP Acct Properties tab |
|
Name |
Name of the remote server; this property is mandatory, and there is no default. |
Description |
Optional description of server. |
HostName |
Required; the LDAP server's hostname or IP address. |
Port |
Required; the default value is 389. Port the LDAP server is listening on. |
Timeout |
Mandatory time interval (in seconds) to wait for LADP-write operation to complete; defaults to 15 seconds. |
ReactivateTimerInterval |
Mandatory time interval (in milliseconds) to activate an inactive server; defaults to 300000 ms. |
BindName |
Optional; the distinguished name (dn) to use when establishing a connection between the LDAP and RADIUS servers. |
EnableKeepAlive |
Required; default is FALSE. This is enabled to send a TCP keepalive to keep the idle connection active. |
Delimiter |
Character used to separate the values of the attributes given in AttributeList property. |
LDAPEnvironmentMultiValueDelimiter |
Optional; allows you to specify a character that separates multi-valued attribute lists when using ldap-accounting. |
BindPassword |
Optional; the password associated with the BindName. |
DnPath |
Required; the path that indicates where in the LDAP database to start the write for user information. |
EntryName |
Required; this specifies the write entry name Cisco Prime AR uses when insetting the LDAP server for user information. When you configure this property, use the notation "%s" to indicate where the user ID should be inserted. For example, a typical value for this property is "(uid=%s)," which means that when insetting for information about user joe, use the fentry name uid=joe. |
LimitOutstandingRequests |
Required; the default is FALSE. Cisco Prime AR uses this property in conjunction with the MaxOutstandingRequests property to tune the RADIUS server's use of the LDAP server. When you set this property to TRUE, the number of outstanding requests for this RemoteServer is limited to the value you specified in MaxOutstandingRequests. When the number of requests exceeds this number, Cisco Prime AR queues the remaining requests, and sends them as soon as the number of outstanding requests drops to this number. |
MaxOutstandingRequests |
Required when you have set the LimitOutstandingRequests to TRUE. The number you specify, which must be greater than zero, determines the maximum number of outstanding requests allowed for this remote server. |
ObjectClass |
Required; list of object classes which are all schemas defined in LDAP server. These schemas define required attributes and allowed attributes for an entry which is inserted from Cisco Prime AR. |
DNSLookup and LDAPAcct RebindInterval |
Specifies the timeout period after which the Cisco Prime AR server will attempt to resolve the LDAP hostname to IP address (DNS resolution). |
Escape Spl.Character in UserName |
FALSE by default. |
AttributeList |
List of comma-separated attribute names. |
Datasource Connections |
Mandatory number of connections to be established; defaults to 8. |
UseLocalTimeZone |
Optional; the default is FALSE. It determines the timezone of accounting records TimeStamp. |
UseSSL |
A boolean field indicating whether you want Cisco Prime AR to use SSL (Secure Socket Layer) when communicating with this RemoteServer. When you set it to TRUE, be sure to specify the CertificateDBPath field in the Advanced section, and be sure the port you specified for this RemoteServer is the SSL port used by the LDAP server. |
AttributestoWrite tab |
|
LDAPAcctAttribute |
Set the LDAP Accounting attribute. |
EnvironmentalAttribute |
A list of name and value pairs in which the name is the name of the data store attribute to retrieve from the user record, and the value is the name of the RADIUS attribute to set to the value of the data store attribute retrieved. The data store attributes must match those defined in the external SQL file. Click the Add button to save the details and list it in the Attributes list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Use the LDAP Acct-RemoteServers page for the following:
•
Adding LDAP Accounting Details
Adding LDAP Accounting Details
To add new LDAP accounting details:
Step 1
Choose Network Resources > RemoteServers > LDAP Accounting. The LDAPAcct-RemoteServers page is displayed.
Step 2
Click Add to add LDAP accounting details. The LDAPAcct RemoteServer Details page is displayed.
Step 3
Enter the required details in the tabs.
Step 4
Click Save LDAP Acct Server to save the specified details in the LDAPAcct RemoteServer Details page. Otherwise click Cancel to return to the LDAPAcct-RemoteServers page without saving the details.
The LDAPAcct-RemoteServers page is displayed with the newly added details or a respective error message is displayed.
Domain Authentication
The Domain Authentication service type, domain-auth, is used with a Remote Server of the same type to provide support for authentication against Windows Domain Controller/Active Directory (WDC/AD).
You can click the Add button in the Domain Authentication-RemoteServers page to add new domain authentication details in the Domain Authentication-RemoteServers Details page. Table 3-58 lists and describes the fields in the Domain Authentication-RemoteServers Details page.
|
|
|
|---|---|
General Properties tab |
|
Name |
Required; name of the domain authentication server. |
Host Name |
Required; hostname or IP address of the remote server. |
Port |
Required; port used for communication with WDC/AD; defaults to 2004. |
Default Domain |
Species the default domain for authentication if the user does not include a domain during log in. Otherwise, authentication is performed on the local domain. |
Agent Connections |
Required; default is 15. Represents the total number of connections Cisco Prime AR can open with the CSRA. |
Description |
Optional; description of the domain authentication server. |
Timeout |
Required; defaults to 15. |
Reactivate Time Interval |
Required; default is 300,000 milliseconds. Specifies the length of time to wait before attempting to reconnect if a thread is not connected to a data source. |
Workstation |
Optional; if a user has this workstation property set to some value, in Active Directory, then during authentication, AD will check with the CLI workstation value of Cisco Prime AR. Only if they match authentication will succeed. If this workstation value is not set in AD, no comparison with CLI workstation field happens. |
Default Usergroup |
User group to be used when no mapping is found in the list of maps in the GroupMap property or when there is no hit in the groups listed in GroupMaps. The DefaultUserGroup is used to authorize users that are authenticated by this domain-auth RemoteServer. |
GroupMaps tab |
|
AR UserGroup |
Select a user group from the drop-down list. |
AD UserGroups |
A list of groups to which the user belongs in the WDC/AD mapped to an internal group in the Cisco Prime AR server. Entries are of the form: 1. "InternalGroup1 = ExternalGroup1, ExternalGroup2, ..." 2. "InternalGroup2 = ExternalGroup3, ExternalGroup4, ..." To configure group mappings, use the following syntax: set 1 "Group1 = ExternalGroup1,ExternalGroup2, ExternalGroup3" Click the Add button to save the details and list it in the attribute list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Use the Domain Authentication-RemoteServers page for the following:
•
Adding Domain Authentication Details
Adding Domain Authentication Details
To add new domain authentication details:
Step 1
Choose Network Resources > RemoteServers > Domain Authentication. The Domain Authentication-RemoteServers page is displayed.
Step 2
Click Add to add domain authentication details. The Domain Authentication-RemoteServers Details page is displayed.
Step 3
Enter the required details in the tabs.
Step 4
Click Add Domain-Auth Server to save the specified details in the Domain Authentication-RemoteServers Details page. Otherwise click Cancel to return to the Domain Authentication-RemoteServers page without saving the details.
The Domain Authentication-RemoteServers page is displayed with the newly added details or a respective error message is displayed.
ODBC/OCI
Specify odbc or oci when you want to use an ODBC or OCI service for authentication, authorization and accounting through an ODBC or OCI data store respectively. Use an ODBC or OCI service to authenticate and authorize an access requests by querying user information through ODBC or OCI and to insert accounting records into a data store through ODBC or OCI.
Note
The ODBC service supports MYSQL and Oracle database service and OCI supports Oracle with 10.2.0 to 11.2.0 Oracle client.
Table 3-59 lists and describes the fields in the ODBC/OCI-RemoteServers Details page.
|
|
|
|---|---|
Name |
Required; name of the ODBC/OCI Server. |
Protocol |
The type of remote server. You select the option ODBC or OCI from the dropdown list. |
Datasource Connections |
Required; default is 8. This represents the total number of connections Cisco Prime AR can open with the ODBC server; total number of threads Cisco Prime AR can create for the ODBC server. |
ODBC Datasource Name |
Required; name of the ODBCDataSource to use and must refer to one entry in the list of ODBC datasources configured under /Radius/Advanced/ODBCDataSources. |
User Password Attribute |
Set the user password. |
SNMPTrapIP |
The SNMP trap IP for the remote servers. |
Description |
Description of the ODBC Server |
Timeout |
Required; the default is 15. The timeout property indicates how many seconds the RADIUS server will wait for a response from the ODBC server. Note |
Reactivate Time Interval |
Required; default is 300,000 milliseconds. Length of time to wait before attempting to reconnect if a thread is not connected to a data source. |
Keep Alive Timer Interval |
Mandatory time interval (in milliseconds) to send a keepalive to keep the idle connection active; defaults to zero (0) meaning the option is disabled |
SNMPTrapPort |
The SNMP trap port for the remote server; defaults to 1521. |
SQL Definitions tab |
|
Name |
SQLDefinition properties define the SQL you want to execute. |
Description |
Description of the SQL |
Type |
Cisco Prime AR supports only type query. |
SQL |
SQL query used to add, update or delete a record from a database |
Execution SequenceNumber |
Sequence number for SQLStatement execution, must be greater than zero (mandatory, no default) |
Marker List |
Defines all markers for the query. MarkerList uses the format UserName/SQL_DATA_TYPE. |
RadiusMappings tab |
|
ODBC/OCI Attribute |
Set the ODBC or OCI attribute |
RADIUS Attribute |
A list of name and value pairs in which the name is the name of the data store attribute to retrieve from the user record, and the value is the name of the RADIUS attribute to set to the value of the data store attribute retrieved. The data store attributes must match those defined in the external SQL file. Click the Add button to save the details and list it in the Attributes list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
CheckItemsMappings tab |
|
Attribute Type |
Select either RADIUS or VENDOR. If Vendor is selected, specify the vendor type from the drop-down list. |
ODBC/OCI Attribute |
Set the ODBC or OCI attribute |
CheckItem |
A list of ODBC attribute/value pairs. Click the Add button to save the details and list it in the Attributes list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
EnvironmentalMappings tab |
|
ODBC/OCI Attribute |
Set the ODBC or OCI attribute |
Environmental Attribute |
A list of name/value pairs in which the name is the name of the data store attribute to retrieve from the user record, and the value is the name of the Environment variable to set to the value of the ODBC attribute retrieved. Click the Add button to save the details and list it in the Attributes list. To navigate between the listed attributes, use the navigation option available adjacent to the list. See Relocating Records for more details. To delete the available attributes, select the relevant attribute and click the Delete button below. |
Use the ODBC/OCI-RemoteServers page for the following:
Adding ODBC/OCI Details
To add new ODBC or OCI details:
Step 1
Choose Network Resources > RemoteServers > ODBC/OCI. The ODBC/OCI-RemoteServers page is displayed.
Step 2
Click Add to add ODBC or OCI details. The ODBC/OCI-RemoteServers Details page is displayed.
Step 3
Enter the required details.
Step 4
Click Add to enter the SQL details in the SQL Definitions tab.
Step 5
Click Save to save the specified details in the SQL Definitions tab or click Cancel to cancel the action.
Step 6
Enter the required details in the tabs.
Step 7
Click Add Server to save the specified details in the ODBC/OCI-RemoteServers Details page. Otherwise click Cancel to return to the ODBC/OCI-RemoteServers page without saving the details.
The ODBC/OCI-RemoteServers page is displayed with the newly added details or a respective error message is displayed.
ODBC/OCI-Accounting
If you use the Oracle Accounting feature, you must configure an ODBC/OCI-Accounting RemoteServer object.
Table 3-60 lists and describes the fields in the Add ODBC/OCI Accounting-RemoteServers page.
Use the ODBC/OCI Accounting-RemoteServers page for the following:
•
Adding ODBC/OCI Accounting Details
Adding ODBC/OCI Accounting Details
To add new ODBC or OCI accounting details:
Step 1
Choose Network Resources > RemoteServers > ODBC/OCI Accounting. The ODBC/OCI Accounting-RemoteServers page is displayed.
Step 2
Click Add to add ODBC or OCI accounting details. The ODBC/OCI Accounting-RemoteServers Details page is displayed.
Step 3
Enter the required details in the tabs.
Step 4
Click Add Accounting Server to save the specified details in the ODBC/OCI Accounting-RemoteServers Details page. The ODBC/OCI Accounting-RemoteServers page is displayed with the newly added details or a respective error message is displayed. Otherwise click Cancel to return to the ODBC/OCI Accounting-RemoteServers page without saving the details.
Others
This feature of GUI allows you to set other specifications. The various types of protocols are:
•
Radius
•
Dynamic DNS
•
Map-Gateway
•
Prepaid-CRB
•
Prepaid IS 835C
•
Sigtran
•
Sigtran-m3ua
Table 3-61 lists and describes the fields in the Remote Server Details page. The fields listed below are the entire list of all the available protocols. The fields are displayed based on the type of protocol selected.
Use the RemoteServers page allows for the following:
Setting Other Specifications
To set up other specifications:
Step 1
Select Network Resources > RemoteServers > Others. The RemoteServers page is displayed.
Step 2
Click Add to add other specifications. The Remote Server Details page is displayed.
Step 3
Enter the required details.
Step 4
Click Add Radius Server to save the specified details in the Remote Server Details page. Otherwise click Cancel to return to the RemoteServers page without saving the details.
The RemoteServers page is displayed with the newly added details or a respective error message is displayed.
Administration
Administration constitutes the maintenance and management of details specific administrator, various statistical data respective to the administrators, backing up and restoring server details, and license management of the server.
This section describes the following:
Administrators
Cisco Prime AR provided super-user administrative access in which administrator can perform all tasks including starting and stopping the system and changing the configuration. Cisco Prime AR also provides view-only administrative access. View-only access restricts an administrator to only being able to observe the system and prevents that user from making changes.
Table 3-62 lists and describes the fields in the Administrator Details page.
Use the Administrators page for the following:
Adding Administrator Details
To add new Administrator details:
Step 1
Choose Administration > Administrators. The Administrators page is displayed.
Step 2
Click Add to add administrator details. The Administrator Details page is displayed.
Step 3
Specify the required details.
Step 4
Click Submit to save the specified details in the Administrator Details page. Otherwise click Cancel to return to the Administrators page without saving the details.
The Administrators page is displayed with the newly added details or a respective error message is displayed.
Statistics
This feature provides statistical information on the specified server.
Table 3-63 lists the statistics information and the meaning of the values.
Resetting Server Statistics
To reset server statistics:
Step 1
Choose Administration > Statistics. The Radius Server Statistics page is displayed.
Step 2
Click Reset to reset all the radius server statistics.
Diameter Statistics
Cisco Prime AR supports statistic of Diameter messages through the CLI/GUI and SNMP. The existing `stats' module has been extended to include additional counters related to Diameter. The diameter statistics includes peer statistics and global summary statistics details on the specified server.
Table 3-64 and Table 3-65 lists the statistics information and the meaning of the values. The statistical information in Table 3-65 is displayed based on the peer selected.
Select the required peer from the Client drop-down list and click the Show Peer Stats button to view the diameter statistics of the peer. Click the Reset button, to reset all the diameter statistics of the peer.
TACACS Statistics
Cisco Prime AR supports CISCO-AAA-SERVER-MIB to describe the statistics of TACACS+ protocol. This is supported through CLI/GUI and SNMP.
Table 3-66 lists the statistics information and the meaning of the values.
Backup and Restore
To backup and restore the server details, Choose Administration > Backup & Restore. The Backup page is displayed with the list of recently backed up details of the server with the date and time. This option allows you to take a backup of the database, sessions, and scripts, and stores it in /cisco-ar/backup directory.
Backup Server Details
To backup the server details:
Step 1
Choose Administration > Backup & Restore. The Backup page is displayed.
Step 2
Click Backup to take a backup of the database, sessions, and scripts, and stores it in /cisco-ar/backup directory. The details will be backed up and appended to the backup list and displayed in the Backup page.
Restoring Server Details
To restore the backed-up server details:
Step 1
Choose Administration > Backup & Restore. The Backup page is displayed.
Step 2
Choose the record from the backup list.
Step 3
Click Restore. The details of the selected back up file will be restored successfully.
License Upload
Cisco Prime AR license information are uploaded using the Upload feature. To upload the license file, Choose Administration > License Upload. The Cisco Prime AR License - Upload page appears. Click the Browse button, to locate the license file. The file selector dialog box appears. Choose the file. To upload the license file, click the Upload button. To clear the text in the field, click the Reset button.
Uploading License File
To upload the Cisco Prime AR license file:
Step 1
Choose Administration > License Upload. The Cisco Prime AR License-Upload page is displayed.
Step 2
Click Browse to locate the license file. The File Upload dialog box is displayed.
Step 3
Choose the required file.
Step 4
Click Upload. The selected file will be uploaded in /cisco-ar/license directory.
Note
You need to ensure that the license file that you want to upload should be in .lic format.
Step 5
Click Reset to clear the text in the Select the File field, if you want to clear the selected path.
Read-Only GUI
Cisco Prime AR provides a read-only GUI that enables an administrator to observe the system but prevents that administrator from making changes.
When you configure a user to be an administrator, check the View-Only check box to limit the administrator to view-only operation. You can also use the CLI by setting the View-Only property to TRUE under /Administrator/admin_name.
When using the Read-Only GUI, the Configuration, Network Resources and Administration sections are displayed as same as a fully-enabled administrator. The details of these sections are displayed in text format and cannot be edited.
Feedback