Release Notes for the Cisco Cloud Native BNG Control Plane, Version 2026.02.1
Available Languages
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.
- US/Canada 800-553-2447
- Worldwide Support Phone Numbers
- All Tools
Feedback
Feedback
Release Notes for the Cisco Cloud Native BNG Control Plane, Version 2026.02.1
Release Notes for the Cisco Cloud Native BNG Control Plane, Version 2026.02.1
This Release Notes identifies changes and issues related to the software release of Cisco Cloud Native BNG Control Plane.
The key highlights for the cnBNG CP Release 2026.02.1 include:
◦ Optimized PPPoE IPAM
Enhances IP address utilization and simplifies routing policy for PPPoE and RADIUS-based subscriber addressing.
For more information about cnBNG Control Plane and related products, see the Related resources section.
Release lifecycle milestones
The following table provides EoL milestones for Cisco cnBNG Control Plane software:
Table 1. EoL milestone information for cnBNG CP, Release 2026.02.1
| Milestone |
Date |
| First Customer Ship (FCS) |
30-Apr-2026 |
| End of Life (EoL) Announcement |
30-Apr-2027 |
| End of Software Maintenance (EoSM) |
30-Apr-2029 |
| End of Vulnerability and Security Support (EoVSS) |
30-Apr-2030 |
| Last Date of Support (LDoS) |
30-Oct-2030 |
This section provides a brief description of the new software features introduced in this release.
Table 2. New software features for cnBNG CP, Release 2026.02.1
| Product impact |
Feature |
Description |
| Ease of Use |
Optimized PPPoE IPAM |
You can now use IP addresses more efficiently and simplify route control for PPPoE and RADIUS-based subscribers. This feature lets the system use RADIUS-assigned IPv4 and IPv6 addresses or prefixes directly, without requiring global static IPAM pools in many cases. It also enhances routing efficiency through granular policy control and optimizes resource usage by allowing the exclusion of specific reserved IPv4 addresses. |
This table lists the resolved issues in this specific software release.
Note: This software release may contain bug fixes first identified in other releases. To see additional information, click the bug ID to access the Cisco Bug Search Tool. To search for a documented Cisco product issue, type in the browser: <bug_number> site:cisco.com
Table 3. Resolved issues for cnBNG CP, Release 2026.02.1
| Bug ID |
Description |
| RadServerStatus Prometheus gauge stuck at 1 (up) while CLI reports server dead after radius-ep helm re-install with persisted etcd |
|
| Standby instance peer not cleared after the CP-UP de-association |
This section lists compatibility information of the software components/packages that are verified to work with this version of the cnBNG Control Plane software.
Table 4. Compatibility information for cnBNG CP, Release 2026.02.1
| Product |
Supported Release |
| BNG UP (ASR 9K) |
IOS XR Release 26.2.1* |
| SMI CEE |
2026.02.1.07 |
| SMI Cluster Deployer |
2026.02.1.07 |
| SMI Base ISO Image |
24.04.0-20260408 |
*Subject to feature availability.
This section provides information about the release packages associated with cnBNG Control Plane software.
Table 5. Software packages for cnBNG CP, Release 2026.02.1
| Software Package |
Description |
Release |
| bng.2026.02.1.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. |
2026.02.1 |
| ncs-6.4.8.2-cisco-bng-nc-1.1.2026.02.0 |
The NETCONF NED package. This package includes all the yang files that are used for NF configuration. Note that NSO is used for the NED file creation. |
6.4.8.2 |
| ncs-6.4.8.2-cisco-bng-smi-deployer-2026.02.0 |
NSO Core-Function-Pack |
6.4.8.2 |
Cloud native product version numbering system
The show helm list command displays detailed information about the version of the cloud native product currently deployed.
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.
To validate the information, calculate a SHA512 checksum using the information in the following table and verify that it matches the one provided on the software download page.
To calculate a SHA512 checksum on your local desktop, see this table.
Table 6. Checksum calculations per operating system
| Operating System |
SHA512 checksum calculation command examples |
| Microsoft Windows |
Open a command line window and type the following command: > certutil.exe -hashfile <filename.extension> SHA512 |
| Apple MAC |
Open a terminal window and type the following command: $ shasum -a 512 <filename.extension> |
| Linux |
Open a terminal window and type the following command: $ sha512sum <filename.extension> OR $ shasum -a 512 <filename.extension> |
| Note: <filename> is the name of the file. <extension> is the file type extension (for example, .zip or .tgz). |
|
If the SHA512 checksum does not match, we advise you not to 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.
This table provides key resources and links to the support information and essential documentation for cnBNG Control Plane and related products.
Table 7. Related resources and additional information
| Resource |
Link |
| cnBNG Control Plane documentation |
|
| cnBNG User Plane documentation |
|
| Physical BNG documentation |
|
| SMI documentation |
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. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2026 Cisco Systems, Inc. All rights reserved.