ASR5K-00-CS01NAT - Cisco NAT 1K Sessions

ASR5K-00-CS01NAT Software Entitlement Identity

ASR5K-00-CS01NAT 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 NAT 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

Create a procurement freeze rule for unresolved descriptions. If Cisco-backed documents do not repeat the complete PID and function, stop the line before approval. A search-result snippet or distributor title cannot be elevated into authoritative technical evidence.

Acceptance record for this line

For this exact order line, the accountable reviewer is the Smart Account custodian. The required evidence package combines the software-release evidence, prerequisite checklist and controlled activation result; review it before activation. If any identifier, account destination, platform scope or capacity statement conflicts, freeze further rollout until capacity and lifecycle evidence are corrected. 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.

Smart Account ownership

Name the Smart Account, virtual account and administrator responsible for registration or transfer. Confirm that the party placing the order can deliver the entitlement into the account used by the target deployment. Test account ownership before the purchase window closes. Include a recovery contact so licensing work is not blocked by a single administrator or an obsolete partner relationship.

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.

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.

Operational ownership

Assign an owner for license alarms, capacity consumption, renewal or migration dates and Smart Licensing communication. Add the exact PID to the configuration inventory so later audits do not rely on a generic router asset record. Define alert thresholds and review frequency. Close stale or duplicate entitlements so the inventory reflects what the platform can actually use.

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