Preview Tool

Cisco Bug: CSCvu76555 - Standby not NSR-ready due to te_control Standby not connected on ASR9K-eXR 731 12i after RPFO

Last Modified

Sep 16, 2020

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases


Description (partial)


1. Router is not NSR ready with te_control complains Standby not connected. 
RP/0/RP1/CPU0:router#show redundancy

Redundancy information for node 0/RP1/CPU0:


Node 0/RP1/CPU0 is in ACTIVE role

Partner node (0/RP0/CPU0) is in STANDBY role

Standby node in 0/RP0/CPU0 is ready

Standby node in 0/RP0/CPU0 is not NSR-ready



Current active rmf state: 4 (I_READY)

All standby not-ready bits clear - standby should be ready

Current active rmf state for NSR: Not ready

<jid>       <node>       <name> Reason for standby not NSR-ready

1086   0/RP1/CPU0   te_control Standby not connected

2. show mpls traffic-eng proc-fsm indicates Perf Meas collaborator is not connected.
3. show performance-measurement proc-fsm location <ACTIVE_RP_LOCATION> output is missing TE collaborator.
4. show performance-measurement proc-fsm location <ACTIVE_RP_LOCATION> missing Role Change End time.

Perf-Meas Process FSM
Current process role : Primary Active (Master)
Current process state: Run

Process Role Change Status:
Role Change Triggered : Tue Jul 14 16:16:43 PDT 2020 (19:15:17 ago)
Role Change Start : Tue Jul 14 16:16:43 PDT 2020 (19:15:17 ago)
Role Change End : No

5. show processes perf_meas waipc service location <ACTIVE_RP_LOCATION> shows pm_services_api is still in Standby Role
RP/0/RP1/CPU0:router#show processes perf_meas waipc service location <ACTIVE_RP_LOCATION>
Mon Jul 20 12:33:26.071 PDT
Process name : perf_meas
LIB initialized : Mon Jul 20 08:46:10 2020 (03:47:16 ago)
Local NODE ID : 32 (node0_RP0_CPU0)
Local ISSU ID : 0

Service/Group Type HA Role ISSU Role
pm_services_api Publisher Standby Primary

Platform independent.

Minimum configuration:
mpls traffic-eng

Intermittent issue triggered by RPFO.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.