Ninox mac database how to#
Ninox mac database full#

Ninox mac database full#

The syslog version makes a a bit more tricky, since the (syslog)log lines are very long and you have to combine the correct lines to get the full message. The downside to this is that you have to have syslog file access or add an additional syslog server to Cisco ISE that you may access (e.g. The other path is by following the syslog output and parsing that feed. Or if you’ve got nothing else to do do it by hand. Feed these MAC addresses to a script and remove them through the Cisco ISE ERS API.

Filtering these results in Excel, or through Python scripting, you are able to extract the MAC Addresses that successfully authenticated with dot1x. There you can export all RADIUS authentications to CSV. I needed a way to get current and past successful dot1x authentications and compare the MAC addresses associated with those entries to the MAC address database, and remove those from that database.Įventually, I found two paths to accomplish this First through the reporting module. There’s no way of exploring past (successful) authentications/authorizations. That is where I had to become creative.įirst I explored the Cisco ISE Monitoring API, but that only gives active connections. However it has no way of reporting on dot1x devices that might still remain in the MAC address database as well.

Ninox mac database how to#

But how to do that? Cisco ISE has a lot of features, and is capable of generating rich reports about almost everything. There are however some Windows / Thin client devices that will remain on the MAC-filtering wifi networks for numerous reasons.Īfter a few tests the migration of the new 802.1x devices has started, but is leaving us with a MAC Address database filled with addresses that can be removed, since they are no longer used…. So, applying setting related to 802.1x are pretty straight forward to distribute. Both of those are managed through either the Microsoft Active Directory or a Thin Client Management Suite.

These devices are consist mainly of Windows machines or Thin Clients. But how to make sure that they are all (still) valid? Remove MAC Addresses After Change In Authenticationįinally, the time has come to implement 802.1x on the wireless network for a substantial amount of these devices. All these MAC addresses are used to gain access to wireless networks protected with WPA2-PSK and MAC-filtering. Imagine having 15.000+ MAC addresses in a Cisco ISE database.