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.

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

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 UPF 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.

> certutil.exe -hashfile filename.extension SHA512 

$ shasum -a 512 filename.extension 

$ sha512sum filename.extension 

$ shasum -a 512 filename.extension 

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.

RCM 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.

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.

The following table provides descriptions for the packages that are available with this release.