Unable to delete TNPs as they are applied to stale Transport Node Collections
search cancel

Unable to delete TNPs as they are applied to stale Transport Node Collections

book

Article ID: 413374

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Deleting the TNP from the UI results in the error "Transport Node Profile is attached to any Compute Collection can not be deleted."
  • Under NSX UI > Fabric > Hosts > Transport Hosts Profiles, the "Applied Clusters" column is not 0, but when clicking on the "Applied Clusters" link you get "No Clusters Available".

Environment

Vmware NSX and VMware NSX-T Data center.

Cause

The issue happens due to stale Transport Node Collections, which could be a result of deleting the clusters directly from the vCenter server without proper NSX configuration.

Resolution

This issue is resolved in VMware NSX 3.2.2 and 4.1.1.0, available at Broadcom downloads. If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.