SM disassociated, Reason: 41

Products ePMP
1

Hello, New to the forum here… I am getting a disconnection every hour on the hour for the same reason and I can’t get it resolved through my service provider, who say it must be my wiring :\

Here is the device log for reference, I hope you guys can help me figure this out

Oct 23 20:19:51 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 331 seconds)
Oct 23 20:14:23 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 313 seconds)
Oct 23 20:08:21 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 345 seconds)
Oct 23 20:02:10 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 355 seconds)
Oct 23 19:56:12 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 342 seconds)
Oct 23 19:50:41 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 313 seconds)
Oct 23 19:46:54 F200_alaadin kernel: [88104.020000] SM associated with AP[00:04:56:27:0d:a2]
Oct 23 19:46:43 F200_alaadin kernel: [88092.320000] SM disassociated from AP[00:04:56:27:0d:a2] F=4985 11naht20. Reason: 41 (RECONNECT TO PRIMARY AP)
Oct 23 19:45:10 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 315 seconds)
Oct 23 19:39:16 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 338 seconds)
Oct 23 19:33:45 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 303 seconds)
Oct 23 19:28:15 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 315 seconds)
Oct 23 19:22:06 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 353 seconds)
Oct 23 19:15:49 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 359 seconds)
Oct 23 19:09:56 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 337 seconds)
Oct 23 19:03:49 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 351 seconds)
Oct 23 18:58:28 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 304 seconds)
Oct 23 18:52:22 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 350 seconds)
Oct 23 18:46:43 F200_alaadin kernel: [84492.310000] SM associated with AP[00:04:56:27:0d:a2]
Oct 23 18:46:36 F200_alaadin kernel: [84485.550000] SM disassociated from AP[00:04:56:27:0a:7a] F=6265 11naht20. Reason: 33 (GPFs MISS)
Oct 23 18:46:19 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 347 seconds)
Oct 23 18:45:14 F200_alaadin kernel: [84403.670000] SM disassociated from AP[00:04:56:27:0a:7a] F=5010 11naht20. Reason: 41 (RECONNECT TO PRIMARY AP)
Oct 23 18:41:04 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 304 seconds)
Oct 23 18:35:19 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 329 seconds)
Oct 23 18:29:28 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 334 seconds)
Oct 23 18:23:52 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 321 seconds)
Oct 23 18:18:08 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 327 seconds)
Oct 23 18:12:03 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 350 seconds)
Oct 23 18:05:51 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 356 seconds)
Oct 23 18:00:25 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 310 seconds)
Oct 23 17:54:59 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 300 seconds)
Oct 23 17:49:07 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 336 seconds)
Oct 23 17:45:14 F200_alaadin kernel: [80803.670000] SM associated with AP[00:04:56:27:0a:7a]
Oct 23 17:45:13 F200_alaadin kernel: [80802.700000] SM cannot be associated on AP[00:04:56:27:0a:7a] F=5010 11naht20. Reason: 24 (LOST INAR)
Oct 23 17:44:49 F200_alaadin kernel: [80779.130000] SM cannot be associated on AP[00:04:56:27:0a:7a] F=5010 11naht20. Reason: 24 (LOST INAR)
Oct 23 17:43:17 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 332 seconds)
Oct 23 17:43:10 F200_alaadin kernel: [80679.350000] SM disassociated from AP[00:04:56:27:0a:7a] F=5010 11naht20. Reason: 41 (RECONNECT TO PRIMARY AP)
Oct 23 17:37:36 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 325 seconds)
Oct 23 17:31:33 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 345 seconds)
Oct 23 17:25:52 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 325 seconds)
Oct 23 17:20:17 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 319 seconds)
Oct 23 17:14:12 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 348 seconds)
Oct 23 17:08:24 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 332 seconds)
Oct 23 17:02:15 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 353 seconds)
Oct 23 16:56:10 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 349 seconds)
Oct 23 16:50:00 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 354 seconds)
Oct 23 16:44:44 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 300 seconds)
Oct 23 16:43:10 F200_alaadin kernel: [77079.340000] SM associated with AP[00:04:56:27:0a:7a]
Oct 23 16:42:59 F200_alaadin kernel: [77068.850000] SM cannot be associated on AP[00:04:56:27:0a:7a] F=5010 11naht20. Reason: 24 (LOST INAR)
Oct 23 16:41:20 F200_alaadin kernel: [76969.570000] SM disassociated from AP[00:04:56:27:0a:7a] F=5010 11naht20. Reason: 41 (RECONNECT TO PRIMARY AP)
Oct 23 16:38:55 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 333 seconds)
Oct 23 16:32:48 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 351 seconds)
Oct 23 16:27:10 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 322 seconds)
Oct 23 16:21:18 F200_alaadin DEVICE-AGENT[4963]: Unable to discover cnMaestro URL (re-discover in 336 seconds)

image
image1333×676 57.8 KB

2

image
image1352×523 42.6 KB

3

Hey there @Aladdin_Elkadiri welcome to the Cambium forums. This forum typically deals with operators that are deploying Cambium equipment, not end users. There’s really not a whole lot that any of us can do to help you with this issue. One suggestion I would have is to see what firmware the operator is using on his radios and if it’s out of date, urge them to update.

From the event logs you have posted, it looks like perhaps that your operator has configured your radio with more then one AP to connect to, and after time, it disconnects, and tries to reconnect to another AP. There are various reasons why this might be happening… perhaps not enough seats have been configured on the primary AP, or your out farther then the AP’s max distance, or perhaps not using the right encryption type. I see that many of the operator’s AP’s are set to OPEN while some are set to WPA2… it could be that your radio is configured to use the wrong encryption type with a specific AP, and it’s failing over to another AP and then retrying after aa certain amount of time. Again… just lots of speculation because we’re only seeing a small part of the picture.

3 Likes
4

Hello Eric, Thank you very much for your reply. I appreciate your guidance. If there is anything else I can provide you to help you better understand my configuration I will be happy to provide. This will in turn allow me to give more concise feedback to my operator who is still insisting that my wiring is to blame. If not I am still very grateful to what you have indicated thus far.

5

Do you have access to the Configuration → Radio page? Can you post a screen shot of that? What firmware version is on your radio?

1 Like
6

F200_alaadin_config
F200_alaadin_config1627×1606 510 KB

7

It does not look like your provider has configured a preferred SSID to connect to, this means that the radio will scan and look for any open AP it can find and then try to connect, if it can’t connect, it will try another open SSID on the scan list. This is really not a good way to operate a WISP IMHO. If you look at the list there are many AP’s operating from what appear to be several different providers. Some of the channels they’re operating on are the same or overlapping, which can cause interference. The error message you’re getting, “No GPF’s from AP” is typically due to heavy RF interference disrupting communications. There’s probably one or more competing AP’s that may be disrupting your radio’s ability to connect.

You should ask your provider to configure your SM to connect to the AP that is the best for you and they should enter this into your radio as the preferred SSID, so the radio will always try to connect to it first. This may take some time to find the best AP to connect to as again, there are so many and even ones with the best signal might not be the best for you to connect if there’s heavy interference. If there’s a secondary/backup AP that is of good quality, they should configure that on your radio as well.

From what I can tell… I’m 99% certain that the issues you are experiencing are not related to a cabling issue. Your issues are due to your ISP’s wireless network. If your ISP continues to blame your cabling and refuses to investigate further, I’d find a new ISP.

1 Like
8

Thank you very much Eric. I will follow your recommendations.