I added a host to the cluster, but the router network configured from the manager does not

[kurotan]

I configured a router from the manager.

I also configured a network with a VLAN on that router.

In the above state, I added a hypervisor host to the cluster.

There were no problems with the network in Management, but the network I added from the manager did not work on the added host.

The added host had already been configured with the same network interface (bond) configuration as the existing host using the hpe-vm command.

Are there any possible causes for this?

[Ranveer]

Hello Kurton,

May i know how was it confirmed? Means network not seen via virsh-net on newly added host?
There were no problems with the network in Management, but the network I added from the manager did not work on the added host

Best Regards

Ranveer

[kurotan]

I set up an instance on a newly added host.

I set up a network with VLAN configured on the VM.

The VM was unable to obtain an IP from the DHCP server.

I checked the switch settings as follows, so there is no problem. (Ports set to Trunk mode)

- I created a VLAN interface for each hypervisor alone, and was able to communicate between the hypervisors.

- I created a teaming interface (VLAN) on the Windows server and plugged it into the same port, and was able to obtain an IP from the DHCP server.

[kurotan]

@Ranveer,

I tried rebuilding the entire environment.

The VMs on Server2 were not able to obtain IP addresses from the DHCP server on Server1, but now they can.

One thing that bothers me is that I had set a VLAN ID in the manager's network settings.
The value in the VLAN ID setting had changed without me noticing.
Is this some kind of bug?

I'll introduce my testing environment.

----------------------------------------

<Environment>
Hosts:
Server1 Ubuntu24.4/VM Essentials 8.0.6
Server2 Ubuntu24.4/VM Essentials 8.0.6

Network:
(Physical/Router/Network)
bond0/Management(Management/Automatically configured when adding a cluster)
bond1/Backend(Manual configuration/NFS Storage Network)
bond2/Backend1g1(Set from Manager)/Backend1g1-100(VLAN100)
bond3/Backend1g2(Set from Manager)/Backend1g2-500(VLAN500)

Storage:
NFS share1
NFS share2
NFS share3

Switch:
VLAN 1 mode access(Management)
VLAN 2 mode access(Backend)
VLAN 100 mode trunk(Backend1g1-100)
VLAN 500 mode trunk(Backend1g3-500)

Instances:
(Name/Host)
DHCP-Server VM/Server1
Linux VM1/Server1
Linux VM2/Server2

Object Storage:
Minio

----------------------------------------

[Ranveer · Accepted solution]

Hello Minio,
If you are still facing issue, please suggest your availability & email id to communicate.
Best Regards

Ranveer

[kurotan]

We found the reason why the VLAN ID had changed.
When I tried to scroll the screen by turning the mouse wheel, the VLAN ID changed.

We're sorry for the fuss, but please be careful everyone.