Network Problem

[Nerdy]

Hello,
i'm facing this problem on my server running proxmox, the server goes down often and if i go to /var/log/dmesg of my lxc container i see this:

[96778.325439] IPv6: ADDRCONF(NETDEV_UP): veth102i0: link is not ready
[96778.595101] fwbr102i0: port 1(fwln102i0) entered disabled state
[96778.595775] vmbr0: port 4(fwpr102p0) entered disabled state
[96778.596429] device fwln102i0 left promiscuous mode
[96778.597028] fwbr102i0: port 1(fwln102i0) entered disabled state
[96778.611450] device fwpr102p0 left promiscuous mode
[96778.612072] vmbr0: port 4(fwpr102p0) entered disabled state
[96778.729019] device fwln102i0 entered promiscuous mode
[96778.729656] fwbr102i0: port 1(fwln102i0) entered forwarding state
[96778.730233] fwbr102i0: port 1(fwln102i0) entered forwarding state
[96778.732251] device fwpr102p0 entered promiscuous mode
[96778.732807] vmbr0: port 4(fwpr102p0) entered forwarding state
[96778.733339] vmbr0: port 4(fwpr102p0) entered forwarding state
[96778.735314] device veth102i0 entered promiscuous mode
[96778.825628] eth0: renamed from vethWX7SUC

and more like this:

[97120.087600] IPv6: ADDRCONF(NETDEV_UP): veth102i0: link is not ready
[97120.359225] fwbr102i0: port 1(fwln102i0) entered disabled state
[97120.359819] vmbr0: port 4(fwpr102p0) entered disabled state
[97120.360429] device fwln102i0 left promiscuous mode
[97120.360960] fwbr102i0: port 1(fwln102i0) entered disabled state
[97120.378147] device fwpr102p0 left promiscuous mode
[97120.378697] vmbr0: port 4(fwpr102p0) entered disabled state
[97120.472812] device fwln102i0 entered promiscuous mode
[97120.473370] fwbr102i0: port 1(fwln102i0) entered forwarding state
[97120.473900] fwbr102i0: port 1(fwln102i0) entered forwarding state
[97120.475865] device fwpr102p0 entered promiscuous mode
[97120.476390] vmbr0: port 4(fwpr102p0) entered forwarding state
[97120.476890] vmbr0: port 4(fwpr102p0) entered forwarding state
[97120.478731] device veth102i0 entered promiscuous mode
[97120.564621] eth0: renamed from vethTGH0KR

Note:
The vmbr0 is the linux bridge we are using that is connected to the eth
phisical interface, the port is the eth2.

And eth0 is the port i can see from ifconfig from my LXC container
running on proxmox.


ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet ip.ip.ip.ip netmask 255.255.255.255 broadcast ip.ip.ip.ip
inet6 ip.ip.ip.ip prefixlen 64 scopeid 0x20<link>
ether ip.ip.ip.ip txqueuelen 1000 (Ethernet)
RX packets 49636 bytes 48323713 (46.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 51055 bytes 7464842 (7.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 20 bytes 2474 (2.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20 bytes 2474 (2.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


Questions:

What can be the cause of this issue? Is a network problem?
There is something wrong in the proxmox config that may cause this error?
If yes, what file of the proxmox config we have to check for troubleshoot?
It can be useful disable the multicast spoofing (pve side) to solve this?

Update:

The maintainer says that we can't use Multicast so we are using Unicast instead.

Waiting a reply from someone can help me to solve this please.

King Regards,

N.

 

[tom]

Up :\

Please stop such empty and useless messages (already two times today) - you will not get any faster answer, instead the opposite is true as reading these posts without any further content costs time which cannot be used for helping.

 

[Nerdy]

Thanks Tom, i'll wait a reply so from the staff.

Regards,
N.

 

[Nerdy]

@fabian @dietmar @manu @martin @wolfgang @tom @dcsapak can you suggest me something please?

Best Regards!

N.

 

[Nerdy]

Update:

if i log in to the proxmox server via ipmi i see this on dmesg messages:

[5733.214171] vmbr0: port 1 (eth2) entered disabled state

Please help, this is really urgent for me!

King Regards,

N.

 

[manu]

NB: anything urgent should be treated via the enterprise support where Developpers will provide you business day reponse guaranteed.

the messages you see are only the normal activity when a VM/CT goes up and down

you need to be more precise about what you mean with " server goes down often"

not reachable via ssh ? shutdown ? hanged / blocked ? rebooted ?

 

[Nerdy]

Hello @manu, thanks a lot for the reply.

The Proxmox server was not reachable via ssh, the only way we can access on it is via IPMI
like i wrote upstairs and we see this error message from the server where Proxmox is installed.

[5733.214171] vmbr0: port 1 (eth2) entered disabled state

If you need more info about the event i can post here all logs/commands you need.

Thank you in advance!

N.

 

[manu]

this message is part of the normal boot sequence when the physical device attached to the switch is boot in promiscuous mode:
[Thu Jun 22 09:10:25 2017] vmbr0: port 1(eno1) entered blocking state
[Thu Jun 22 09:10:25 2017] vmbr0: port 1(eno1) entered disabled state
[Thu Jun 22 09:10:25 2017] device eno1 entered promiscuous mode

if your network goes down again, check the following thing:

Please check in this order:

Are the underlying network links seeing network traffic ?
ip link show dev eth0
ip link show dev eth1
...

here you should look for the string LOWER_UP indicating the NIC is seeing traffic at the Ethernet Level

can you ping the gateway ?
can you ping an external server ?
can your resolve DNS ?

 

[Nerdy]

Thanks for the reply @manu
so next time i'll do what you suggest me for a better troubleshooting.

So according all details i posted here i have this 2 questions for you:

There is something wrong in the proxmox config that may cause this error?
If yes, what file of the proxmox config we have to check for troubleshoot?
It can be useful disable the multicast spoofing (pve side) to solve this?

If the network link is faulty, what will be the value of the string "LOWER_UP"?

King Regards,

N.