Connecting Cloud Innovators: Building Community at .NEXT 2024
Using LCM to update Foundation to version 5.4 I am finding that it consistently fails on Lenovo hardware.I’ve tried two clusters so far that were both at AOS version 6.5.2 but both LCM updates of Foundation to version 5.4 failed.Ominously there is mention in the Field Installation Giude for Foundation 5.4 (link below) that “Software Update” should not be used to update Foundation on Lenovo platforms, and advises to use the command line instead.It worked when using the command line, so my question is: what’s going wrong when LCM attempts this?https://portal.nutanix.com/page/documents/details?targetId=Field-Installation-Guide-v5_4:fie-upgrade-foundation-vm-c.htmlWhat tends to happen is that most nodes except 1 or 2 are successfully updated, with the remaining node neeing to be done by hand from the command line.
Our 5-node Nutanix Mine with Veeam is using the default 75% as the watchdog capacity.The Nutanix Mine administration guide mentions paramters associated with this:restart_jobs_threshold_percentcancel_jobs_threshold_percentstop_issuing_jobs_threshold_percentand advises customers should contact support if they wish to tweak these.My question is this: Which organisation’s support covers this? Veeam or Nutanix?
We recently performed a cluster shutdown with hardware power off of an AHV cluster running AOS 5.15.5.1.We powered on all the nodes, and waited 10 minutes for the AHV hypervisor to boot and the CVMs to boot and get ready.Even after 30 minutes the CVMs did not recognise the confirmed correct password for the “nutanix” userID during ssh login attempt to any CVM.Fortunately one SSH key had previously been registered into Prism Element, which allowed SSH via this key. The cluster was NOT configured to be locked down.The key owner successfully connected to a CVM via SSH and performed sudo passwd set of the “nutanix” userID to a confirmed password.Despite setting this password, the same CVM still refused to accept the “nutanix” userID and confirmed correct password during SSH password login. I am suspecting that with the cluster service stopped, but with one SSH key present, that the CVMs operate as if lockdown were enabled.Can someone please confirm for this?This prevented the password hol
As seen in this attached screenshot, Prism Central appears to have lost track of this “running” task. Updates of network security rules normally finish very quickly (I think might have clicked an apply button twice after editing a FLOW security policy during on-site FLOW training.) Is this something only Nutanix Support can clear away?
I started a 1-click ESXi HyperVisor upgrade of a 7-node cluster which progressed well and had already successfully upgraded 4 of the nodes, when one of the hosts wasn’t able to enter maintenance mode because one of the VMs was spending too long consolidating a snapshot. After many hours had passed, the remaining 1-click update tasks all appeared to have aborted. I manually resolved the issue involving the guest, and then started the 1-click update again. It prompted for vCenter details, and then created new hypervisor update tasks to update the remainder of the ESXi hosts.These also completed successfully.All Hypervisor update Tasks appear to be completed, and all the ESXi hosts are updated.All NCC checks also pass OK. The cluster is healthy, the Health Icon is green, and Data Resiliencey is OK.Howerver, the CVMs all still believe there is a Hypervisor upgrade in progress:nutanix@NTNX:~$ ncli host ls | egrep 'upgrade|99825' Hypervisor Version : VMware ESXi 6.7.0 build-1749
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.