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

Booting ESXi host without starting the vSphere HA (FDM agent) on startup (79561)

Last Updated: 10/6/2020Categories: How toTotal Views: 2973Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

This article provides how to prevent failover of virtual machine(s) during recovery of an HA enabled Cluster from a Datacenter wise outage.

Solution

Please use it as per recommended steps given below in this KB article. VMware recommends that you use this KB under the direction of VMware Technical Support.

Recommended Steps

Boot All ESXi host of cluster using boot param "fdm=no".

Power on the vCenter Server VM. If the vCenter Server VM is deployed on the same cluster, It need to power on using the vim-cmd command. For more information, see Powering on a virtual machine from the command line when the host cannot be managed using vSphere Client (1038043).

Disable High Availability (HA) in vCenter Server UI.

Once HA is disabled, reboot all the ESXi Host normally without the boot param "fdm=no").

Once completed and HA protection is disabled on the cluster, the virtual machine(s) can be powered on.

Limitations

Do not perform any steps other than what is specified under point 2 & 3 on the vCenter Server or ESXi host when host are booted with param “fdm=no”

Any other step other than above may lead to unspecified behavior.

All ESXi host(s) must be down prior to performing the above steps. Performing the above steps on a partially down cluster may lead to undesired behavior.

Prerequisite

The vCenter Server should be greater than version 7.0 Update 1.

The corresponding fdm agent on each ESXi should be upgraded (upgrade of fdm agent happens automatically whenever the ESXi host syncs to the upgraded vCenter Server on an HA enabled cluster). Verify this by running the “esxcli software vib list | grep fdm” command on the ESXi host.

Note:

Boot param fdm can be given to ESXi while booting through:

a. Network (PXE boot).
b. ILO.
c. Physically on grub prompt.

The boot param “fdm” can have these values:

a. fdm=no is used on boot time fdm agent service will not start after ESXi is booted up.
b. fdm=yes is used on boot time is equivalent to boot ESXi without using fdm boot param. in this case ESXi will boot normally.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
vRealize Automation 7.x プロビジョニングの失敗の根本原因の特定 (79611)

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

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant