If NSX Edge services do not work as expected after a force sync, you can redeploy the NSX Edge instance.

Before you begin

Verify the hosts have enough resources to deploy additional NSX Edge Services Gateway appliances during the redeploy. See the System Requirements for NSX for the resources required for each NSX Edge size.

  • For a single NSX Edge instance, there will be two NSX Edge appliances of the appropriate size in the poweredOn state during redeploy.

  • Starting in NSX 6.2.3, when redeploying an NSX Edge instance with HA, both replacement appliances are deployed before replacing the old appliances. This means there will be four NSX Edge appliances of the appropriate size in the poweredOn state during upgrade of a given NSX Edge. Once the NSX Edge instance is redeployed, either of the HA appliances could become active.

  • Prior to NSX 6.2.3, when redeploying an NSX Edge instance with HA , only one replacement appliance is deployed at time while replacing the old appliances. This means there will be three NSX Edge appliances of the appropriate size in the poweredOn state during the redeploy of a given NSX Edge. Once the NSX Edge instance is redeployed, usually the NSX Edge appliance with HA index 0 becomes active.

About this task

Note:

Redeploying is a disruptive action. It is recommended that you first apply a force sync and if the issue is not fixed, then redeploy.

Redeploying an NSX Edge instance results in the following actions:

  • Edge appliances are deleted and freshly deployed with the latest configuration applied

  • Logical routers are deleted from the controller and then recreated with the latest configuration applied

  • Distributed logical router instances on hosts are deleted and then recreated with the latest configuration applied

OSPF adjacencies are withdrawn during redeploy if graceful restart is not enabled.

Important:

In a cross-vCenter environment it is required that theNSX Edge instance be redeployed first on the primary NSX manager and after that is complete, then redeploy the NSX Edge instance on secondary NSX managers. It is required that both the primary and the secondary NSX managers are redeployed.

Procedure

  1. Log in to the vSphere Web Client.
  2. Click Networking & Security and then click NSX Edges.
  3. Select an NSX Edge instance.
  4. Click the Actions (More Actions icon) icon and select Redeploy Edge.

Results

The NSX Edge virtual machine is replaced with a new virtual machine and all services are restored. If redeploy does not work, power off the NSX Edge virtual machine and redeploy NSX Edge again.

Note:

Redeploy may not work in the following cases.

  • Resource pool on which the NSX Edge was installed is no longer in the vCenter inventory or its Managed Object ID (MoId) has changed.

  • Datastore on which the NSX Edge was installed is corrupted/unmounted or in-accessible.

  • dvportGroups on which the NSX Edge interfaces were connected are no longer in the vCenter inventory or their MoId (identifier in vCenter server) has changed.

If any of the above is true, you must update the MoId of the resource pool, datastore, or dvPortGroup using a REST API call. See NSX API Programming Guide.