Troubleshoot Multi-NSX Issues

Docs

Docs
(current)
VMware Communities

Twitter Facebook LinkedIn 微博

Troubleshoot issues related to Multi-NSX environments. In a Multi-NSX environment, more than one NSX Manager is registered to a single vCenter Server.

What to read next

Cannot Enable Multiple NSX-T on Single vCenter Server
If an old NSX-T extension exists in vCenter Server, you cannot enable multiple NSX-T on the vCenter Server as NSX-T is already registered.
Override NSX-T Ownership Constraints
When a transport node profile (TNP) is applied to a cluster if any validations (VMs are running on hosts) fail then Transport Node is not created. After ensuring validations pass, you can reapply cluster configuration using API. However, if you want the node to give up ownership of its managed objects you can call the override_nsx_ownership parameter in the API call.
Preparing Standalone Host Cluster Results in Failure
Preparing a standlone host cluster for NSX-T 3.2.2 results in failure.
Traffic Performance Issues Related to NSX Edge VMs in Multiple NSX-T Data Center Environment
In a multiple NSX-T Data Center environment, only the NSX Manager which deployed NSX Edge VM can use it for routing and Inter TEP communication. None of the other NSX Managers registered to the same vCenter Server can use it for routing and Inter TEP communication. The other NSX Manager instances consider the NSX Edge VM as a regular VM. This scenario can cause traffic performance issues on the NSX Edge VM.

Parent topic: Host Transport Nodes

Share on Social Media?

:

|

x

" "?