Client rapidly roaming between APs

jpjeffery
Getting noticed

Client rapidly roaming between APs

Hi

 

Our new WiFi system, using Meraki MR36 APs, has been pretty solid since we went live with it in the summer.

 

However, just occasionally we get people saying they're experiencing bad connectivity, even in areas where signal strength looks strong according to i) our Visiwave Site Survey software and ii) other users in the same areas experiencing no issues.

 

I've not had much luck establishing what the issue might be, but today we had a visitor in the office who kept moving with his laptop from a meeting room, to his desk, to a communal table, and back again. After his meeting finished he came over to report that he was getting very poor connectivity.

 

I got his laptop's hostname and investigated, and discovered that, according to the Meraki console timeline, his PC was rapidly switching between APs, or even switching from an AP...to the same AP.

 

In the space of a minute just after he arrived the timeline shows 11 events, culminating in the last of which showing he had an steady connection for 18 minutes.

 

After that 18 minutes of peace, the timeline gets busy, as the client roams from AP to AP, with sometimes the second AP being the same as the AP it roamed from. For example:

 

11:09:29Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.

 

(The first number in the WAP name represents the floor number. The fella in question and I are on the 3rd floor)

 

From 11:09:20 to 11:18:59 there are 90 roaming events (including a 5 minute settled period at around 11:17).

 

Then from 11:52 to 11:59:53 we have 75 roaming events.

 

That's a grand total of 176 roams in about 70 minutes.

 

I compared that to other devices but couldn't find anything like that much going on with other clients.

 

Since so many other people get no problems, I'm inclined to think it's a client-side issue, but could do with something more concrete than a mere hunch!

 

So, the question is, do such rapid roaming events explain the poor connectivity (either as a cause or as a symptom)?

 

I shall reply to this post with the full timeline (as tidied and anonymised in Excel) for your delectation and delight!

8 Replies 8
jpjeffery
Getting noticed

Here's the full spreadsheet of the timeline:

 

DateTimeEventEvent DescriptionDetailExtra Detail

Dec-08

10:51:11Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-3NB.TIME TO CONNECT650

Dec-08

10:51:16Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA.TIME TO CONNECT30

Dec-08

10:51:23Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA.TIME TO CONNECT40

Dec-08

10:51:31Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA, and then the client roamed to access point WAP-3NB.TIME TO CONNECT20

Dec-08

10:51:37Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT210

Dec-08

10:51:47Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA.TIME TO CONNECT40

Dec-08

10:51:53Successfulconnection to SSID GUESTS for 2 minutes on access point WAP-3SA, and then the client roamed to access point WAP-4NA.TIME TO CONNECT40

Dec-08

10:51:59Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.TIME TO CONNECT40

Dec-08

10:52:06Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-3NB.TIME TO CONNECT30

Dec-08

10:52:09Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA.TIME TO CONNECT40

Dec-08

10:52:17Successfulconnection to SSID GUESTS for 18 minutes on access point WAP-4NA.TIME TO CONNECT50

Dec-08

11:09:20Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:09:29Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:09:36Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:09:49Successfulconnection to SSID GUESTS for a few seconds on access point WAP-1N1, and then the client roamed to access point WAP-3SA.TIME TO CONNECT60

Dec-08

11:09:49Disconnectedfrom SSID GUESTS from access point WAP-3NB, and then the client roamed to access point WAP-1N1.802.11 REASON (CODE 2)Invalid authentication

Dec-08

11:09:49Successfulconnection to SSID GUESTS for a few seconds on access point WAP-1N1.  

Dec-08

11:09:50Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA.TIME TO CONNECT110

Dec-08

11:09:58Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:10:07Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:10:14Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT690

Dec-08

11:10:20Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA.TIME TO CONNECT60

Dec-08

11:10:29Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA, and then the client roamed to access point WAP-3NB.TIME TO CONNECT20

Dec-08

11:10:35Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:10:42Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT60

Dec-08

