Aruba Airwave Triggers

An intro to Triggering with Aruba Airwave.

Advertisements

Recently we had a new site come up that only needed one access point. It’s a small doctors office that we are renting space in so one of our doctors can use it every other Wednesday.

There was some confusion of how the network was going to be installed and it ended up that we had to install all our own gear instead of using a VPN from their gear. Property managers… meh.

Since the site was only in use once every 2 weeks, we installed everything but didn’t have a cable run for the access point (AP215). It was estimated that the signal coverage would be good enough coming from the IT closet. It was confirmed with an AirCheck in the patient rooms. After the first couple of weeks that the practice was open, the staff decided that the AP was not in a good location and proceeded to move it to their liking instead of calling us. Then of course, we started getting complaints about how it was installed and where it was. Great. I’d love to go push their EKG machines around the office and hide it in a broom closet somewhere claiming that it worked better.

This brought up a new topic with our manager about our monitoring of APs and where the alerts are going. We hadn’t set up any monitoring for the APs because usually I’d end up in the controller once a day or so and if I saw one go down I’d look into it. Either that or I’d get a ticket about crappy coverage. It also brought concerns about the possibility of people stealing our APs. I was tasked to setup alerts so we’d get a notice every time certain APs went down.

So on to Airwave. I had setup an Airwave server (Device management and monitoring from Aruba Networks if you aren’t familiar) to monitor the new Aruba system that we are installing. I’ve got a thousand permanent licenses and 2500 eval licenses to play with. So I ended up adding all our current Juniper APs as well as the new Arubas that are going in. I’ll pull all the Junipers out when the aruba system is live.

Triggering from Airwave is quite easy. Go to the “System” tab at the top and then “Triggers”:

Screen Shot 2016-04-09 at 4.41.55 PM

Click Add and you’ll end up here:

Screen Shot 2016-04-09 at 4.43.55 PM

Since I was only worried about APs that went down, I chose the “Device down” type. There are a couple different options here that I left default. I’ve also read some advanced threads about triggering where more advanced options can be use to really dive into configuration alerts, etc. Nothing I need right now but good to keep in mind.

The main purpose of my trigger was to receive an email when an AP goes down so I created a group for “Monitored APs” (under the Groups tab) and checked the email notification button. This opened another set of options:

Screen Shot 2016-04-09 at 4.48.34 PM

The sender address is the email you want the message to come from. Initially this confused me because I thought we’d have to get Sys Admins to create an exchange account and then setup all this crap just to get it to work. Wrong. Airwave has a built in SMTP service. You can literally just pick some email address to type in and thats what it will use as the sender. I wouldn’t suggest using your CEO’s email address but I had toyed with the notion of using BigBrother@WhiteHouse.gov just for kicks.

Fill out the addresses you want the notifications to be sent to and you are ready to go.

One note… the “Suppress Until Acknowledged” means you will only receive 1 email and it won’t send another notice about the AP/device until you go into Alerts and click “Acknowledge”. This will reset the status and send the email again when its necessary. I turned it off because for now I’m not Acknowledging any of the alerts. I may change it later but a lot of the time I need to be bugged in order to keep stuff on my mind. Other the other hand, if an AP is bouncing, it would probably send me an email every 3-5 minutes. That would get on my nerves. I’ll fix it if needed.

Once you are finished with all your options, click add and its active right away. Now just pick some of the devices or APs that you want to monitor and add them to the Monitored APs group.

For testing I just unplugged the AP at my desk. Success.

Let me know some of the cool things you’ve done with Triggers below. And as always, feel free to correct me. I’m learning too!

 

’til next time…

 

Introduction

Might as well start somewhere…

My name is Joey Feci(FeeChee) and I’m the Wireless Engineer at Northeast Georgia Hospital System in Gainesville, GA. I’ve never had a blog, never enjoyed writing, and grammar is not my strong suit. Hopefully this blog will help me learn about Wifi AND writing!

I first got started in IT in 2005 when I got sick of playing original music(drums) for tables and chairs in Atlanta for $25 bucks a night -split 4 ways. Not knowing anything about researching schools or choosing colleges, I saw an ad for DeVry university being the leader in technical education and chose to go there because there was no entrance exam really, I only had to sign some papers about loans, and they had the word Cisco in one of their program listings. Ahh, to be young and dumb.

