This is a known issue affecting NSX-T 3.1.2
Workaround:
To apply the workaround for this issue, you must use the following procedure to disable and enable the ENS on all the transport nodes of the ENS enabled cluster.
1. To find out the ENS enabled uplinks on the ESXi hosts execute the below command to confirm which of the uplinks that are ENS capable and ENS driven(highlighted text below):
# esxcfg-nics -e
2. To get the DvsPortset-name on which the ENS enabled uplinks (of the ESXi hosts) reside, execute the below command on all the ESXi hosts:
#net-stats -l
From the above output we gather that vmnic4 and vmnic5 which are the ENS enabled uplinks on the transport node are bound to DvsPortset-1.
3. Disable ENS on all the transport nodes of the ENS enabled cluster by executing the below command on all the ESXi hosts sequentially:
#esxcfg-vswitch -Y <DvsPortset-name>
Example: #esxcfg-vswitch -Y DvsPortset-1
Note: The successful execution of the above command will not return any output but will just give back the command prompt without any errors.
4. Wait for 10 seconds and enable ENS on all the transport nodes of the ENS enabled cluster by executing the below command on all the ESXi hosts sequentially:
#esxcfg-vswitch -y <DvsPortset-name>
Example: #esxcfg-vswitch -y DvsPortset-1
Note: The successful execution of the above command will not return any output but will just give back the command prompt without any errors.
Verification
After executing the commands in steps 3 and 4 above, verify the tunnels are up on the transport nodes by executing the below command and confirm that the status of the tunnels is ‘up’ by checking the status under the ‘local_state’ column:
# nsxdp-cli bfd sessions list