Switchport tracing and suppression not working!

[jkemery]

Anybody have any insight into the new switchport suppression feature. I'm setup with WLSE 2.11, AP's=12.3(2)JA2 connected to 3560-48POEs.

WDS, self-healing, auto re-site survey, rougue detection with suppression turned on. I have one AP Scanner only wap in my building. I was able to successfully setup a rogue AP and detect in about 10mins. But the tracing failed so the switchport did not suppress. I'm guessing it's either a SNMP setup issue on the switch or the AP's need the newest code??? Anyone have experience with this? Does it work most of the time, or not? Is there a trick to setting it up. I can't find any specific pre-requisites for the switches. The documentation just says that it uses SNMP on the switch??? Does it need a Writeable community string???

Any insight is appreciated.

[rmushtaq]

From: Understanding Switch Port Tracing and Suppression

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_11/u_gd/wids.htm#wp1000229

Switch port tracing and suppression is a best-effort approach and is not 100% guaranteed to yield accurate results.

[mikeharpe]

I have the same problem. I wanted to see how switchport tracing works and I set up an AP1200 with 12.3(7)-JA3 on it as a rogue AP. I used a port at my desk that I knew and configured the AP to be an open AP.

WLSE found the rogue and a did a fair job of traingulating but the switchport trace fails every time. We use a lot of other SNMP applications so I know SNMP is OK.

I have a case open with TAC about this but I would like to hear from other users.

Our WLSE version is 2.13.

Thanks!

Michael Harpe

Yum Brands, Inc.