7 Responses

  1. Gerold Gruber
    Gerold Gruber 5 febbraio 2016 at 23:32 |

    same issue here with fresh set up 3 hosts vsphere6 landscape

    Reply
  2. mikemike6193353
    mikemike6193353 17 febbraio 2017 at 14:40 |

    remove the host from the cluster and re add it

    Reply
  3. Rakesh
    Rakesh 4 maggio 2017 at 5:36 |

    If the service agent of an esxi is down, what will be its status in vsphere client?

    Reply
  4. Bill
    Bill 14 febbraio 2018 at 16:51 |

    I had the same issue, and was able to resolve it by 1. turn off HA 2. disconnect the host. 3. reconnect the host. 4 turn HA back on for the cluster.

    Reply
  5. Vic
    Vic 12 novembre 2018 at 4:48 |

    Same problem here – in our case it turned out to be caused by old data in the hosts file on each of the hosts. When we were on a Windows vCenter we had multiple IP’s (1 for inbound RDP sessions / management traffic and 1 on the same vlan as the hosts’ service consoles). When you migrate to a VCSA you can only use a single IP which is the one in DNS.

    Reply

Lascia un commento

Questo sito usa Akismet per ridurre lo spam. Scopri come i tuoi dati vengono elaborati.

By continuing to use the site, you agree to the use of cookies. more information

The cookies settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then tou are consenting this.

Close