5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Hello @hienle, It looks like a similar issue seen earlier. Upgrade AOS to versions such as "5.17/5.10.10/5.15.1/5.16.1" or higher before upgrading the firmware. Hi @Nashma , I am sorry for my previous post, actually, the AOS version is 5.10.10.2 LTS (not 5.10.0.2) and it looks like the issue has already been resolved on this AOS version?
@Nashma One question about the firmware package used for darksite LCM: I downloaded the package named lcm_dark_site_bundle_2.3.1.3.18618.tar.gz and extracted it to the IIS root folder. Is this the only package needed to upgrade firmware on DX platform? Do I need anything else? By the way, I tried downloading the Foundation package to test the LCM web server and it ran smoothly so I am thinking about lacking of doing something in order to successfully upgrade firmware on DX.
Hi @Nashma Have a good day. I have tried upgrading AOS from 5.10.10.2 to 5.15.1.1 and unfortunately, nothing changed. On the other hand, it is worse than before as the DX now cannot detect the Foundation package in the LCM server (when the AOS was 5.10.10.2, it could detect the a newer Foundation version in the LCM).
For updating information for this case: the current LCM 2.3.2 is having a bug that prevents HPE DX cluster from accepting the latest 2020.03 version for upgrade from 2019.03 version. This bug will be fixed in the upcoming LCM 2.3.3.
Basic workflow on how to start an AHV node- Log on to AHV host with SSH. Find the name of Controller VM (cvm) Determine if CVM is running. If the CVM is shut off, start it. If the node is in maintenance mode, Log on to the CVM of this host and take the node out of the maintenance mode. Log on to another CVM of this cluster with SSH and check if all services are up on all the CVMs. In the step 5, if the node is in maintenance mode, its CVM will be also in the maintenance state(?!) and will not able to contact the service serving for the NCLI command. So, I think there is no way but login to other CVM and run the command to take the node out of maintenance mode.
Basically the manage_ovs command will recreate the bond interface so you might get the link down in 1 or 2 seconds. What the “recreate” means is that it will delete the current bond interface and then add the uplinks to a newly created bond interface based on the parameters you provide.So my recommendation is that you should put the host into maintenance mode before doing anything relates to network configuration.
The reason why Foundation fails to mount Phoenix images may vary due to some specific circumstances. It might be the problem of network config, the IPMI problem and etc.It could be helper if you uploaded some screenshots or error messages or logs around this
Hi @Alona As this is a standalone node so I don’t think I would be allowed to run the ncc command.
Hi @Alona I might be wrong but I meant that as the NCC command requires the cluster running so for standalone node, I am not able to run it. I will try running the smartctl command you provided but before that, let me confirm a little bit. In G6 model, the sda belongs to the one of 2 SSDs disk, in G7, is there any difference?And in G7 model, 2 M2 drives are running in RAID1. I don’t know exactly they are being run by soft-RAID or hard-RAID, how can I check which partition is from M2 RAID?
Hi @Alona It’s is a single-node only and will be used for cluster expansion.I will get back to you about the smartctl command result later after confirmation.
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.