I use it mainly for three things. For one, I use it for wired connection. I also use it for a couple of things on the wireless mode, and I use it a fair amount for the wireless locate function.
I'm using AirCheck G2. I know they just came out with G3, which I don't have. G3 has some new features that sound interesting.
It is a pretty useful tool for some situations. It is a handheld device. It reminds me of something a UPS or a FedEx driver would have. This device is in my bag, and whenever I have to go on-site, I always bring it because I never know if I'm going to run into a wired situation where I want to do a wired test, or I need VLAN or port information. So, I just bring it. I already used it this week for that. It is always there, and it is a really simple test to run. With the live link, I can get historical data on that or at least store it. I use it for that a lot.
It is useful for wireless packet captures. I used it for that this week, and I've solved one of the biggest issues we had with a vendor. I was using it to get the captures and eventually found the solution based on those captures. It is a pretty easy device to do wireless captures. In some of our wireless environments, for example, in our Aruba environment, we can do captures on the APs, but in some of our Cisco environments, they've somewhat taken that functionality away on our 3800 APs. This device is small and convenient. It doesn’t need external antennas, and I can take it to a spot, do wireless captures pretty much anywhere, and then use Wireshark for analysis.
It is helpful for finding an access point. We're doing an upgrade at a hospital. I work with a cabling vendor who says, "You said you have an AP here, but I can't find it." I can search based on a MAC address or an SSID, find that, and use the locate function. It'll give me a dial indicator and a beep indicator of where this device is. I routinely find access points that we can't physically see, for example, above the ceiling.
It is useful when you're having reports of poor wireless. In such a case, one of the things I'll do is I'll just set this on check SSIDs. For example, in our hospitals, we use very specific SSIDs. If I see one that's not ours, and I know that's not supposed to be there, I want to find that device, and I want to know what's going on with that device. Sometimes, it is a vendor device, or someone has put a hotspot on, but sometimes, it isn't supposed to be there. For example, in a hospital, it is very common to have waiting rooms, and there is a cable TV set up in these waiting rooms. Sometimes, the cable company just turns their wireless on by default. I go in there, and then we contact the cable company to turn their wireless off there because it is impacting us.
I bought one out of my own money. So, I found enough value to spend my own money on it. The guys on our team saw it, and they used to say, "Wow, what's that? What are you doing with that? We should have one of those." I convinced my boss to buy one for the team. Tomorrow, we're going to do a big wireless upgrade in the hospital, and I'm bringing my AirCheck G2. Very likely, we'll run into a situation where it would be an easy tool to use for quickly diagnosing or understanding what's going on.
Wireless planning was one of the things for which we used it a lot last summer. That may seem counterintuitive, but our healthcare system is going through a big wireless upgrade, moving from Cisco to Aruba. We're a rural healthcare system. In some cases, we have a clinic in a town of 1,500 people. I had interns take the G2 and go through the northern part of our state and visit our sites. They used AirCheck to verify wall density and signal degradation through walls. With that information, we could more accurately model those locations in the software we use for wireless planning. We were able to use 20% to 25% fewer access points because I had accurate wall information. We saw the benefit right away of sending our interns to test these remote sites. We could see that we don't need as many APs because we actually measured, and we were not guessing about the wall density. We did that at 15 sites and saved thousands and thousands of dollars. I don't use AirMapper at big sites, but small sites are where we could potentially use it. Its functionality is so easy to use. It allows a less experienced person to be more productive personally. Some of the guys who were doing this work were summer interns. They're not network engineers yet. This tool is easy to use.
Speed of resolution is another benefit, and with that comes customer satisfaction. At one of the hospitals, I work with our Biomed team. I took my AirCheck with me because they were moving some monitors around. They were not network savvy. I was able to just quickly plug the Aircheck into our emergency department network jacks and document everything and say, "We're going to reserve that port for this device, and that port for this other device." I could send them an email with all the documentation. They were all set. They could go and implement the solution. To a large degree, our emergency department personnel don't know what happened, but it all works. That's a big thing.
We were having some voice quality issues with some of our iPhones, and it seemed like the Android devices didn't see it. A lot of nurses use little handheld devices that have messengers. So, they have texting on there, and they have voice calls. They also can use it, for example, to scan medication and things like that. They were reporting some voice quality issues. I ended up using my AirCheck to resolve the issue. I was able to show the vendor that on their iPhones, they were not using the correct QoS markings. What was happening was that the QoS was being effectively lost once it left their iPhone. So, we're not giving QoS priority throughout our network. It was a huge issue for us because not only does it impact the nurses, it potentially also impacts patient care.
It makes the speed to resolution faster, and then our staff goes on to the next issue. It enhances our end-users' happiness because they want their problems fixed fast. When I had those guys go out to our small clinics, I didn't have to send a more qualified engineer to be doing this work because obviously, they need to be doing other more intensive network work. So, it frees up the time of our skilled people to do other stuff. It is difficult for me to quantify that from a productivity standpoint, except to say that I saw thousands and thousands of dollars of savings, and I had my engineers doing other things. From what we pay a network engineer to what you pay an intern, might be a $30 per hour delta. I can give this tool to a summer intern making 25 bucks an hour to have him do this work versus having to send a $50 per hour engineer to do the work.
It is hard to measure the reduction in troubleshooting time because I'm never without it. I just bring it, and it is with me all the time. If I go remote, it is packed in my remote box. It is not the only tool I'm using, but certainly, for some issues, it can cut down the troubleshooting time in half or less. For example, one of the tools I use is Ekahau Connect, When I need to use Ekahau, it takes me 10 minutes just to get that set up so I can start using it. After I hit the power button on my AirCheck, it is ready to go in 15 seconds. Depending on the issue, it is just much faster to find a solution.