vmbr0: port 10(tap109i0) entering disabled state

[fcukinyahoo]

This can not be good. I have too many disconnects from ssh clients. Below started happening in kernel log recently ~~ 2weeks. The system was at 3.0. when the first time it started happening. Updated to 3.1 no change. It was working beautifully for over a year Any idea how to solve this issue?

Thanks in advance...

root@proxmox:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

Jan 19 23:37:35 proxmox kernel: vmbr0: no IPv6 routers present
Jan 19 23:37:35 proxmox kernel: eth0: no IPv6 routers present
Jan 19 23:37:36 proxmox kernel: device tap100i0 entered promiscuous mode
Jan 19 23:37:36 proxmox kernel: vmbr0: port 2(tap100i0) entering forwarding state
Jan 19 23:37:41 proxmox kernel: venet0: no IPv6 routers present
Jan 19 23:37:41 proxmox kernel: device tap101i0 entered promiscuous mode
Jan 19 23:37:41 proxmox kernel: vmbr0: port 3(tap101i0) entering forwarding state
Jan 19 23:37:45 proxmox kernel: device tap102i0 entered promiscuous mode
Jan 19 23:37:45 proxmox kernel: vmbr0: port 4(tap102i0) entering forwarding state
Jan 19 23:37:47 proxmox kernel: tap100i0: no IPv6 routers present
Jan 19 23:37:49 proxmox kernel: kvm: emulating exchange as write
Jan 19 23:37:49 proxmox kernel: device tap104i0 entered promiscuous mode
Jan 19 23:37:49 proxmox kernel: vmbr0: port 5(tap104i0) entering forwarding state
Jan 19 23:37:51 proxmox kernel: tap101i0: no IPv6 routers present
Jan 19 23:37:54 proxmox kernel: device tap105i0 entered promiscuous mode
Jan 19 23:37:54 proxmox kernel: vmbr0: port 6(tap105i0) entering forwarding state
Jan 19 23:37:56 proxmox kernel: tap102i0: no IPv6 routers present
Jan 19 23:37:59 proxmox kernel: device tap106i0 entered promiscuous mode
Jan 19 23:37:59 proxmox kernel: vmbr0: port 7(tap106i0) entering forwarding state
Jan 19 23:38:00 proxmox kernel: tap104i0: no IPv6 routers present
Jan 19 23:38:04 proxmox kernel: tap105i0: no IPv6 routers present
Jan 19 23:38:05 proxmox kernel: device tap107i0 entered promiscuous mode
Jan 19 23:38:05 proxmox kernel: vmbr0: port 8(tap107i0) entering forwarding state
Jan 19 23:38:09 proxmox kernel: device tap108i0 entered promiscuous mode
Jan 19 23:38:09 proxmox kernel: vmbr0: port 9(tap108i0) entering forwarding state
Jan 19 23:38:10 proxmox kernel: tap106i0: no IPv6 routers present
Jan 19 23:38:15 proxmox kernel: device tap109i0 entered promiscuous mode
Jan 19 23:38:15 proxmox kernel: vmbr0: port 10(tap109i0) entering forwarding state
Jan 19 23:38:15 proxmox kernel: tap107i0: no IPv6 routers present
Jan 19 23:38:20 proxmox kernel: tap108i0: no IPv6 routers present
Jan 19 23:38:22 proxmox kernel: device tap110i0 entered promiscuous mode
Jan 19 23:38:22 proxmox kernel: vmbr0: port 11(tap110i0) entering forwarding state
Jan 19 23:38:25 proxmox kernel: tap109i0: no IPv6 routers present
Jan 19 23:38:28 proxmox kernel: device tap111i0 entered promiscuous mode
Jan 19 23:38:28 proxmox kernel: vmbr0: port 12(tap111i0) entering forwarding state
Jan 19 23:38:32 proxmox kernel: tap110i0: no IPv6 routers present
Jan 19 23:38:35 proxmox kernel: device tap113i0 entered promiscuous mode
Jan 19 23:38:35 proxmox kernel: vmbr0: port 13(tap113i0) entering forwarding state
Jan 19 23:38:38 proxmox kernel: tap111i0: no IPv6 routers present
Jan 19 23:38:46 proxmox kernel: tap113i0: no IPv6 routers present
Jan 20 00:23:40 proxmox kernel: vmbr0: port 10(tap109i0) entering disabled state
Jan 20 00:23:40 proxmox kernel: vmbr0: port 10(tap109i0) entering disabled state
Jan 20 00:27:44 proxmox kernel: device tap109i0 entered promiscuous mode
Jan 20 00:27:44 proxmox kernel: vmbr0: port 10(tap109i0) entering forwarding state
Jan 20 00:27:55 proxmox kernel: tap109i0: no IPv6 routers present
Jan 20 00:44:14 proxmox kernel: vmbr0: port 10(tap109i0) entering disabled state
Jan 20 00:44:14 proxmox kernel: vmbr0: port 10(tap109i0) entering disabled state
Jan 20 00:52:44 proxmox kernel: vmbr0: port 2(tap100i0) entering disabled state
Jan 20 00:52:44 proxmox kernel: vmbr0: port 2(tap100i0) entering disabled state
Jan 20 00:56:46 proxmox kernel: device tap100i0 entered promiscuous mode
Jan 20 00:56:46 proxmox kernel: vmbr0: port 2(tap100i0) entering forwarding state
Jan 20 00:56:57 proxmox kernel: tap100i0: no IPv6 routers present
Jan 20 00:59:31 proxmox kernel: vmbr0: port 2(tap100i0) entering disabled state
Jan 20 00:59:31 proxmox kernel: vmbr0: port 2(tap100i0) entering disabled state
Jan 20 00:59:50 proxmox kernel: device tap100i0 entered promiscuous mode
Jan 20 00:59:50 proxmox kernel: vmbr0: port 2(tap100i0) entering forwarding state
Jan 20 01:00:00 proxmox kernel: tap100i0: no IPv6 routers present
Jan 20 03:23:46 proxmox kernel: hrtimer: interrupt took 4373 ns
Jan 20 20:43:49 proxmox kernel: vmbr0: port 11(tap110i0) entering disabled state
Jan 20 20:43:49 proxmox kernel: vmbr0: port 11(tap110i0) entering disabled state

