Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Below 3 key symptoms were observed post occurrence of the issue, however, the bug can cause portions of a configuration to disappear. - The controller going back to day 0 config post a switchover to the standby chassis 0. The cause of the switchover is irrelevant. - The controller will have its platform independent IOS-XE configuration intact like ip addresses, vlans, aaa configs etc. but will have lost its wireless and telemetry specific configuration - Inability to apply any wireless configuration. Doing so gives the below error. Country XX is unsupported. Please configure supported country code
9800 in HA-SSO
You can proactively monitor for one or more of the symptoms below: 1. repm will have high CPU usage: show processes cpu platform | include repm Pid PPid 5Sec 1Min 5Min Status Size Name -------------------------------------------------------------------------------- 17795 17785 83% 89% 89% S 910372 repm 2. Monitor the flap count field of the below command: show platform software replication chassis st R0 peer details 3. Monitor the Standby and Active chassis' running-configs for parity. - Active: "show running-config" - Standby: SSH to the RMI ip address of the standby controller and issue "show running-config" If you have one or more of the above symptoms, you can do the below to recover: * Delete the persistent binary config file from both Active and Standby. All commands are issued in the Active WLC: delete /force /recursive bootflash:.dbpersist/persistent-config.tar.gz delete /force /recursive bootflash:.dbpersist/persistent-config.meta delete /force /recursive stby-bootflash:.dbpersist/persistent-config.tar.gz delete /force /recursive stby-bootflash:.dbpersist/persistent-config.meta * Reload the whole stack(Active and Standby together): reload -> This steps will cause a downtime for a few minutes until the Active controller reloads and comes back.
If you run into the high repm cpu. Do the below to recover: 1. Delete the persistent binary config file from both Active and Standby: delete /force /recursive bootflash:.dbpersist/persistent-config.tar.gz delete /force /recursive bootflash:.dbpersist/persistent-config.meta 2. Reload the whole stack(Active and Standby together): reload -> This steps will cause a downtime for a few minutes until the Active controller reloads and comes back. 3. Install SMU for hot-fix. Available for 17.9.5 & 17.12.3 For other software versions, contact TAC.