Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
One glaring issue, your group is named "nagiocmd" was this intentional? By default it should be, and is expected to be, "nagcmd"...unless you intentionally switched it when you originally configured nagios.
Hi, yes it was by intentional. I have reinstalled Nagios because it was taking too long to resolve this issue.
Thanks to all of you for the replies. I will still like to keep this thread open because I havent tested the original wifi monitoring thing.
Fair enough. Let us know if you have further issues.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Ok- so check_aruba.pl worked after doing the changes in OIDs. SO this thread is okay to close.
If anyone looking for the script - Please feel free to use the attached script. I have made the required changes so now it works with DELL W-650 wifi (Aruba OS). I used it for monitoring Access points (up and down status only). One have to explore if they want more things to be monitored.
You might get error
/usr/bin/perl^M: bad interpreter: No such file or directory
while running the script, to resolve this I Removed ^M control chars by using following command