CISCO ASR5K-00-CS10MPLS ASR 5000 Series

ASR5K-00-CS10MPLS Software Entitlement Identity

ASR5K-00-CS10MPLS is a Cisco ASR 5000 / StarOS software-license order code. It is not an ASR chassis or a physical WAN router. This page must be used to verify a software entitlement, not to select ports, power supplies, airflow, rack hardware or cabling.

Cisco's current ASR5K software end-of-life table identifies this exact PID as MPLS, per 10K Sessions.

What this order does not include

No ASR 5000 chassis, packet-processing card, interface module, cable, power component, rack accessory or physical appliance is included by this software PID. Hardware availability and compatibility must be handled as separate order lines.

Exact feature and capacity evidence

The public Cisco table supplies the exact description shown above and identifies a 10K capacity unit. Do not extend that statement to a different ASR5K, ASR55 or LIF5K code.

PID-specific procurement case

Create a support-readiness record for this entitlement. Preserve support contract, covered node, entitlement administrator, Cisco case route and out-of-hours contact. Activation should not proceed when the team cannot demonstrate who will resolve a licensing fault.

Acceptance record for this line

For this exact order line, the accountable reviewer is the Smart Account custodian. The required evidence package combines the pre-change license inventory, approved feature request and post-change status; review it during handover. If any identifier, account destination, platform scope or capacity statement conflicts, freeze further rollout until capacity and lifecycle evidence are corrected. Close the record only when another engineer can reproduce the entitlement decision from the stored evidence without relying on the product-page wording.

Entitlement identity

Require the Cisco quotation and entitlement record to repeat the complete PID, quantity and commercial term. Reject a line that shortens the code or replaces it with a family label because adjacent ASR5K licenses can authorize different functions and capacities. The approver should sign the exact order string and retain the Cisco source used to interpret it. If the source and quotation disagree, stop release and ask Cisco to resolve the discrepancy.

Installed release evidence

Record the StarOS release, platform identifier and current software inventory before ordering. The receiving owner should compare the new authorization with that baseline and retain the post-install license output instead of treating an order confirmation as activation evidence. The baseline should include command date, node role and software build. Repeat the capture after activation so the change can be reviewed independently of the sales paperwork.

Feature dependency

Ask Cisco or the authorized source for prerequisite features, base licenses and release constraints. A feature entitlement may still be unusable when the required service, interface, charging function or policy package is absent. List every prerequisite as an owned configuration item. Verify those dependencies in staging or a controlled maintenance window before declaring the new feature available.

Support coverage

Verify which support contract covers software assistance, defect handling and entitlement administration. Record the contract owner and escalation route because a software PID does not automatically include every support service. Support ownership should include contract number, covered node and entitlement administrator. Escalation details belong in the operational record, not only in procurement email.

Change control

Document the activation window, pre-check, rollback method and success criteria. Confirm that the target software release accepts the entitlement before a production change and retain the post-change license status. The rollback must cover both configuration and entitlement state. Confirm that temporary registrations or reservations are cleaned up if the activation test fails.

Audit retention

Store the quote, entitlement notification, Smart Account transaction, activation output and acceptance result under one reference. Keep the exact PID searchable so an auditor can distinguish it from failover and different-capacity variants. Retain machine-readable outputs as well as screenshots. The record should let another engineer prove what was purchased, where it landed and whether it was accepted.

Lifecycle and migration check

The Cisco bulletin classifies the affected line as application software, lists March 31, 2025 as the end-of-sale date and July 31, 2027 as the last date of support. Confirm active support-contract terms and the migration path before purchase.

Related ASR 5000 license records

• ASR5K-00-CS01MPLS software entitlement
• ASR5K-00-CS01ICFP software entitlement
• ASR5K-00-CS01ITC software entitlement

Official Cisco references

• Cisco ASR5K software end-of-life announcement and PID table
• Cisco ASR 5500 Smart Licensing administration guide
• Cisco ASR 5000 Series support portal