Recovering from a Stack Unit Configuration Mismatch
When a configuration mismatch occurs, the active controller logs and displays a configuration mismatch message and puts the mismatched unit into a non-operational state. In the following example, the original stack unit 2 has failed, and a replacement unit has been installed that does not match the configuration of the original unit. You should see the following message.
Warning! put stack unit 2 to non-operational reason= config mismatch
Complete the following steps to recover from a configuration mismatch.
- Enter the
show stackcommand to see the status of the stack, and theshow running-configcommand to see the configurations of the stack units.ICX7850-32Q Router# show stack T=12m52.2: alone: standalone, D: dynamic cfg, S: static ID Type Role Mac Address Pri State Comment 1 S ICX7850-32Q active d4c1.9e18.3731 128 local Ready 2 S ICX7850-48FS standby d4c1.9e18.8dd9 0 remote NON-OP: config mismatch ICX7850-32Q Router# show running-config Current configuration: ! ver 09.0.00 ! stack unit 1 module 1 icx7850-32q-port-management-module module 2 icx7800-100g-12port-1200g-module module 3 icx7800-100g-8port-800g-module priority 128 stack-trunk ethernet 1/3/1 to 1/3/8 stack unit 2 module 1 icx7850-48fs-port-management-module module 2 icx7800-100g-8port-800g-module stack-trunk ethernet 2/2/1 to 2/2/8 stack enable stack mac d4c1.9e18.3731 ! !
- To resolve the mismatch, you must
remove the configuration for stack unit 2. Use the
no stack unitcommand in configuration mode.This removes configuration related to unit 2.
If you are unable to remove the configuration because of a multi-slot trunk configuration or other configuration identified by system output, you must first manually remove the problem configuration.
When you have successfully deleted the mismatched stack unit, a re-election is triggered, and the active controller learns the correct module configuration from the standby controller or from other stack members. No reload is required.