topic Bond Creation post VME install in HPE Morpheus VM Essentials Software

Bond Creation post VME install

mouradb — Mon, 30 Mar 2026 14:32:24 GMT

have several vLAN presented to 2 Nic Interfaces, I need to create a Bond and add these two nics to it, can we do this after we installed VME rather then reinstalling everything from scratch?

Re: Bond Creation post VME install

controles — Mon, 30 Mar 2026 14:02:59 GMT

Hi, In VME (HPE Morpheus VM Essentials), network bonding is not created or modified by the VME Manager after installation. If the server was initially installed with single NIC interfaces and later a bonded configuration is required, the bond must be created at the host operating system level. VME Manager only consumes existing network configurations and does not create or change Linux bonds or bridges. For Linux-based nodes, the supported approach is: - Configure the bond on the node using standard OS networking tools. - Create or update the bridge on top of the bonded interface if required. - Restart networking services as needed. - Once the bond and bridge exist on the node, VME Manager can make use of them. Reinstalling VME is not required, but networking changes must be handled outside of VME Manager and carefully validated to avoid connectivity loss. Hope this helps clarify the behavior.

Re: Bond Creation post VME install

Arnout_Verbeken — Mon, 30 Mar 2026 21:02:27 GMT

Another supported way is to use hpe-vm tool to create the bond (and vlan tagging if needed).

Keep however in mind that tagging in the OS (with netplan or hpe-vm) is only needed for management network. You should add your compute networks (vlans) from within the manager (during cluster creation or afterwards via "Infrastructure - Networks).

But bonds should always be created in the OS. hpe-vm tool is most easy. Or you use netplan (/etc/netplan and adapt files)

Re: Bond Creation post VME install

controles — Mon, 30 Mar 2026 21:30:27 GMT

To complement the previous responses, VME does not automatically create or modify network bondings after installation when the system was initially deployed using a single NIC. This behavior is expected and consistent with VME’s design scope.

VME primarily focuses on system monitoring, inventory, and lifecycle management, while network constructs such as bonding, LACP, and VLAN configuration are intended to be handled at the OS and network layer. As mentioned earlier, these configurations must be applied manually when required.

From a best‑practice perspective, especially in production environments, network bonding and redundancy should be defined and validated prior to onboarding the server into VME. This ensures predictable connectivity and avoids post‑installation network changes.

Aligning network design upfront and treating VME as a management and visibility platform leads to more consistent and supportable deployments.