ASR5K-00-ME10LIC - Cisco MME Bundle, 10K sessions

ASR5K-00-ME10LIC Software Entitlement Identity

ASR5K-00-ME10LIC 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 MME Bundle, 10K 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 10K capacity unit. Do not extend that statement to a different ASR5K, ASR55 or LIF5K code.

PID-specific procurement case

Use a release-upgrade impact assessment for this entitlement. Compare pre-upgrade and post-upgrade license behavior using Cisco documentation and controlled output. Do not assume a valid authorization remains usable across every StarOS release.

Acceptance record for this line

For this exact order line, the accountable reviewer is the configuration audit owner. The required evidence package combines the support-contract mapping, entitlement identifier and escalation contact; review it before activation. If any identifier, account destination, platform scope or capacity statement conflicts, hold payment acceptance until the exact PID and destination account agree. 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.

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.

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 evidence

Review Cisco's current product notice and support documentation on the decision date. Record the exact PID match; do not apply an end-of-sale date from a related code when the exact order line is absent from the notice. Capture the notice revision date and whether the exact PID is present. If it is absent, document that lifecycle remains quote-verified rather than importing a date from another product.

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-SN01REC software entitlement
• ASR5K-00-GN10HMAG software entitlement
• ASR5K-00-CS01LASR 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