CPC Release Notes, Release 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
Ultra Cloud Core CPC, Release 2026.02.1
Ultra Cloud Core CPC, Release 2026.02.1
This Release Notes identifies changes and issues related to the release of Ultra Cloud Core Converged Policy and Charging (CPC), software release.
For more information about the Ultra Cloud Core CPC documentation, see the Related resources section.
Release lifecycle milestones
Table 1. EoL milestone information for CPC, Release 2026.02.1
| Milestone |
Date |
| First Customer Ship (FCS) |
23-April-2026 |
| End of Life (EoL) |
23-April-2026 |
| End of Software Maintenance (EoSM) |
23-Oct-2027 |
| End of Vulnerability and Security Support (EoVSS) |
23-Oct-2027 |
| Last Date of Support (LDoS) |
31-Oct-2028 |
These milestones and the intervals between them are defined in the Cisco Ultra Cloud Core (UCC) Software Release Lifecycle Product Bulletin available on cisco.com.
There is no new software features introduced in this release.
There are no behavior changes introduced in this release.
This table lists the resolved issues in this specific software release.
Note: This software release may contain bug fixes first introduced in other releases. To see additional information, click the bug ID to access the Cisco Bug Search Tool.
Table 2. Resolved issues for Ultra Cloud Core CPC, Release 2026.02.1
| Bug ID |
Description |
| Need to support <networkId xmlns=""> in Soap Request in soap proxy kafka migration. |
This table lists the open issues in this specific software release.
Note: This software release may contain open bugs first introduced in other releases. To see additional information, click the bug ID to access the Cisco Bug Search Tool.
Table 3. Open issues for Ultra Cloud Core CPC, Release 2026.02.1
| Bug ID |
Description |
| TAC debug is not capturing logs in the latest CNDP build. |
|
| Policy Builder and CPC Central display incorrect default role for new SMI users. |
This section lists compatibility information of the Cisco UCC software products that are verified to work with this version of the UCC CPC cnAAA software.
Table 4. Compatibility information for Ultra Cloud Core CPC, Release 2026.02.1
| Product |
Supported release |
| Ultra Cloud Core SMI |
2026.02.1.07 |
| Ultra Cloud Core CDL |
2.2 |
| Unified Load Balance (ULB) |
2026.02.0.31 |
This section provides information about the release packages associated with Ultra Cloud Core CPC, cnAAA software.
Table 5. Software packages for Ultra Cloud Core CPC, Release 2026.02.1
| Software package |
Description |
Release |
| cpc.2026.02.1.SPA.tgz |
The CPC offline release signature package. This package contains the CPC deployment software as well as the release signature, certificate, and verification information. |
2026.02.1 |
Cloud native product version numbering system
The show helm list command displays detailed information about the version of the cloud native product currently deployed.
This is a sample for version numbering system:
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.
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.
This is a sample for software integrity verification.
At the bottom, you will find the SHA512 checksum. If you do not see the whole checksum, you can expand
it by pressing "..." at the end.
To validate the information, calculate a SHA512 checksum using the information in Table 1 and verify that
it matches the provided on the software download page.
To calculate a SHA512 checksum on your local desktop, refer to the following 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 |
| <filename> is the name of the file. <extension> is the file type extension (for example, .zip or .tgz). |
|
Certificate validation
CPC software images are signed through x509 certificates. For information and instructions on how to validate the certificates, refer to the .README file packaged with the software.
This table provides key resources and links to the support information and essential documentation for Ultra Cloud Core CPC AAA products.
Table 7. Related resources and additional information
| Resource |
Link |
| UCC CPC AAA Configuration and Administration Guide, Release 2026.02 |
For more information on CPC AAA documentation, contact Cisco account representative. |
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.