HPE Morpheus VM Essentials Software
1870471 Members
3378 Online
110549 Solutions
New Discussion

VME Essentials

 
imran242424
Senior Member

VME Essentials

Hi I have deployed two node setup for VM Essentials version 9.02 latest release and 3rd node as a virtual machine for witness node

Deployment completed sucessfully and when i have also deployed the VME Manager as well

in my network setup we are not using any VLAN just deployed with 2 nics created bond at the time of depoyment of hypervisor and there is no VLAN in our network 

I am unable to create a virtual switch in VME Manager

Please advise.

4 REPLIES 4
CalvinZito
Neighborhood Moderator

Re: VME Essentials

My Copilot Notebook based on the v9.0.0 documentation says this:

The lack of VLANs is not by itself a problem. VM Essentials supports an untagged network: for an HVM Standard Network, VLAN ID 0 is transparent/pass-through mode.

The more likely issue is that VM Essentials has not properly discovered the bond interface on both HVM hosts. The documentation specifically says the OVS Bridge Domain virtual switch must be backed by a host interface such as bond0, and the interface selected must exist on every host in the cluster.

What I would check

  1. Go to Administration > Integrations > Plugins and verify HVM Networking Plugin is present and Enabled. It should be installed automatically. 
  2. Go to Infrastructure > Network > Routers > + Add > OVS Bridge Domain. Select the HVM cluster and choose Create New for Host Bridge. The Network Interface field should offer the bond that was created during deployment, such as bond0. 
  3. If bond0 does not appear in that Network Interface list, that is where I would focus. The documentation says the list is populated from physical, bonded, and VLAN interfaces discovered on the cluster hosts. It also specifically calls out incomplete bond discovery as a condition that prevents network mapping. 
  4. Check Infrastructure > Activity for pending or failed AddWorker activity. The documented troubleshooting steps say to confirm that VM Essentials has discovered the required bond interfaces and that the host inventory shows the expected interfaces. 
  5. Also check Administration > Health > Morpheus Logs and search for HvmNetwork. That is the documented log filter for HVM Networking Plugin problems. 
One other useful detail: the earlier HVM networking documentation says VM Essentials may not discover interfaces that aren't represented correctly in netplan. The interfaces need to be present in netplan, applied on the hosts, and then the HVM cluster refreshed in the UI. 

So I would not add a VLAN just to solve this. First verify that the bond, presumably bond0, is visible to VM Essentials on both physical HVM nodes. Once the OVS Bridge Domain is successfully created on that bond, you can create the HVM Standard Network with VLAN ID 0 for untagged/pass-through traffic. 

In the v9.0.0 VM Essentials documentation, these sections are were the response came from:


I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
imran242424
Senior Member

Re: VME Essentials

I tried all the troubleshooting steps which was suggested but still no luckPicture1.pngPicture2.pngPicture3.pngPicture4.png

dya
Trusted Contributor

Re: VME Essentials

I apologize if my understanding is insufficient.

It appears that there is already a configuration that looks like a Linux bridge (br0) in 50-cloud-init.yaml. 50-cloud-init.yaml is a file generated during the host OS installation, and I have never seen such a configuration in it before. Was it configured manually? That is the first thing I am curious about.

Since an interface already in use by another OVS bridge cannot be added to a new OVS bridge, bond0, which is already used by br0, might not be usable. What I have verified in the past is that an interface used by another OVS bridge cannot be used in a newly created OVS bridge; however, since it is not a Linux bridge in this case, I apologize if I am mistaken.

Additionally, network configurations such as OVS bridges and Libvirt networks are easier to set up during cluster creation.

Since v9.0.2 may be helpful for installation and other tasks, I recommend checking it out:https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.html

Also, the following might be helpful as well:https://support.hpe.com/hpesc/public/docDisplay?docId=sd00008401en_us&page=GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.html#ariaid-title1

CalvinZito
Neighborhood Moderator

Re: VME Essentials

Thanks, the screenshots are helpful. Both hosts show eno1 and eno2 combined into bond0, and bond0 is already being used by the Linux management bridge. I also notice the bridge is named mgmt on node1 but br0 on node2.
 
The VM Essentials documentation states that creating a new OVS Bridge Domain requires an available physical interface or bond, and the selected interface must exist on every host in the cluster. Based on these screenshots, I don't see an unused interface or bond available on either host.
Could you also share the HvmNetwork log entries from Administration > Health > Morpheus Logs immediately after attempting to create the OVS Bridge Domain? That should confirm whether the existing bond/bridge configuration is what is causing the failure. The documentation specifically recommends those logs for HVM Network Plugin troubleshooting.

Sources: Infrastructure → Clusters → HVM clusters → HVM Cluster Networking → Adding Routers, HVM Network Plugin → Prerequisites,  HVM Network Plugin → Creating an OVS Bridge Domain Virtual Switch

The HVM Network Plugin Prerequistites section says:
  • OVS must be installed and running on each host.
  • An OVS Bridge Domain must exist for Standard Networks.
  • The bridge must be backed by a host network interface, with examples such as mgmt or bond0.
  • Suitable interfaces must be available on the cluster hosts for the applicable network types.


 


I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo