Cisco Prime Access Registrar 8.0.3.1 Release Notes

---

Table 1 Minimum Hardware and Software Requirements for Prime Access Registrar Server

OS Version	RHEL 7.7 CentOS 6.5 and above Note Prime Access Registrar has no special OS dependencies; therefore there are no restrictions from upgrading to newer releases of RHEL or CentOS.
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

---

Binding Address Support in Prime Access Registrar

With this feature, a new BindingAddress attribute has been added under Radius/Advanced/Diameter/TransportManagement to allow you to control the local address the server will use for outbound connections. This should be used if the host has a virtual IP address or when the host has multiple addresses to assure the correct address is used for these connections.

---

Note You can only configure this to be an IPv4 or IPv6 address, not both.

If the configured address is not available at the time when an outbound connection is initiated, the connection fails and the server retries to connect periodically. Ensure that the correct address is configured.

Following is a sample CLI for this feature:

Changes to Diameter-TCP Connection Parameters

Enhancements are made to server connection handling to ensure better response and reporting of issues, if any. As part of this enhancement, new TCP connection parameters (timeout and count) are introduced to control how long the server can wait to receive a Diameter message. If no data is received within the timeout period for the count attempts, the server considers the connection down.

If you increase the time, this may reduce how quickly the server reacts to other connection issues (such as if closed because of a send failure). If you increase the count, the server can be more resilient to short- term network issues (such as link flaps).

Generally, it is recommended to adjust the count and leave the time at the default value.

The following fields are introduced to Diameter-TCP connection parameters:

• ConnectionTimeout—Indicates the time (in milliseconds) the server can wait to receive data. Setting this to a lower value can make the server more responsive to connection failures. Default value is 30,000 (milliseconds).
• MaxTimeoutCount—Indicates the number of times in a row the server receive must timeout before the connection is closed. Increasing this value can reduce connection closes if there are frequent short connectivity outages. The default value is 3.

Following is a sample CLI for this feature:

In remote server configuration, existing parameters given below are used for managing the connection timeout:

• DWatchDogTimeout—Indicates the time (in milliseconds) the server can wait to receive data. Setting this to a lower value can make the server more responsive to connection failures. Default value is 2,500 (milliseconds).
• MaxTries—Indicates the number of times in a row the server receive must timeout before the connection is closed. Increasing this value can reduce connection closes if there are frequent short connectivity outages. The default value is 3.

Following is a sample CLI of the Diameter remote server configuration:

Fixed Anomalies in Cisco Prime Access Registrar 8.0.3.1

Table 2 lists the anomalies fixed in Prime Access Registrar 8.0.3.1 release.

 

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 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.3.1, 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.

 

---

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.

© 2020 Cisco Systems, Inc. All rights reserved.