This issue is resolved in NSX-T 3.2.2, available at Broadcom Downloads.
Workaround:
If you believe you have encountered this issue, please open a support request with Broadcom Support and refer to the KB Creating and managing Broadcom support cases article.