Ultra Cloud Serving Gateway Control Plane Function
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 |
30-Apr-2024 |
|
End of Life |
EoL |
30-Apr-2024 |
|
End of Software Maintenance |
EoSM |
29-Oct-2025 |
|
End of Vulnerability and Security Support |
EoVSS |
31-Oct-2025 |
|
Last Date of Support |
LDoS |
31-Oct-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-2024.02.0.SPA.tgz |
2024.02.0 |
|
NED package |
ncs-5.6.8-ccg-nc-2024.02.0 ncs-6.1-ccg-nc-2024.02.0 |
|
NSO |
5.6.8 6.1.3 |
Descriptions for the various packages provided with this release are available in the Release Package Descriptions section.
 Note |
The ccg.<version>.SPA.tgz software package is common to both the cnSGWc and SMF 5G Network Functions (NF). The deployment and configuration procedure determines the NF deployment. |
Verified Compatibility
|
Products |
Version |
|---|---|
|
Ultra Cloud Core SMI |
2024.02.1.14 |
|
Ultra Cloud CDL |
1.11.7 |
|
Ultra Cloud Core UPF |
2024.02.0 |
|
Ultra Cloud SMF |
2024.02.0 |
For information on the Ultra Cloud Core products, refer to the documents for this release available at:
What's New in this Release
Features and Enhancements
This section covers a brief description of the features and enhancements introduced in this release. It also includes links to detailed documentation, where available.
| Feature | Description |
|---|---|
|
With UPF supporting the collapsed-data path functionality, cnSGW supports charging with converged UPF (UPF + SGW-U). This support prevents affecting the Local Breakout (LBO) calls for which the carrier uses SGW-based CDRs for reporting and charging. Default Setting: Not Applicable |
|
|
cnSGW-c enables the dual stack transport for Data Plane using the dual-stack-transport { false | true } CLI command in the UPF network profile. With this support, you can:
Default Setting: Disabled – Configuration Required |
|
|
Converged Core Gateway provides the following support:
This optimization helps in reduced session and Call Events Per Second (CEPS) loss during the upgrade procedure. The configurable rolling upgrade enhancements enable smooth rollout of the changes. This feature introduces the new CLI command supported-features [ app-rx-retx-cache | app-tx-retx | rolling-upgrade-all | rolling-upgrade-enhancement-infra ] in the converged core profile. Default Setting: Disabled – Configuration Required |
|
|
Supporting IPv6 Only eNB Insertion through Show and Clear Subscriber CLI commands |
Before you add IPv6 only eNBs in a network, all UPFs in a mesh must be IPv6 enabled for successful handovers of IPv4 only eNB sessions to IPv6 only eNB sessions. In addition, all sessions must have V4V6 tunnel before inserting a V6 only eNB. To support this IPV6 only eNB insertion, cnSGW-c includes the following CLI commands:
Default Setting: Not Applicable |
Behavior Changes
There are no behavior changes in this release.
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 the one provided on the software download page.
To calculate a SHA512 checksum on your local desktop please see the following table.
|
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 |
|
NOTES: filename is the name of the file. extension is the file 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
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.
Open Bugs for this Release
The following table lists the open bug in this specific software release.
Note |
This software release may contain open bugs first identified in other releases. Additional information for all open bugs for this release are available in the Cisco Bug Search Tool. |
|
Bug ID |
Headline |
|---|---|
|
IntraMME, InterEnB HO failures seen during Rolling upgrade |
|
|
Evaluation of sgw for HTTP/2 Rapid Reset Attack vulnerability |
Resolved Bugs for this Release
The following table lists the known bug that is resolved 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 are available in the Cisco Bug Search Tool. |
|
Bug ID |
Headline |
Behavior Change |
|---|---|---|
|
On Converged Core (cn-ccg-smf)when trying the 4G attach User plane Selection failure Occured |
No |
|
|
udp-prox is listening to all the IPs/Ports; needs to have some restrictions around it |
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
This table lists provide descriptions for the packages that are available with this release.
|
Software Packages |
Description |
|---|---|
|
ccg.<version>.SPA.tgz |
The offline release signature package. This package contains the deployment software 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. |
Note |
The ccg.<version>.SPA.tgz software package is common to both the cnSGWc and SMF 5G Network Functions (NF). The deployment and configuration procedure determines the NF deployment. |
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