Prior to vCenter Server 7.0 Update 1, FDM configuration was present at location /etc/opt/vmware/fdm/fdm.cfg. You can modify these configurable values of FDM for various purposes.
As ConfigStore is available in ESXi host starting with vCenter Server 7.0, the FDM configuration present in file: /etc/opt/vmware/fdm/fdm.cfg under section <FDM>...</FDM> are migrated to ConfigStore. Hence, FDM process uses the values present in the ConfigStore. However, the rest of the other contents of this file is still being used by FDM process.
Property Name in fdm.cfg (until vCenter Server 7.0) | New Property Name | Name in ConfigStore |
fdm.memReservationMB | No Change | mem_reservation_MB |
fdm.memoryCheckerTimeInSecs | No Change | memory_checker_time_in_secs |
fdm.nodeGoodness | No Change | node_goodness |
fdm.stateLogInterval | No Change | state_log_interval |
fdm.reportFailoverFailEvent | No Change | report_failover_fail_event |
fdm.deadIcmpPingInterval | No Change | dead_icmp_ping_interval |
fdm.hostTimeout | No Change | host_timeout |
fdm.isolationPolicyDelaySec | No Change | isolation_policy_delay_sec |
fdm.icmpPingTimeout | No Change | icmp_ping_timeout |
fdm.storageVmotionCleanupTimeout | No Change | storage_vmotion_cleanup_timeout |
fdm.ft.cleanupTimeout | fdm.ftCleanupTimeout | ft_cleanup_timeout |
fdm.event.maxMasterEvents | fdm.maxMasterEvents | max_master_events |
fdm.event.maxSlaveEvents | fdm.maxSlaveEvents | max_slave_events |
fdm.policy.unknownStateMonitorPeriod | fdm.unknownStateMonitorPeriod | unknown_state_monitor_period |