CISCO ASR5K-00-PW01LIC ASR 5000 Series

ASR5K-00-PW01LIC Software Entitlement Identity

ASR5K-00-PW01LIC 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 PGW Bundle, 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

Create a legal-and-security review packet before enabling this entitlement. Identify the authorized purpose, data-access boundary, named approver and evidence-retention rule. Procurement must not convert a commercial license line into operational permission.

Acceptance record for this line

For this exact order line, the accountable reviewer is the network change approver. The required evidence package combines the Cisco sales-order line, entitlement notification and target-account receipt; review it after registration. 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.

Capacity boundary

Do not infer a session count from price or from a neighboring PID. Where Cisco publishes a capacity in the exact description, preserve that unit in the order and acceptance record; otherwise obtain a Cisco-backed capacity statement before purchase. Capacity acceptance should use the same unit Cisco uses for that PID. A session, subscriber, SAAU, system or chassis entitlement must not be converted into another measure without written vendor guidance.

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.

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.

Lifecycle evidence

Review Cisco's current product notice and support documentation on the decision date. Record the exact PID match; do not apply an end-of-sale date from a related code when the exact order line is absent from the notice. Capture the notice revision date and whether the exact PID is present. If it is absent, document that lifecycle remains quote-verified rather than importing a date from another product.

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-SN01CHRG software entitlement
• ASR5K-00-SNXXALES software entitlement
• ASR5K-00-PG10S-K9 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