How to configure non-Management networks

[kurotan]

I don't think the documentation provides detailed instructions, so I'd like to know the procedure.

After running the hpe-vm command, configure the network and create a bridge interface.

I set it up by loading an xml file with virsh net-create.

The network I created was also created on the manager screen, but could you tell me the correct method?

[Arnout Verbeken]

Can you please elaborate what you are trying to do...?

If you just want to specify dedicated nics for VM compute traffic:

- create a bond over the NICs. (don't give it an IP)

-in VME:

**Go to Infrastructure / Network / Router / Add.  Fill in all required fiels and select the bond you created

** Go to Clusters / Networks / Add.  Add the VLANs you want to use for compute.

[kurotan]

I would like to create an interface other than the "Management" interface that is created by default.

The way I added the network was as follows:

After creating a Bond interface using the "Configure Network" command of the "hpe-vm" command, I also created a Bridge interface.
For the Bridge interface, I assigned an IP address and bond interface, and enabled openvswitch.
I then added a network with the following steps.

Create a network with the "virsh net-define" command.
```
virsh # net-define --file /opt/backend-network.xml
Network Backend defined from /opt/backend-network.xml
```
Example) backent-network.xml file
```
<network>
<name>Backend</name>
<forward mode='bridge'/>
<bridge name='backend'/>　#Enter the bridge name you set earlier here
<virtualport type='openvswitch'/>
</network>
```

A network called Backend is created in the cluster.

Start the network.
```
virsh # net-start Backend
Network Backend started
```

Set automatic startup.
```
virsh # net-autostart Backend
Network Backend marked as autostarted
```

The method you taught me seemed to produce similar results.
The results of "virsh net-list" were similar.
Also, the results of "virsh net-info <name>" were similar, both with my method and the method you taught me.

```

virsh # net-info Backend
Name: Backend
UUID: 9695c412-40d1-4af3-bbca-a2f1454822ab
Active: yes
Persistent: yes
Autostart: yes
Bridge: backend

virsh # net-info Backend10G1
Name: Backend10G1
UUID: 96bbde6a-9ca0-4627-bdbb-9fc73433d0de
Active: yes
Persistent: yes
Autostart: yes
Bridge: backend10g1

```

** Go to Clusters / Networks / Add. Add the VLANs you want to use for compute.

I set the VLAN ID and added a network, but the interface of the Mac address assigned to the VM was not displayed on the host server as a VLAN interface. Similar to vSphere vSwitch, if you set a VLAN on the switch side (network), VLAN settings are not required on the VM OS, and the port to which that interface on the hypervisor host is connected is set as a Trunk port, is that correct?

[mnavada]

Hi Kurotan,

Could you please share your email ID? So, will send the document which explains easy way to configure the non-management network in HPE-VM. Due to some  technical issues, I am unable to attach the document here. 

[Arnout Verbeken · Accepted solution]

I understand you were able to create a bridge and add vlans via the correct way in the GUI.

You are correct that your VM NIC needs to be untagged.  You are correct that the physical ports used by the bond/bridge need to be set in trunk.  You however do NOT need to add any vlans directly to the bond/bridge via netplan.  You just add the vlans in the Web GUI under Clusters/Networks.

Where are you looking for the MAC address on the host itself?  Did you install the VirtIO drivers in the VM OS (assuming windows)?

[kurotan]

The VM is running on Linux.

I check from the OS with the "ip a" command.

I also check from the OS on the hypervisor host with the "ip a" command.

I check from the VM's network tab in the manager.

[kurotan]

Do you require an email address? Can't you send to Box?