Hi guys,
as the header briefly describes I encountered a strange behaviour today while upgrading our vsx cluster from r81.10 to r81.20.
I wanted to go with the mvc upgrade path but after I installed the first of 2 nodes the upgraded node came back up directly into the cluster.
Turned out that mvc was directly turned to state "on".
At first I assumed that we missed to turn off the mvc after the last updates but when the second node came back up after upgrade with also mvc turned on it must have happend during upgrade/reboot?
I can say a 100% that mvc was disabled before the upgrade and it wasnt touched from no one in between.
Any experiences with cases like that?
This was just the first of 3 cluster to update like this and the next 2 will be way more critical and are not allowed to have any bigger outtimes. As well the operate about 10 vs per cluster which need to be in a healthy state...
Thank you for any thoughts!
