WS-12-250-DC Stopped passing traffic to ePMP-AP's

[tcknudson]

switch stays up, ports show lit, but no traffic to ap.
happened twice last week, now twice this am.

Rebooted ap's with netonix by turning power off and back on and traffic was resumed, (port bounce did not work),
Suspected spanning tree, but it has been disabled and still happening.
2 other Canopy 5750ap's kept pinging and passing traffic,
When this happens you cannot ping ap from switch,

found if I lock the port at 1 gig, it starts passing traffic again with no reboot of ap,

any clues?

have about 40 netonix switches, this is only one that I know is doing this,

[sirhc]

Yes, do NOT set port speed to 1G leave set to Auto

If you hard code a port speed to 1G and the communications needs to migrate down even for a second it can drop the connection.

When you reboot the radios you cause the link to renegotiate and it achieves 1G but if the right events occur the link can be dropped since it can not auto negotiate down if needed.

Also note that if you keep up on our forum that a few people had reported a similar issue with Flow Control with ePMP 2000 radios

So, I would:
1) set port speed to Auto - NEVER HARD CODE PORT SPEED EXCEPT IN EXTREME RARE CIRCUMSTANCES
2) if you still have issues then disable Flow control on the ports facing ePMP radios

[tcknudson]

I disabled flow control and radios came right up,

[sirhc]

I disabled flow control and radios came right up,

I am sorry that does not prove the problem is NOT the hard coded 1G speed and Flow Control may have nothing to do with your problem.

When you disable Flow Control is causes the Ethernet connection to be dropped and then renegotiate.

Please do it in the order I asked:
1) Set port speed to Auto and leave Flow Control ON - NEVER A GOOD IDEA TO HARDCODE PORT SPEED DUPLEX

2) If it still happens then disable Flow Control

[StrataNet]

Hi Chris,

I'm seeing a similar issue with an AF5U. In my case, both the radio and switch are negotiating 1G but not passing traffic; however a reboot won't fix it. I've tried everything, and I cannot get traffic to flow across this ethernet link. The cable test passes, but I can't get traffic to flow. I've checked VLAN settings, but everything is untagged (and the radio has no management VLAN assigned). The radio has the exact same settings as the radio at the other end (expect IP etc), but I can't get traffic flow no matter what I try. It used to work last time I used it about a year ago (redundant link).

Little niggles like this end up being major headaches with Netonix. Maybe I keep getting all of the dodgy units, I don't know.

Any ideas?
Cheers!

[sirhc]

Hi Chris,

I'm seeing a similar issue with an AF5U. In my case, both the radio and switch are negotiating 1G but not passing traffic; however a reboot won't fix it. I've tried everything, and I cannot get traffic to flow across this ethernet link. The cable test passes, but I can't get traffic to flow. I've checked VLAN settings, but everything is untagged (and the radio has no management VLAN assigned). The radio has the exact same settings as the radio at the other end (expect IP etc), but I can't get traffic flow no matter what I try. It used to work last time I used it about a year ago (redundant link).

Little niggles like this end up being major headaches with Netonix. Maybe I keep getting all of the dodgy units, I don't know.

Any ideas?
Cheers!

You assume this is a Netonix issue by default?

If you have both switch and AF ports set to AUTO and FLow Control is turned OFF then turn POE OFF on the port unplug the AF radio and plug in your laptop and see if the port is passing data to your laptop. Make sure you assign a valid IP for that port to your laptop. Maybe you have a bad radio or it's something else?

[StrataNet]

Hi Chris,

Thanks for your speedy reply.

You assume this is a Netonix issue by default?

I've seen other similar issues with Netonix, so my assumption is that it's either the switch, or some sort of compatibility issue between the two devices.

I'll try plugging my laptop in directly next time I'm at the site. I only discovered the issue today (remotely).
Cheers.