When trying to upgrade NOS or NCC I'm getting this error: "Error while executing HTTP REST request: Could not connect to Genesis"
The updates have already downloaded. This occurs even if I pick a lower version to upgrade to.
I'm going from 4.1.4 to 4.5.1.2 (NOS) and 2.01 to 2.1.4.
Any ideas? Is there a service I should restart or something?
Thanks!
Mike
Page 1 / 1
Firstly, I'd recommend opening a support ticket on portal.nutanix.com if NX-xxxx gear. If Dell XC, go through dell first.
They can help you through all of this.
Past that, Note that NOS upgrades come with new NCC by default, so you shouldn't have to do it twice, unless you want to do NCC first, then run some health checks, then upgrade NOS.
lastly, genesis might actually be down, you could check by SSHing to any CVM, then do a cluster status.
They can help you through all of this.
Past that, Note that NOS upgrades come with new NCC by default, so you shouldn't have to do it twice, unless you want to do NCC first, then run some health checks, then upgrade NOS.
lastly, genesis might actually be down, you could check by SSHing to any CVM, then do a cluster status.
you could also run "ncc health_checks run_all" while you are in CLI, to see if anything comes up
- Also, I moved this topic out of the CE forums, and to the traditional Nutanix install/config forum.
I'm running through the pain of Dell support now. I figured I'd try the forums while I'm waiting.
When on one of the CVM's, running cluster status shows everything as fine. The other two give me the error "WARNING genesis_utils.py:512 Failed to reach a node where Genesis is up. Retrying... "
Health check is giving me an "Err" when checking all Sata controllers and I'm getting a "Fail" in "Check MTU settings".
Is there a "kickstart genesis" command?? 🙂
When on one of the CVM's, running cluster status shows everything as fine. The other two give me the error "WARNING genesis_utils.py:512 Failed to reach a node where Genesis is up. Retrying... "
Health check is giving me an "Err" when checking all Sata controllers and I'm getting a "Fail" in "Check MTU settings".
Is there a "kickstart genesis" command?? 🙂
yep, allssh genesis restart
Standard disclaimer here, never do anything CLI unless support tells you do, but thats the "kickstart" command, so to speak.
Also, RE Dell support: If you aren't getting the level of support you need, please have them either escalate internally at Dell, or escalate to Nutanix support, and they can get one of our SRE's invovled.
Standard disclaimer here, never do anything CLI unless support tells you do, but thats the "kickstart" command, so to speak.
Also, RE Dell support: If you aren't getting the level of support you need, please have them either escalate internally at Dell, or escalate to Nutanix support, and they can get one of our SRE's invovled.
The problem with Dell support is getting through the three levels of triage before they tell me that they have to get someone to call me back... It's just a pain to get through the initial levels of support.
Understood. It's your call, I'd assume it will naturally bubble up to us after Triage, but if you want or need it to go faster, Just ask to escalate to Nutanix support, and they can do it. They have a well defined process on that.
allssh genesis restart fixed my problem. Thanks for the help. Still waiting for Dell to call me back....
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.