Hi Magnus, thanks for the video. I'm running my large MDS environment for a few month now with the R81.20 without any Problems. I upgraded from R80.40 to R81.20. It works just perfectly. The CPMDoc script shows a few warns. I solfed most of them and after that the installer did his job very handsome. Now I will upgrade the Security Gateways with the CDT from R80.40 to R81.20.
Nice, am supriced how many seam to have kept there mgmt on R80.40 because R81.10 for mds and such has worked perfectly the last year or so. I think we will see alot of ppl upgrading the next couple of weeks so personally i will wait 1-2 more recommended JFA before i upgrade gateways, :)
Many thanx for this video! Now I feel more confident as I have to upgrade AWS MDS from R80.40 to R81.20 and I was waiting for a recommended stable release!
Your welcome :) Am currently running my MDS on R81.10 and it has been working out great. First real MDS production boxes being upgraded to R81.20 in a few days. In large enviroment going to r81.10 from R80.40 speed up the process working with VSX ALOT (task such as adding interface / routes etc on VSX:s) But same here, i have been holding off upgrading untill i did see it was recommended, especially during summer period. /Magnus
Hello, Magnus. One doubt, if I am on a version R80.40, and I need to go to R81.20, I have to necessarily "jump" to previous versions like R81, R81.10? Or can I go straight to R81.20? Using the CPUSE UPGRADE method, of course. Cheers. :)
Hi, You can go directly to R81.20. Just make sure to upgrade the CPUSE version :) CPUSE will tell you if an upgrade is supported or not, but oyu can always check the upgrade wizard. supportcenter.us.checkpoint.com/supportcenter/portal?eventSubmit_doShowupgradewizard Regards, Magnus
Hi Mr. Magnus. Blessed Good day to you. I just upgraded my R81.10 SMS and Clustered Gateways however the cluster is not working. I got error with my cluster as indicated that the version of the object does not match the version of the install software. Really need help how to resolve this. Will delete and add new cluster help and re-attached the license? I will actually upgrade soon my production devices and I am afraid same issue will persist. What advice procedure I need to take? Appreciate your helpful and positive response.
When upgrading a cluster to a new version, you do need to change it to the correct version in the smartconsole so it’s match what’s installed and then install the policy.
Hi Magnus, thanks for the video. I'm running my large MDS environment for a few month now with the R81.20 without any Problems. I upgraded from R80.40 to R81.20. It works just perfectly. The CPMDoc script shows a few warns. I solfed most of them and after that the installer did his job very handsome. Now I will upgrade the Security Gateways with the CDT from R80.40 to R81.20.
Nice, am supriced how many seam to have kept there mgmt on R80.40 because R81.10 for mds and such has worked perfectly the last year or so.
I think we will see alot of ppl upgrading the next couple of weeks so personally i will wait 1-2 more recommended JFA before i upgrade gateways, :)
Please let me know how the CDT works for you on that version, i think CP is mostly pushing the smartconsole upgrade path instead of CDT
@@MagnusHolmberg-NetSec Can share to us the links for upgrade from R81 to R81.20 SMS and VSX.
Many thanx for this video! Now I feel more confident as I have to upgrade AWS MDS from R80.40 to R81.20 and I was waiting for a recommended stable release!
Your welcome :)
Am currently running my MDS on R81.10 and it has been working out great.
First real MDS production boxes being upgraded to R81.20 in a few days.
In large enviroment going to r81.10 from R80.40 speed up the process working with VSX ALOT (task such as adding interface / routes etc on VSX:s)
But same here, i have been holding off upgrading untill i did see it was recommended, especially during summer period.
/Magnus
Hello, Magnus.
One doubt, if I am on a version R80.40, and I need to go to R81.20, I have to necessarily "jump" to previous versions like R81, R81.10? Or can I go straight to R81.20?
Using the CPUSE UPGRADE method, of course.
Cheers. :)
Hi,
You can go directly to R81.20. Just make sure to upgrade the CPUSE version :)
CPUSE will tell you if an upgrade is supported or not, but oyu can always check the upgrade wizard.
supportcenter.us.checkpoint.com/supportcenter/portal?eventSubmit_doShowupgradewizard
Regards,
Magnus
Hi Mr. Magnus. Blessed Good day to you. I just upgraded my R81.10 SMS and Clustered Gateways however the cluster is not working. I got error with my cluster as indicated that the version of the object does not match the version of the install software. Really need help how to resolve this. Will delete and add new cluster help and re-attached the license? I will actually upgrade soon my production devices and I am afraid same issue will persist. What advice procedure I need to take? Appreciate your helpful and positive response.
When upgrading a cluster to a new version, you do need to change it to the correct version in the smartconsole so it’s match what’s installed and then install the policy.