11:10:48Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:10:54Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:11:00Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:11:06Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:11:12Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:11:18Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:11:24Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT70

Dec-08

11:11:30Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT60

Dec-08

11:11:36Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:11:42Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:11:48Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.  

Dec-08

11:11:53Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:11:59Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:12:05Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:12:11Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:12:17Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:12:23Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:12:29Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:12:35Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT60

Dec-08

11:12:41Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:12:47Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:12:53Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:12:59Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:13:05Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.  

Dec-08

11:13:11Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:13:16Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:13:22Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:13:28Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:13:34Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:13:40Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT80

Dec-08

11:13:46Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:13:52Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:13:58Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:14:04Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:14:10Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:14:16Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA.  

Dec-08

11:14:16Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA.TIME TO CONNECT50

Dec-08

11:14:26Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA, and then the client roamed to access point WAP-4NA.TIME TO CONNECT40

Dec-08

11:14:32Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.TIME TO CONNECT40

Dec-08

11:14:32Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.  

Dec-08

11:14:40Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA.TIME TO CONNECT40

Dec-08

11:14:46Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA.TIME TO CONNECT40

Dec-08

11:14:59Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:15:06Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA.TIME TO CONNECT70

Dec-08

11:15:12Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA.TIME TO CONNECT40

Dec-08

11:15:37Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA.TIME TO CONNECT30

Dec-08

11:15:42Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA.TIME TO CONNECT60

Dec-08

11:15:44Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA, and then the client roamed to access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:15:45Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3N1.TIME TO CONNECT30

Dec-08

11:15:54Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.TIME TO CONNECT1840

Dec-08

11:15:54Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3SA, and then the client roamed to access point WAP-3N1.  

Dec-08

11:15:54Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.  

Dec-08

11:16:02Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.TIME TO CONNECT40

Dec-08

11:16:09Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:16:19Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-3N1.TIME TO CONNECT50

Dec-08

11:16:26Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1, and then the client roamed to access point WAP-3N1.TIME TO CONNECT40

Dec-08

11:16:32Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.TIME TO CONNECT40

Dec-08

11:16:42Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:16:49Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:17:00Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:17:26Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4N1.TIME TO CONNECT40

Dec-08

11:17:35Successfulconnection to SSID GUESTS for 5 minutes on access point WAP-4N1, and then the client roamed to access point WAP-4NA.  

Dec-08

11:17:35Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1, and then the client roamed to access point WAP-3N1.TIME TO CONNECT60

Dec-08

11:17:36Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-4NA.TIME TO CONNECT50

Dec-08

11:17:44Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.TIME TO CONNECT60

Dec-08

11:17:44Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.  

Dec-08

11:17:50Successfulconnection to SSID GUESTS for a few seconds on access point WAP-2N2.TIME TO CONNECT40

Dec-08

11:18:01Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-3N1.TIME TO CONNECT50

Dec-08

11:18:07Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.TIME TO CONNECT60

Dec-08

11:18:16Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-2N2.TIME TO CONNECT30

Dec-08

11:18:23Successfulconnection to SSID GUESTS for a few seconds on access point WAP-2N2.TIME TO CONNECT80

Dec-08

11:18:31Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.TIME TO CONNECT60

Dec-08

11:18:38Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-2N2.TIME TO CONNECT240

Dec-08

11:18:44Successfulconnection to SSID GUESTS for a few seconds on access point WAP-2N2, and then the client roamed to access point WAP-3N1.TIME TO CONNECT30

Dec-08

11:18:52Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.TIME TO CONNECT60

Dec-08

11:18:59Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.TIME TO CONNECT30

Dec-08

11:52:26Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-2N1.  

Dec-08

11:52:26Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3N1.TIME TO CONNECT60

Dec-08

11:52:32Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-2N1.TIME TO CONNECT40

Dec-08

11:52:38Successfulconnection to SSID GUESTS for a few seconds on access point WAP-2N1.TIME TO CONNECT40

Dec-08

11:52:38Successfulconnection to SSID GUESTS for a few seconds on access point WAP-2N1.  

Dec-08

