Hello, I have a healthy three-node PVE 3.2 cluster running. I want to implement VLAN tagging so that I can virtualize hosts that are on a different VLAN where the IP's cannot change. The hosts are Windows 2008R2.
On the VM config I define the VLAN tag of 618 when creating the network config. The Windows server boots and PVE creates two network interfaces on the PVE host: bond0.618 and vmbr0v618. The host boots, and the network is configured for the 618 VLAN, but it does not have network access.
I'm told by the network admins that the 618 VLAN has been trunked to the native VLAN/port that the PVE host is on. All of the network gear is Cisco managed switches.
The bonded interface of bond0 comprises two interfaces, eth0 and eth1 in active-backup mode. vmbr0 is bridge to bond0 on the 437 VLAN, and is functioning as expected. All other VM's on the 437 VLAN function correctly.
Am I missing a step? Can anyone give me a clue what might be wrong? Thanks!
On the VM config I define the VLAN tag of 618 when creating the network config. The Windows server boots and PVE creates two network interfaces on the PVE host: bond0.618 and vmbr0v618. The host boots, and the network is configured for the 618 VLAN, but it does not have network access.
I'm told by the network admins that the 618 VLAN has been trunked to the native VLAN/port that the PVE host is on. All of the network gear is Cisco managed switches.
The bonded interface of bond0 comprises two interfaces, eth0 and eth1 in active-backup mode. vmbr0 is bridge to bond0 on the 437 VLAN, and is functioning as expected. All other VM's on the 437 VLAN function correctly.
Am I missing a step? Can anyone give me a clue what might be wrong? Thanks!