CISCO Version 2024.02.gh0 StarOS Software User Manual

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
CSCwi91038| ePDG- VPC-DI-21.28.mh14.92736-Session loss and data loss observed post unplanned active SF reboot| epdg
CSCwj48267| EPDG fails to update the NAT change seen in data traffic following a NAT reboot| epdg
CSCwj17471| Planned srp switchover is succeeded though bgp monitor in stby upf is down| staros
CSCwj08070| intermittent rmmgr task failures on Hermes branch| staros
Bug ID| Headline| Product Found
---|---|---
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

cups-cp
CSCwi19980| Incorrect gtpc teid format in s8hr ims media packets| cups-cp
CSCwj21677| CUPS CP ICSR – 2G/3G -> WLAN HO fails after CP switchover/sessmgr recovery occurred| cups-cp
CSCwe61003| Unexpected “URR node not found at CP for URR-id” logs observed| cups-cp
CSCwj51924| VPCDI // 21.28.m15 (91862) //h Assertion failure at sess/snx/drivers/saegw/saegw_recovery.c:35| cups-cp
CSCwj38556| In roaming scenraio – MCC-only feature rejects the bearer after 4G3G mobility d| cups-cp
CSCwf59908| SAEGW does NOT send CSResp even if SAEGW receives CCA-i with DIAMETER_AUTHORIZATION_REJECTED (5003)| 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| Lot of error logs – [SXAB] Failed to remove Traffic Endpoint with Traffic Endpoint ID| 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
Bug ID| Headline| Product Found
---|---|---
CSCwi35960| Huge amount of “ICMP packet parse failure” logs in 21.28.m15 with NAT| cups-up
CSCwj21736| CUPS UP sessmgr restart in uplane_handle_recvd_tcp_OOO_packet()| cups-up
CSCwj58282| TCP retransmission are seen and connections are closed after ipsec rekey| cups-up
CSCwj23372| sessmgr restart on CUPS UP at – sessmgr_uplane_prepare_gtpu_udpip_hdr_and_send_pkt| cups-up
CSCwi69056| VPP buffer leak caused a VPP restart| cups-up
CSCwa21897| UP socket bind failure happening in some cases| cups-up
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
CSCwj52492| While triggerring the interim CDR, there is no aaa_sess_handle and sessmgr restart| pdn-gw
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
CSCwj52492| While triggerring the interim CDR, there is no aaa_sess_handle and sessmgr restart| pdn-gw
CSCwi39772| Di-net drops on 21.28.mh branch| staros
Bug ID| Headline| Product Found
---|---|---
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

Release Package Descriptions

Table 4 provides descriptions for the packages that are available with this release. For more information about the release package information of older releases such as 21.12.0 and later releases or pre-21.12.0 releases, refer to the previous release notes.
Table 4 – Release Package Information

ASR 5500
asr5500-