Stepping back a little further, I built and owned my first PC only two years prior in 2003. While visiting some friends back home in Virginia Beach, I had the budget to get my first computer from a tax return and was guided by one of the most awesome guys I know(Tim Gawne) into the world of building your own PC because it was cheaper and you could get better components. Before this, I had only surfed the web on friends’ computers, and gotten completely addicted to Half-life and Counter-Strike.

So my DeVry education in IT started. At the end of 2006 I received an email from a friend of mine with a job description attached. It was for a repair tech in the Repair Services Department of LXE, a manufacturer of rugged scanners and computers. I went in for a basic interview where it was determined that my current skill set was not enough to be one of the techs they were hiring for. However, a couple days later I got an offer from the manager for a QC position. I would be checking all the repaired computers; configuring them back to customer settings; and passing them to shipping so they could be returned. It paid a little more than my current job in an appliance warehouse and was in the field I was studying for so I accepted and my career began…

Since the computers and scanners that were built were for warehouse installations, I was then introduced into the technology of wireless communication! Through the next couple years I was able to learn the complete product suite of LXE terminals while configuring and learning different client configuration parameters. Most of the configuration I was doing was to Cisco Aironet and Summit wireless radios. I’d configure the authentication and encryption methods as well as power management settings, roaming thresholds, and tx power settings.

I graduated from DeVry in 2008 with loads of debt and not much education. I had moved around Repair Services and ended up back in the QC position when the new guy couldn’t handle the position and I was brought back in to clean up his mess. For some reason I was the only guy in the department that could QC and configure 100+ terminals a day without holding up the line. I was eventually introduced to the Technical Support manager and after 6 months or so, I was offered a position on their level 1 team. This is when I finally learned that brain power was worth a lot more money than man power, lol. Unfortunately, 2009 had taken its toll on LXE and EMS(its parent company) and the company was put up for sale and bought by Honeywell in 2011. Thats when I learned about corporate takeovers. In the beginning it was “We are going to work together and make the warehouse terminal world a better place!” 3 months later they had fired all my friends in repair services and moved everything else to China. Kumbuya. Technical services and some sales and engineering were kept around because of contracts and knowledge transfer but everyone else was told to have a good life. I missed the layoff by 1 month.

I stayed with Tech Services for another year, all along, putting my resume on every site there was and submitting to every craigslist post that had the work “network” in the title. I sent 200 resumes and got 3 responses. In 2011 during the takeover, I had started going to Gwinnett Technical College where I was able to graduate from the OFFICIAL Cisco academy and started pursuing my CCNA.

Then in 2012 during the end of my Cisco course I received a random email. A company called Layer 3 Communications had received a resume from somewhere and called me in for an interview. 6 hours later I was hired and my call to Wireless Engineering was confirmed. I started in September of 2012 with the best company I’ve worked for so far and enjoyed a quick 2.5 year span with them before joining the hospital.

During my time at Layer 3 I was quickly thrown into the world of Wireless design. RF topics were not really mentioned in meetings and some of my first networks (I’m ashamed to say) were designed with Visio instead of Ekahau or AirMagnet. We had an older copy of AirMagnet but it was a couple months before I installed it. Luckily, that was short lived because we were getting ready to purchase Ekahau for the increased workload. Through the Ekahau site and videos, I was able to hear about people such as Keith Parsons, Devin Aiken, and Andrew Von Nagy. After seeing a bunch of Twitter handles, I figured out that it was the fastest way for me to learn from these guys. I created an account and so far I’ve built up a following list of 168 Wifi professionals and I check it daily to get my 10 minutes of Wifi training or at least some laughs about RRM.

Then I got the opportunity of the year. I had the interview with my hospital and took the position -starting on Memorial day of 2015. On my first employee-less day (remember “Memorial day”?) I was walking around with a colleague and lo and behold, here I am standing in front of Mr. Devin Akin. Devin had been contracted by the hospital before I got hired to perform a completed predictive design of 7 major buildings in the vicinity of our main tower. 1465 access points. Through the next 6 months I was able to build up a pretty good friendship with Devin and learn more than I had in the past 6 years of doing it on my own. While the education was mostly about design, I did have a fun time going toe to toe with a particular vendor that Devin later wrote about on his blog (http://divdyn.com/blog/). Just search “Technical Analysis”. You’ll figure it out. If you already know -then yes, I’m taking credit for that introduction. You’re Welcome.

Recently I was able to attend the WLPC2016 conference in Phoenix and meet some of the people that have helped me and others that are in the same boat. It was an awesome experience and hopefully I will continue to get the opportunity to go in future years.

’til next time…