CISCO ASR5K-00-CS01P2PD ASR 5000 Series

ASR5K-00-CS01P2PD Software Entitlement Identity

ASR5K-00-CS01P2PD 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 Application Detection and Control, 1K 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 1K capacity unit. Do not extend that statement to a different ASR5K, ASR55 or LIF5K code.

PID-specific procurement case

Define machine-readable evidence for this line. Save license status output, entitlement transaction and configuration reference alongside the human-readable approval. Screenshots alone are insufficient when later engineers need to search or compare the result.

Acceptance record for this line

For this exact order line, the accountable reviewer is the telecom procurement reviewer. The required evidence package combines the pre-change license inventory, approved feature request and post-change status; review it at receiving. If any identifier, account destination, platform scope or capacity statement conflicts, quarantine the entitlement and return the line to procurement reconciliation. 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.

Activation acceptance

Define a successful activation test that is specific to the ordered feature. Preserve the license state, relevant configuration and one controlled functional result, then remove temporary test settings and close exceptions. The evidence should show the intended feature working and no unexpected license alarm. Record the reviewer and timestamp so a later support case can reproduce the entitlement state.

Migration planning

Link the line item to the approved ASR5K migration design, target release and replacement platform. Available inventory does not by itself establish continued support or compatibility with the planned core-network architecture. Set a dated decision for continued use, migration or retirement. Recheck product notices before buying extra capacity because lifecycle conditions can change after a quote is issued.

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.

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-CS01ECG1 software entitlement
• ASR5K-00-CS01HDRE software entitlement
• ASR5K-00-CS01NAT 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