topic Re: Catalyst 9800-40 Standby initialization (cold-bulk) in Wireless

Catalyst 9800-40 Standby initialization (cold-bulk)

Macarena — Mon, 05 Jul 2021 19:40:25 GMT

Hi Community,

Last saturday we upgraded the IOS-XE version of our C9800-40 (x2) and the standby one is in initialization state still:

ESGSDC-WLC#sh redundan state
my state = 13 -ACTIVE
peer state = in progress to standby cold-bulk
Mode = Duplex
Unit = Primary
Unit ID = 2

Redundancy Mode (Operational) = sso
Redundancy Mode (Configured) = sso
Redundancy State = sso
Maintenance Mode = Disabled
Manual Swact = disabled (peer unit not yet in terminal standby state)
Communications = Up

client count = 146
client_notification_TMR = 30000 milliseconds
RF debug mask = 0x0

Current client in progression = BINOS_BULKSYNC_CLIENT (33010)
Time since client was sent progression (ms) = 2245569
History for this client progression = RF_PROG_STANDBY_BULK, rc 0

ESGSDC-WLC#

We do not know why it has not yet synchronized and we have not found information on the Cisco website to help us.

Could you tell us the reason why the standby has not synchronized or how we can force it? We need to configure some additional parameters and right now we can't:

ESGSDC-WLC#conf t
Config mode cannot be entered during Standby initialization or when switch is in recovery mode

Thank you in advance.
Regards.

Re: Catalyst 9800-40 Standby initialization (cold-bulk)

balaji.bandi — Tue, 20 Oct 2020 11:57:16 GMT

Looks like part of the upgrade it was freezed, how about other device - works as expected.

since it was occured during the upgrade, suggest contact TAC so they assits better.

Re: Catalyst 9800-40 Standby initialization (cold-bulk)

jasonm002 — Mon, 16 Jun 2025 18:40:02 GMT

Just so other people find this solution when searching:

use the following commands to see if there might be any configuration elements it's getting stuck on and remove the offending configuration, it should sync after that:

show redundancy config-sync failures bem
show redundancy config-sync failures mcl
show redundancy config-sync failures prc
show redundancy config-sync failures historic mcl

In my case I had a WLAN with an invalid configuration in 17.15.x which was valid in 17.12.x, the PRC config sync-failure list got stuck on "no shutdown" because it threw a parser error when it tried to issue "no shutdown", quick workaround was to just shut the WLAN profile down, then config-sync worked.

Also if it's failing to complete the config sync, it will reload after a few minutes throwing the pair back into simplex mode, then you can change the config again.