Cisco Cloud Native BNG Control Plane
Introduction
This Release Notes identifies changes and issues related to this software release.
Release Package Version Information
Software Packages |
Version |
---|---|
bng.2024.03.0.SPA.tgz |
2024.03.0 |
Descriptions for the various packages provided with this release are available in the Release Package Descriptions section.
Verified Compatibility
This version of the cnBNG Control Plane has been verified with the following software components/packages. Consult the individual components/packages release notes for details.
Products | Version |
---|---|
BNG UP (ASR 9K) | IOS XR Release 24.3.1 |
SMI CEE | 2024.03.1.i13 |
SMI Cluster Deployer | 2024.03.1.i13 |
SMI Base ISO Image | 20.04.0-20240709 |
What's New in this Release
New in Documentation
This version of Release Notes includes a new section titled What’s New in this Release comprising all new features, enhancements, and behavior changes applicable for the release.
This section will be available in all the 5G release notes and will supersede content in the Release Change Reference (RCR) document. Effective release 2024.02, the RCR document will be deprecated.
Features and Enhancements
This section covers a brief description of the features and enhancements introduced in this release. It also includes links to detailed documentation, where available.
Feature | Description |
---|---|
This feature enhances performance by distributing AAA messages across servers, ensuring faster response times. It selects the RADIUS server with the fewest outstanding transactions, rather than using the previous First server or Round Robin methods, which did not account for server load. This results in a more efficient handling of authentication, authorization, and accounting tasks. |
|
This feature provides higher service availability using Geographical Redundancy for cnBNG all-in-one (AIO) Control Plane clusters, reducing the risk of outages. CP-GR feature, previously available for 3-server and 4-server clusters, has been expanded to include AIO clusters. |
|
We have enhanced the system performance by preventing packet identifier (PID) exhaustion with the new Asynchronous mode for sending RADIUS Accounting messages. The cnBNG now releases PIDs after dispatching messages, rather than waiting for long time to receive server responses. This change allows for PID reuse, mitigating scale issues and improving KPIs. |
|
Maintenance Operation Procedure (MOP) for cnBNG Node Scaling |
This MOP outlines the steps to scale a cnBNG Control Plane deployment from Half-Rack to Full-Rack. The procedure includes adding new servers, scaling up Kubernetes (K8s) clusters, scaling up CDL, and scaling up services. |
Related Documentation
For a complete list of documentation available for this release, go to:
Installation and Upgrade Notes
This Release Note does not contain general installation and upgrade instructions. Refer to the existing installation documentation for specific installation and upgrade considerations.
Software Integrity Verification
To verify the integrity of the software image you have from Cisco, you can validate the SHA512 checksum information against the checksum identified by Cisco for the software.
Image checksum information is available through Cisco.com Software Download Details. To find the checksum, hover the mouse pointer over the software image you have downloaded.
The following screenshot is an example of a cnBNG CP release posted in the Software Download page.
At the bottom you find the SHA512 checksum, if you do not see the whole checksum you can expand it by pressing the "..." at the end.
To validate the information, calculate a SHA512 checksum using the information in Table 1 and verify that it matches either the one provided on the software download page.
To calculate a SHA512 checksum on your local desktop, refer to the following table.
Operating System |
SHA512 checksum calculation command examples |
---|---|
Microsoft Windows |
Open a command line window and type the following command:
|
Apple MAC |
Open a terminal window and type the following command:
|
Linux |
Open a terminal window and type the following command:
Or
|
NOTES: filename is the name of the file. extension is the file extension (for example, .zip or .tgz). |
If the SHA512 checksum matches, you can be sure that no one has tampered with the software image or the image has not been corrupted during download.
If the SHA512 checksum does not match, we advise you to not attempt upgrading any systems with the corrupted software image. Download the software again and verify the SHA512 checksum again. If there is a constant mismatch, please open a case with the Cisco Technical Assistance Center.
Certificate Validation
cnBNG CP software images are signed via x509 certificates. View the .README file packaged with the software for information and instructions on how to validate the certificates..
Open Bugs for this Release
The following table lists the open bugs in this specific software release.
Note |
This software release may contain open bugs first identified in other releases. Additional information for all open bugs for this release are available in the Cisco Bug Search Tool. |
Bug ID |
Headline |
---|---|
[SVI-CPGR-APRIL24] All UP associations got cleared post nm & cache pod restart | |
[SVI-CPGR-APRIL24] IPAM Churn allocation metric isn't populating as expected during MB-Churn |
Operator Notes
Cloud Native Product Version Numbering System
The show helm list command displays detailed information about the version of the cloud native product currently deployed.
The appropriate version number field increments after a version has been released. The new version numbering format is a contiguous sequential number that represents incremental changes between releases. This format facilitates identifying the changes between releases when using Bug Search Tool to research software releases.
Release Package Descriptions
The following table provides descriptions for the packages that are available with this release.
Software Packages |
Description |
---|---|
bng.<version>.SPA.tgz |
The cnBNG CP offline release signature package. This package contains the cnBNG CP deployment software as well as the release signature, certificate, and verification information. |
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, refer to https://www.cisco.com/c/en/us/support/index.html.