SHARE

Alas, my strained relation with Cisco wireless controllers rolls on. My 8540s are on super-wonderful-we-REALLY-tested-it-this-time 8.5.140.0 code, yet *gasp* I’m looking at yet another bug-driven upgrade. Or I can just disable MU-MIMO as listed in the work-around and yet again not use what I paid for! But you don’t care about that rot, as that has nothing to do with the point of this blog. That was just pre-content bitching, as an added bonus.

Let’s get on to the meat and taters of it all.

Take a look at this:

When I’m in the WLC interface, there are various ways to sort for specific APs or groups of APs. The ability to search on Speed is fairly new, and if it’s not obvious it’s talking about the wired connectivity of the AP and is relevant where mGig switch ports are in use. That’s fairly innocuous, yes?

But here’s WHAT COULD HAVE BEEN.

Suppose that Speed search gave another option- for 100 Mbps? Some of you know where this is going…

In a perfect world, all 3000+ access points on this 8540 would connect to their switch ports at Gig or mGig, depending on models of hardware in play. But the world isn’t perfect. Occasionally, some of those thousands of APs connected to hundreds of switches for whatever reason only connect at 100 Mbps. More often than not, that’s indicative of a cabling issue. Once in a great while it’s a switch misconfig or a bad AP in play.

As is, there is no easy way to find those APs that have joined at 100 Mbps in the controller. An AP that connects at 100 Mbps doesn’t trigger a fault. You can’t sort on the speed column, and basically have to wade through almost 50 pages in my case looking for the elusive 100 in a sea of 1000s in the speed column.

Boy it would have been handy if the developers gave us a 100 Mbps option in that Speed search.

 

LEAVE A REPLY

Please enter your comment!
Please enter your name here