Introduction
This Release Notes identifies changes and issues related to this software release.
Release Lifecycle Milestones
|
Release Lifecycle Milestone |
Milestone |
Date |
|---|---|---|
|
First Customer Ship |
FCS |
31-Oct-2023 |
|
End of Life |
EoL |
31-Oct-2023 |
|
End of Software Maintenance |
EoSM |
30-Apr-2025 |
|
End of Vulnerability and Security Support |
EoVSS |
30-Apr-2025 |
|
Last Date of Support |
LDoS |
30-Apr-2026 |
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.
Release Package Version Information
|
Software Packages |
Version |
|---|---|
| ccg-2023.04.3.SPA.tgz | 2023.04.3 |
| NED package |
ncs-5.6.8-ccg-nc-2023.04.3 ncs-6.1-ccg-nc-2023.04.3 |
| NSO |
5.6.8 6.1.3 |
Descriptions for the various packages provided with this release are available in the Release Package Descriptions section.
Verified Compatibility
|
Products |
Version |
|---|---|
|
Ultra Cloud Core SMI |
2023.04.1 |
|
Ultra Cloud CDL |
1.11.5 |
|
Ultra Cloud Core UPF |
2023.04.0 |
|
Ultra Cloud cnSGWc |
2023.04.3 |
For information on the Ultra Cloud Core products, refer to the documents for this release available at:
Behavior Changes for this Release
The following behavior change is visible in this release.
Simultaneous Clearing of Subscribers Associated to Different UPFs
Old Behavior:
Clearing of subscribers associated to a single UPF was supported.
Any new clear subscriber command initiated during an ongoing clear subscriber operation used to get blocked irrespective of the GR instance ID.
There was no provision to display the estimated time for the completion of clear subscriber operation.
New Behavior:
SMF can simultaneously clear subscribers associated to any of the UPFs provided through the clear subscriber upf-list command, with a maximum limit of 20 UPFs.
The clear subscriber operation with upf-list option is successful irrespective of the presence of nf-service in the command syntax. In such scenarios, it clears the matching subscribers for both SMF and cnSGW-C.
SMF does not block the clear subscriber operation unless another clear subscriber command is initiated on the same GR instance ID.
 Note |
The GR instance must be in PRIMARY role for the command to take its effect. |
SMF displays the wait time to clear the UPF subscribers as part of the clear subscriber command output.
Related Documentation
Installation and Upgrade Notes
This Release Note does not contain general installation and upgrade instructions. Refer to the existing installation documentation for specific installation and upgrade considerations.
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.
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 table below.
|
Operating System |
SHA512 checksum calculation command examples |
||
|---|---|---|---|
|
Microsoft Windows |
Open a command line window and type the following command:
|
||
|
Apple MAC |
Open a terminal window and type the following command:
|
||
|
Linux |
Open a terminal window and type the following command:
OR
|
||
|
|||
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
SMF 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.
Open Bugs for this Release
There are no open bugs in this release.
Resolved Bugs for this Release
The following table lists the resolved bugs in this specific software release.
Note |
This software release may contain bug fixes first introduced in other releases. Additional information for all resolved bugs for this release is available in the Cisco Bug Search Tool. |
|
Bug ID |
Headline |
Behavior Change |
|---|---|---|
|
Support of clearing the subscriber for multiple UPF simultaneously, through CLI |
Yes |
|
|
Online CHF down - with NRF discovery enabled, SMF not falling back to locally configured IP |
No |
|
|
SMF does not remove the PDR for 5g-4g HO collision with IM exit |
No |
|
|
Multiple remove FAR with FUA-T and quota exhaust resulting in N4 MOD Cause 69 |
No |
|
|
SMF to suppress v6 tunnel information in OHC FAR when UPF is v4 |
No |
|
|
SMF - no radius ACCT when only online chf available and is down |
No |
|
|
SMF should support QoS rules and QoS description with the length of two octets Option in PCO IE |
No |
|
|
Ancient_Cache_Pod excludes pod affinity Once affinity stream connection flap multiple times |
No |
|
|
SMF - Fallback incase of UPF blocked to different precedence not working. |
No |
|
|
SGW_POD Restart after DIMM error causing IPC Streams failed on gtpc-ep1 streams to sgw-Service |
No |
|
|
EPSFB IDLE-DLDR - NRF discovery empty AMF instance seen. |
No |
|
|
SMF-Service pod crash with Panic Message during WIFI to NR HO – MsgPduSessionReleaseRequest |
No |
|
|
RS not replied during WLAN to 4G HO with active voice-call |
No |
|
|
sgw-service pod panic on receiving CBRes with ULI change - GetBearerFromCreateBearerProcInfo |
No |
|
|
SMF is not sending ULI info in N40 update/Rel after Idle/Active transition |
No |
Operator Notes
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.
Release Package Descriptions
The following table provides descriptions for the packages that are available with this release.
|
Software Packages |
Description |
|---|---|
|
ccg.<version>.SPA.tgz |
The SMF offline release signature package. This package contains the SMF deployment software, NED package, as well as the release signature, certificate, and verification information. |
|
ncs-<nso_version>-ccg-nc-<version>.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. |
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, refer to https://www.cisco.com/c/en/us/support/index.html.
Feedback