Preview Tool

Cisco Bug: CSCuq05728 - RSP FO in cluster system with Scale config leads to sync failures

Last Modified

Aug 07, 2018

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases


Description (partial)

After RPFO in an ASR9k cluster system, NSR is not ready state due to sysdb config and data replication not complete.

1) This issue is seen when RSP failover  is triggered in an ASR9k cluster system with scaled configuration of 450k+ lines of config. 
2) The failure to sync happens on a cluster system when the ACTIVE RSP and ACTIVE  SWITCH (switch  being used for the front panel sfp+ ports) are not on the same RSP card.
3) Most common scenario : SFP+ links on RSP0 are given higher priority. So assuming ACTIVE RSP of Primary DSC is 0/RSP0/CPU0 or 1/RSP0/CPU0, and on next RPFO when ACTIVE RSP of Primary DSC is 0/RSP1/CPU0 OR 1/RSP1/CPU0 you are most likely to see the issue.

Example of this case :  0/RP1/CPU0 is the ACTIVE RSP and 0/RP0/CPU0 is the ACTIVE SWITCH

RP/0/RP1/CPU0:GOT-PE1#admin show dsc                     
           Node  (     Seq)     Role       Serial State
     0/RP0/CPU0  (  409267)  STANDBY  FOX1746GJ08 NON-DSC
     0/RP1/CPU0  (       0)   ACTIVE  FOX1746GJ08 PRIMARY-DSC <--------------------
     1/RP0/CPU0  (  387405)  STANDBY  FOX1740G1AE NON-DSC
     1/RP1/CPU0  (  468594)   ACTIVE  FOX1740G1AE BACKUP-DSC

RP/1/RP0/CPU0:GopaTB#sh nv edge control control-link-protocols location 0/RP0/CPU0 | begin Prio
Priority lPort             Remote_lPort      UDLD STP
======== =====             ============      ==== ========
0        0/RP0/CPU0/0     1/RP0/CPU0/0     UP   Forwarding <---------------------
1        0/RP0/CPU0/1     1/RP1/CPU0/1     UP   Blocking  
2        0/RP1/CPU0/0     1/RP1/CPU0/0     UP   On Partner RSP
3        0/RP1/CPU0/1     1/RP0/CPU0/1     UP   On Partner RSP
Active Priority is 0
Active switch is   RP0 <----------------------------------------------------------------------
CLM Table version is 20
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.