Oziwifi

One could think that troubleshooting happens when you have a poor or no design at all. Not always, that is the case. You can have former designs, so what could be wrong if you are only replacing old AP for brand-new ones? The not-so-old Cisco 3600 was working well; they could not keep up with the number of users and that was all. Wrong!!! There are lots of things that could be wrong, and admittedly, it would be handy to have more training when you are troubleshooting not only one issue but a sum of five different problems; that are not even entirely wireless.

So, do you think you can dance?? I mean, do you think you can troubleshoot a wireless network? Most of the time, I think I do, and most of our proud and engineering mindset leads us to believe we are terrific. We are not prone to have competitors in our offices or even ready to hear second opinions, at least to be honest I don’t. I have a strong technical background; I am a bit nerd and stubborn; hence changing my opinion is quite tricky for me.

I had to diagnose multiple issues remotely over a recently deployed Meraki wireless network with 15 access points MR-45. It seemed not to be a big deal, but actually, it did; it was for the most critical branch in APAC, and the people who complained were the VIP users of the network. I think these kinds of issues made themselves more traumatic as you are not there, and you can’t go as we were with COVID restrictions.

I had issues such as random interference generated from legacy APs on my own network not documented, non-WiFi devices abusing the wireless, lazy laptops not using their capabilities, crazy access points that transmitted with too much power, or even buggy firmware on some access points that do not obey the dashboard as they should.

All in all, I needed to be there with all my toys and definitely with more training. Ekahau ECSE gave me a lot of ideas. I think I needed Ekahau Troubleshooting for being both more accurate and faster in solving those issues.