CISCO ASR5K-00-ME01BASE ASR 5000 Software License

ASR5K-00-ME01BASE Software Entitlement Identity

ASR5K-00-ME01BASE 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

Use a quote-to-entitlement reconciliation sheet for this line. The sheet should show the requested PID, Cisco sales-order PID, delivered entitlement identifier, destination account and approving engineer. A clean commercial invoice without matching entitlement evidence is not sufficient acceptance.

Acceptance record for this line

For this exact order line, the accountable reviewer is the core licensing administrator. The required evidence package combines the Cisco sales-order line, entitlement notification and target-account receipt; review it before quote approval. If any identifier, account destination, platform scope or capacity statement conflicts, cancel the change window and restore the recorded license baseline. 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.

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.

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.

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-PW01REC software entitlement
• ASR5K-00-PTXXPIF software entitlement
• ASR5K-00-PW10GTWY 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