Steps to delete a failed traffic group

Products

• VMware NSX
• VMware Cloud on AWS

Issue/Introduction

This KB article provides information to remediate/delete a failed traffic group (TG).

Symptoms:
Whenever a Traffic Group (TG) creation fails due to any reason (mostly due to compute resource crunch, etc), the TG creation shows up as Failed.
To understand the cause, hover the mouse over i beside Failed.

Environment

VMware NSX 4.1.0
VMware NSX 4.0.0.1

Cause

Most of the times a traffic group (TG), deployment fails due to insufficient resources on the SDDC or due to anti-affinity rules blocking the TG VM to power-ON on a given host.

Resolution

We recommend deleting any failed TGs from the SDDC to ensure they won't pose any risk to upgrades.
Steps to delete a TG:

1. To remove a traffic group, you must first remove its association maps.
   • Find the traffic group on the Traffic Groups page. Click the  button, then select Edit.
   • Click the minus icon  to the right of the Status label under Association Maps to select the map for deletion, then click SAVE to delete the map.
   • Click CLOSE EDITING, then return to the traffic group on the Traffic Groups page. Click its ellipsis button and then select Delete.
2. It can take up to 30 minutes to remove a traffic group. Removing the traffic group removes the T0 router that was created to support it. HCX, if in use, creates its own association map, which you can view but not modify. To remove an association map created by HCX, you have to uninstall HCX. See Uninstalling VMware HCX in the VMware HCX User Guide.

   
Workaround:
Failed TGs do not carry any live traffic; therefore, we recommend deleting them instead of following any workaround.

Additional Information

Refer VMware Docs:
https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-networking-security/GUID-306D3EDC-F94E-4216-B306-413905A4A784.html

Impact/Risks:
If the failed TG continues to be in the same state, upgrade pre-checks identify the failed TGs and block the SDDCs from upgrading. This results in delaying the upgrade cycle for the SDDC.