Cisco Prime Access Registrar 8.0.4 Release Notes
Co-Existence With Other Network Management Applications
Enhanced Features in Cisco Prime Access Registrar 8.0.4.1
SNMP Trap Support for Throttling Active and Inactive States
Support for Preemptive Recovery
Support for Duplicate Authentication Request Detection
Enhanced Features in Cisco Prime Access Registrar 8.0.4
Configuring Unique TAG number for Vendor-Specific Sub Attributes
Cisco Prime Access Registrar 8.0.4 Bugs
Fixed Anomalies in Cisco Prime Access Registrar 8.0.4.2
Fixed Anomalies in Cisco Prime Access Registrar 8.0.4.1
Fixed Anomalies in Cisco Prime Access Registrar 8.0.4
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) 7.7 or CentOS 6.5 and above operating system. Prime Access Registrar has no special OS dependencies; therefore there are no restrictions from upgrading to newer releases of RHEL or CentOS.
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 8.0.4.x.
Prime Access Registrar supports JDK versions 1.7 and 1.8.
Note These are the minimum system requirements to have Prime Access Registrar up and running. This may vary based on the deployments. Please contact your BU team to know the specific system requirements for your deployment.
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 “Configuring Cisco Prime Access Registrar” chapter of the Cisco Prime Access Registrar 8.0 Administrator Guide.
Cisco Prime Access Registrar 8.0.4.1 provides the following enhancements:
A new parameter ThrottlingMonitorFrequencyInSecs is introduced under RADIUS/Advanced/Diameter/TransportManagement/ to support this feature. Prime Access Registrar monitors whether traffic is throttled every second over the configured interval. If throttling occurs for at least half of the configured seconds, a throttling trap is sent from Prime Access Registrar. E.g. if the configured value is 60 seconds, and throttling occurs for at least 30 seconds during the configured duration of 60 seconds, then throttling trap is sent from Prime Access Registrar. When no throttling occurs during the entire interval, a throttling reset trap is sent.
By default, ThrottlingMonitorFrequencyInSecs is set to zero (0), which indicates that throttling trap functionality is disabled and throttling traps should not flow even if throttling conditions are met. Minimum non-zero value that can be configured is 20.
Reporting of All Workers Temporarily Busy warning has been added to the System Stats Log under the parameter Peak Worker Thread Queue / sec, and is only reported if the condition has occurred during the last statistics interval.
The Preemptive recovery enhancement addresses the automatic recovery of Prime Access Registrar when it enters into a presumed unrecoverable state. Following are the conditions when Prime Access Registrar can enter into a presumed unrecoverable state:
Following are the parameters introduced to support this feature:
When the EnablePreeemptiveRecovery parameter is enabled and the presumed unrecoverable state is detected, Prime Access Registrar sends a PreemptiveRecovery Trap and restarts the RADIUS process. This trap indicates that preemptive recovery has been initiated because the number of DER EAP-AKA Challenge (DER2) received by Prime Access Registrar is less than 10% of the successful DER EAP-AKA responses being sent for the initial Identity request (DEA1).
With this enhancement, Prime Access Registrar can detect duplicate authentication requests based on UE session ID. If any diameter request packet has a Session ID same as that of a packet that is already being processed, the new request is silently dropped/ignored from processing.
A new parameter EnableDuplicateSessionIdDetection is introduced under /Radius/Advanced/ to support this functionality. By default, this parameter is enabled.
This enhancement is primarily provided so that the server does not respond with a 3004 (Diameter Too Busy) status for a request that is already in progress; instead drop the duplicate request packet silently.
Cisco Prime Access Registrar 8.0.4 provides the following enhancement:
With this enhancement, Prime Access Registrar allows you to configure a unique tag number for each of the multiple vendor-specific sub-attributes available for a user profile. This enhancement is applicable for multi-tag valued vendor-specific attributes with type as TAG_STRING and TAG_INT.
This section contains the following information:
Table 2 lists the anomaly fixed in Prime Access Registrar 8.0.4.2 release.
Table 3 lists the anomalies fixed in Prime Access Registrar 8.0.4.1 release.
Table 4 lists the anomalies fixed in Prime Access Registrar 8.0.4 release.
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.
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 8.0.4, 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.
For a complete list of Cisco Prime Access Registrar documentation, see the Cisco Prime Access Registrar 8.0 Documentation Overview.
Note We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.