In a VCF environment new Transport Node Profiles are present after upgrade
Article ID: 324203
Updated On:
Products
VMware Cloud Foundation
VMware NSX Networking
Issue/Introduction
Symptoms:
- VCF 4.x environment.
- Upgrade of NSX-T Data Center earlier than 3.1.0 to NSX-T Data Center 3.1.0 or later version.
- New Transport Node Profiles (TNP) are present after upgrade with the naming convention
<VC Name>-<cluster-MoRef>
Environment
VMware NSX-T Data Center
Cause
In earlier versions of VCF, Transport Node Profiles(TNP) were detached from clusters once NSX-T cluster preparation was completed.
In VCF environments using NSX-T 3.1.0 and above, TNPs should always remain attached to prepared clusters.
To ensure this process change is handled for brownfield environments and to remove any dependencies on older TNPs, new TNPs are created during the VCF NSX-T upgrade and attached to the NSX-T clusters.
In VCF environments using NSX-T 3.1.0 and above, TNPs should always remain attached to prepared clusters.
To ensure this process change is handled for brownfield environments and to remove any dependencies on older TNPs, new TNPs are created during the VCF NSX-T upgrade and attached to the NSX-T clusters.
Resolution
Not applicable.
Workaround:
No workaround is required.
The new TNPs will remain attached to the clusters therefore the old TNPs can be deleted if desired.
Workaround:
No workaround is required.
The new TNPs will remain attached to the clusters therefore the old TNPs can be deleted if desired.
Feedback
Yes
No
Powered by
