CISCO ASR5K-00-PW01REC ASR 5000 Series

ASR5K-00-PW01REC Software Entitlement Identity

ASR5K-00-PW01REC 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 public ASR5K software end-of-life table does not provide an exact-description row for this PID. The code is therefore retained without expanding its acronym or claiming a feature or capacity that Cisco has not confirmed in the public source.

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 exact feature expansion and capacity are deliberately not inferred from the PID tokens. Require a Cisco sales record, entitlement document or official product notice that repeats the complete code before approval.

PID-specific procurement case

Treat this line as a capacity-governance decision. Record the measured baseline, forecast horizon, Cisco-published unit and approval threshold. Do not accept a capacity label copied from another SKU, even when the price or suffix appears similar.

Acceptance record for this line

For this exact order line, the accountable reviewer is the packet-core release manager. The required evidence package combines the Cisco sales-order line, entitlement notification and target-account receipt; review it at receiving. If any identifier, account destination, platform scope or capacity statement conflicts, remove temporary registration state and preserve the failed activation output. 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.

Redundancy scope

State whether the entitlement is required on active, standby or both systems and whether failover rights are separate. Do not transfer a capacity or feature statement from a primary license to a recovery PID without Cisco evidence. Link redundancy rights to the exact topology and recovery procedure. Validate failover behavior only when Cisco documentation and the purchased PIDs explicitly cover it.

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.

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.

Lifecycle and migration check

Do not transfer the bulletin's dates from a neighboring ASR5K PID to this exact code. Ask Cisco or the authorized source to confirm lifecycle, migration and support status in the quotation, then retain that evidence with the entitlement record.

Related ASR 5000 license records

• ASR5K-00-PW10GTWY software entitlement
• ASR5K-00-PT10S-K9 software entitlement
• ASR5K-00-PW01LIC 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