I also saw this on front end gui under node's network section.

"Pending changes (Please reboot to activate changes)"
--- /etc/network/interfaces	2012-07-31 20:02:17.000000000 -0400
+++ /etc/network/interfaces.new	2014-01-20 00:12:24.000000000 -0500
@@ -1,6 +1,10 @@
+# network interface settings
 auto lo
 iface lo inet loopback
 
+auto eth0
+iface eth0 inet manual
+
 auto vmbr0
 iface vmbr0 inet static
 	address 192.168.1.10
@@ -9,3 +13,4 @@
 	bridge_ports eth0
 	bridge_stp off
 	bridge_fd 0
+

 

[sunghost]

Hello,
is there any solution? i have the same with usb nic on wan connected. first the kernel.log say entering forwarding state and than entering disabled state and i cant connect through this nic. if i reboot the whole machine all is ok.

 

[unze]

Sorry for digging up an old thread, hope that helps someone.

I got the same problems with HP MicroServer Gen8 (Broadcom BCM5720 network cards) and Proxmox 4.1

I ended up disabling all offload features on all network cards

apt-get install ethtool
ethtool --offload eth0 gso off tso off sg off gro off

then reboot your host

now everything is fine

 

[Dvizhok99]

Sorry for digging up an old thread, hope that helps someone.

I got the same problems with HP MicroServer Gen8 (Broadcom BCM5720 network cards) and Proxmox 4.1

I ended up disabling all offload features on all network cards

apt-get install ethtool
ethtool --offload eth0 gso off tso off sg off gro off

then reboot your host

now everything is fine

Hello.
I have still a problem? What else can I do?