vSAN1

 View Only
  • 1.  VSAN 6.7

    Posted Jun 27, 2024 02:47 PM

    Hello you beautiful vsan people,

    Can I get some ideas from you all? Troubleshooting a weird one, one of six 6.7u3 hosts died a few weeks ago but everything had been functioning fine due to only have 1 hit to the fault domain.

    After a reboot, 20/27 vms became invalid and list with a 3 digit number.

    Finally got the host replaced and added to the VSAN (redid the unicast agent list successfully)

    Currently, we have the "Hosts disconnected from VC" health alarm. When viewing the alert via CLI, each host claims all the other hosts are disconnected. (The new host is not listed in the alarm for the 5 existing hosts oddly enough)

    Other than that, the VSAN is still messed up with 305 inaccessible objects lol. We'll probably be rebuilding before there is a reply but I'd love some ideas for my notes.



  • 2.  RE: VSAN 6.7

    Posted Jun 28, 2024 03:16 PM

    First, before you rebuilt the host, did you remove it from inventory or just create a new server with the same name and IP? The failed server needs to be removed from inventory and the rebuilt one added. There is a key, user, etc generated when a host is added to vCenter. These will not exist on a rebuilt host. What was the failure tolerance of your environment set for? If you remove the inaccessible VM from inventory and then find it on the storage, are you able to re-register it?




  • 3.  RE: VSAN 6.7

    Posted Jun 28, 2024 04:02 PM

    Ah this makes sense, we were unable to remove the old host due to vcenter being inaccessible and missing from our datastore. We created a new vcenter after replacing the failed host and added all hosts to the new vcenter.

    With no access to the old Vcenter, are there further steps to take to rebuild the cluster?

    FTT is set for 1, Currently all VMs I can find in the VSAN are accessible, the remaining appeared to be missing.




  • 4.  RE: VSAN 6.7
    Best Answer

    Posted Jun 29, 2024 08:24 AM
    Did you try going to the vCenter server from one of the other host and powering it on before building a new one?

    If it is not available, it sounds like you need to import/migrate the vSAN to the new vCenter. There is a KB for that process.

    <https: knowledge.broadcom.com/external/article/326849/moving-a-vsan-cluster-from-one-vcenter-s.html="">
    Moving a vSAN cluster from one vCenter Server to another<https: knowledge.broadcom.com/external/article/326849/moving-a-vsan-cluster-from-one-vcenter-s.html="">
    knowledge.broadcom.com<https: knowledge.broadcom.com/external/article/326849/moving-a-vsan-cluster-from-one-vcenter-s.html="">
    [X]<https: knowledge.broadcom.com/external/article/326849/moving-a-vsan-cluster-from-one-vcenter-s.html="">




  • 5.  RE: VSAN 6.7

    Posted Jul 10, 2024 11:43 AM

    It was not available but those KBs were very helpful, thank you!