HPE VME (VM & VME Manager is not powering ON)

[manishciinfo]

I have configured VME with a 3-node cluster. After shutting down Node 1, the VM and VME Manager successfully moved to Node 3. However, after powering Node 1 back on, both VMs (VM and VME Manager) were shut down and are not powering on.

Also we have tried  to VM power on  to Node 3 but not luck..

Please find attached screenshot for your reference (PFB). Kindly check and advise on the resolution.

[dya]

When you run the following command on nodes 1, 2, and 3 to check, what is the situation?

# virsh list --all

Seeing the “Input/Output error” message makes me wonder if the virtual machine is running or already started on another node.
If that were the case, it would be strange that the virtual machine is visible on hpe-vm.

Also, I'm curious—is the cluster a Ceph cluster? Or is it a standard HVM cluster?

※Apologies if this is unclear due to machine translation.

[manishciinfo]

Hi 

I have run the vrish command on all nodes. The VME Manager shows:

• Node 1: Running

• Node 3: Shutdown

Additionally, the VME IP is pinging successfully, but I am unable to access it via a browser. The error displayed is: “This site can’t be reached.”

Kindly advise on the next steps to resolve this issue.

.

[dya]

We have confirmed that “vmemanager” is running on Node 1.

If the ping for “vmemanager” is OK, the OS appears to be booted. Please log in to the manager via SSH/virsh console and try the following:

# morpheus-ctl status

If not all show “run”, please try the following commands sequentially:

# morpheus-ctl stop
# morpheus-ctl status
# morpheus-ctl start
# morpheus-ctl status

It's puzzling that “vmemanager” is also present on Node 1. By the way, is this a Ceph cluster? Or a standard HVM cluster?
I can't recall if it was the same issue, but I've seen a similar phenomenon on a Ceph cluster before. We didn't resolve it at that time.

Translated with DeepL.com (free version)

※ I'm attaching the command execution results from the test environment for reference.

[manishciinfo]

Hi

Previously, the VME Manager was running on Node 1. I restarted Node 1 and tried to start the VME Manager, but it is still not starting.

Currently, the VME Manager shows on both Node 1 and Node 3, but the issue persists on both nodes.

For reference, I had created a three-node cluster from the VME Manager.

Kindly advise on the next steps to bring the VME Manager online.

Also 

[Arnout_Verbeken]

You have I/O errors, so something is not correct with your storage.

What storage do you use?

I fear this will be one for Peter via the support channel.

[manishciinfo]

Hi

I am using HPE MSA2060.

[manishciinfo]

Hi Team,

I have removed the existing setup and reinstalled HVM and VME Manager from scratch. Current setup details:

• VME Manager is running on Node 1.

• One Windows VM is running on Node 2.

Observations:

1. Manual migration of the Windows VM from Node 2 → Node 3 was successful.

2. After powering off Node 3, the Windows VM migrated successfully to another node.

3. However, when we powered ON Node 3 again, the Windows VM and VME Manager powered off automatically and became inaccessible. We had to power it on manually.

4. Additionally, manual migration of the VME Manager VM is failing.

PFA screenshot for your reference (FYR) and provide solution.

[manishciinfo]

Dear Team,

PFB my queries. Kindly provide the solution and detailed steps:

a. Our VME Manager is not migrating manually and the task fails. Please confirm if there are any standard steps for migration of the VME Manager from one node to another Node.

b. When I power off one node and then power it on again, both VME Manager and Windows VM shut down automatically. Please confirm if there is any standard process to validate failover in this case.

c. Please confirm the location of VME Manager and VM configuration files (similar to how VMware stores VMX files).

Request your guidance and step-by-step resolution for the above.

[PeterTzvetanov]

Hello Manishciinfo,

send a mail to hpe-sw-trial-vmessentials@hpe.com and we will have a look in a remote session.

With regards

[manishciinfo]

Dear HPE Team,

Due to an unavoidable situation, I have shut down the infrastructure.

Once the infrastructure is powered on, I will update you accordingly.