The CiscoWorks Wireless LAN Solution Engine (WLSE) has detected a spoofed MAC address. henever the Wireless Domain Services (WDS) detects an authentication taking place for a known MAC address, it verifies that the same user ID is being used. If the user ID does not match, the authentication is rejected and a fault is issued.
Why does the Client MAC Spoofing fault reappear after it has been cleared?
A. The WLSE raises faults for all clients identified by MIB ciscoWdsIdsMacSpoofClient (188.8.131.52.184.108.40.206.4220.127.116.11.1.3). It retains the history of all spoofed MAC addresses.
Because the WDS maintains the history of all spoofed MAC addresses, the WLSE raises the MAC spoofing fault during the poll cycle, even after the fault is cleared on the WLSE. If you have cleared the MAC spoofing condition in the network, you need to Acknowledge the fault on WLSE.
An entry from the WDS MIB is cleared when on of the following occurs:
–The WDS AP reaches the maximum number of events to hold for a reporting non-WDS AP. The maximum number is determined by the following MIBs: ciscoWdsIdsMaxMacAddresses and ciscoWdsIdsMaxEntriesPerMac.
–The WDS is unconfigured.
Note: When this fault is cleared, the No Wireless Client MAC Spoofing Detected message is displayed.
CiscoWorks Wireless LAN Solution Engine (WLSE)
Wireless Network Management
MAC address authentication (Media Access Control)
Wireless Devices Errors, Warnings, Statistics and Log Messages
Hi, I have a vWLC in a remote lab where im using the interface G1 for WLC admin and also as wireless management interface. Then, at my home I have an AP 3702 in a network that can reach the WLC via VPN. The AP can ping the WLC and the WLC can pi...
I have three AERONET Aeronet AIR 1832I-E-K9 Wireless AP connected to Catalyst 9200 Switch I dont have any wieless controller. I need to configure them I have assigned them IP using "Capwap ap ip netmask"How can I make them work as an AP and I w...
Using 2x 1562's in this exact setup for bridging. I get to the part for whitelisting the MAC address (done), and enabling bridging (done) but the MAP never joins the RAP, with this error in the CLI: CRIT-MeshAwppAdj: Blacklisting Adjacency due to ...