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?