VMware: Sådan foretager du fejlfinding af vSphere HA, hvis den ikke aktiveres, eller hvis domæneadministratoragenten ikke installeres på ESXi-værterne

Summary: I denne artikel forklares kravene til aktivering af vSphere HA i en VMware-klynge og løsning af problemer med installation af FDM-agenter (Fault domain Manager) på ESXi-værter.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

Foretag fejlfinding af problemer, når du aktiverer vSphere HA i en vSphere-klynge, eller når FDM-agenten (Fault Domain Manager) ikke installeres på ESXi-værterne.

Fakta:
vSphere HA
vSphere klynger
FDM-agent (Fault Domain Manager).

Procedure:

  • Hvis vSphere HA ikke aktiveres, skal du gøre følgende:
  1. Deaktiver og genaktiver eller omkonfigurer vSphere HA på klyngen. Denne kontrol løser de fleste problemer.
  2. Se produktbemærkningerne for at se, om der er kendte problemer med vSphere HA, og kontrollér, at vSphere har den nyeste version.  
  3. Kontroller FDM-logfilerne (Fault domain Manager), der findes på ESXi-værterne, og søg efter fejlmeddelelser.

Logfiler, der skal gennemses på ESXi-værten for at finde årsagen til problemet. 

  • FDM Operations log: /var/log/fdm.log or /var/run/log/fdm
  • Installationslogfil for FDM-agent: /var/log/fdm-installer.log

Mulige årsager til dette problem

  • vSphere HA er ikke konfigureret korrekt.
  • Datalageret for vSphere HA heartbeats er ikke tilgængeligt for alle værter.
  • FDM-agenten er ikke installeret korrekt på ESXi-værten.
  • Netværksforbindelsen mellem ESXi-værten og vCenter Server mistes.
  • ESXi-værten er ikke sluttet korrekt til vCenter Server.

 

  • FDM-agenten installeres ikke på ESXi-værten.

Hvis FDM-agenten ikke kan installeres på ESXi-værten, skal du udføre følgende kontroller:

  1. Kontroller FDM-loggen for fejl: /var/log/fdm.log
  2. Kontroller, at der er tilstrækkelig netværksbåndbredde mellem ESXi-værten og vCenter Server.
  3. Kontroller, om der er et hardwareproblem, hvis netværkstrafikoverførselshastigheden er årsag til problemet.
  4. Kontroller, at der er ledig diskplads på ESXi-værten i /var and /tmp. Brug kommandoen:
vdf -h 


Hvis problemet med installationen af FDM Agent på ESXi-værten er relateret til netværkstrafik, skal du identificere, hvad årsagen til problemet er:

  • Hardwareproblem med netværksinterfacecontrolleren (NIC)
  • Uoverensstemmelse mellem NIC-hastighed og switchhastighed
  • Hardware eller firewall blokerer eller bremser trafikken.

Du kan også kontrollere, at FDM-agentfilerne blev sendt fra vCenter til ESXi-værten, ved at kontrollere, at følgende filer findes på ESXi-værten i /etc/opt/vmware/fdm mappe:

  • Klyngekonfiguration: Clusterconfig
  • FDM-konfigurationsfil: fdm.cfg
  • Liste over værtsmedlemskaber: Hostlist
  • Liste over alle virtuelle maskiner (VM) og de værter, de er kompatible med: Vmmetadata
Se eksempelskærmbilledet nedenfor:


Kontroller, at filer blev sendt fra vCenter til ESXi-værtenFigur 1: Kontroller, at filer blev sendt fra vCenter til ESXi-værten.

Additional Information

Relaterede VMware-artikler:

Affected Products

PowerFlex rack, ScaleIO, PowerEdge FC640, PowerEdge M640, PowerEdge M640 (for PE VRTX), PowerEdge MX740C, PowerEdge MX750c, PowerEdge MX760c, PowerEdge MX840C, PowerEdge R240, PowerEdge R250, PowerEdge R260, PowerEdge R340, PowerEdge R350 , PowerEdge R360, PowerEdge R440, PowerEdge R450, PowerEdge R470, PowerEdge R540, PowerEdge R550, PowerEdge R640, PowerEdge R6415, PowerEdge R650, PowerEdge R650xs, PowerEdge R6515, PowerEdge R6525, PowerEdge R660, PowerEdge R660xs, PowerEdge R6615, PowerEdge R6625, PowerEdge R670, PowerEdge R740, PowerEdge R740XD, PowerEdge R740XD2, PowerEdge R7415, PowerEdge R7425, PowerEdge R750, PowerEdge R750XA, PowerEdge R750xs, PowerEdge R7515, PowerEdge R7525, PowerEdge R760, PowerEdge R760XA, PowerEdge R760xd2, PowerEdge R760xs, PowerEdge R7615, PowerEdge R7625, PowerEdge R770, PowerEdge R7715, PowerEdge R7725, PowerEdge R840, PowerEdge R860, PowerEdge R940, PowerEdge R940xa, PowerEdge R960, PowerEdge T140, PowerEdge T150, PowerEdge T160, PowerEdge T340, PowerEdge T350, PowerEdge T360, PowerEdge T40, PowerEdge T440, PowerEdge T550, PowerEdge T560, PowerEdge T640, VMware ESXi 7.x, VMware ESXi 8.x, VxBlock and vBlock Systems Series ...

Products

PowerEdge R250, PowerEdge R260, PowerEdge R340, PowerEdge R350, PowerEdge R360, PowerEdge R440, PowerEdge R450, PowerEdge R470, PowerEdge R540, PowerEdge R550, PowerEdge R640, PowerEdge R6415, PowerEdge R650, PowerEdge R650xs, PowerEdge R6515 , PowerEdge R6525, PowerEdge R660, PowerEdge R660xs, PowerEdge R6615, PowerEdge R6625, PowerEdge R670, PowerEdge R740, PowerEdge R740XD, PowerEdge R740XD2, PowerEdge R7415, PowerEdge R7425, PowerEdge R750, PowerEdge R750XA, PowerEdge R750xs, PowerEdge R7515, PowerEdge R7525, PowerEdge R760, PowerEdge R760XA, PowerEdge R760xd2, PowerEdge R760xs, PowerEdge R7615, PowerEdge R7625, PowerEdge R770, PowerEdge R7715, PowerEdge R7725, PowerEdge R840, PowerEdge R860, PowerEdge R940, PowerEdge R940xa, PowerEdge R960, PowerEdge T140, PowerEdge T150, PowerEdge T160, PowerEdge T340, PowerEdge T350, PowerEdge T360, PowerEdge T40, PowerEdge T440, PowerEdge T550, PowerEdge T560, PowerEdge T640, VMware ESXi 7.x, VMware ESXi 8.x ...
Article Properties
Article Number: 000207170
Article Type: How To
Last Modified: 09 May 2025
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.