SMS upgrade keep managing gateways

[Jesus_Cano]

Hi,

Im upgrading a SMS in VM on friday. Im still thinkg to do the advanced upgrade from CPUS, or the fresh install from CPUSE. I think it will be easie just the upgrade so thats why i prefer that. Any diference doing upgrade to fresh install?? any known issues?

on the another hand, the SMS will be have the R80.10. So this SMS can manage gateways in R77.20? what happen if i install policy in R80 to gateways in R77.20? it will work?

thanks

[PhoneBoy]

In this case you should do a fresh install of R80.20 and migrant export/import.

This will allow you to leverage the xfs filesystem added in this release.

R80.20 Management can manage gateways from R75.20 and above.

[Jesus_Cano]

We are going to R80.10. So, i understand that its more recomendable to do fresh install, right? To clean all.

i wanted to do a upgrade CPUSE for an easy way.

thanks

[PhoneBoy]

R80.10 does not have the new filesystem, so it's really up to you.

That said, it is a good idea to confirm the migration will be successful by doing a clean install + migrate export/import.

You can do a CPUSE upgrade when you do the real migration if you prefer.

[Maarten_Sjouw]

Compatibility goes back even further, although it is not supported. The backward compatibility files for R65 and R71 are also still on the management server.

[PhoneBoy]

I've pushed policy to an R65 gateway from R80.10 Management, so it works

BUT...only if the management server was upgraded from R77.x.

This is because the Internal CA on R80+ Management is signed with SHA2.

R71 is the first version that supports SHA2 hashes for the Internal CA.

Of course, all of the above is merely for trivia.