SSA: VSB member change not sync config to replaced unit

[Volker_Kull]

SSA: VSB member change not sync config to replaced unit Using the kb:14688 the VSB replace procedure does not copy the existing configuration of the replaced VSB member. VSB is up and working. Using the stored config at local flash ends with error because of wrong chassis ID. Looking at B/C-Series we had no problems changing a stack member and have back the whole configuration of the replaced units. Having a much more featured SSA/S-series I expect that this function is implemented and working.

[Anonymous]

Dear Volker, Thank you for bringing this issue to our attention. In reviewing the KB article you referenced and verifying this in the lab we discovered that there is a step missing that is critical to getting the configuration on the replacement system. As you mentioned you tried using the configure command but received an error in doing so. When using the configure command you must use the chassis-id option, specifying the replacement chassis id. For example, if SSA 2 failed in a VSB pair, after following the other steps in the KB document you would also run the configure command 'configure slotx/filename.cfg chassis-id 2' This reloads the configuration and tells the remaining unit to push the configuration file to the replacement unit. We will update the current document with this information and post it to the community in our FAQ section this week.

[Tamera_Rousseau]

Hi Volker. I know the GTAC group was testing this in the lab yesterday, so they will update you shortly.