I am using VSS configuration on a pair of 6509s with IOS 12.2(33)SXI3. After VSL link goes down the standby chassis sucessfully detects the complete VSL failure and initiates SSO correctly. This causes a dual-active scenario and the former active chassis shuts down its ports (recovery action). During the time VSL is still not operational if the current active (previous standby) chassis fails this is not detected by the chassis in recovery mode and this results a complete failure of both of the chassis. My question is: Is this an expected behaviour and how (if possible) can I configure the chassis in recovery mode to reload automatically and assume the standby role so at least one chassis from VSS is functional in case of power outage for example?
My suggestion is to exclude the MEC port channel interfaces (connected to access layer switches and used by Enhanced PAgP) from the automatic shutdown in case of recovery scenario, but I am afraid this could cause some other undesired effect (like spanning tree loop or some other L2 problem). I am not sure if this will help, but I expect VSS chassis in recovery mode to detect the active chassis failure and take some action to become active in turn.
Additional info: If the VSL link is operational again, the chassis in recovery mode detects that and reloads automatically. Also, I am not making any config changes on the chassis in recovery mode.
Definetely BFD will help me with dual-active detection, but I think this detection is working fine now with Enhanced PAgP. As I have mentioned previously, the former active chassis is correctly entering recovery mode, but it is not auto reloaded to take the standby role if the VSL is not up again.
Do you think that BFD will solve this scenario or it is a known issue?
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...