CISCO ASR5K-00-IG01BDC ASR 5000 Software License

ASR5K-00-IG01BDC Software Entitlement Identity

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

Prepare an operational handover specific to the confirmed license function. Include owner, dashboards, alarm route, support contact, evidence location and migration note. Handover is incomplete if only the procurement team can locate the entitlement record.

Acceptance record for this line

For this exact order line, the accountable reviewer is the telecom procurement reviewer. The required evidence package combines the software-release evidence, prerequisite checklist and controlled activation result; review it at the migration gate. If any identifier, account destination, platform scope or capacity statement conflicts, quarantine the entitlement and return the line to procurement reconciliation. 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.

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.

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

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-IG10BDC software entitlement
• ASR5K-00-CS01CSFB software entitlement
• ASR5K-00-SN01FLEX 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