VMware NSX-T Data Center 3.x
This is a condition that may occur in a VMware NSX environment.
Workaround: