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.
Feedback
Unified Load Balancer, Release 2026.02.0
Unified Load Balancer, Release 2026.02.0
This Release Notes identifies changes and issues related to the release of Unified Load Balancer (ULB).
For more information about ULB, see the Related resources section.
There are no new software features introduced in this release.
There are no behavior changes in this release.
There are no resolved issues in this specific software release.
This table lists the open issues in this specific software release.
Note: This software release may contain open bugs 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 1. Open issues for ULB, Release 2026.02.0
| Bug ID |
Description |
| LB service is not able to differentiate between TCP and UDP protocol |
|
| Fragmented ingress packets, dropped by cilium. |
|
| No mapping for NAT masquerade drops observed on VIP movement |
|
| IEGP based egress Traffic: egress IP is not reflected in Cilium-agent |
This section lists compatibility information of the products that are verified to work with this version of the ULB software.
Table 2. Compatibility information for ULB, Release 2026.02.0
| Product |
Supported Release |
| Ultra Cloud Core SMI |
2026.02.1.07 |
| Cilium |
1.17.9 |
This section provides information about the release packages associated with ULB software.
Table 3. Software packages for ULB, Release 2026.02.0
| Software Package |
Description |
Release |
| ulb-2026.02.0.SPA.tgz |
The ULB offline release signature package. This package contains the ULB deployment software, release signature, certificate, and verification information. |
2026.02.0 |
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
Software integrity version
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.

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 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 4. 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 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 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.
Certificate validation
The software images are signed via 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 ULB and SMI.
Table 5. Related resources and additional information
| Resource |
Link |
| SMI documentation |
|
| Service request and additional information |
For ULB documentation, contact your 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.