RunNSX

When using IP discovery on logical switches in VMware NSX for vSphere 6.2.0, you experience these symptoms:

• The ESXi 5.x and 6.x host fails with a purple diagnostic screen
• The purple diagnostic screen contains entries similar to:

@BlueScreen: CPU xx /World xxxxx tried to re-acquire lock dvfg.sec.confg
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]PanicvPanicInt@vmkernel#nover+0x37e
0xnnnnnnnn:[0xnnnnnnnn]Panic_NoSave@vmkernel#nover+0x4d

In order to protect from this issue you must disable IP discovery for all logical switches.  This prevents the issue from occurring.

NOTE:  Disabling IP discovery disables broadcast suppression for ARP traffic.  Which may, or may not cause a performance hit depending on the environment.  Additionally if you used new features in NSX 6.2 to allow for the use of object based rules in the DFW for virtual machine that do not have VMware tools, disabling IP discovery will stop the DFW from working with these workloads.

VMware ESXi 5.x and 6.x experiences a purple diagnostic screen when using IP discovery in VMware NSX for vSphere 6.2.0 (2134329)