CISCO Release Notes for the StarOS Software User Guide

CISCO Release Notes for the StarOS Software

Release Notes for the StarOS™ Software Version 2024.02.l0

• First Published: April 30, 2024
• Last Updated: May 03, 2024

Introduction

This Release Notes identifies changes and issues related to the Legacy Gateway (ASR 5500) software release.

Release Lifecycle Milestones

Release Package Version Information

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

What’s New in this Release
This version of Release Notes includes a new section titled What’s New in this Release comprising all new features, enhancements, and behavior changes applicable for the release.
There are no new features or enhancements for this Release.

Features and Enhancements

This section covers a brief description of the features and enhancements introduced in this release.

Related Documentation

For a complete list of documentation available for this release, go to:
http://www.cisco.com/c/en/us/support/wireless/asr-5000-series/products- installation-and-configuration-guides-list.html

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.

Firmware Updates
There are no firmware upgrades required for this release.

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

Table 1 – Checksum Calculations per Operating System

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>

NOTES:

_< filename> _is the name of the file.

_< extension> _is the file extension (e.g. .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

• In 2024.01 and later releases, software images for StarOS, VPC-DI, and VPC-SI, and the companion software packages for StarOS and VPC are signed via x509 certificates.
• USP ISO images are signed with a GPG key.
• For more information and instructions on how to validate the certificates, refer to the README file available with the respective software packages.

Open Bugs for this Release

The following table lists the open bugs 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.

Table 2 – Open Bugs in this Release

egtpu_process_update_req_evt()egtpu_handle_user_sap_event()sess- mgr_uplane_gtpu_tx_update()| cups-up
CSCwj24130| Inconsistency in counters in gtpu bulkstats for UP| cups-up
CSCwj36352| Assertion failure at sess/mme/mme-app/app/mme_tau_proc.c:1701| mme
CSCwj72131| Improper output for PDN GW Name in ‘show mme-service db record ‘

is a display issue.

| mme
CSCwj66981| Sessmgr crash-egtpc_send_ind_evt()| pdn-gw
CSCwj52492| While triggerring the interim CDR, there is no aaa_sess_handle and sessmgr restart| pdn-gw
CSCwj25382| UDP flows are not getting blocked when 0 quota is received from OCS| pdn-gw
CSCwj78838| Assertion failure at “sit_api_rct_task_death_req” on 21.28.m23.93362| pdn-gw
CSCwj70487| Assertion failure at sess/snx/drivers/sgw/sgw_drv.c:374| sgw
CSCwj68378| ASR5500 SPGW Assertion failure at sgwdrv_send_tx_setup_to_egtpu| sgw
Bug ID| Headline| Product Found
---|---|---
CSCwj68218| Assert observed at sgwdrv_collect_pdn_info| sgw
CSCwj17471| Planned srp switchover is succeeded though bgp monitor in stby upf is down| staros
CSCwi59036| Port redundancy Failed in 4-port deployment VPC SI| staros
CSCwd99519| Error logs seen on UPF PDR not found with PDR ID 0x149 and Remove PDR PDR with ID 0x2ce| upf

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.

Table 3 – Resolved Bugs in this Release

// 21.28.m15 (91862) //h Assertion failure at sess/snx/drivers/saegw/saegw_recovery.c:35| cups-cp
CSCwj00472| sessmgr 12341 error when HO between SGWs| cups-cp
CSCwj50864| Assertion failure at sess/smgr/sessmgr_pgw.c:9924| cups-cp
CSCwi71670| X3 Lawful Intercept is marked as wrong EBI when using ipv6 session over dedicated bearer| cups-cp
CSCwi94768| Documentation to update the max entries supported in Gx local-policy- service| cups-cp
CSCwi28946| [BP- CUPS] Lot of error logs – [SXAB] Failed to remove Traffic Endpoint with Traffic Endpoint ID| cups-cp
CSCwj38556| In roaming scenraio – MCC-only feature rejects the bearer after 4G3G mobility d| cups-cp
CSCwi53552| sessmgr Fatal Signal 11: 11 uplane_free_nat_binding_info()uplane_free_app_data_flow()| cups-up
CSCwc99110| Assertion failure at sess/smgr/sessmgr_gtpu.c sessmgr_egtpu_signalling_routine()| cups-up
CSCwi35960| huge amount of “ICMP packet parse failure” logs in 21.28.m15 with NAT| cups-up
CSCwi69056| VPP buffer leak caused a VPP restart| cups-up
CSCwj85083| CUPS UP : npumgr crashes after upgrade to 21.28.m22| cups-up
Bug ID| Headline| Product Found
---|---|---
CSCwj44782| MME wrongly selecting s2b PGW record (x-3gpp-pgw:x-s2b-gtp+nc- smf) for 5G capable UE’s| mme
CSCwi85182| Sessmgr restart due to Assertion failure at function sn_gt_release_mm_teid()| mme
CSCwi55030| Observed multiple sessmgr went to warn/over state in 21.28.m18.92419 during regression| mme
CSCwd25108| DNS Failure – TCP READ, Kernel Closed – req_read_len = 0| mme
CSCwi48857| Sessmgr Assertion failure at egtpc_send_req_msg()| mme
CSCwc83863| Assertion failure at sess/mme/mme-app/app/mme_app_util.c:18558| mme
CSCwj29750| Sessmgr restart after SW upgrade to 21.28.m19, mme_auth_awt_hss_hss_resp()| mme
CSCwj30320| vplmn- address option is not showing under call-control-profile| mme
CSCwj33658| sessmgr crash due to Fatal Signal 11: 11 PC: [06bbc47f/X] smgr_process_iri_hi2()| pdn-gw
CSCwj24901| Empty APN list in “show s8hr config” after node reload| pdn-gw
CSCwi54796| VPC-SI – bfd sometimes sending ipv6 packets with udp checksum 0x0 – which is invalid| pdn-gw
CSCwj24886| ipsecmgr restart seen after the rekeying process| pdn-gw
CSCwj15020| ASR5500 – [SPGW] – sessctrl failure| pdn-gw
CSCwj72598| user- plane traffic stops when sgw-u (Sxa) and pgw-u (Sxb) functions are hosted on the same UP| pdn-gw
CSCwi67492| For gtpu-schema , few bulkstat counters not incremented| pdn-gw
CSCwj24899| Few sessmgrs having TCP connect issues on Checkpointmgr| rcm
CSCwi68538| RCM- Checkpointmgr crash due to fatal error concurrent map read and map write| rcm
CSCwi79878| IP Pool flush enhancements for planned RCM UPF SWO| rcm
CSCwj36377| Help ? for rcm-config-ep write-timeout shows inconsistency not similar with other| rcm
CSCwi69314| Planned swo gives incorrect message in ops-centre| rcm
CSCwi87259| StandbySessmgrDisconnected trap is not generated when upf reload due to planned switchover fails| rcm
CSCwi65948| format of dateandtime used by RCM does not comply to snmpv2| rcm
CSCwi73027| Stale data in RCM post switchover| rcm
Bug ID| Headline| Product Found
---|---|---
CSCwi74961| TCP hardening – Timeout observed during socket write during switchover| rcm
CSCwi23288| session manager restart at sn_dp_utran_process_purge_req_evt fucntion| sgsn
CSCwi70115| SNS- Add messages were not sent after adding new NSVL instance| sgsn
CSCwj26308| Assertion failure at sess/sgsn/sgsn-app/gtp_c/gtapp_tun_fsm.c:6936| sgsn
CSCwi63250| Despite “monitor system card-fail” config, switchover does not occur| staros
CSCwi59951| TCP length issue in DNS query causing time out| staros
CSCwi67402| Sessmgr restart at saegwdrv_ue_fsm_st_active_evt_snx_abortcall(),| staros
CSCwi65052| [BP- CUPS] [connectedapps 203750 error CONNECTEDAPPS ERROR:Unable to open the btmp file /var/log/btmp| staros

Operator Notes

StarOS Version Numbering System
The output of the show version command displays detailed information about the version of StarOS currently running on the ASR 5500 or Cisco Virtualized Packet Core platform.
NOTE: Starting 2024.01.0 release (January 2024), Cisco is transitioning to a new release versioning scheme. The release version is based on the current year and product. Refer to Figure 1 for more details.
During the transition phase, some file names will reflect the new versioning whereas others will refer to the 21.28.x-based naming convention. With the next release, StarOS-related packages will be completely migrated to the new versioning scheme.
Version Numbering for FCS, Emergency, and Maintenance Releases

Figure 1 – Version Numbering

Release Package Descriptions
Table 4 provides descriptions for the packages that are available with this release. For more information about the release packages up to 21.28.x releases, refer to the corresponding releases of the release note.

Table 4 – Release Package Information

ASR 5500

asr5500-.zip

| Contains the signed ASR 5500 software image, the signature file, a verification script, the x509 certificate, and a README file containing information on how to use the script to validate the certificate.

asr5500_T-.zip

| Contains the signed, trusted ASR 5500 software image, the signature file, a verification script, the x509 certificate, and a README file containing information on how to use the script to validate the certificate.
StarOS Companion Package

companion-.zip

| Contains numerous files pertaining to this version of the StarOS including SNMP MIBs, RADIUS dictionaries, ORBEM clients. These files pertain to both trusted and non-trusted build variants.
VPC-DI
qvpc-di-.bin.zip| Contains the VPC-DI binary software image that is used to replace a previously deployed image on the flash disk in existing installations.
qvpc-di_T-.bin.zip| Contains the trusted VPC-DI binary software image that is used to replace a previously deployed image on the flash disk in existing installations.s
qvpc-di-.iso.zip| Contains the VPC-DI ISO used for new deployments, a new virtual machine is manually created and configured to boot from a CD image.
qvpc-di_T-.iso.zip| Contains the trusted VPC-DI ISO used for new deployments, a new virtual machine is manually created and configured to boot from a CD image.
---|---
qvpc-di-template-vmware-