CISCO ASR5K-00-PT01S-K9 ASR 5000 Software License

ASR5K-00-PT01S-K9 Software Entitlement Identity

ASR5K-00-PT01S-K9 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

Use an exception-controlled substitute process. A proposed alternative must receive a fresh comparison of exact feature, capacity unit, platform scope, term and licensing method. Procurement may not approve substitution based only on a matching ASR5K family name.

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 pre-change license inventory, approved feature request and post-change status; review it after registration. 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.

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.

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.

Order substitution

Require written approval for any proposed substitute. Compare function, capacity, active or failover scope, term, platform and licensing method rather than accepting a similar-looking ASR5K code. A substitute review must be completed before invoicing. If the replacement has a different token, capacity or licensing mode, create a new technical approval rather than editing the original record.

Environment mapping

Map the entitlement to the target chassis or software instance, service context and responsible network function. An unassigned license line creates no operational value and is difficult to validate during renewal or migration. The mapping should survive staff changes: include node, service, account, environment and owner. Update it whenever the licensed workload moves.

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