PDF(353.1 KB) View with Adobe Reader on a variety of devices
Updated:August 28, 2024
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
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.x and 8.8 or CentOS 7.x operating system. Also, Prime Access Registrar is qualified with VMWare ESXi 7.0 Update 3, OpenStack Xena.
Contents
This release note contains the following sections:
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.
Table 1 Minimum Hardware and Software Requirements for Prime Access Registrar Server
OS Version
RHEL 7.x and 8.8
CentOS 7.x
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.
Model
X86
CPU Type
Intel Xeon CPU 2.30 GHz
Processors
4
CPU Speed
2.30 GHz
Memory (RAM)
8 GB
Swap Space
10 GB
Disk Space
1*146 GB
Prime Access Registrar supports JDK versions 1.8.x and 11.x. Also, Prime Access Registrar is qualified with VMWare ESXi 7.0 Update 3, 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
rpm
RHEL OS Version 7.x
RHEL OS Version 8.x
brotli
No
Yes
c-ares
Yes
Yes
cyrus-sasl-lib
Yes
Yes
gamin
Yes
Yes
glibc
Yes
Yes
gdome2
Yes
Yes
glib
Yes
Yes
glib2
Yes
Yes
json-c
Yes
Yes
keyutils-libs
Yes
Yes
krb5-libs
Yes
Yes
libbson
No
Yes
libcom_err
Yes
Yes
libcurl
Yes
Yes
libicu
Yes
Yes
libidn2
No
Yes
libgcc
Yes
Yes
libmongocrypt
No
Yes
libnghttp2
No
Yes
libnsl
No
Yes
libpsl
No
Yes
libselinux
Yes
Yes
libssh
No
Yes
libstdc++
Yes
Yes
libtool-ltdl
Yes
Yes
libunistring
No
Yes
libxcrypt
No
Yes
libxml2
Yes
Yes
libzstd
No
Yes
lksctp-tools
Yes
Yes
mongo-c-driver-libs
No
Yes
ncurses-libs
Yes
Yes
nss-softokn-freebl
Yes
Yes
nss-util
Yes
Yes
nspr
Yes
Yes
nss
Yes
Yes
openldap
No
Yes
openssl-libs
Yes
Yes
pcre
Yes
Yes
pcre2
No
Yes
pcre-cpp
No
Yes
snappy
No
Yes
sqlite-libs
No
Yes
tcl
No
Yes
unixODBC
No
Yes
xz-libs
No
Yes
zlib
Yes
Yes
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.
New and Enhanced Features in Cisco Prime Access Registrar 9.3
Cisco Prime Access Registrar 9.3 provides the following features:
The graphical user interface (GUI) for Prime Access Registrar has been upgraded to Angular Spring Boot framework to address the security vulnerabilities with the existing Struts framework. All the GUI features are maintained intact with the current migration.
Strong Password Policy
Following are the criteria that an admin user password should meet as per the strong password policy settings in Prime Access Registrar.
The password must:
contain at least 8 characters (12+ recommended)
contain at least one uppercase letter and at least one lowercase letter
contain at least one numerical value
contain at least one special character (! ? # $ % & ' () * +, -. / : ; < = > ? @ [ \ ] ^ _ ` { | } ~)
NOT contain space
Also, we recommend that the password:
does not contain more than two identical characters in a row
does not contain first name, last name, email address mailbox or domain, or company name
does not match commonly used passwords or password character patterns
Note While upgrading from an existing version to Prime Access Registrar 9.3, all admin user passwords will be reset to the default password Aicuser@123.
Cisco Prime Access Registrar 9.3 Bugs
For information on a specific bug or to search all bugs in a particular Prime Access Registrar release, see Using the Bug Search Tool
Fixed Anomalies in Cisco Prime Access Registrar 9.3.0.3
Table 5 lists the anomalies fixed in Prime Access Registrar 9.3.0.3 release.
Table 5 Fixed Anomalies in Prime Access Registrar 9.3.0.3
Bug
Description
CSCwf53731
Memory leak observed while handling OCI service traffic.
Fixed Anomalies in Cisco Prime Access Registrar 9.3.0.2
Table 6 lists the anomalies fixed in Prime Access Registrar 9.3.0.2 release.
Table 6 Fixed Anomalies in Prime Access Registrar 9.3.0.2
Bug
Description
CSCwe95813
In encrypted IMSI, private key decryption failed.
Fixed Anomalies in Cisco Prime Access Registrar 9.3.0.1
Table 7 lists the anomalies fixed in Prime Access Registrar 9.3.0.1 release.
Table 7 Fixed Anomalies in Prime Access Registrar 9.3.0.1
Bug
Description
CSCwa27878
Prime Access Registrar stops working on longevity when ErrorBasedRouting is FALSE.
CSCwc37825
carServerSessionUsage counter is not getting updated properly.
CSCwc50844
Prime Access Registrar stops working due to synchronization issues during Mutex lock.
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.
BST allows you to:
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 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 9.3, 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.
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.