Transit Connect related configuration is not fully correctly realized. Possible issues could be failing to retrieve provider information or some transient provider communication error. Action required: If this alarm is not auto-resolved within 10 minutes, retry the most recent transit connect related request(s). For example, if a TGW attachment API request triggered this alarm, retry the TGW attachment API request again. If alarm does not resolve even after retry, then try the following steps: 1. Check if the task keeps failing, or the task has recovered. a) Identify leader Manager node. After logging into one of the nodes, run command: - `su admin` - `get cluster status verbose` This will show the leader Manager node b) Log in to NSX leader Manager node. check vmc-app.log on the NSX leader Manager node: - `tail -f /var/log/policy/vmc-app.log` c) Check logs for following prints - If any of these error messages keeps showing every two mins, that means task keeps failing. - Failed to get TGW route table for []. Error: [] - Failed to get TGW routes for attachment [] in route table []. Error - Failed to get TGW attachment VPC ID for []. Error: [] - Failed to get TGW attachment resource ID for []. Error: Unknown resource type - Failed to get TGW attachments for TGW []. Error: [] - Failed to get local TGW attachment []. Error: [] - Failed to find correct TgwAttachment state in AWS, state: [], skipping TGW route update task - TGW attachment [] is not associated with any route table - No local TGW SDDC attachment found for [] 2. Check if all AWS calls from NSX Manager failed, on leader Manager node. Run following command: - `export HTTP_PROXY=http://<pop ip>:3128` - `export HTTPS_PROXY=http://<pop ip>:3128` - `export NO_PROXY=169.254.169.254` - `aws ec2 describe-instances If aws command failed with error, then there might be a system issue in HTTP reverse proxy configuration on pop, or there is AWS service side issue. 3. Check whether TGW attachment still exists in AWS. a) TGW attachment ID could be found with GET cloud-service/api/v1/infra/associated-groups - `aws ec2 describe-transit-gateway-attachments If TGW attachment has been deleted, contact VMware Support, share SDDC ID and TGW attachment ID. After VMware support team identified the issue, manually delete the object left behind, if needed. b) Check if this TGW attachment exists on AWS console. c) Another option is logging in to NSX Manager, using aws command to check the state of TGW attachment: - `aws ec2 describe-transit-gateway-attachments