Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

NSX Manager connectivity is lost when powered off and migrated to another host prepared cluster (51459)

Last Updated: 12/20/2018Categories: TroubleshootingTotal Views: 9800Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

NSX Manager connectivity is lost when powered off and migrated to another host prepared cluster.

Cause

This issue occurs because the NSX Manager is in the list of excluded VMs for Distributed Firewall by default. The NSX Manager sends the list of excluded VMs that reside on a given cluster to hosts of that cluster. NSX Manager keeps track of VMs that are moved from one cluster to another and sends this information to hosts upon VM migration.

But if the NSX Manager is powered off, there is no communication between the hosts and the NSX Manager to send the updated exclude list down to the migrated cluster. When the NSX VM is migrated, it ends up having a DFW filter and existing DFW rules will be applied disrupting the NSX Manager communication.

VMware recommends NOT to deploy the NSX Manager inside a host prepared cluster.

To avoid getting into this issue before migrating the NSX Manager VM to another host prepared cluster, one of the these workaround applies.

Change the default rule to Allow.

Add a couple of temporary rules allowing traffic from/to NSX Manager IP (applied to ANY). Migrate the VM from one cluster to another. Once the VM is up and running, delete the temporary rules.

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.0, available at VMware Downloads.

Workaround

To work around this issue if you do not want to upgrade:

Clear the rules for the NSX Manager DFW filter on the host where the VM was migrated.
a. SSH into the ESXi host that has the NSX Manager VM.
b. Run the command summarize-dvfilter or vsipioctl getfilters to find out the filter name that is protecting the NSX VM. The filter  name starts with `nic-', such as nic-12345-eth0-vmware-sfw.2.
c. Run the command vsipioctl getrules -f <filter-name> to get the ruleset of the firewall. There should be two rulesets, such as domain-c7 and domain-c7_L2. The first ruleset like domain-c7 is the one you need to remove.
d. Run the command vsipioctl vsipfwcli -f <filter-name> -c "create ruleset <ruleset-name>;" to clear the ruleset.
e. Run the command vsipioctl getrules -f <filter-name> to get the ruleset of the firewall. The first ruleset should be empty without any rules. NSX VM should be online now.

Reboot the NSX Manager.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

Take Our Survey

Support Assistant