CISCO ASR5K-00-PT10S-K9 ASR 5000 Series

ASR5K-00-PT10S-K9 Software Entitlement Identity

ASR5K-00-PT10S-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

Link this order to a software-release compatibility decision. Capture current StarOS build, planned build, Cisco documentation reference, prerequisite licenses and the engineer who approved the combination. Recheck the decision if the release plan changes.

Acceptance record for this line

For this exact order line, the accountable reviewer is the core licensing administrator. The required evidence package combines the pre-change license inventory, approved feature request and post-change status; review it before activation. If any identifier, account destination, platform scope or capacity statement conflicts, cancel the change window and restore the recorded license baseline. 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.

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.

Security review

For encryption, filtering, lawful-intercept or traffic-control functions, obtain the required legal and security approvals before activation. Limit access to entitlement and configuration evidence to the authorized operational teams. Record the authorized business purpose and the teams permitted to view configuration or usage evidence. This control is especially important where the feature affects subscriber traffic or regulated functions.

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

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