CISCO ASR5K-00-CS01MPLS MPLS License, 1K

ASR5K-00-CS01MPLS Software Entitlement Identity

ASR5K-00-CS01MPLS 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 License, 1K.

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. Do not extend that statement to a different ASR5K, ASR55 or LIF5K code.

PID-specific procurement case

Treat the purchase as a migration checkpoint rather than indefinite expansion. Record the remaining support horizon, approved successor architecture, final-use date and owner of the retirement decision. Available stock does not cancel an end-of-life plan.

Acceptance record for this line

For this exact order line, the accountable reviewer is the network change approver. The required evidence package combines the pre-change license inventory, approved feature request and post-change status; review it at the migration gate. If any identifier, account destination, platform scope or capacity statement conflicts, open a Cisco licensing case before consuming or transferring the right. 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.

Operational ownership

Assign an owner for license alarms, capacity consumption, renewal or migration dates and Smart Licensing communication. Add the exact PID to the configuration inventory so later audits do not rely on a generic router asset record. Define alert thresholds and review frequency. Close stale or duplicate entitlements so the inventory reflects what the platform can actually use.

Commercial reconciliation

Reconcile the purchase order, Cisco sales order, entitlement identifier and target Smart Account. Resolve quantity or PID mismatches before the license is consumed because corrections become harder after activation. Receiving should verify all identifiers while the supplier can still correct them. Attach the final account destination and activation owner to the accepted line.

Decommission control

When the related service is retired, remove or reassign the entitlement only through Cisco-supported procedures. Preserve the final license state and migration approval so unused rights are not mistaken for active capacity. Close monitoring and capacity records when a license is retired. Keep the final evidence with the migration project to prevent the same PID from being counted twice.

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-CS01PIF software entitlement
• ASR5K-00-CS01TRPO software entitlement
• ASR5K-00-CS01FW 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