The server has networking, everything appears to be ok on the server's side.
But none of our VMs are getting DHCP assignments after the upgrade to v4.2
FWIW, I don't know why there's a VLAN20 - we had one at one point but it is no longer in service.
I don't see how to remove it. Is that the problem?
But none of our VMs are getting DHCP assignments after the upgrade to v4.2
Code:
pveversion -v
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie
Code:
cat interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!
auto lo
iface lo inet loopback
#auto eth0
#iface eth0 inet dhcp
auto eth1
iface eth1 inet manual
iface eth2 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.28.200
netmask 255.255.255.0
gateway 192.168.28.1
bridge_ports eth1
bridge_stp off
bridge_fd 0FWIW, I don't know why there's a VLAN20 - we had one at one point but it is no longer in service.
I don't see how to remove it. Is that the problem?