CISCO ASR5K-00-SN01CHRG ASR 5000 Series

ASR5K-00-SN01CHRG Software Entitlement Identity

ASR5K-00-SN01CHRG 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 UMTS Overcharging Protection, 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 two-person acronym review for this order. One reviewer obtains the Cisco-backed feature expansion; the second compares it with the full PID and target software inventory. Any disagreement leaves the line unapproved rather than resolved by interpreting the code.

Acceptance record for this line

For this exact order line, the accountable reviewer is the service assurance lead. The required evidence package combines the Cisco sales-order line, entitlement notification and target-account receipt; review it during handover. 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.

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.

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.

Audit retention

Store the quote, entitlement notification, Smart Account transaction, activation output and acceptance result under one reference. Keep the exact PID searchable so an auditor can distinguish it from failover and different-capacity variants. Retain machine-readable outputs as well as screenshots. The record should let another engineer prove what was purchased, where it landed and whether it was accepted.

Decommission control

When the related service is retired, remove or reassign the entitlement only through Cisco-supported procedures. Preserve the final license state and migration approval so unused rights are not mistaken for active capacity. Close monitoring and capacity records when a license is retired. Keep the final evidence with the migration project to prevent the same PID from being counted twice.

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-PG10S-K9 software entitlement
• ASR5K-00-ME01BASE software entitlement
• ASR5K-00-PT01R-K9 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