VMware Cloud Community
Jauneorange972
Enthusiast
Enthusiast
Jump to solution

NSX edge tenant / DR scenario

Hello,

Let say that we lose the datastore that host the nsx edge for the tenant, how can recovery the nsx edge ?

We are looking for a solution in order to get back the nsx in this type of scenario.

We have try to present a new datastore in the existing storage policie and try "redeploy" option on the nsx edge, it is not working. It seems that vCD need to access to the existing nsx edge for redeployment.

Best regards

Reply
0 Kudos
1 Solution

Accepted Solutions
sk84
Expert
Expert
Jump to solution

Okay. Since you have reconfigured the storage policy, did you try to delete the ESG appliance configurations, as I mentioned?

These values are also defined after deployment. You can see them by selecting the Edge Gateway in the Networking & Security tab of the vSphere (Web) Client and under Manage -> Settings -> Configuration -> NSX Edge Appliances.

If you select one of the two appliances there and click on the red X, it will not delete your entire ESG configuration as it is stored in the NSX Manager. Only the resource configurations of the ESG VMs and the ESG VMs themselves are deleted.

If you can delete the two entries there and if you already have changed the default storage policy a redeploy in vCD should work.

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.

View solution in original post

Reply
0 Kudos
6 Replies
sk84
Expert
Expert
Jump to solution

As long as the old edge appliance is in the inventory of vCenter, the NSX manager will try to contact it for shutdown, etc.

So you need to delete the disconnected or orphaned vm object first. After that the redeployment should work.

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.
Reply
0 Kudos
Jauneorange972
Enthusiast
Enthusiast
Jump to solution

It is not working for us.

I have unmount the volume / datastore on netapp site, and unmount on vsphere side to simulate the outage.

The nsx edge was marked as "orphaned", as you said, i removed it from the vcenter inventory.

Even trying to redeploy, we have the same error, here is the detail:

Could not find resource pool for placement of edge gateway e4bdc618-3442-446d-92e0-2579d18a1417. This is because compute, storage or network requirements are not satisfied by any of the resource pools.  - No gateway found with this name: 6d5a7cce-6cd6-4840-90bf-37154f184a35

6d5a7cce-6cd6-4840-90bf-37154f184a35 = the old nsx edge.

vCD is still try to reach the old nsx edge.

Any idea ?

Reply
0 Kudos
sk84
Expert
Expert
Jump to solution

Okay. Now I understand what you mean and what you did.

By default, the edge gateways are deployed in a specific system ressource pool and on the default storage policy of an orgVDC. These values are also defined after deployment. You can see them by selecting the Edge Gateway in the Networking & Security tab of the vSphere (Web) Client and under Manage -> Settings -> Configuration -> NSX Edge Appliances.

Since the default storage policy for an orgVDC has no longer a backing storage device in this scenario, vCD cannot deploy the edge gateway again.

But this also applies to the VMs that use this storage policy. They should be orphaned as well. What does your DR concept look like here?

If the storage device is now permanently gone (e.g. burned or stolen), then you would either have to create new edge gateways or you can try to delete the edge appliance configurations in the Networking & Security tab, set new default storage policies for the orgVDCs or have them point to another storage (don't forget to refresh the storage policies). And then try the redeployment again. Either via vCD or via the Networking & Security tab in the vSphere Client.

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.
Reply
0 Kudos
Jauneorange972
Enthusiast
Enthusiast
Jump to solution

Hello sk84,

Thx for your help.

To summarize, we plan to deploy a vCD on two site (L2 stretched) and trying to figure out all case of outage, including storage point (we don't have shared storage like vSAN stretched).

We are trying to figure out a workaround in case we lose the storage (NSX edge especially), we need to way to restore NSX edge for traffic N/S. We thought that redeploy could work.

Since the default storage policy for an orgVDC has no longer a backing storage device in this scenario, vCD cannot deploy the edge gateway again.

==> The default SP have a new storage device because i am presenting a new storage which is matching the default SP. Under SP on vsphere, we can see the new storage, including on vCD by doing a refresh on vCenter and checking SP under vCD.

But after all, we still could not re deploy the NSX edge for the tenant. Maybe it is normal that it won't work ??!!

And maybe the only way is to destroy the NSX edge and deploy from the beginning with NAT, FW, etc... huge SPOF.

I am searching here if it is possible.

Best regards

Reply
0 Kudos
sk84
Expert
Expert
Jump to solution

Okay. Since you have reconfigured the storage policy, did you try to delete the ESG appliance configurations, as I mentioned?

These values are also defined after deployment. You can see them by selecting the Edge Gateway in the Networking & Security tab of the vSphere (Web) Client and under Manage -> Settings -> Configuration -> NSX Edge Appliances.

If you select one of the two appliances there and click on the red X, it will not delete your entire ESG configuration as it is stored in the NSX Manager. Only the resource configurations of the ESG VMs and the ESG VMs themselves are deleted.

If you can delete the two entries there and if you already have changed the default storage policy a redeploy in vCD should work.

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.
Reply
0 Kudos
Jauneorange972
Enthusiast
Enthusiast
Jump to solution

Hi sk84,

Thx to you, we find out that we can redeploy an NSX edge directly from NSX Manager.

Here are the details:

- We delete the NSX edge from vSphere side, simulate an outage on storage or directly on NSX edge.

- The tenant EDGE is not working anymore, no update possible, errors when trying to update ou submit some thing.

- From NSX manager under GUI vSphere, we have to find out the right NSX edge for the tenant, and click "deploy". Then NSX starts to deploy a new EDGE even if we don't have any more EDGE.

Best regards

Reply
0 Kudos