First Published: January 29, 2025

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

31-Jan-2025

End of Life

EoL

31-Jan-2025

End of Software Maintenance

EoSM

1-Aug-2026

End of Vulnerability and Security Support

EoVSS

1-Aug-2026

Last Date of Support

LDoS

31-Aug-2027

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-2025.01.0.SPA.tgz

2025.01.0
NED package

ncs-5.6.8-ccg-nc-2025.01.0

ncs-6.1.14-ccg-nc-2025.01.0
NSO

5.6.8

6.1.14

Descriptions for the various packages provided with this release are available in the Release Package Descriptions section.

Verified Compatability

Products

Version

Ultra Cloud Core SMI

2025.01.1.14

Ultra Cloud CDL

 1.12.0

Ultra Cloud Core UPF

2025.01.0

Ultra Cloud SMF

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

Event Failure Logs for Service Pods

With this feature, the consistent event failure logs are enhanced to support the Delete Bearer Command, Change Notification, and PDN Disconnect procedures for the service pods.

3GPP LI Support

The 3GPP LI support is enhanced to adhere to the 3GPP standards for lawful interception.

Important

 
This feature is fully qualified in this release. For more information, contact your Cisco account representative.

Behavior Changes

This section covers a brief description of behavior changes introduced in this release.

Behavior Change Description

S8e GTPC Endpoints configuration for echo request optimization

Previous Behavior: The Nodemgr environment variable "ROAMING_PEER_ECHO_MODULATOR" controls the echo request generation towards the roaming peer. When the value of "ROAMING_PEER_ECHO_MODULATOR" changes, the NodeMgr pod restarts.

New Behavior: To optimize this behaviour, use of environment variable ROAMING_PEER_ECHO_MODULATOR is deprecated and support is added to configure different echo intervalsdone for roaming peers using S8e interface configuration. If the S8e interface echo configuration is enabled, then cnSGW-C uses this configuration for Echo Request generation towards roaming peer.

The following sample configuration is added: 


config 
   instance instance-id 1 
      endpoint gtp 
         interface s8e 
         echo interval 300 
         echo retransmission-timeout 10 
         echo max-retransmissions 4 
         path-failure detection-policy pf1 
      exit 
   exit 
exit 
config 
   policy path-failure-detection pf1 
      max-remote-rc-change 2 
      ignore echo-failure 
      exit

Note

 

If the S8e interface configuration is not present, then cnSGW-c uses the Environment variable ROAMING_PEER_ECHO_MODULATOR to control echo request generation towards the roaming peer.

Customer Impact: You can avoid the pod restart if you use the S8e configuration on the GTPC interface.

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

Table 1. 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 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

There are no open bugs in this software 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 are available in the Cisco Bug Search Tool.

Bug ID

Headline

CSCwn26804

S5DeleteBearerReq Failing with Error Message : Session not found

CSCwn29556

Disabling the oveload feature results in single instance of sgw-service restart

CSCwn33214

GR switchback results in GR Instance detecting false overload and throttling happens for 10 mins

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.

Table 2. Release Package Information

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.