Release Notes for Ultra Cloud Core Redundancy Configuration Manager, Release 2025.03.0
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
Redundancy Configuration Manager, Release 2025.03.0
Redundancy Configuration Manager, Release 2025.03.0
This Release Notes identifies changes and issues related to the software release of Ultra Cloud Core (UCC) Redundancy Configuration Manager (RCM).
For more information on RCM, see the Related resources section.
The following table provides EoL milestones for Cisco UCC RCM software:
Table 1. EoL milestone information for RCM, Release 2025.03.0
| Milestone |
Date |
| First Customer Ship (FCS) |
14-Aug-2025 |
| End of Life (EoL) |
14-Aug -2025 |
| End of Software Maintenance (EoSM) |
12-Feb-2027 |
| End of Vulnerability and Security Support (EoVSS) |
12-Feb-2027 |
| Last Date of Support (LDoS) |
29-Feb-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 are no new features and enhancements in this release.
There are no behavior changes in this release.
There are no resolved issues in this specific software release.
There are no open issues in this specific software release.
This section lists the known issues in this specific software release.
RCM Ops Center Logging Levels
It is recommended to use the following logging levels for RCM Ops Center to ensure that logs do not overflow.
logging level application debug
logging level transaction debug
logging level tracing off
logging name infra.dpd.core level application off
logging name infra.dpd.core level transaction off
logging name infra.dpd.core level tracing off
logging name infra.application.core level application off
logging name infra.application.core level transaction off
logging name infra.application.core level tracing off
logging name infra.etcd_client.core level application warn
logging name infra.etcd_client.core level transaction warn
logging name infra.etcd_client.core level tracing off
logging name infra.dispatcher.core level application warn
logging name infra.dispatcher.core level transaction warn
logging name infra.dispatcher.core level tracing off
logging name infra.virtual_msg_queue.core level application warn
logging name infra.virtual_msg_queue.core level transaction warn
logging name infra.virtual_msg_queue.core level tracing off
logging name infra.edr.core level application warn
logging name infra.edr.core level transaction warn
logging name infra.edr.core level tracing off
logging name infra.ipcstream.core level application warn
logging name infra.ipcstream.core level transaction warn
logging name infra.ipcstream.core level tracing off
logging name infra.memory_cache.core level application warn
logging name infra.memory_cache.core level transaction warn
logging name infra.memory_cache.core level tracing off
logging name infra.topology_lease.core level application warn
logging name infra.topology_lease.core level transaction warn
logging name infra.topology_lease.core level tracing off
logging name infra.ipc_action.core level application warn
logging name infra.ipc_action.core level transaction warn
logging name infra.ipc_action.core level tracing off
logging name infra.vrf_etcd_update.core level application warn
logging name infra.vrf_etcd_update.core level transaction warn
logging name infra.vrf_etcd_update.core level tracing off
logging name infra.config.core level application warn
logging name infra.config.core level transaction warn
logging name infra.config.core level tracing off
logging name infra.heap_dump.core level application warn
logging name infra.heap_dump.core level transaction warn
logging name infra.heap_dump.core level tracing off
logging name infra.resource_monitor.core level application warn
logging name infra.resource_monitor.core level transaction warn
logging name infra.resource_monitor.core level tracing off
logging name infra.topology.core level application warn
logging name infra.topology.core level transaction warn
logging name infra.topology.core level tracing off
logging name infra.transaction.core level application warn
logging name infra.transaction.core level transaction warn
logging name infra.transaction.core level tracing off
logging name infra.diagnostics.core level application warn
logging name infra.diagnostics.core level transaction warn
logging name infra.diagnostics.core level tracing off
This section lists compatibility information of the Cisco UCC software products that are verified to work with this version of the UCC RCM software.
Table 2. Compatibility information for RCM, Release 2025.03.0
| Product |
Supported Release |
| Ultra Cloud Core SMI |
2025.03.1.10 |
| Ultra Cloud CDL |
1.12.2 |
| Ultra Cloud Core UPF |
2025.03.0 |
| Ultra Cloud cnSGWc |
2025.03.0 |
This section provides information about the release packages associated with UCC RCM software.
Table 3. Software packages for Redundancy Configuration Manager, Release 2025.03.0
| Software Package |
Description |
Release |
| rcm-2025.03.0.SPA.tgz |
The RCM offline release signature package. This package contains the RCM deployment software, NED package, as well as the release signature, certificate, and verification information. |
2025.03.0 |
| ncs-6.4.5-rcm-nc-2025.03.0.tar.gz |
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.5 |
| ncs-6.1.14-rcm-nc-2025.03.0.tar.gz |
6.1.14 |
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. SHA512 checksum commands for different operating systems
| 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 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
UPF software images are signed via x509 certificates. Please view the .README file packaged with the software for information and instructions on how to validate the certificates.
This table provides key resources and links to the support information and essential documentation for UPF and RCM.
Table 5. Related resources and additional information
| Resource |
Link |
| UPF and RCM documentation |
|
| Service request and additional information |
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.
© 2025 Cisco Systems, Inc. All rights reserved.