Cisco Prime Access Registrar 7.2.2 Release Notes
Available Languages
Table of Contents
Cisco Prime Access Registrar 7.2.2 Release Notes
Co-Existence With Other Network Management Applications
Enhanced Feature in CiscoPrimeAccessRegistrar 7.2.2
Cisco Prime Access Registrar 7.2.2 Bugs
Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.4
Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.3
Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.2
Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.1
Cisco Prime Access Registrar 7.2.2
Release Notes
Cisco Prime Access Registrar (Prime Access Registrar) is a high performance, carrier class, 3GPP-compliant, 64-bit RADIUS/Diameter solution that provides scalable, flexible, intelligent authentication, authorization, and accounting (AAA) services.
Prime Access Registrar comprises a RADIUS/Diameter server designed from the ground up for performance, scalability, and extensibility for deployment in complex service provider environments including integration with external data stores and systems. Session and resource management tools track user sessions and allocate dynamic resources to support new subscriber service introductions.
Note Prime Access Registrar can be used with Red Hat Enterprise Linux (RHEL) 6.4/6.6/7.0/7.2 and CentOS 6.5 64-bit operating systems using kernel and Glibc.
System Requirements
This section describes the system requirements to install and use the Prime Access Registrar software.
Table 1 lists the system requirements for Prime Access Registrar 7.2.2.
Co-Existence With Other Network Management Applications
To achieve optimal performance, Prime Access Registrar should be the only application running on a given server. In certain cases, when you choose to run collaborative applications such as a SNMP agent, you must configure Prime Access Registrar to avoid UDP port conflicts. The most common conflicts occur when other applications also use ports 2785 and 2786. For more information on SNMP configuration, see the Configuring SNMP section, in the Cisco Prime Access Registrar 7.2 Installation and Configuration Guide .
Enhanced Feature in Cisco Prime Access Registrar 7.2.2
Prime Access Registrar 7.2.2 provides the following feature:
Location AVP Support
In 3GPP authorization service, if the FetchLocationInformation parameter is enabled, Prime Access Registrar tries to fetch the location information of the client by sending a User Data Request (UDR) to HSS. The HSS sends a User Data Response (UDA), which includes the geographical location type and location information of the client.
Prime Access Registrar parses the UDA and encodes the geographical location information into 3GPP-User-Location-Info AVP and sends it as part of the Diameter-EAP-Answer (DEA) to the client.
A sample configuration of the 3GPP authorization service is given below:
And, 3GPP-User-Location-Info AVP is added to the Diameter Dictionary.
Cisco Prime Access Registrar 7.2.2 Bugs
For more information on a specific bug or to search all bugs in a particular Prime Access Registrar release, see Using the Bug Search Tool.
This section contains the following information:
- Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.4
- Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.3
- Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.2
- Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.1
Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.4
Table 2 lists the anomalies fixed in Prime Access Registrar 7.2.2.4.
Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.3
Table 3 lists the anomalies fixed in Prime Access Registrar 7.2.2.3.
Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.2
Table 4 lists the anomalies fixed in Prime Access Registrar 7.2.2.2.
Fixed Anomalies in Cisco Prime Access Registrar 7.2.2.1
Table 5 lists the anomalies fixed in Prime Access Registrar 7.2.2.1.
Using the Bug Search Tool
Use the Bug Search tool (BST) to get the latest information about Cisco Prime Access Registrar bugs. BST allows partners and customers to search for software bugs based on product, release, and keyword, and it aggregates key data such as bug details, product, and version.
- Quickly scan bug content
- Configure e-mail notifications for updates on selected bugs
- Start or join community discussions about bugs
- Save your search criteria so you can use it later
When you open the Bug Search page, check the interactive tour to familiarize yourself with these and other Bug Search features.
Step 1 Log into the Bug Search Tool.
a. Go to https://tools.cisco.com/bugsearch .
b. At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Search page opens.
Note If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.
Step 2 To search for a specific bug, enter the bug ID in the Search For field and press Return.
Step 3 To search for bugs in a particular release:
a. In the Search For field, enter the product name and the release version, e.g. Cisco Prime Access Registrar 7.2.2, and press Return. (Leave the other fields empty.)
b. When the search results are displayed, use the filter and sort tools to find the types of bugs you are looking for. You can search for bugs by severity, by status, how recently they were modified, according to the number of support cases associated with them, and so forth.
Related Documentation
The following documentation is available for Prime Access Registrar 7.2.2:
- Cisco Prime Access Registrar 7.2 User Guide
- Cisco Prime Access Registrar 7.2.2 Release Notes (this guide)
For a complete list of Cisco Prime Access Registrar 7.2 documentation, see the Cisco Prime Access Registrar 7.2 Documentation Overview .
Note We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Feedback