Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Stack member (No Active nor Standby) gets stuck in "initializing" State and never gets "Ready" state when first added to the stack and gets recovered after a power cycle. Then no further stack issues are seen. Another side affect to this is seen if the new switch has a different license than the stack license. In this case, the new switch will hang and also cause the the existing active switch (or switch 1) to go into Initialing state. This requires a full stack reload or power cycle.
+ cat9300 Stack of more than 2 switches. + All new Switches are with factory default settings all numbered as Switch 1. + After power cycling, device is added successfully except if the license mis-match issue exists, a full stack power cycle or reload is required. + No further stack issues seen after power cycling the affected device. + Issue has been seen on IOS XE 16.6.3 & 16.8.1a.
+ Power cycle the unresponsive stack member will bring the device back and joined successfully to the running stack. + If the license mismatch issue is seen you will need to either power cycle or reload the entire stack and bring them all up at the same time.
When stacking cat9300 switches for the first time (No config / All switches numbered as Switch 1), after Active & Standby Switches are elected the 3rd Switch get stuck in "Initializing" and never get "Ready" state and affected switch console is stuck in: ############################################################# Waiting for 120 seconds for other switches to boot Switch is in STRAGGLER mode, waiting for active Switch to boot Active Switch has booted up, starting discovery phase ####################################################################################################################### Switch number is 3 Under the active switch we can see: Switch#sh sw Switch/Stack Mac Address : 501c.b079.7200 - Local Mac Address Mac persistency wait time: Indefinite H/W Current Switch# Role Mac Address Priority Version State ------------------------------------------------------------------------------------- *1 Active 501c.b079.7200 1 V01 Ready 2 Standby 00bf.7715.e900 1 V01 Ready 3 Member f87b.2076.b800 1 V01 Initializing After power cycling, no further issues are seen, Switches can be rebooted and they will join the stack without any issues. So this issue can be reproducible only when adding switches to the stack for the very first time. This issue has been reproduced in 16.6.3. If the license mis-match issue is seen, the following will be seen on the switches... Console of the newly added switch: Waiting for 120 seconds for other switches to boot Switch is in STRAGGLER mode, waiting for active Switch to boot Switch 1 has a license mismatch with the stack. Only on activating a compatible license will the switch join Existing stack, switch 1 goes to initializing state and will eventually reload... Switch# Role Mac Address Priority Version State ------------------------------------------------------------------------------------- *1 Active 70d3.7985.d200 15 V01 Initializing 2 Standby 046c.9d1e.1400 13 V01 Ready 3 Member 046c.9d1e.4a80 11 V01 Ready