CSM 4.2(10) Config Sync Status Delay

Unanswered Question
Oct 10th, 2008

With the latest CSM 4.2(10) code I've noticed that after initiating a config sync from the active CSM it takes approximately 30 secs for the standby CSM to register the configuration download status as 'PENDING'. CSM code prior to 4.2(10) would register the status instantaneously. The risk with this is anyone who isn't aware of this delay could potentially 'write mem' too soon and risk saving a partial config to the standby CSM. I've actually seen this happen where a big chunk of the standby CSM config was missing because 'show mod csm 1 status' was not used before doing 'write mem'. Is this delay with 4.2(10) code normal behavior?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
sachinga.hcl Mon, 10/13/2008 - 12:28

Hi Long,

Which version of IOS you are using on your switch. Use IOS Release 12.2(18).

A configuration synchronization check for the active and standby CSMs may fail for configurations that contain the following subcommands: script, ARP, variable, match, failaction, NAT client, probe, domain, and url-hash. When you use these subcommands, and then you change configurations only in the active or the standby CSM, the wrong configuration synchronization state might be displayed. The module might incorrectly display synchronized configurations as "out-of-sync," and configurations that are out of synchronization as synchronized.

Resolved in Cisco IOS Release 12.2(18).


Sachin Garg

lbhoang Thu, 10/16/2008 - 09:56

I appreciate the info but we're using 12.2(18)SXF train.

Just to follow-up on the issue the config sync feature is sort of unpredictable with CSM code 4.2(10). I've had one instance where a config sync was initiated but it never actually occurred. A subsequent config sync did occur after the previously reported ~30 sec delay.

stephendrkw Thu, 10/30/2008 - 09:53

If you haven't already 'show mod csm 3 tech-support ft' will give you some interesting stuff like LRP and HA errors. Sniff the ft vlan, issue a sync command and see if you can see anything.

Also what are the logs saying when the problem occurs?


This Discussion