Page 1 of 1

switch stopped passing traffic

Posted: Wed Jan 13, 2016 9:56 am
by swang2002
I experienced a random event last night, and wanted to see if anyone here has any idea what could have caused it. I recently deployed the 8 port AC model at a new site with a Mini 6 port model attached to port 2 (100 ft of cable in between). The 8 port switch stopped passing traffic, but was still accessible around 11:15 pm, so I logged in and saw a bandwidth graph showing 15 mbps steady on the download, and 0 upload on all ports. Having unhappy customers, I quickly reboot the switch and things returned to normal for about an hour. When I woke up at 4:00 am to calls and texts, I noticed that the switch had again stopped passing traffic at around 12:10 am, and after logging in I saw the same bandwidth graph described above. This time, I simply powered down the port that was powering the Mini, and immediately traffic returned to normal.

My first thought was a network loop, and seeing as I didn't have any STP enabled, that was a possibility. Just wondering if anyone else has seen anything similar to this, and if so, what their diagnosis and resolution was. I realize there's not much to go on here.

Management VLAN is 99, and each AP attached to the switch gets its own VLAN back to the router (vlans 31-36). VLAN 1 has been removed from the switch.

Re: switch stopped passing traffic

Posted: Wed Jan 13, 2016 10:34 am
by sirhc
No, I never heard of this.

What firmware versions?

Please post up any of the Tabs that have configuration changes from default of both switches.

Also next time it happens check the switch logs and post that.

Re: switch stopped passing traffic

Posted: Thu Jan 14, 2016 9:26 am
by tma
For me, this appears to be quite similar to what I observed and described in my post FW 1.3.2 static LAG weird behavior. Unfortunately, I had seen this on a LAG between two Netonixes first and so we got into a discussion about static and LACP LAGs and whether they need STP or not. In the linked post, though, I reported that it had happened to me between two Netonixes on a single(!) link. I promised to try to make this reproducible but I failed until it happened once more (when I wasn't prepared to capture details) and never since.