CISCO ROUTER LIFECYCLE GUIDE
Cisco ASR 1000 Lifecycle and Migration Matrix
A PID-level planning guide for ASR1001, ASR1002, ASR1001-X and ASR1002-X estates moving toward supported Catalyst 8500 edge platforms.
Lifecycle status must be checked at PID level
Cisco lifecycle notices apply to listed part numbers, not every product that contains the words ASR 1000. The original ASR1001 and ASR1002 were replaced by X-generation platforms in an earlier bulletin. Cisco later announced ASR1001-X and ASR1002-X end of sale, with IOS XE 17.9 identified as the last supported release for those products.
| Installed platform or component | Lifecycle evidence | Official replacement direction | Required validation |
|---|---|---|---|
| ASR1001 | Earlier generation; official 2016 bulletin maps chassis and many bundles to ASR1001-X. | Do not stop at the historical X replacement; the X platform now has its own lifecycle deadline. | Record IDC, license, crypto, power and interface dependencies. |
| ASR1002 | Earlier generation; official bundle notices map multiple ASR1002 PIDs to ASR1002-X. | Re-evaluate against the current Catalyst 8500 direction rather than buying an expired intermediate target. | Record ESP, SIP, SPA, VPN and service requirements. |
| ASR1001-X | End of sale August 1, 2022; last support July 31, 2027; last supported IOS XE 17.9. | C8500L-8S4X for the base chassis PIDs in Cisco's bulletin. | Compare 1G/10G media, throughput license, features and operational model. |
| ASR1002-X | Same bulletin milestones and IOS XE boundary as ASR1001-X. | C8500-12X or C8500L-8S4X for specified base PIDs. | Do not assume one target fits every ASR1002-X bundle or SPA dependency. |
| RP1 / SIP10 / ESP5 / ESP10 | Listed in earlier component-level notices with exact successor PIDs where available. | Examples include RP2, SIP40 and higher ESP classes, but chassis support must also be checked. | A component replacement is not a chassis lifecycle extension. |
Read Cisco replacement rows as a starting point
Cisco maps the ASR1001-X chassis to C8500L-8S4X. For ASR1002-X, the bulletin lists C8500-12X and C8500L-8S4X for specific chassis PIDs. These are migration options, not guarantees of feature, port, scale or configuration equivalence.
C8500L-8S4X path
Start here for designs compatible with eight 1GbE SFP and four 10GbE SFP+ interfaces, then validate service scale and software.
C8500-12X path
Evaluate where ASR1002-X workload, port design or scale requires the larger Catalyst 8500 option named in the bulletin.
Retain only with a dated exit
Existing supported equipment may remain temporarily, but the July 31, 2027 last-support date must be in the funded migration schedule.
Throughput and service licenses are migration inputs
The ASR1001-X integrated ESP can be software-activated from 2.5Gbps up to 20Gbps. ASR1002-X starts at 5Gbps and can be activated to 10, 20 or 36Gbps. Cisco's lifecycle bulletin separately lists performance, IPsec, built-in 10GE and technology-package PIDs.
A chassis label therefore does not reveal the production entitlement. Capture license state, enabled throughput, IPsec capacity, CUBE, broadband, AVC, firewall and SD-WAN functions before comparing a target platform.
- Exact chassis PID, serial number, memory and power configuration.
- ESP, RP, SIP, SPA and line-card inventory where modular.
- Activated throughput and crypto licenses.
- IOS XE release, ROMMON, packages and feature use.
- Peak forwarding, IPsec, session, route, QoS and telemetry load.
Build a physical and logical dependency map
| Dependency | Why it blocks a blind replacement | Migration evidence |
|---|---|---|
| Ports and optics | Built-in GE, 10GE licenses, SPAs and media may not map one-for-one. | Interface inventory with speed, optic PID, reach and peer. |
| Routing | Route scale, convergence and policy behavior must remain within the target design. | RIB/FIB scale, protocols, BFD, VRF and policy inventory. |
| Services | NAT, IPsec, CUBE, firewall, broadband and QoS can drive platform choice. | Feature matrix with measured scale and required licenses. |
| Operations | Management, telemetry, automation and software lifecycle change with platform. | NMS, AAA, logging, NETCONF/RESTCONF and upgrade-process tests. |
Migration checklist
- Normalize PIDs: separate chassis, bundle, spare, license and module part numbers.
- Confirm lifecycle: match each installed PID to Cisco's current EOL listing.
- Measure: collect forwarding, crypto, sessions, routes, QoS and interface utilization.
- Map services: document every feature and entitlement that must survive the move.
- Select target: use the Cisco migration row, then validate the candidate data sheet and software support.
- Lab: test configuration translation, routing convergence, VPN, QoS, telemetry and failure scenarios.
- Cut over: define acceptance criteria, maintenance window and rollback with both platforms available.
Related product records
Use the exact PID pages to distinguish chassis and successor options during bill-of-material review.
Official manufacturer sources
- Cisco ASR 1000 end-of-life notice index
- ASR1001-X and ASR1002-X lifecycle bulletin
- ASR1001, ASR1002 and component lifecycle bulletin
- Cisco ASR 1000 Series data sheet
- Cisco ASR 1000 ordering guide
This independent lifecycle guide is not a Cisco publication and does not claim partner authorization. Cisco bulletins can be revised; verify every PID, date, software release and migration option before procurement.