Hi,
It will be greatly appreciated if someone can confirm / clarify whether each vmbr need to have an IP assigned
Here is a scenario:
- blade server with 2 NICs
- 2 VLANs - one for management one for VMs
Solution:
create a bonded interface "bond0" between the 2 NICS
create 2 interfaces bond0.2 ( vlan2) bond0.3 ( vlan3)
create 2 vmbr and bridge them to the above interfaces
The above works fine as long as I allocate an IP to each vmbr
But I do not need an IP for the vmbr( bridge) used by my VMs
Question:
Is it possible to create a bridge/vmbr on a bonded interfaces and a specific VLAN without assigning it an IP ??
pveversion --verbose
pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1
It will be greatly appreciated if someone can confirm / clarify whether each vmbr need to have an IP assigned
Here is a scenario:
- blade server with 2 NICs
- 2 VLANs - one for management one for VMs
Solution:
create a bonded interface "bond0" between the 2 NICS
create 2 interfaces bond0.2 ( vlan2) bond0.3 ( vlan3)
create 2 vmbr and bridge them to the above interfaces
The above works fine as long as I allocate an IP to each vmbr
But I do not need an IP for the vmbr( bridge) used by my VMs
Question:
Is it possible to create a bridge/vmbr on a bonded interfaces and a specific VLAN without assigning it an IP ??
pveversion --verbose
pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1