VMotion gets stuck at 19%.

Products

• VMware NSX

Issue/Introduction

• The nsxa status displays as down in net-vds, causing the VM port attachment failure to n-vds switch. vMotion then fails, and any attempt to attach the VM port to LS also fails.
• During the migration using vMotion to the upgraded host, you see these errors similar to:
  Currently connected network interface" 'Network adapter X' uses network 'Internal_X("N-VDS name" :nsxa down)', which is not accessible. 
• The net-dvs command outputs of the upgraded host display the nsxa status as down.
  For example:    
  net-dvs -l | grep "nsxa"
"component.nsxa = down"

Environment

VMware NSX
VMware NSX-T Data Center

Resolution

Workaround:
To work around this issue, we will need to work on both the ESXi host(s) and NSX manager.

Steps:

1 - ESXi:

1. Verify if the issue is, in fact, nsxa, using the above command: net-dvs -l | grep "nsxa"
2. Assuming it's down, remove the files under the nsxa folder: rm -rf /etc/vmware/nsxa/*

2 - Make API call to recreate the deleted config

1. Make the following MP API calls to re-populate the contents of the host_config file.
   a. GET api/v1/transport-nodes/<tn-id>.
   b. PUT api/v1/transport-nodes/<tn-id> with the returned payload in step 1);
   c. Repeat Step 1) and 2) again.
    
2. After Step 1, re-check the "host_config" file.
   For example:
   [/etc/vmware/nsxa] ls -l
   total 4
   -rw-r--r-T 1 root root 528 22:18 host_config.bin
   -rw-r--r-T 1 root root 0 06:06 host_config_mmode.bin

3 - ESXi:

1. Restart ESXi host services: services.sh restart
2. Wait a few seconds and run the check again; nsxa should be up.