* Janne Johansson <icepic...@gmail.com> [04.09.2013. @15:59:56 +0200]: > I've seen similar issues when the network port had the same network/VLAN > both untagged and tagged at the same time. > The end result was that the switch decided that the mac was on the physical > (untagged) port only, and would not talk to the same mac tagged against the > vlan IF, meaning it basically fell off the net. > > Gross misconfiguration, but it took a while to figure out why.
The switch seems to be configured correctly, no vlan is tagged and untagged at the same time. We are using Dell Powerconnect switches, and all machines using OpenBSD have ports configured in the exactly same way on them - the port is in general mode, with vlan1 untagged and the rest tagged - yet only one machine has the described earlier vlan problems. > 2013/9/4 Wiesław Kielas <wieslaw.kie...@bluemedia.pl> > > > Hi misc@, > > > > I have a Dell PowerEdge M600 machine running OpenBSD 5.3 which causes > > frequent problems - once about every few days vlan interfaces stop > > working. > > > > Ifconfig reports them being up the whole time, but when trying to ping > > anything in the given vlan, the ping fails (this also applies to the > > loopback address on the interface - it doesn't reply as well), as if no > > packets were transmitted on it. This applies to all packets on the > > interface, not just ICMP ones. > > > > This doesn't seem to be a PF issue, since disabling it doesn't help, and > > non-vlan interfaces (like trunk0 with trunkproto failover) continue to > > work. > > > > Putting the interface down and up, destroying and creating it or running > > /etc/netstart doesn't help - a reboot is required, after which the > > machine works correctly again for some time. > > > > I checked the logs and dmesg and found there nothing of any value - no > > new messages around the time of the crash. > > > > As this is a blade machine, most hardware issues (like memory problems) > > would be reported by the chassis, and it reports none. > > > > I have a couple other M600 machines running OpenBSD, with the same > > network cards, and only once this problem did occur on another machine - > > a slave for the problematic one, running pfsync, sasync and acting as a > > carp backup. > > > > Could anyone provide me with some tips on how to debug the problem > > further? Turn on some kernel debug mode, make use of the kernel > > debugger? I'm at my wits end here. > > > > If there is any information that I could provide to help solve the > > problem, please don't hesitate to ask. > > > > The dmesg is attached below: > > <snip> -- regards, Wiesław Kielas
