Re: WCS Switch Port Tracing - Error

chaijoo_lau · ‎04-14-2009

I have added all switches in the network into WCS with snmp version 2c read only.

When I try to trace one of rogue AP that I have connected into one of switch, the WCS return with an error message shown as below:

"2009/04/14 20:02:34 Switch port trace failed. Please see the wcs log for failure reason. You can download the log from Administration -> Logging and search for "Switch Port Tracing Start for rogue <rogue mac address>" in wcs-x-x.log (Ex: wcs-0-0.log) ".

Below is part if error log that extract from WCS log:

4/14/09 18:24:11.718 INFO[general] [21]

*************************** Switch Port Tracing Start for rogue AP: 00:1f:f3:02:d8:07 ***************************

4/14/09 18:24:11.734 INFO[general] [21] SPT: No Clients associated with this Rogue :00:1f:f3:02:d8:07

4/14/09 18:24:11.968 INFO[general] [38] SPT: Get neighbours for the reporting AP :172.16.101.86

4/14/09 18:24:12.0 INFO[general] [38] COMMON-11,SnmpSwitch

4/14/09 18:24:12.0 INFO[general] [38] SPT: Snmp Credentials are not available for this node [172.16.101.81]. Skipping ...

4/14/09 18:24:12.0 INFO[general] [38] SPT: Get neighbours for the reporting AP :172.16.101.85

4/14/09 18:24:12.31 INFO[general] [38] SPT: This node is already processed, skipping 172.16.101.81

4/14/09 18:24:12.31 INFO[general] [38] SPT: Get neighbours for the reporting AP :172.16.101.101

4/14/09 18:24:12.46 INFO[general] [38] COMMON-11,SnmpSwitch

4/14/09 18:24:12.46 INFO[general] [38] SPT: Snmp Credentials are not available for this node [172.16.101.97]. Skipping ...

4/14/09 18:24:12.46 INFO[general] [38] SPT: Get neighbours for the reporting AP :172.16.101.87

4/14/09 18:24:12.78 INFO[general] [38] SPT: This node is already processed, skipping 172.16.101.81

4/14/09 18:24:12.78 INFO[general] [38]

4/14/09 18:24:12.78 INFO[general] [38] SPT: Traced not sucessfull

Remark: 172.16.101.81 & 172.16.101.97 are IP of switch

I have not idea what configuration that I have miss out. Please advice any thing that I have miss out. Thanks.

sbilgi · ‎04-20-2009

If traces show similar symtoms as previously shown, then:

* Check the network path between the Subscriber and Publisher Cisco CallManager Servers.

* Check the switch ports on which the Cisco CallManager Server is connected.

If you receive errors on switch ports, change the NIC setting on the server. If the NIC port speed is hardcoded to 100/Full, change it to 100/Auto. This can help clean the error, which is mostly caused due to port setting mismatch.

When no errors are seen on switchport of the switch, the SDLLINK out-of-service message should no longer be reported, and the call drops so the issue should be resolved.

chaijoo_lau · ‎04-24-2009

Hi sbilgi,

tks for ur reply.

BTW, the problem described is related to Wireless Control System.