Hi,
I`m runnig a Proymox Backup Servas as a VM in PVE enviroment. The PS always looses LAN connection from time to time. Everytime when the VM looses connection the System log of the PVE shoes the message:
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 1(fwln203i0) entered blocking state
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 1(fwln203i0) entered forwarding state
How can I prevent this?
Regards
I`m runnig a Proymox Backup Servas as a VM in PVE enviroment. The PS always looses LAN connection from time to time. Everytime when the VM looses connection the System log of the PVE shoes the message:
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 1(fwln203i0) entered blocking state
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 1(fwln203i0) entered forwarding state
Code:
Jun 05 14:50:31 NAB6 qm[292916]: start VM 203: UPID:NAB6:00047834:001DC724:66605F17:qmstart:203:root@pam:
Jun 05 14:50:31 NAB6 qm[292910]: <root@pam> starting task UPID:NAB6:00047834:001DC724:66605F17:qmstart:203:root@pam:
Jun 05 14:50:31 NAB6 kernel: sdb: sdb1 sdb2
Jun 05 14:50:31 NAB6 kernel: sda: sda1 sda2
Jun 05 14:50:31 NAB6 systemd[1]: Started 203.scope.
Jun 05 14:50:31 NAB6 kernel: tap203i0: entered promiscuous mode
Jun 05 14:50:31 NAB6 kernel: vmbr0: port 11(fwpr203p0) entered blocking state
Jun 05 14:50:31 NAB6 kernel: vmbr0: port 11(fwpr203p0) entered disabled state
Jun 05 14:50:31 NAB6 kernel: fwpr203p0: entered allmulticast mode
Jun 05 14:50:31 NAB6 kernel: fwpr203p0: entered promiscuous mode
Jun 05 14:50:31 NAB6 kernel: vmbr0: port 11(fwpr203p0) entered blocking state
Jun 05 14:50:31 NAB6 kernel: vmbr0: port 11(fwpr203p0) entered forwarding state
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 1(fwln203i0) entered blocking state
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 1(fwln203i0) entered disabled state
Jun 05 14:50:31 NAB6 kernel: fwln203i0: entered allmulticast mode
Jun 05 14:50:31 NAB6 kernel: fwln203i0: entered promiscuous mode
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 1(fwln203i0) entered blocking state
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 1(fwln203i0) entered forwarding state
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 2(tap203i0) entered blocking state
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 2(tap203i0) entered disabled state
Jun 05 14:50:31 NAB6 kernel: tap203i0: entered allmulticast mode
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 2(tap203i0) entered blocking state
Jun 05 14:50:31 NAB6 kernel: fwbr203i0: port 2(tap203i0) entered forwarding state
Jun 05 14:50:31 NAB6 qm[292910]: <root@pam> end task UPID:NAB6:00047834:001DC724:66605F17:qmstart:203:root@pam: OK
Jun 05 14:51:21 NAB6 snmpd[1149]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
Jun 05 14:52:21 NAB6 snmpd[1149]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
Jun 05 14:53:21 NAB6 snmpd[1149]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
Jun 05 14:53:28 NAB6 pvedaemon[252800]: <root@pam> successful auth for user 'root@pam'
How can I prevent this?
Regards