topic Re: Cloudguard Upgrade in NSX-T from R80.30 to R81 in Cloud Firewall

Cloudguard Upgrade in NSX-T from R80.30 to R81

Sanjay_S — Tue, 20 Sep 2022 09:19:35 GMT

Hi All,

We have planned Cloudguard upgrade on Friday. I am following the below document for the upgrade.

Could you please help me confirm the below steps as i am bit confused on these.

Step 2: Configuring the NSX-T Components:

=> Can we use the existing Host Transport Nodes & NSGroup Objects instead of creating the new ones while upgrade from R80.30 to R81?

Step 4: Configuring the CloudGuard Management Server Properties:

=> Do we need to create the new controller or can we use the existing one?

Step 5: Registering a New CloudGuard Gateway Service:

=> Do we need to uninstall the existing Cloudguard gateways before we install the new ones?

If yes then what is the fall back option we have? How can we get back to the old setup in case of issues?

Regards,

Sanjay S

Nir_Shamir — Tue, 20 Sep 2022 11:02:26 GMT

Hi,

Step 2: Configuring the NSX-T Components:

=> Can we use the existing Host Transport Nodes & NSGroup Objects instead of creating the new ones while upgrade from R80.30 to R81?

Yes , you can use the same Nodes and NSGroups.

Step 4: Configuring the CloudGuard Management Server Properties:

=> Do we need to create the new controller or can we use the existing one?

No , you can use the same controller because it's the same NSX-T .

Step 5: Registering a New CloudGuard Gateway Service:

=> Do we need to uninstall the existing Cloudguard gateways before we install the new ones?

No, keep the old Gateway Service for Rollback. You need to create a new one that holds the new R81 OVF files.

Sanjay_S — Wed, 21 Sep 2022 05:57:08 GMT

Thankyou Nir for your prompt response.

What is the best way to backup/restore our current configuration?

Regards,

Sanjay S

Nir_Shamir — Wed, 21 Sep 2022 08:10:23 GMT

We basically deploying new GWs side by side with the old ones.

So after the deployment you will route the traffic through the new GWs . if there's an issue , you route it back through the old one.