topic Re: MAC violation not deleted through CLI. in Wireless

MAC violation not deleted through CLI.

Prasanna Damodaran — Sun, 04 Jul 2021 05:13:44 GMT

WLC 4404 is configured as Anchor controller, the MAC violation are captured by Controller. the Violated MAC are deleted manually through GUI, but when tried deleting through CLI using command

>Config exclusionlist delete <mac address>

we get error message as

error deleting user <mac address>

Please let me know

MAC violation not deleted through CLI.

Amjad Abdullah — Sun, 03 Jun 2012 09:52:52 GMT

Prasanna:

How you delete the user from the GUI? what is the process you try to do to delete it?

I don't think the command on CLI does the same what you do on GUI.

Amjad

MAC violation not deleted through CLI.

Saravanan Lakshmanan — Sun, 03 Jun 2012 22:48:26 GMT

If its an Anchor WLC without APs then you don't see client exclusion in achor rather you would see it in the foreign.

Are clients getting excluded due to Violating Client Exclusion policy.

See if anything listed.

WLC-Foreign>show exclusionlist

WLC-Anchor>show exclusionlist

MAC violation not deleted through CLI.

Prasanna Damodaran — Tue, 26 Jun 2012 13:09:51 GMT

Hi Amjad / Saravanan

Thanks your reply. PFA, I have tried those commands and shared the output

Re: MAC violation not deleted through CLI.

Saravanan Lakshmanan — Tue, 26 Jun 2012 23:16:46 GMT

it works on code 6.0 and not on 7.0, i'm neither able to add nor delete the existing mac entry for client exclusion on 7.0 code using cli. so what you're seeing is a bug.

Re: MAC violation not deleted through CLI.

Saravanan Lakshmanan — Thu, 28 Jun 2012 18:31:56 GMT

i was incorrect on my earlier post, i was trying to add group address and couldn't add it, also deleting wrong address.

you're right on your finding.

Manually added clients on GUI were able to be deleted it, But dynamically updated clients couldn't be deleted and it is still a bug.

MAC violation not deleted through CLI.

Saravanan Lakshmanan — Wed, 23 Jan 2013 00:39:14 GMT

it is resolved on 7.4(100.0)

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCua69301