- Community Home
- >
- Software
- >
- HPE Morpheus Software
- >
- HPE Morpheus VM Essentials Software
- >
- VME Essentials
Categories
Company
Local Language
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
2 weeks ago
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
2 weeks ago
Re: VME Essentials
My Copilot Notebook based on the v9.0.0 documentation says this:
bond0, and the interface selected must exist on every host in the cluster.What I would check
-
Go to Administration > Integrations > Plugins and verify HVM Networking Plugin is present and Enabled. It should be installed automatically.
-
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. -
If
bond0does 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. -
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.
-
Also check Administration > Health > Morpheus Logs and search for
HvmNetwork. That is the documented log filter for HVM Networking Plugin problems.
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:
-
Integration Guides → Networking Integrations → HVM Network Plugin → Prerequisites
Page 419
Supports the statement that an OVS Bridge Domain virtual switch must be backed by a host network interface, withmgmtandbond0given as examples. It also says the HVM Network Plugin is automatically installed and enabled. -
Integration Guides → Networking Integrations → HVM Network Plugin → Adding the HVM Networking Plugin
Page 420
Documents checking Administration > Integrations > Plugins and confirming that HVM Networking Plugin appears as Enabled. -
Integration Guides → Networking Integrations → HVM Network Plugin → Creating an OVS Bridge Domain Virtual Switch
Pages 420–422, especially 421
This is the key reference for creating the bridge. It documents Infrastructure > Network > Routers > + Add > OVS Bridge Domain, selecting Create New, and choosing the Network Interface. It explicitly says the interface list is populated from discovered physical, bonded, and VLAN interfaces and that the selected interface must exist on every host in the cluster. -
Integration Guides → Networking Integrations → HVM Network Plugin → Creating HVM Network → Creating HVM Standard Network
Pages 424–426, especially 425
This is the strongest citation for your VLAN statement. Under VLAN ID, it says:“Use VLAN ID 0 to enable transparent (pass-through) mode." -
Integration Guides → Networking Integrations → HVM Network Plugin → Creating HVM Standard Network → VLAN Modes and Traffic Behavior in HVM Standard Networks
Pages 427–428
Provides additional explanation of Access, Hybrid, and Trunk-only behavior, including untagged traffic and transparent mode. -
Integration Guides → Networking Integrations → HVM Network Plugin → Viewing the HVM Networking Plugin Status → Viewing HVM Networks, Virtual Switches, and Plugin Logs
Page 443
Documents checking Administration > Health > Morpheus Logs and filtering onHvmNetwork. -
Integration Guides → Networking Integrations → HVM Network Plugin → Troubleshooting → New Host Does Not Receive Networks
Page 444
This is the key troubleshooting source for your bond-discovery recommendation. It explicitly says that if bond interface discovery remains incomplete, Morpheus cannot complete network mapping. It recommends checking AddWorker jobs, confirming discovery of required bond interfaces, checking host inventory, and reviewing Infrastructure > Activity for failures or alarms. -
And, if
bond0is missing, HVM Cluster Networking, pp. 80–81 for the netplan/discovery requirement.
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]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
2 weeks ago
Re: VME Essentials
I tried all the troubleshooting steps which was suggested but still no luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
2 weeks ago
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
2 weeks ago
Re: VME Essentials
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.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
mgmtorbond0. - 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]