Cluster doesn't start unable to reach node where genesisi is starting

  • 17 November 2015
  • 11 replies
  • 5586 views

Badge +5
Dears,

i have below situation happened to my nutanix block
my college changged hostname of all ESXi servers and then try to change CVM IPs without stopping cluster after that he rebooted CVM but cluster is not started with error message unable to reach node where genesis is started i have check genesis service in all node and it's running correclty and all nodes are reachable suing hosts in /etc/hosts file and all of them in same lan how can i get original hostname of esxi and does change of it's hostname cause this issue and also hos i resolve this issue

thanks in advance

This topic has been closed for comments

11 replies

Userlevel 6
Badge +29
What's the block serial number?
Badge +5
it's demo unit and license expired from 2 weeks So i am not able to open support case
Userlevel 6
Badge +29
You should not have had to re-foundation the cluster.

Did you open a support case?

If so, can you please send me your ticket number to jon@nutanix.com? Happy to look into it.

If not, please consider doing so in the future, we're here to help !
Badge +5
no i didn't find solution to the issue So i have re-image all nodes and re-create cluster using foundation VM thanks you all for your Help
Userlevel 7
Badge +34
Hi 

Did you find a solution to your issue?
Badge +5
i already done this steps and not suceed to start cluster again after that i re-imaged cluster
Userlevel 2
Badge +17
How about:
1. SSH to new CVM IP and then change it back to orginial IP? You can do this by just "sudo ifconfig eth0 IP/netmask" command

2. Then restart the cluster again?

If not succeeded, I am afraid of having to recreate cluster again.
Userlevel 6
Badge +29
If I had to bet, it would be that you tried changing the IP Addresses against the documented IP Change process, and the cluster didn't like that.

Please open a support ticket and we'll help you fix it.
Badge +5
Thanks Alot for your update , but i am sure that we didn't delete internal switch
Userlevel 6
Badge +29
Ahmed,
Is this for a production Nutanix install?

If so, I'd recommend that you open a ticket on portal.nutanix.com, so we can help you power through your issues and get you stable again.
Userlevel 1
Badge +9
Hello ,

Based on the description you've provided, it does sound like there may have been a removal or conversion of the Nutanix internal vSwitch on the ESXi hosts.

Please review the following KB on the Nutanix Support Portal.
http://portal.nutanix.com/kb/1129

Cheers, Art