CISCO WLC BLACKLIST MAC ADDRESS HOW TO
In this post – we’ll walk through how to set up a new SSID with client MAC filtering. This network uses both a pre-shared key for authentication as well as MAC-based filtering. One of my SSIDs is dedicated to any IoT devices and is more restrictive than the other networks. Most of my current config is fairly straightforward – a few SSIDs, two APs, and a guest network with captive portal.
CISCO WLC BLACKLIST MAC ADDRESS FREE
Today I am using Ubiquiti APs, which come with their own free controller software. In order to play around with the new controller, I decided to try to build a new configuration that mimics my current home wireless.
Trying to get a good understanding of how the new Catalyst 9800 wireless controller works, and how it differs from some of the previous iterations. I’ve been spending a bit of time over the past few weeks building up a wireless lab. If so, check out the video above which walks through the ‘Advanced’ setup and bypasses this error. If you come across this error, it’s a known bug ( CSCvt18875) specific to only the ‘Basic’ setup wizard (which is what I used in this post below). If you’re using the ‘Basic’ Wireless setup, you may see an error when trying to apply the policy: “switch 1 dbm wireless Use of default ACL preauth v4 is not permitted” Option r but unfortunately sending a notification on for recovery is not possible.Update 2020 / 05 / 19 – I’ve added a video above that walks through the steps detailed in this blog post. From service_notification_options we only need Look at the service_notification_commands. This contactgroup only contains one member: Option -r whith host address and without community string (does the same) or it can be resetted via a trick byĬommand_line /usr/lib/nagios/my_plugins/check_snmp_cisco_wlc -H $HOSTADDRESS$ -C $ARG1$ -showerrorĬontactgroup wlc-recover is important. To reset the alarm the cached data (old) can be removed by hand (but I am too lazy for this), by calling the plugin with If there are APs in the old data but not in the actual data an critical alert is caused. If old data is a subset of actual data old data is overwritten with the actual data. If there is no old data (first check) the actual data is storedĪnd will be used as old data the next run. The plugin compares the old data with the actual data. In my case to speed up cached results the cache directory is a tmpfs. Therefore we will have a file to cache to old results (variable $plugin_cache around line 88). The other more flexible method is to compare it with This is not a monitorable alert (normally) because the AP simply disappears from the WLCĪnd after a power on it is back. The main problem in monitoring AP is the get an alert in case of a breakdown or power off ofĪn AP. The plugin will determine this and give a warning. If an new AP joins the WLC is automatically added with a default name (ap_name.MAC-address). If it is disassociated it will give a critical alert. If an AP is downloading it is not available. At present this plugin is focussed on the availability of the access Version 1.1 Thanks to Mihail Karageorgiev.Ĭisco Wireless Lan Controller (WLC) is in some parts a little bit tricky to
If used with -isregexpĮvery item of the list is interpreted as regular expression. Is a case sensitive comma seperated list. Added blacklist support (-B|-blacklist) for AP names. Fixed some small issues in help und usage.
Now it is deleted from the hash instead of skipped only. The blacklisted AP was still written to the AP list because it was still in the hash storing all elements. This will only show WLCs causing trouble. Martin Fuerstenau, Oce Printing Systems GmbH, martin.fuerstenau_at_oce.com Check_snmp_cisco_wlc is a Nagios plugin to monitor the status ofĬisco Wireless Lan Controller (former Airespace) access points
0 kommentar(er)