11:52:44Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1, and then the client roamed to access point WAP-4N1.TIME TO CONNECT240

Dec-08

11:52:49Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.TIME TO CONNECT30

Dec-08

11:52:56Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.TIME TO CONNECT50

Dec-08

11:52:56Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1, and then the client roamed to access point WAP-3N1.  

Dec-08

11:52:56Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.  

Dec-08

11:53:02Successfulconnection to SSID GUESTS for a minute on access point WAP-3SA.TIME TO CONNECT50

Dec-08

11:53:08Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-4NA.TIME TO CONNECT30

Dec-08

11:53:13Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.TIME TO CONNECT50

Dec-08

11:53:21Successfulconnection to SSID GUESTS for a few seconds on access point WAP-2N1.TIME TO CONNECT80

Dec-08

11:53:21Disconnectedfrom SSID GUESTS from access point WAP-4NA, and then the client roamed to access point WAP-2N1.802.11 REASON (CODE 2)Invalid authentication

Dec-08

11:53:21Successfulconnection to SSID GUESTS for a few seconds on access point WAP-2N1.  

Dec-08

11:53:23Successfulconnection to SSID GUESTS for a few seconds on access point WAP-2N1, and then the client roamed to access point WAP-4N1.  

Dec-08

11:53:23Successfulconnection to SSID GUESTS for a few seconds on access point WAP-2N1, and then the client roamed to access point WAP-4NA.TIME TO CONNECT50

Dec-08

11:53:24Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.TIME TO CONNECT50

Dec-08

11:53:30Successfulconnection to SSID GUESTS for 3 minutes on access point WAP-4N1.TIME TO CONNECT40

Dec-08

11:53:30Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.  

Dec-08

11:53:38Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT80

Dec-08

11:53:45Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.  

Dec-08

11:54:02Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA.TIME TO CONNECT540

Dec-08

11:54:09Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.TIME TO CONNECT40

Dec-08

11:54:17Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:54:23Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT530

Dec-08

11:54:37Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:54:44Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:54:51Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT90

Dec-08

11:54:57Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:55:10Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:55:16Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:55:23Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:55:29Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:55:39Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:55:45Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:55:54Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:56:00Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT40

Dec-08

11:56:09Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT60

Dec-08

11:56:15Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:56:24Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA.TIME TO CONNECT60

Dec-08

11:56:30Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-4N1.TIME TO CONNECT80

Dec-08

11:56:38Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.TIME TO CONNECT60

Dec-08

11:56:44Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA.TIME TO CONNECT50

Dec-08

11:56:49Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.TIME TO CONNECT50

Dec-08

11:56:58Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.TIME TO CONNECT90

Dec-08

11:57:05Successfulconnection to SSID GUESTS for a minute on access point WAP-4NA, and then the client roamed to access point WAP-4N1.  

Dec-08

11:57:05Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-3NB.TIME TO CONNECT20

Dec-08

11:57:11Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4N1.TIME TO CONNECT50

Dec-08

11:57:19Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.TIME TO CONNECT40

Dec-08

11:57:19Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.  

Dec-08

11:57:27Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:57:34Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:57:42Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT90

Dec-08

11:57:48Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.  

Dec-08

11:57:49Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4N1.TIME TO CONNECT960

Dec-08

11:57:58Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.TIME TO CONNECT80

Dec-08

11:58:06Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.TIME TO CONNECT30

Dec-08

11:58:14Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.TIME TO CONNECT40

Dec-08

11:58:21Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1, and then the client roamed to access point WAP-3NB.TIME TO CONNECT30

Dec-08

11:58:27Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB.TIME TO CONNECT50

Dec-08

11:58:36Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB.TIME TO CONNECT80

Dec-08

11:58:43Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4N1.TIME TO CONNECT30

Dec-08

11:58:50Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.TIME TO CONNECT50

Dec-08

11:58:57Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.TIME TO CONNECT30

Dec-08

11:59:03Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA.TIME TO CONNECT80

Dec-08

11:59:11Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4NA.TIME TO CONNECT50

