The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Feedback
StarOS™ Software, Release 2026.02.g0
StarOS™ Software, Release 2026.02.g0
The key highlights of this release include:
· Enhanced MME capabilities for inter-operator roaming during emergency calls.
· Adjusted S1 handover guard timers to prevent timeout issues and optimize network resources.
· Improved reliability and flexibility in charging data handling for P-GW.
· Ensured dual-stack connection success by anchoring IPv6 sessions to the same User Plane as the HOLD IPv4 session.
· Added support for filtering monitor subscriber commands by specific sessmgr instances for pgw, sgw, saegw, and ggsn.
· Enabled Gz tariff time replication from Gy buckets to prevent signaling storms in CUPS deployments.
For more information about the StarOS product documentation, see the Related resources section.
Qualified products and platforms
Table 1. Products and platforms qualified in this release
| Component |
Qualified? |
| Products |
|
| CUPS |
Yes |
| MME |
Yes |
| ePDG |
Yes |
| P-GW |
Yes |
| SAEGW |
Yes |
| SGSN |
Yes |
| Platforms |
|
| ASR 5500 |
No |
| VPC-DI |
Yes |
| VPC-SI |
Yes |
The following table provides EoL milestones for Cisco StarOS software:
Table 2. EoL milestone information for StarOS™ Software
| Milestone |
Date |
| First Customer Ship (FCS) |
23-Apr-2026 |
| End of Life (EoL) |
23-Apr-2026 |
| End of Software Maintenance (EoSM) |
22-Oct-2027 |
| End of Vulnerability and Security Support (EoVSS) |
22-Oct-2027 |
| Last Date of Support (LDoS) |
31-Oct-2028 |
These milestones and the intervals between them are defined in the Cisco ASR 5500 and Ultra Packet Core software release lifecycle product bulletin available on cisco.com.
This section provides a brief description of the new software features introduced in this release.
Table 3. New software features for StarOS™ Software, Release 2026.02.g0
| Product impact |
Feature |
Description |
| Software Reliability |
Configurable MME S1 HO guard timer duration
|
This feature allows the network operator to modify the default hardcoded S1 HO guard timer value of 50 seconds into configurable range between 10 to 50 seconds specifically for the inbound S1 handover procedure over the S10 interface. This prevents external MME timeout issues and optimizes network resource usage during mobility events. Command introduced: under MME service configuration mode. · default policy handover s10 guard-timer · policy handover s10 guard-timer <guard-timer seconds> - Enter the Guard timer intervals between 10-50 seconds. |
| Software Reliability |
MME Emergency Profile Selection based on IMSI Range and Service PLMN ID |
This feature enhances MME capabilities to handle network outages by enabling inter-operator roaming for emergency calls. You can now configure LTE Emergency Profiles based on specific IMSI ranges and service PLMN IDs, ensuring communication services during disasters. It allows only authenticated emergency calls while rejecting other attach requests with configured emm cause code. This is achieved by associating LTE Emergency Profiles with operator policies, selected via IMSI and PLMN ID. Commands introduced: · enable-imsi-based-lte-emergency-profile (under mme-service) · associate lte-emergency-profile <profile name> (under operator-policy name <policy name>) Commands updated: · attach restrict access-type eps [allow-emergency-auth ] [ emm-cause-code <code>] (under call-control profile <ccp>) |
| Software Reliability |
This feature enables secure delayed charging over TLS/QUIC with improved reliability and flexibility in charging data handling. |
|
| Software Reliability |
Anchors IPv6 session to the same User Plane (UP) as the HOLD IPv4 session during reassociation, overriding standard UP selection algorithms to ensure dual-stack connections are successful. |
|
| Software Reliability |
Monitor Subscriber Sessmgr Instance Filtering |
Added support for filtering monitor subscriber commands by specific sessmgr instance. This feature is supported only for pgw, sgw, saegw, and ggsn call types. |
| Software Reliability |
The feature enables replication of Gz tariff time from the Gy bucket. It ensures suppression of Sx Query-URR to prevent signalling storms in CUPS deployments. Command introduced: egcdr tariff replicate-ocs-tariff-time-change- This CLI command is configured in Active Charging Service command mode. Default settings: Disabled-Configuration required to Enable |
This section provides a brief description of the behavior changes introduced in this release.
Table 4. Behavior changes for StarOS™ Software, Release 2026.02.g0
| Description |
Behavior changes |
| PGW IMSI Suppression during unauthenticated emergency attach messages [CSCwt19501] |
Previous Behavior: · Subscription-Id-Type: END_USER_E164 (0) · Subscription-Id-Data: 9890098900 · Subscription-Id-Type: END_USER_IMSI (1) · Subscription-Id-Data: 404005123456788 New Behavior: · Subscription-Id-Type: END_USER_E164 (0) · Subscription-Id-Data: 9890098900 Command introduced under the PGW service configuration mode: subscription-id service-type { closed_rp | ggsn | ha | ipsg | l2tplns | mipv6ha | pdsn | pgw | samog-epdg } { e164 | imsi | nai | lsm-emergency-imei-instead-of-uimsi } Note: This keyword is configured under the 'ims-auth service' for emergency APNs. It applies only to emergency APNs over TLS/QUIC, providing improved reliability and flexibility for charging data handling. |
| NOA/NPI is added to the servedMSISDN field in the PGWCDRs [CSCwt19446] |
Previous behavior: servedMSISDN of the PGWCDR does not contain NOA/NPI New behavior: PGWCDRs supports the Nature of Address (NOA) and Numbering Plan Indicator (NOI) parameters aligning with 3GPP TS 29.002. These parameters are used in routing calls and messages to determine how a phone number should be interpreted. Command introduced: include-msisdn-noa-npi- Indicates NOA/NPI(0x91) in the PGWCDR MSISDN. Customer impact: When this include-msisdn-noa-npi CLI is enabled you can have the new behavior visibility. |
| Colocated gateway selection during EPSFallback for roaming PLMN [CSCwq14755 ]
|
Previous behavior: During a Tracking Area Update (TAU) for EPS fallback, roaming subscribers did not utilize the configured co-location or topology criteria for SGW selection. New behavior: The gw-selection command within the Call Control Profile configuration mode has been enhanced with the apply-for-roamer option. When this configuration is enabled, roaming subscribers will now undergo SGW selection based on the configured co-location or topology criteria during EPS fallback TAU scenarios. Customer Impact: The customer will have better control over resource management for roaming subscribers. |
| ConfD schema compatibility handling [CSCwo47013] |
Previous behavior: During ConfD upgrades, version incompatibilities with persisted schema files could lead to initialization failures and repeated confdmgr crashes; as there was no CLI utility available to clear this data, it was necessary to manually remove the contents of the /mnt/hd-raid/meta/confd directory during the upgrade process to ensure system stability. New behavior: A new CLI command, clear confdmgr confd all, has been introduced to clear all persistent ConfD data, which facilitates a clean reinitialization and prevents initialization failures during upgrades. For more information on the method of procedure, refer to the Upgrade the confd version |
This table lists the resolved issues in this specific software release.
Note: This software release may contain bug fixes first introduced in other releases. To see additional information, click the bug ID to access the Cisco Bug Search Tool. To search for a documented Cisco product issue, type in the browser: <bug number> site:cisco.com.
Table 5. Resolved issues for StarOS™ Software, Release 2026.02.g0
| Bug ID |
Description |
Product Found |
| Unauthorized Session Establishment Triggered by Gy CCR-U and RAR Timing Collision |
cups-cp |
|
| sxdemux task memory usage high leading to a restart |
cups-cp |
|
| Sx Sess-Mod-Req failure with CC 69 Mandatory IE Incorrect |
cups-cp |
|
| Sessmgr restarted at function egtpc_handle_user_sap_event |
cups-cp |
|
| High number of CC category misses |
cups-cp |
|
| Addition of a trap after the state of the peer user plane changes from configured to not configured or vice versa. |
cups-cp |
|
| Wrong Time Quota observed in second SX_SESSION_MODIFICATION_REQUEST when new quota with RAR Trigger |
cups-cp |
|
| Gy session out of SU reports huge volume threshold in SxModify |
cups-cp |
|
| Sessmgr restart due to Segmentation fault: acsmgr_allocate_cups_sef_info() |
cups-cp |
|
| Difference in the volume reported in Sx-Volume Measurement and monsub- CALL STATS |
cups-up |
|
| Abnormal CC-Total-Octets values after UP reload |
cups-up |
|
| Memory leak observed in func mme_db_cache_alloc_non_current_security_context w/ n26 |
mme |
|
| Observed sessmgr assert during Outbound Handover to peer MME |
mme |
|
| In a failover scenario, MME does not retry properly to all the recieved RR's from DNS based on priority |
mme |
|
| TAU is rejected post inbound HO when MICR check and decor is enabled |
mme |
|
| Emergency call-garbage value seen in bulkstat and show mme-ser statistics lte-emergency-profile profile-name lte1 |
mme |
|
| Colocated gateway selection during EPSFallback for roaming PLMN |
mme |
|
| MME rounding down APN-AMBR value received from ULA before comparing with ctx-resp |
mme |
|
| Observing sessmgr crash for function :: mme_egptc_set_pdn_state in version |
mme |
|
| GW is sending CCR-U with charging rule report with cause "Rule-Failure-Code: UNSUCCESSFUL_QOS_VALIDATION" |
pdn-gw |
|
| Unexpected S6b Event File Generation on PGW Gateways |
pdn-gw |
|
| Unable to convert date-time string in the Diameter credit-control-request message processing. |
pdn-gw |
|
| Traffic is being re-directed in error by the PGW due to GOR ruledef update |
pdn-gw |
|
| Assertion failure: EGTP-C service is being used by another MME/SGW/PGW service |
pdn-gw |
|
| PGW is sending '0x40' for IpAddress instead of '0x04' |
pdn-gw |
|
| Assertion failure at diameter/diabase/diabase' |
pdn-gw |
|
| Incorrect MSISDN Encoding: Missing NOA/NPI Octet in PGW-CDRs 3GPP TS 32.298 Compliance |
pdn-gw |
|
| Some of the http flows are not getting accelerated |
pdn-gw |
|
| PGW (VPC) incorrectly charges for Router Solicitation (RS) packets in IPv6 sessions. |
pdn-gw |
|
| sessmgr restart at sn_aaa_client_action_item_lookup_by_key() |
pdn-gw |
|
| Legacy-GW: VzW ASR5500: sessmgr restart observed at PC: [0684595b/X] sessmgr_ipv4_process_user_pkt_part3() when perform the unconfigure / configure of new apn, new rulebase, new fw-nat-policy and SRP switchover on stdby |
pdn-gw |
|
| Active-charging MBR change after Gx CCR-U |
pdn-gw |
|
| PGW Session Setup Failure: Static IPv4 Address Mismatch for APN "nemo-cust101" |
pdn-gw |
|
| Some of the http flows are not getting accelerated |
pdn-gw |
|
| P-CSCF Address Missing in CSRsp When DNS Returns Only CNAME Without Resource Records |
pdn-gw |
|
| High speed traffic is not reported in CDR and Gy |
pdn-gw |
|
| PGW sends the IMSI in the CCR-I message to the PCRF for unauthenticated emergency calls |
pdn-gw |
|
| UDP quic traffic detection problem |
pdn-gw |
|
| MFP4.0 April 2026 the build need to support cilium instead of calico. Hitting issues with calico during RCM deployment. Also, rcm ned needs correction to proper 4G CUPS based RCM NED currently its 5G SMI based. |
nso-mob-fp |
|
| Mobility MFP 3.4.3 / CommandSanitizer incorrectly removing configuration from string |
nso-mob-fp |
This table lists the open issues in this specific software release.
Note: This software release may contain open bugs first introduced in other releases. To see additional information, click the bug ID to access the Cisco Bug Search Tool. To search for a documented Cisco product issue, type in the browser: <bug number> site:cisco.com.
Table 6. Open issues for StarOS™ Software, Release 2026.02.g0
| Bug ID |
Description |
Product Found |
| Context removal & addition leads to incorrect flow creation leading to TCP flows recognized incorrect |
cups-cp |
|
| sessctrl_handle_mgr_notify_server_list_ipaddr_status_update() |
cups-up |
|
| Zero volume Usage seen in UNIT_BEFORE_TARIFF_CHANGE in Gy CCR Update while validity Time |
cups-cp |
|
| While Rulebase change CP creates the Static rule URRs causing Gy Replicate functionality |
cups-cp |
|
| Multiple TCP connection over X3 interface |
cups-up |
|
| Silent sessctrl restart during booting up of n:m UP after reload/switchover. Crash list not updated |
cups-up |
|
| Valgrind Observations seen for April26 FCS release |
cups-up |
|
| Multiple sessmgr restart with Assertion failure at diameter/diabase/diabase with acsmgr_mscc_tx_timeout() |
pdn-gw |
|
| WhatsApp calls blocking accuracy problem |
pdn-gw |
|
| Error: application communication failure upon running RCM Ops-Center commands |
rcm |
This section describes the known issue that may occur during the upgrade of the StarOS image.
Install 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.
When upgrading the StarOS image from a previous version to the latest version, issues may arise if there is a problem with the Cisco SSH/SSL upgrade. To avoid such issues, ensure that the boot file for Service Function (SF) cards is properly synchronized.
To synchronize the boot file for all the Service Function (SF) VPC-DI non-management cards, use the following CLI command:
[local] host_name# system synchronize boot
This ensures that the changes in boot file are identically maintained across the SF cards.
Note: Ensure that you execute the system synchronize boot command before reloading for a version upgrade from any version less than 21.28.m23 to 21.28.m23, or versions higher than 21.28.m23.
Upgrade the confD version
This section explains upgrading third-party software. Upgrade the confD software to ensure system compatibility and performance.
Note: During StarOS 2026.02 release, confD is upgraded to 8.6 version.
Prerequisites:
· Ensure you have appropriate permissions to perform this upgrade.
· Back up all necessary data and configurations to avoid permanent loss during file deletion.
· ConfD must be unconfigured (stopped) before running the clear confdmgr confd all CLI command.
Perform these steps to upgrade the confD version on the system.
1. Enter the debug shell using debug shell command.
2. Navigate to the confD directory.
3. Run the command: cd /mnt/hd-raid/meta/confd/ to access the directory.
4. Remove existing files with the command; rm -rf *
-or-
Run the StarOS CLI command clear confdmgr confd all to clear the same confD contents.
Note: The /mnt/hd-raid/meta/confd directory will be empty. After clearing, confD can be started again as required. This clear cli should be used only during ConfD upgrade scenarios and not on each reload or reboot.
All files and subdirectories are deleted, preparing the system for a fresh installation. To preserve data across the Method of Procedure, users with ConfD configured must contact their Cisco account representative.
Method of Procedure (MOP): Upgrade/Downgrade Between Non-Hermes and Hermes Builds
CSCwr80301: HD-RAID Not Ready During Upgrade from Non-Hermes to Hermes
Issue: When upgrading from a non-Hermes (202x.0x.gx) to a Hermes (202x.0x.ghx) build on both Virtualized Packet Core—Distributed Instance (VPC-DI) and Virtualized Packet Core—Single Instance (VPC-SI) platforms, the HD-RAID may not come up as expected.
Workaround: To avoid this hd-raid failure, follow the steps below during the upgrade and downgrade (for example, from 2025.03.g0 to 2025.04.gh0):
1. Pre-requisite: Back up all files stored in /hd-raid before upgrading from the .mx to .mhx build.
Note: All data in /hd-raid will be lost during recovery.
2. Before the upgrade: On the .mx build, run the hd raid clear command.
3. Reboot and upgrade: Reboot the node to upgrade to the .mhx build.
4. Perform the CF card migration in case of VPC-DI or Reload the chassis on VPC-SI. Wait for the HD-RAID to recover.
Note: It is recommended to use this Method of Procedure (MOP) for both upgrading and downgrading between .mx and .mhx StarOS builds.
This section provides compatibility information about the StarOS package version, and the hardware and software requirements for the Legacy Gateway and CUPS software release.
Compatible StarOS package version
Table 7. Release package version information
| StarOS packages |
Version |
Build number |
| StarOS package |
2026.02.g0 |
21.28.m43.100466 |
Compatible software and hardware components
This table lists only the verified basic software and hardware versions. For more information on the verified software versions for the products qualified in this release contact the Cisco account representative.
Table 8. Compatibility software and hardware information, Release 2026.02.g0
| Product |
Version |
| ADC P2P Plugin |
2.74.16.2789 |
| RCM |
20260417-160533Z |
| ESC |
6.0.0.55 |
| CVIM |
5.0.4 |
| Host OS |
RHEL 9.2 |
| RedHat OpenStack |
RHOSP 17.1 |
| Intel XL710C NIC Version |
Driver version: i40e-2.17.4 Firmware: 7.00 0x80005119 0.385.115 |
| CIMC |
4.2 (3) |
| NSO MFP |
4.0 Note: MFP 4.0 includes two OpenStack NED versions: 4.2.33 and 4.2.34. For deployments using Red Hat OpenStack Platform 13, it is recommended to use NED version 4.2.33 due to an API version incompatibility between NED 4.2.34 and OSP 13. |
Note: CVIM and ESC versions are qualified as part of 2025.04.0 release.
This section provides information about the release packages associated with StarOS Classic Gateway, Control, and User Plane Separation (CUPS) software.
Table 9. Software packages for Release 2026.02.g0
| Description |
|
| NSO |
|
| nso-mob-fp-4.0-2026.02.g0.zip |
Contains the signed NSO 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. |
| VPC companion package |
|
| companion-vpc-2026.02.g0.zip |
Contains numerous files pertaining to this version of the VPC including SNMP MIBs, RADIUS dictionaries, ORBEM clients. These files pertain to both VPC-DI and VPC-SI, and for trusted and non-trusted build variants. |
| VPC-DI |
|
| qvpc-di-2026.02.g0.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-2026.02.g0.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. |
| qvpc-di-2026.02.g0.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-2026.02.g0.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-2026.02.g0.zip |
Contains the VPC-DI binary software image that is used to on-board the software directly into VMware. |
| qvpc-di-template-vmware_T-2026.02.g0.zip |
Contains the trusted VPC-DI binary software image that is used to on- board the software directly into VMware. |
| qvpc-di-template-libvirt-kvm-2026.02.g0.zip |
Contains the same VPC-DI ISO identified above and additional installation files for using it on KVM. |
| qvpc-di-template-vmware-2026.02.g0.zip |
Contains the VPC-DI binary software image that is used to on-board the software directly into VMware. |
| qvpc-di-template-libvirt-kvm_T-2026.02.g0.zip |
Contains the same trusted VPC-DI ISO identified above and additional installation files for using it on KVM. |
| qvpc-di-2026.02.g0.qcow2.zip |
Contains the VPC-DI binary software image in a format that can be loaded directly with KVM using an XML definition file, or with OpenStack. |
| qvpc-di_T-2026.02.g0.qcow2.zip |
Contains the trusted VPC-DI binary software image in a format that can be loaded directly with KVM using an XML definition file, or with OpenStack. |
| VPC-SI |
|
| intellig3nt_onboarding-2026.02.g0.zip |
Contains the VPC-SI onboarding signature package that is used to replace a previously deployed image on the flash disk in existing installations. |
| qvpc-si-2026.02.g0.bin.zip |
Contains the VPC-SI binary software image that is used to replace a previously deployed image on the flash disk in existing installations. |
| qvpc-si_T-2026.02.g0.bin.zip |
Contains the trusted VPC-SI binary software image that is used to replace a previously deployed image on the flash disk in existing installations. |
| qvpc-si-2026.02.g0.iso.zip |
Contains the VPC-SI ISO used for new deployment. A new virtual machine is manually created and configured to boot from a CD image. |
| qvpc-si_T-2026.02.g0.iso.zip |
Contains the trusted VPC-SI ISO used for new deployments a new virtual machine is manually created and configured to boot from a CD image. |
| qvpc-si-template-vmware-2026.02.g0.zip |
Contains the VPC-SI binary software image that is used to on-board the software directly into VMware. |
| qvpc-si-template-vmware_T-2026.02.g0.zip |
Contains the trusted VPC-SI binary software image that is used to on-board the software directly into VMware. |
| qvpc-si-template-libvirt-kvm-2026.02.g0.zip |
Contains the same VPC-SI ISO identified above and additional installation files for using it on KVM. |
| qvpc-si-template-libvirt-kvm_T-2026.02.g0.zip |
Contains the same trusted VPC-SI ISO identified above and additional installation files for using it on KVM. |
| qvpc-si-2026.02.g0.qcow2.zip |
Contains the VPC-SI binary software image in a format that can be loaded directly with KVM using an XML definition file, or with OpenStack. |
| qvpc-s3_T-2026.02.g0.qcow2.zip |
Contains the trusted VPC-SI binary software image in a format that can be loaded directly with KVM using an XML definition file, or with OpenStack. |
| RCM |
|
| rcm-vm-airgap-2026.02.g0.ova.zip |
Contains the RCM software image that is used to on-board the software directly into VMware. |
| rcm-vm-airgap-2026.02.g0.qcow2.zip |
Contains the RCM software image in a format that can be loaded directly with KVM using an XML definition file, or with OpenStack. |
| rcm-vm-airgap-2026.02.g0.vmdk.zip |
Contains the RCM virtual machine disk image software for use with VMware deployments. |
StarOS product 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.
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 the figure for more details.
Note: 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.

Note: For any clarification, contact your Cisco account representative.
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. Click Linux and then choose the Software Image Release Version.
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 the table and verify that it matches the one provided on the software download page. To calculate a SHA512 checksum on your local desktop see the table.
Table 10. 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
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.
This table provides key resources and links to the support information and essential documentation for StarOS and CUPS products.
Table 11. Related resources and additional information
| Resource |
Link |
| Cisco ASR 5500 documentation |
|
| Cisco Ultra Packet Core documentation |
|
| Service request and additional information |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2026 Cisco Systems, Inc. All rights reserved.