MVC (Multi Version Cluster) state reset (off) after upgrade

[Emil_T]

I upgraded a firewall cluster from R81.10 to R82 Jumbo Hotfix Take 103 and I noticed that the MVC state parameter resets after the upgrade. It was ON before upgrade and OFF after it.

Is this expected behavior? In the documentation it appears that the setting should survive upgrade.

Thx

[emmap]

The upgrade documentation states to enable it after the version upgrade has been completed, so that suggests that it's expected behaviour.

[Emil_T]

In the upgrade documentation the procedure states to

1. Enable MVC after upgrade of one member has been completed

2. On each Cluster Member, disable the MVC mechanism

just because by default, MVC state is off.

Actually we can conclude from this that the state does not reset after upgrade, otherwise they would not ask to disable it.

[emmap]

Yes it is, except for any R81.20 JHF take higher than take 14.

[Emil_T]

Sorry, what do you mean by "Yes it is" ?

[emmap]

Yes, it is disabled by default. Just confirming your statement, noting the exception in R81.20 JHF takes.

So you upgrade a member, enable MVC on that upgraded member, upgrade the other member, disable MVC on the one you upgraded. 

[Emil_T]

That's clear. But the question was - does this setting survive upgrade. For example - setting is ON before upgrade - what will be the state after upgrade? 

[emmap]

As a general rule it will be Off (and would also be Off before the upgrade). The exception is R81.20 JHFs, which complicates things, because installing the JHF over R81.20 will enable it. 

[Emil_T]

That's understood. But again, that's not what I'm asking. My question is "does this setting survive upgrade"

[emmap · Accepted solution]

Apologies for being unclear. No it will not survive upgrade.