Dec-08

11:59:17Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3N1.TIME TO CONNECT50

Dec-08

11:59:24Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.TIME TO CONNECT40

Dec-08

11:59:33Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.  

Dec-08

11:59:43Successfulconnection to SSID GUESTS for a few seconds on access point WAP-2N1.TIME TO CONNECT50

Dec-08

11:59:49Successfulconnection to SSID GUESTS for a few seconds on access point WAP-4N1.  

Dec-08

11:59:51Successfulconnection to SSID GUESTS for a few seconds on access point WAP-3N1.TIME TO CONNECT30

Dec-08

11:59:53Failedconnection to SSID GUESTS on access point WAP-4N1 during authentication because the client did not provide credentials.MERAKI REASON (CODE 101)EAPoL timeout

 

alemabrahao
Kind of a big deal
Kind of a big deal

There could be several reasons why this is happening.

 

Some devices have more aggressive roaming algorithms than others. If the device’s roaming algorithm is set to switch APs at the slightest signal fluctuation, it could lead to frequent roaming.

 

If the coverage areas of your APs overlap too much, a device might constantly switch between them. This is especially likely if the signal strengths of the APs are similar.

 

Certain features on the APs, like Client Balancing or Band Steering, can influence client roaming behavior. If these features are not configured properly, they might cause the client to roam more often than necessary.

 

To troubleshoot this issue, you could try the following

 

If possible, adjust the roaming aggressiveness on the client device,


Try disabling features like Client Balancing or Band Steering to see if it affects the roaming behavior.


If you suspect a particular AP might be causing the issue, try resetting it or replacing it with a known good AP.


Running packet captures can help you understand what’s happening during the roaming events.


Remember, every environment is unique, so what works for one might not work for another. It’s all about finding the right balance for your specific needs.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
GIdenJoe
Kind of a big deal
Kind of a big deal

Hmm tough one.  If it's a single client it could be a driver issue.  However it would be a great idea to have an over the air capture at the location of that client on the channels of both AP's there and try to see when it decides to roam if anything precedes it.

Some stuff that can precede it:
- interference from something else

- alot of retransmissions

- 802.11v messages from the AP's to the client.

jpjeffery
Getting noticed


@GIdenJoe wrote:

Hmm tough one.  If it's a single client it could be a driver issue.


I wondered that too, but it's not one of ours so can't really do anything about it. 😞

 


@GIdenJoe wrote:

...it would be a great idea to have an over the air capture at the location of that client...


Honestly, I've no idea where to even start with that idea!

cmr
Kind of a big deal
Kind of a big deal

I'd check to see if the same happens when the client has a power adapter connected, it could be a poor driver making a mess of power saving modes. Otherwise, if you have client balancing enabled on that SSID, try disabling it.

jpjeffery
Getting noticed


@cmr wrote:

I'd check to see if the same happens when the client has a power adapter connected, it could be a poor driver making a mess of power saving modes. 


That's an interesting point. I can't be sure, but I *think* it may have only started when he unplugged his laptop to join his meeting in a meeting room. He also didn't seem to have any issues after that meeting ended and he was back at the desk he was using and so plugged in to a power supply.

cmr
Kind of a big deal
Kind of a big deal

In that case disable all power saving on the wireless adapter on that laptop and make sure it has the latest drivers.  With Intel chipsets there is a (2021 from memory) update that pretty much fixed the issue for WiFi5 adapters.  Look at the Intel drivers from their site, the OEM may not have published the newer ones...

jpjeffery
Getting noticed


@cmr wrote:

In that case disable all power saving on the wireless adapter on that laptop and make sure it has the latest drivers.  With Intel chipsets there is a (2021 from memory) update that pretty much fixed the issue for WiFi5 adapters.  Look at the Intel drivers from their site, the OEM may not have published the newer ones...


If I ever see him again, I'll suggest it to him. 🙂

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels