Shulou(Shulou.com)05/31 Report--

VSphere HA 5.x series of advanced parameters and detailed use of what, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain in detail for you, people with this need can come to learn, I hope you can gain something.

Das.allowNetworkX-allows you to specify a specific management network for vSphere HA's heartbeat network. X can be the Arabic numeral 0-9. This option is not valid when the vSAN function is activated in 5.5

Das.ignoreRedundantNetWarning-if the ESXi Host managed by vSphere HA does not have a redundant network, it will alarm, so you can use this parameter to skip the alarm

Das.heartbeatDsPerHost-vSphere HA defaults to configuring 2 Heartbeat Datastore per ESXi Host. This option helps specify the amount of heartbeat storage for the host, up to 5.

Das.ignoreInsufficientHbDatastore-this option is used to skip this warning detection when ESXi Host does not have enough heartbeat storage. The value can be True.

Das.includeFTcomplianceChecks-this option is used to check whether the relevant configuration of Cluster meets the requirements of Fault Tolerance. If this option is False, there is no need to test.

Das.vmMemoryMinMB-this option indicates the minimum reserved value of the virtual machine in MB when the reserved memory of the virtual machine is 0

Das.vmCpuMinMHz-this option is the minimum reservation value of the virtual machine, in MHz, when the CPU of the virtual machine is reserved as the default. The default is 32.

Das.slotCpuInMHz-this option represents the maximum value of the CPU part of the Slot Size, and the parameter is MHz

Das.slotMemInMB-this option represents the maximum value of the CPU part of the Slot Size, and the parameter is MB

Das.maxvmrestartcount-this option indicates how many times the FDM Master host attempted to restart the virtual machine on the HA applause host. It is recommended that this value not be set too high, and it is usually used with das.maxvmrestartperiod, that is, the number of attempts to restart the virtual machine within a limited time. However, the Secondary VM generated for FT needs to use this parameter to solve the das.maxftvmrestartcount parameter.

Das.maxvmrestartperiod-this parameter is used to limit the time for FDM Master to attempt to restart VM. If the time exceeds, it will not be tried again (in seconds). This parameter is usually used in conjunction with das.maxvmrestartcount.

Das.maskCleanShutdownEnabled-when the virtual machine is shut down and its Datastore is inaccessible, HA cannot detect whether the virtual machine has been restarted successfully. In this case, activating this option is tantamount to telling the FDM Master host that the virtual machine needs to be restarted, and the FDM Master host will perform a restart attempt. If this value is false, FDM Master will ignore the problem, pretending that VM does not need to restart.

Das.respectVmVmAntiAffinityRules-attempt to restart virtual timing after an attempt HA failure to clarify the anti-affinity rule between vm and vm. This value defaults to false and can be adjusted to true

Das.isolationAddressX-this is the isolated response address, and the default is the default gateway. However, users can add up to 10 isolated response addresses from 0 to 9 according to their needs to solve the redundant isolated response address problem. In vSphere 5.5, if vSAN's vmkernel interface type is enabled, this address is also selected for internal isolation response detection

Das.useDefaultIsolationAddress-this option is usually used with das.isolationAddressX, and needs to be set to false when you need to use das.isolationAddressX

Das.config.fdm.isolationPolicyDelaySec-the time interval for this uxanxiangzeshiFDM Agent to wait for the isolation response policy to be executed, with a minimum of 30 seconds, that is, how long it is detected that the host has been quarantined before performing the isolation response action

Das.isolationShutdownTimeout-this parameter is how long FDM waits for the virtual machine to perform the Power Off action after Shutdown Guest. If it is not set, it defaults to 300 seconds.

Das.iostatsInterval-FDM detects the existence of the heartbeat of the virtual machine and triggers the monitoring policy of the virtual machine or Application when the heartbeat disappears. FDM checks to see if there is an Icano occurring during the ioStatsInterval time. If not, the instruction to reset the virtual machine is triggered. This value defaults to 120 seconds.

Das.maxFtVmsPerHost-this parameter indicates the maximum number of VMs on each ESXi Host that can enable FT. If it is not set, it defaults to 4. If-1 or 0, it means to disable and limit the number of virtual machines that enable FT. This restriction is made by vCenter.

Das.config.log.maxFileNum-this parameter controls the number of FDM log files

Das.config.log.maxFileSize-this option sets the maximum value of the FDM log file, usually the 1MB size

Vpxd.dads.aamMemoryLimit-this option indicates the memory limit of the aam resource pool, usually 100MB, which affects all Cluster under vCenter Server Inventory

What is the interval between vpxd.das.electionWaitTimeSec-vCenter Server hosts waiting for the election. If it is not set, it is 120 seconds. This option is mainly used to control the election time range between Slave hosts.

Fdm.nodeGoodness-when the Master election is executed, the FDM Agent will exchange the value of the goodness, and then the host with the higher goodness value will become the new Master host. Of course, the MOID of the host takes precedence over this Goodness parameter. If you want to forcibly designate an ESXi Host as the Master host, you can set this value a little higher, which does not work at the Cluster level, but at the host level

Vpxd.das.sendProtectListIntervalSec-this option represents the minimum time interval for the vCenter Server to send Protected List to the Master host, which, if not set, defaults to 60 seconds; the setting of this option controls how often the Master host obtains VM changes from vCenter Server

Fdm.cluster.vsanDatastoreLockDelpy-represents the delay before the vSAN Datastore object acquired. Virtual machine failover is not performed on the Datastore until the vSAN Datastore is Master acquired. This value defaults to 30 seconds

The global virtual machine reservation value set by vpxd.das.slotMemMinMB-vCenter Server, which will be overridden by the previous das.slotMemMinMB

The global virtual machine reservation value set by vpxd.das.slotCpuMinMHz-vCenter Server, which will be overridden by the previous das.slotCpuMinMHz

Das.config.fdm.hostTimeout-controls how long FDM hosts wait for FDM Agent on Slave hosts. If it is not set, it defaults to 10s.

Fdm.deadIcmpPingInterval-when the FDM cannot communicate with the Master host, the interval between checking whether the network of the Slave host can reach ICMP ping. Default is 10 seconds.

Das.config.fdm.icmpPingTimeout-defines the timeout for FDM to wait for feedback from ICMP ping values. If not set, it defaults to 5s.

Vpxd.das.heartbeatPanicMaxTimeout-this option is the length of time to wait for the host to be in PSOD state. The default is 60s. After the timeout, the virtual machine will be restarted.

Das.config.fdm.policy.unknowStateMonitorPeriod-defines how long HA Master Agent waits to detect virtual machine failures, default is 10s

Das.perHostConcurrentFailoversLimit-indicates the number of virtual machine Failover concurrent at a time, default is 32

Das.config.fdm.ft.cleanupTimeout-this parameter represents the detection of the FT virtual machine. The default is 900s.

Das.config.log.outputToFiles-indicates that the output FDM log file

Das.config.log.directory-indicates the specified FDM log file directory, which can be in the format / var/log/vmware/vdm

Das.config.fdm.stateLogInterval-indicates the frequency with which FDM logs are generated. Default is 600s.

Das.config.fdm.event.maxMasterEvents-defines the maximum number of event caches for Master hosts, default is 1000

Das.config.fdm.event.maxSlaveEvents-defines the maximum number of event caches for Slave hosts, which defaults to 600

Vpxd.das.reportNoMasterSec-indicates how long the vCenter Server detection has not received feedback from FDM Agent on the Master host. Default is 120 seconds.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.