I will verify on the second member if it thinks it's active as well.
VSF member priority – default value is 128; configurable; Member priority determines the possibility of a member device to be elected the Commander. A member with higher priority is more likely to be elected the Commander.
-> What determines the commander role election? Is it based on MAC address if prio is the same? I see the term "more likely" used, which doesn't give me much confidence that it will become commander even if i give it a higher priority. If VSF member 1 with prio 255 goes down, VSF member 2 with prio 128 takes over. Will VSF member 1 take the Commander role again once it returns back online due to prio 255? Will in turn, unit 2 be rebooted again since it became the Standby again?
My scenario would be replacing the L3/SVI functionality of the current 5400zl switches running VRRP, with the single VSF chassis. The firewalls and WAN connectivity are connected on both switches at this moment.
I will look into the MAD configuration.
Is there a good documentation/drawing, of how traffic flows from a distribution switch for example, connected to a VSF core? When the distribution switch is stacked and has one logical port channel connecting to the cores. Will it load balance traffic on both physical links to the core, or?