Troubleshoot issues with host profiles and TNPs when they are used to auto deploy stateless clusters.
|Host Profile is not portable.||
Issue: None of the vCenter servers can use the host profile containing NSX-T configuration.
|Auto Deploy Rule Engine||
Issue: Host profile cannot be used in auto deploy rules to deploy new clusters. If new clusters are deployed, the hosts get deployed with basic networking and remain in maintenance mode.
Workaround: Prepare each cluster from NSX-T GUI. See Apply TNP on Stateless Cluster.
|Check compliance errors.||
Issue: Host profile remediation cannot fix the compliance errors related to the NSX-T configuration.
Workaround: Ensure the NSX-T configuration matches on Host Profile and TNP. Reboot the host to realize the configuration changes. The host comes up.
Issue: If there are any NSX-T specific compliance errors, host profile remediation on that cluster is blocked.
Workaround: Ensure that the NSX-T configuration matches on Host Profile and TNP. Reboot the host to realize the configuration changes. The host comes up.
Issue: In a cluster configured with NSX-T, host profile cannot be attached at the host-level.
Issue: Detaching and attaching a new host profile in a cluster configured with NSX-T does not remove the NSX-T configuration. Even though the cluster is compliant with newly attach the host profile, it still has the NSX-T configuration from a previous profile.
Issue: If the user has changed NSX-T configuration in the cluster, then extract a new host profile. Update the host profile manually for all the settings that were lost.
|Host-level transport node configuration||
Issue: After anportsport node was auto-deployed, it acts as individual entity. Any update to that transport node might not match with the TNP.
Workaround: Update the cluster. Any update in a standalone transport node cannot persist its migration specification. The migration might fail to post the reboot.
|Cannot apply the host profile because mux_user password policy and password were not reset.||
Issue: Only on hosts running versions earlier than vSphere 6.7 U3. Host remediation and host profile application on hosts might fail unless the mux_user password is reset.
Workaround: Under Policies & Profiles, edit the host profile to modify the mux_user password policy and reset the mux_user password.
|PeerDNS configuration is not supported on the VMkernel adapter selected for migration to the NVDS switch.||
Issue: If a VMkernel adapter selected for migration to NVDS is peer-DNS enabled, then host profile application fails.
Workaround: Edit the extracted host profile by disabling peer-DNS setting on the VMkernel adapter that must be migrated to an NVDS switch. Alternatively, ensure that you do not migrate peer-DNS enabled VMkernel adapters to an NVDS switch.
|DHCP address of the VMkernel NIC address not retained||
Issue: If the reference host is stateful, then any stateless hosts using profile extracted from the stateful reference host cannot retain their VMkernel management MAC address derived from PXE started MAC. It results in DHCP addressing issues.
Workaround: Edit extracted host profile of stateful host and modify the 'Determine how MAC address for vmknic should be decided' to 'Use the MAC address from which the system was PXE started'.
|Host Profile application failure in vCenter can lead to NSX configuration errors on the host.||
Issue: If host profile application fails in vCenter, NSX configuration might also fail.
Workaround: In vCenter, verify that host profile was successfully applied. Fix the errors and try again.
|LAGS are not supported on stateless ESXi hosts.||
Issue: The uplink profile configured as LAGs in NSX is not supported in a stateless ESXi host managed by a vCenter Server or in NSX.