Cisco Prime Access Registrar 9.3.3.3.RJIL Release Notes
Available Languages
Table of Contents
Cisco Prime Access Registrar 9.3.3.3.RJIL Release Notes
Co-Existence With Other Network Management Applications
Cisco Prime Access Registrar 9.3.3.3.RJIL Bugs
Fixed Anomalies in Cisco Prime Access Registrar 9.3.3.3.RJIL
Cisco Prime Access Registrar 9.3.3.3.RJIL
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) 8.x ( upto 8.10) or CentOS 7.x operating system. Also, Prime Access Registrar is qualified with VMWare ESXi 8.0, OpenStack Xena.
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 9.3.3.3.RJIL.
| You must have the 64-bit rpm files for the relevant RHEL versions while installing Prime Access Registrar. For the list of required rpms for the relevant OS versions, see Required 64-bit rpms for Relevant RHEL OS Versions. |
|
Prime Access Registrar supports JDK versions 1.8.x and 11.x. Also, Prime Access Registrar is qualified with VMWare ESXi 8.0, OpenStack Xena.
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.
Required 64-bit rpms for Relevant RHEL OS Versions
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 “Configuring Cisco Prime Access Registrar” chapter of the Cisco Prime Access Registrar 9.3 Administrator Guide
Cisco Prime Access Registrar 9.3.3.3.RJIL Bugs
This section contains the following information:
Fixed Anomalies in Cisco Prime Access Registrar 9.3.3.3.RJIL
Table 2 lists the anomalies fixed in Cisco Prime Access Registrar 9.3.3.3.RJIL release.
Related Documentation
For a complete list of Cisco Prime Access Registrar documentation, see the Cisco Prime Access Registrar 9.3 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.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)