Recently we have had problems syncing between our pair of redundant CSM's.
Here is the behavior we observe when we run the command on one of our 6500.
! config 6500-2
module ContentSwitchingModule 2
ft group 1 vlan 4
priority 10 alt 20
! config 6500-1
module ContentSwitchingModule 2
ft group 1 vlan 4
6500-2#hw-module csm 2 standby config-sync
After we run this command on 6500-2 the log shows that the sync happens and the CSM config is deleted on 6500-1 and then nothing happens.
Here is the exact logout on each of the 6500.
6500-2(ACTIVE)
May 28 17:45:11.353 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Bulk sync started
May 28 17:45:11.369 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Sending configurations to Standby CSM, this may take several minutes!
May 28 17:45:12.749 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Sending configuration to Standby CSM
May 28 17:45:14.869 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Sending configuration to Standby CSM
May 28 17:45:24.345 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Manual bulk sync completed
May 28 17:45:24.349 est: %CSM_SLB-4-REDUNDANCY_WARN: Module 2 FT warning: Config Sync does not save Standby running-config to startup-config
6500-1(STANDBY)
May 28 17:45:17.088 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Started clearing configuration
May 28 17:45:17.088 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Completed clearing configuration
May 28 17:45:17.096 est: %CSM_SLB-4-REDUNDANCY_WARN: Module 2 FT warning: Standby: Config Sync does not save running-config to startup-config
May 28 17:45:17.100 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Previous configuration are being deleted from supervisor
May 28 17:45:17.104 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Previous configuration being deleted on Standby CSM
May 28 17:45:17.104 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: New configuration are being configured
As you can see the configuration ends up being deleted from the STANDBY and the new configuration never gets configured to 6500-1(STANDBY).
We have tried replacing the SUP engine however this did not help. We will try to replace the CSM next. If anyone can shed some light on why this would happen I would apreciate it.
