CISCO ASR5K-00-CS01ITC ASR 5000 Series

ASR5K-00-CS01ITC Software Entitlement Identity

ASR5K-00-CS01ITC 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 Intelligent Traffic Control, 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

Prepare a feature-prerequisite matrix for this line. Each prerequisite should show installed state, owning team, Cisco evidence and remediation owner. The matrix prevents a correctly delivered entitlement from being mistaken for a complete deployable solution.

Acceptance record for this line

For this exact order line, the accountable reviewer is the platform migration architect. The required evidence package combines the quoted PID, capacity unit, platform serial and virtual-account assignment; review it at the migration gate. If any identifier, account destination, platform scope or capacity statement conflicts, reject the substitute and restart technical approval with the proposed code. 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.

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.

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.

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.

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

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-CS01FW software entitlement
• ASR5K-00-IG10BDC software entitlement
• ASR5K-00-CS01CSFB 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