LearnNetwork
Cisco ASR family

Cisco ASR — the IOS XE and IOS XR provider edges

10 min

ASR = Aggregation Services Router. Cisco uses the name across two very different platform families that both fit similar roles in operator and large-enterprise networks. Know which family you're working on — the OS, CLI, and configuration model differ.

The two families

| | ASR 1000 | ASR 9000 | |---|---|---| | OS | IOS XE (modular IOS on Linux) | IOS XR (microkernel-based, BSD-derived) | | Typical role | Enterprise WAN aggregator, smaller ISP edge | Operator PE, large ISP core/edge, multi-Tbps | | CLI feel | Mostly classic IOS, with some modern syntax | Different — commit-based, more like Junos | | Form factors | RP1/RP2/RP3, 4/6/9 slot | 9001 (2 RU compact) up to 9922 (44-slot) | | Where you meet it | Branch-to-region, cloud-on-ramps, mid-tier ISP | Tier-1 carrier, hyperscale, large enterprise core |

The 7750 SR-a8 we just covered is roughly equivalent to the ASR 9001 / 9006 in market positioning.

ASR 1000 / IOS XE

IOS XE is a modular evolution of classic IOS — same show ip route, enable, configure terminal muscle memory, but the platform underneath is a Linux kernel with Cisco services running as processes. ZTP, REST APIs, NETCONF/YANG, Python on-box — modern enterprise OS hidden behind the familiar CLI.

A typical config block looks like:

Cisco IOSASR 1000 IOS XE — interface + OSPF
[object Object],[object Object]

Strengths: high throughput per platform-RU, modular ESPs (Embedded Services Processors) for crypto/services scale, mature feature set, familiar to anyone who's used Cisco for years.

ASR 9000 / IOS XR

IOS XR is a different beast. Configuration is transactional: you stage changes, then commit them (or rollback). Like Nokia SR OS or Juniper Junos. Show commands also differ a bit.

Cisco IOS XRASR 9000 IOS XR — interface + OSPF, commit-style
[object Object],[object Object]

Strengths: extreme scale (full internet table, line-rate at 100/400G), separate route processors and forwarding ASICs, modular control-plane processes that can restart without dropping traffic.

Working between the families

Operators frequently run both: ASR 1000 at branch / regional aggregation, ASR 9000 at the core / PE. Migration scripts, automation, and even RANCID-style backups have to know which family they're talking to — the CLI grammar diverges enough that single-script automation breaks if you assume IOS-only syntax.

Cisco's modern direction is Cisco 8000 for the highest-end (replacing the largest ASR 9000s) and various converging IOS XR variants. ASR 1000 / IOS XE remains the enterprise/mid-tier workhorse.

What to remember

  • ASR 1000 = IOS XE = modular IOS on Linux. Enterprise/mid-tier. Classic IOS feel.
  • ASR 9000 = IOS XR = transactional, commit-based, BSD-derived microkernel. Operator/core. Different CLI feel.
  • Both share Cisco "service provider" feature sets: MPLS, BGP scale, segment routing, MACsec.
  • When automating, branch by show version family — the syntax differs enough to break naive scripts.