Cisco Prime Access Registrar 6.0.2 Release Notes
Available Languages
Table of Contents
Cisco Prime Access Registrar 6.0.2 Release Notes
Enhanced Features in Cisco Prime Access Registrar 6.0.2
Support for Parallelization in SIGTRAN / M3UA Remote Servers
Co-Existence With Other Network Management Applications
Known Anomalies in Cisco Prime Access Registrar 6.0.2.4
Known Anomalies in Cisco Prime Access Registrar 6.0.2.3
Known Anomalies in Cisco Prime Access Registrar 6.0.2.1
Known Anomalies in Cisco Prime Access Registrar 6.0.2
Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.4
Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.3
Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.2
Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.1
Anomalies Fixed in Cisco Prime Access Registrar 6.0.2
Obtaining Documentation and Submitting a Service Request
Cisco Prime Access Registrar 6.0.2
Release Notes
Cisco Prime Access Registrar (Prime Access Registrar) is a high performance, carrier class 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 5.3/5.4/5.5/6.0/6.1/6.2 32-bit /64-bit operating system (64-bit operating system can be used with the required 32-bit libraries installed) using kernel 2.6.18-128.el5 or later versions of 2.6, and Glibc version: glibc-2.5-34 or later.
Contents
This release note contains the following sections:
- Enhanced Features in Cisco Prime Access Registrar 6.0.2
- System Requirements
- Co-Existence With Other Network Management Applications
- Known Anomalies in Cisco Prime Access Registrar 6.0.2.4
- Known Anomalies in Cisco Prime Access Registrar 6.0.2.3
- Known Anomalies in Cisco Prime Access Registrar 6.0.2.1
- Known Anomalies in Cisco Prime Access Registrar 6.0.2
- Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.4
- Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.3
- Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.2
- Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.1
- Anomalies Fixed in Cisco Prime Access Registrar 6.0.2
- Related Documentation
Enhanced Features in Cisco Prime Access Registrar 6.0.2
Prime Access Registrar has the following enhancements for 6.0.2:
HLR GT Caching
The Home Location Registry (HLR) Global Title address (GT address in calling party address (CgPA)) from the SendAuthenticationInfo (SAI) response is cached and used for subsequent authorization request. This cached HLR GT is added to the environment dictionary of the packet to be available for the authorization flow.
The following environment dictionary variables are added to hold the cached HLR GT:
- HLR-GlobalTitle-Cached—Set as TRUE to indicate the HLR GT is cached
- Cached-HLR-GlobalTitle-Digits
- Cached-HLR-Translation-Type
- Cached-HLR-Numbering-Plan
- Cached-HLR-Encoding-Scheme
- Cached-HLR-Nature-Of-Address
- Cached-HLR-GT-Format
The cached HLR GT overrides both the configured destination GT values and GT script provided GT values. The HLR GT caching works by default for RTE_GT. The cached HLR GT can be overridden by updating the environment variable HLR-GlobalTitle-Cached to FALSE (or anything other than TRUE) in the GT script.
Support for Parallelization in SIGTRAN / M3UA Remote Servers
Whenever Prime Access Registrar sends a packet to a remote server, it waits for a response from the remote server before sending further packets to the same or other remote servers (as configured). This causes performance impact. Prime Access Registrar 6.0.2 introduces a feature that allows mutiple simultaneous outstanding requests to be sent to the same or other remote servers (as configured).
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 6.0.2.
Note
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 Installing and Configuring Cisco Prime Access Registrar, 6.0.
Known Anomalies in Cisco Prime Access Registrar 6.0.2.4
Table 2 lists the known anomalies in Prime Access Registrar 6.0.2.4.
Known Anomalies in Cisco Prime Access Registrar 6.0.2.3
Table 3 lists the known anomaly in Prime Access Registrar 6.0.2.3.
Known Anomalies in Cisco Prime Access Registrar 6.0.2.1
Table 4 lists the known anomaly in Prime Access Registrar 6.0.2.1.
Known Anomalies in Cisco Prime Access Registrar 6.0.2
Table 5 lists the known anomaly in Prime Access Registrar 6.0.2.
Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.4
Table 6 lists the anomalies fixed in Prime Access Registrar 6.0.2.4.
Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.3
Table 7 lists the anomalies fixed in Prime Access Registrar 6.0.2.3.
Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.2
Table 8 lists the anomalies fixed in Prime Access Registrar 6.0.2.2.
Anomalies Fixed in Cisco Prime Access Registrar 6.0.2.1
Table 9 lists the anomalies fixed in Prime Access Registrar 6.0.2.1.
Anomalies Fixed in Cisco Prime Access Registrar 6.0.2
Table 10 lists the anomalies fixed in Prime Access Registrar 6.0.2.
Related Documentation
The following is a list of the documentation for Prime Access Registrar 6.0.2. You can access the URLs listed for each document at www.cisco.com on the World Wide Web. We recommend that you refer to the documentation in the following order:
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
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. (1110R)
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