CISCO ASR5K-00-CS10ICAP ASR 5000 Software License

ASR5K-00-CS10ICAP Software Entitlement Identity

ASR5K-00-CS10ICAP 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 a service-impact statement for the intended use. Describe the network function, affected traffic domain, maintenance boundary and rollback authority without claiming capabilities not stated by Cisco. Technical approval must precede any customer-facing promise.

Acceptance record for this line

For this exact order line, the accountable reviewer is the network change approver. The required evidence package combines the quoted PID, capacity unit, platform serial and virtual-account assignment; review it at receiving. If any identifier, account destination, platform scope or capacity statement conflicts, open a Cisco licensing case before consuming or transferring the right. 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.

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.

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

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-CS01HDRE software entitlement
• ASR5K-00-CS01NAT software entitlement
• ASR5K-00-AN01REC 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