cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2895
Views
0
Helpful
4
Replies

AIR-AP2802i: Clients connection failure related to invalid staid from log

steiostb1
Level 1
Level 1

Problem

  • We are suspecting some client are unable to connect to 2802 APs. Clients are not connected to the nearest AP. even if a client is standing right in front of an AP, other APs with weaker signal are prefered.
  • Affected clients are both Apple and other brands (Dell etc.) and are not related to 2.4Ghz or 5Ghz.
  • Affected APs are running with power level 1* on 2.4Ghz & 5Ghz.
  • On these APs logs are flooded with invalid staid recieved:

Apr 26 00:48:49 kernel: [*04/26/2017 00:48:48.9936] invalid staid 63 received
Apr 26 00:48:49 kernel: [*04/26/2017 00:48:49.0988] invalid staid 63 received
Apr 26 00:48:49 kernel: [*04/26/2017 00:48:49.1960] invalid staid 63 received
Apr 26 00:48:49 kernel: [*04/26/2017 00:48:49.2949] invalid staid 63 received
Apr 26 00:48:49 kernel: [*04/26/2017 00:48:49.3962] invalid staid 63 received
Apr 26 00:48:49 kernel: [*04/26/2017 00:48:49.4966] invalid staid 63 received
Apr 26 00:48:49 kernel: [*04/26/2017 00:48:49.5976] invalid staid 63 received
Apr 26 00:48:49 kernel: [*04/26/2017 00:48:49.6953] invalid staid 63 received

  • These logs corresponding well with when we see clients are unable to connect, but are also present sometimes at night when no users are connected.
  • The log output have been present after we upgraded software to 8.2.151.0 (from 8.2.131.0).

What does these logs mean?

I have found two bugs related to this: 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc06325

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvd47081/

Troubleshooting

  • Installed newest network card drivers on the clients
  • Turned of the 5Ghz radio on the AP
  • Turned of the 2.4Ghz radio on the AP
  • Rebooted AP
  • Users who connected right before the "invalid staid recieved"  indicated that this is not related to a sertain hardware. 
  • "invalid staid recieved" might be triggered by clients that tries to connect, but are unable.

Solution so far

  • Affected APs have been replaced with older 1142 APs (running on the same controller & software) and the affected clients are now able to connect to the APs. Clients in the region have reported to have better signal strenght.
4 Replies 4

steiostb1
Level 1
Level 1

Have anybody have simular experienced or something to add?

Thanks

Please read https://supportforums.cisco.com/discussion/13284941/82mr6-interim-release-availability 

I seem to have the exact same issue. I have just opened a TAC case about it. Will let you (and others who read this thread) about the conclusion once the case is closed.

Good to see that this really is a issue. Because my TAC was closed with this explanation:

This is a cosmetic error message; it has no impact on APs operations, it will be addressed on below bug:
CSCva37010    invalid staid XXX received
 
Bug link:
 
The bug will be fixed on 8.2MR6 and future 8.3MRs.
 
Review Cisco Networking for a $25 gift card