CISCO ASR5K-00-CS01ECG1 ASR 5000 Series

ASR5K-00-CS01ECG1 Software Entitlement Identity

ASR5K-00-CS01ECG1 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 Enhanced Charging Bundle 1, 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

Use a staged consumption policy for this entitlement. Name the reservation owner, permitted activation window, release condition and process for returning unused rights. This prevents a test registration from silently consuming production capacity.

Acceptance record for this line

For this exact order line, the accountable reviewer is the configuration audit owner. 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, hold payment acceptance until the exact PID and destination account agree. 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.

Activation acceptance

Define a successful activation test that is specific to the ordered feature. Preserve the license state, relevant configuration and one controlled functional result, then remove temporary test settings and close exceptions. The evidence should show the intended feature working and no unexpected license alarm. Record the reviewer and timestamp so a later support case can reproduce the entitlement state.

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.

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.

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 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-CS01DCC software entitlement
• ASR5K-00-CS01ICFS software entitlement
• ASR5K-00-FY10SW 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