How to work around my issue in NSX for vSphere?

Products

• VMware NSX Networking

Issue/Introduction

This article is intended to document commonly used workarounds to resolve an issue with your NSX for vSphere (NSX-v) environment. Please refer to the section that describes best your current situation.

Note: This article does not supersede documented workarounds for specific issues documented in KB articles or release notes. If you encounter an issue that is documented, use the associated workaround, if any.

Resolution

NSX-v Manager is unresponsive

• Reboot the NSX-v Manager appliance.
  • From its VM console: 
    1. enable
    2. reboot
  • or from the ESXi host running the appliance,
  • or from vCenter.
• Or restore the NSX-v Manager from backup. See documentation.

NSX-v Manager shows high CPU utilization

• Reboot the NSX-v Manager appliance.
  • From its UI,
  • or from its VM console:
    1. enable
    2. reboot
  • or from the ESXi host running the appliance,
  • or from vCenter.

NSX-v Manager cannot be upgraded

• Use alternative upgrade procedure:

1. Complete an FTP backup on the current NSX Manager.
2. Shut down current NSX Manager. (Do not delete it at this stage.)
3. Deploy a new NSX-v Manager in same version, from the OVA. (Ensure that both NSX Managers are NOT online at the same time.)
4. Restore the FTP backup in the new NSX-v Manager.
5. Complete the upgrade in the new NSX-v Manager with the upgrade file.

NSX-v Controller is disconnected

• Restart the clustering process on the NSX-v Controller appliance:
  • Via SSH: restart controller
  • or from its VM console: restart controller
• Or reboot the NSX-v Controller appliance:
  • Via SSH: restart system force
  • or from its VM console: restart system force
  • or from the ESXi host running the appliance,
  • or from vCenter.
• Or redeploy the NSX-v Controller. See documentation.

NSX-v Controller Cluster is unhealthy

• Redeploy the NSX-v Controller Cluster. See documentation.

NSX-v Controller Cluster cannot be upgraded

• Use alternative upgrade procedure:
  • Redeploy the NSX-v Controller Cluster. See documentation.

NSX-v Edge is unresponsive or unhealthy or services stopped working (BGP, VPN, etc.)

• Force sync the NSX-v Edge. See documentation.
• Or reboot the NSX-v Edge appliance:
  • From the ESXi host running the appliance,
  • or from vCenter.
• Or redeploy the NSX-v Edge appliance. See documentation.

NSX-v Edge cannot be upgraded

• Use alternative upgrade procedure:
  • Documented workaround from KB#57183.

NSX-v Guest Introspection is unhealthy

• Redeploy Guest Introspection.

NSX-v related issues on an ESXi host (DFW, VXLAN, GI, VIB upgrade, etc.)

• Force sync services. See documentation.
• Or reprepare the ESXi host for NSX-v:

1. Drag the ESXi host out of the cluster.
2. Reboot the ESXi host.
3. Drag the host back into the cluster.

• If the ESXi host fails to install NSX-v VIBs, reimage the ESXi host.

vSphere cluster preparation cannot be upgraded in NSX-v

• Use alternative upgrade procedure:

1. Create a new Cluster.
2. Prepare the new Cluster with newer NSX-v version.
3. Drag the first ESXi host out of the old cluster.
4. Reboot the ESXi host.
5. Drag the ESXi host in the new cluster.
6. Repeat for all ESXi hosts in the old cluster.

VM traffic is incorrectly affected by NSX-v DFW

• Temporarily add the affected VM to the DFW exclusion list. See documentation.

Issues with NSX-v features

• Migrate to NSX-T. See documentation.

NSX-v Troubleshooting Guide

• See documentation.

The NSX-v release notes document workarounds for more specific issues

• See release notes.
• See UI plugin functionality updates.