CISCO ASR5K-RCC-K9 ASR 5000 Series

ASR5K-RCC-K9 Redundancy Role

ASR5K-RCC-K9 is the Redundancy Crossbar Card for the Cisco ASR 5000. Its purpose is not packet processing or system management by itself: Cisco's card-mapping documentation describes the RCC as creating a path from a standby processing card to line cards when functions migrate away from the directly associated processing card.

Path and slot planning

Document the installed RCC slots and the line-card ranges served by each crossbar. Cisco `show card mappings` output identifies mappings such as RCC 40 or RCC 41 when a line card communicates with a processing card that is not directly in front of it. Compare that live topology with the chassis redundancy design before replacing or adding a card.

Failure-domain validation

Determine which processing-card and line-card relationships depend on each RCC. Review card operational state, single-point-of-failure indication, alarms and historical failover events. A healthy inventory entry is insufficient if a migrated service cannot reach its line card through the alternate crossbar path.

Controlled redundancy test

Before maintenance, save card inventory, mappings, alarms and service health. After insertion, verify PID/version/serial, card usability and the expected crossbar mappings. Exercise an approved processing-card failover, confirm that the relevant line cards remain reachable, inspect counters and alarms, and restore the intended active/standby state.

Spare and revision control

For legacy stock, record hardware revision, provenance and mechanical condition. Keep replacement scope aligned to the existing chassis and StarOS release, and preserve a known-good spare only after a successful redundancy test. Similar physical dimensions do not make an SPIO, SMC or line card an RCC substitute.

Lifecycle boundary

Cisco lists ASR5K-RCC-K9 in the end-of-sale/end-of-life announcement for the ASR 5000. This item is one redundancy crossbar card and does not include processing cards, line cards, an SMC, an SPIO, chassis software, support entitlement or migration services.

Official Cisco evidence: RCC path and card-mapping behavior, RCC component and reliability reference and Exact RCC PID lifecycle record.