Clients Not Detected on MSE (2710 Location Appliance)

Unanswered Question
Sep 14th, 2010

I have been having problems with clients not being detected on the MSE (2710 Location Appliance) since going to version 7.0.98.0 on the controllers. (a mixture of WISMs, 3750s and 5508s). I am running 7.0.164.0 on WCS.

The errors I seem to be getting on the 2710 are as follows: (there are hundreds of these errors)

AesLocationMathPureJava.validateInputsAndPrepareForCalculation Reason: Client Tx Power out of bounds. Expected -30 < clientTxPower < 60. Obtained: -128

The location appliance is sucessfully locating rogue aps (and their clients) with no problems. It is also locating one CCX v5 Client. We do not have any RFID tags at present.

If anyone has an idea what might be causing this that would be great.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
PerseSchool_2 Tue, 09/14/2010 - 04:55

I have the exact same issue with WCS Version 7.0.164.0, Controller version 7.0.98.0 & the WLA Version 6.0.102.0 , The Rouges show but no clients with the same error logged.

Please can someone post on this issue.

chris.brunt Tue, 09/14/2010 - 08:08

I have just heard from Cisco that the 2710 with 6.0.102.0 and 7.0.98.0 Controller / 7.0.164.0 WCS is not currently supported at the moment and they have asked me to log a TAC case. I will update here when I have more info.

PerseSchool_2 Wed, 09/15/2010 - 00:06

Many thanks for the information and good luck with the case. Looking forward to your update.

Regards

Paul

chris.brunt Wed, 09/15/2010 - 01:53

TAC case still proceeding. This is actually a known issue CSCth48443 -  Location Appliance stops tracking Wireless Client when WLC code is  7.0

PerseSchool_2 Tue, 09/21/2010 - 06:23

Thanks for the info Rob, anyway of getting the new version other than a TAC?

chris.brunt Tue, 09/21/2010 - 06:28

Yeah would be useful. I've just found out my service contract is out on the 2710 so I can't get it from TAC. In the process of renewing.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode