CISCO ASR5K-00-CS01HDRE ASR 5000 Series

ASR5K-00-CS01HDRE Software Entitlement Identity

ASR5K-00-CS01HDRE 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 Header Enrichment, 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

For this PID, require a serial-to-entitlement mapping where the licensing method uses a platform identity. Verify formatting, node role and account destination before registration. Correct mismatches while the supplier and Cisco transaction records are still available.

Acceptance record for this line

For this exact order line, the accountable reviewer is the service assurance lead. The required evidence package combines the quoted PID, capacity unit, platform serial and virtual-account assignment; review it before activation. If any identifier, account destination, platform scope or capacity statement conflicts, escalate the mismatch to the platform owner and authorized source. 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.

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.

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.

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.

Change control

Document the activation window, pre-check, rollback method and success criteria. Confirm that the target software release accepts the entitlement before a production change and retain the post-change license status. The rollback must cover both configuration and entitlement state. Confirm that temporary registrations or reservations are cleaned up if the activation test fails.

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