CISCO ASR5K-00-CS01E-K9 ASR 5000 Series

ASR5K-00-CS01E-K9 Software Entitlement Identity

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

Build an activation rehearsal for this PID in a controlled environment. Preserve the pre-check, registration method, expected license state, test result and cleanup steps. Production approval should reference the rehearsal rather than relying on a reseller description.

Acceptance record for this line

For this exact order line, the accountable reviewer is the Smart Account custodian. The required evidence package combines the Cisco sales-order line, entitlement notification and target-account receipt; review it before activation. If any identifier, account destination, platform scope or capacity statement conflicts, freeze further rollout until capacity and lifecycle evidence are corrected. 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.

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.

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.

Operational ownership

Assign an owner for license alarms, capacity consumption, renewal or migration dates and Smart Licensing communication. Add the exact PID to the configuration inventory so later audits do not rely on a generic router asset record. Define alert thresholds and review frequency. Close stale or duplicate entitlements so the inventory reflects what the platform can actually use.

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-CSXXL4TH software entitlement
• ASR5K-00-CS01GRET software entitlement
• ASR5K-00-CS01DCC 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