RF Session Lost Repeatedly

smwtech · January 9, 2012, 3:01am

We have a problem we’re trying to run down for a customer. They are stating that their signal constantly, repeatedly, and randomly drops. We’ve replaced connectors, power supply,and the SM but haven’t resolved it yet.

Here is some info from the radio:

Software Version :
CANOPY 11.1 SM-DES
Board Type : P11
FPGA Version : 090711
FPGA Type : C25E
PLD Version : 1
Uptime : 22:38:41
…
Session Uptime : 09:15:56
…
Power Level :
Actual: -62 dBm Min: -81 dBm Max: -59 dBm
Transmit Power Level : 23 dBm
Jitter (Interference Level) : Actual: 2 Min: 1 Max: 15
Air Delay : 608 approximately 5.659 miles (29883 feet)
…
Latest Local Link Test Results
Current Results Stats for LUID: 60 Test Duration: 2 Pkt Length: 1522

Downlink Rate: 9811968 bps (9.81 Mbps)
Uplink Rate: 3025408 bps (3.03 Mbps)
Aggregate Rate: 12837376 bps (12.84 Mbps, 1042 pps)
Pkt Xmt (Act/Exp): 494/0 (247 pps)
Pkt Rcv (Act/Exp): 1591/0 (795 pps)

Downlink Efficiency: 96 Percent
Downlink Index (Act/Max): 96/100
Frag Count (Act/Exp): 39910/38328

Uplink Efficiency: 100 Percent
Uplink Index (Act/Max): 100/100
Frag Count (Act/Exp): 11818/11818

Here is the last two entries from the SM Session Log

01/08/2012 : 17:28:33 UTC : Event: SMSESFAIL, MsgType: REGREQTOMAXERR, NewState: OOSERVICE, Flag 0
01/08/2012 : 17:28:38 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/08/2012 : 17:28:38 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/08/2012 : 17:28:38 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/08/2012 : 17:29:01 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 761
01/08/2012 : 17:29:06 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/08/2012 : 17:29:10 UTC : Event: SMSESMSG, MsgType: REGREQTO, NewState: REGISTERING, Flag 0
01/08/2012 : 17:29:10 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/08/2012 : 17:29:10 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times

Anyone have any ideas what may be causing this? The AP is not overloaded, control slots are set correctly, and we have an unobstructed line of sight to the AP. This has been happening since the customer was installed two months ago, and we’ve upgraded the firmware from 11.0.1 to 11.1 with no change.

smwtech · January 9, 2012, 4:39pm

Okay, we have a second SM on a completely different tower doing the same thing, but in it’s SM Session Log, there is a bunch of entries like this one.

01/09/2012 : 06:53:56 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 581
01/09/2012 : 06:54:01 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/09/2012 : 06:54:05 UTC : Event: SMSESMSG, MsgType: REGREQTO, NewState: REGISTERING, Flag 0
01/09/2012 : 06:54:05 UTC : Event: SMAUTHENMSG, NewState: REGISTERING, Flag 0
01/09/2012 : 06:54:05 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/09/2012 : 06:54:05 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times

Link status page results:

Uplink Status
Power Level : -56 dBm
Jitter (Interference Level) : 1
Latest Remote Link Test Efficiency Percentage : NA %
Downlink Status
Power Level : -51 dBm
Jitter (Interference Level) : 1
Latest Remote Link Test Efficiency Percentage : 100 %
BER Results : 7.883514e-05
…

Current Results Stats for LUID: 42 Test Duration: 2 Pkt Length: 1522

Downlink Rate: 5108224 bps (5.11 Mbps)
Uplink Rate: 1628928 bps (1.63 Mbps)
Aggregate Rate: 6737152 bps (6.74 Mbps, 551 pps)
Pkt Xmt (Act/Exp): 272/0 (136 pps)
Pkt Rcv (Act/Exp): 831/0 (415 pps)

Downlink Efficiency: 100 Percent
Downlink Index (Act/Max): 100/100
Frag Count (Act/Exp): 19954/19954

Uplink Efficiency: 100 Percent
Uplink Index (Act/Max): 100/100
Frag Count (Act/Exp): 6363/6363

Our monitoring software shows no changes in the RF signal or jitter prior to the signal loss. This has happened the past couple of weeks, before and after the firmware upgrade from 11.0.1 to 11.1.

simon021 · January 8, 2013, 3:54pm

I’m seeing the same thing at a house with a signal in the mid 60s with perfect LOS to a tower thats very lightly loaded. AP and SM both on 11.2. Link tests are 100/100 in 2x. They are complaining of random outages a couple times a night. Everything looks great on the graphs and in Wireless Manager, but today I noticed these entries in the log.

12/31/2012 : 04:51:51 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
12/31/2012 : 04:51:51 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
12/31/2012 : 04:51:51 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/01/2013 : 01:51:47 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/01/2013 : 01:51:55 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/01/2013 : 01:51:55 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/01/2013 : 01:51:55 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/01/2013 : 19:13:13 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/01/2013 : 19:13:20 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/01/2013 : 19:13:22 UTC : Event: SMSESMSG, MsgType: REGREQTO, NewState: REGISTERING, Flag 0
repeated 1 times
01/01/2013 : 19:13:25 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/01/2013 : 19:13:25 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/03/2013 : 03:25:37 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/03/2013 : 03:25:45 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/03/2013 : 03:25:45 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/03/2013 : 03:25:45 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/03/2013 : 22:05:33 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/03/2013 : 22:05:40 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/03/2013 : 22:05:42 UTC : Event: SMSESMSG, MsgType: REGREQTO, NewState: REGISTERING, Flag 0
01/03/2013 : 22:05:42 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/03/2013 : 22:05:42 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/03/2013 : 22:25:15 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/03/2013 : 22:25:22 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/03/2013 : 22:25:22 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/03/2013 : 22:25:23 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/06/2013 : 18:01:30 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/06/2013 : 18:01:38 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/06/2013 : 18:01:38 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/06/2013 : 18:01:38 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/06/2013 : 21:55:32 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/06/2013 : 21:55:39 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/06/2013 : 21:55:39 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/06/2013 : 21:55:39 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/07/2013 : 03:05:14 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/07/2013 : 03:05:21 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/07/2013 : 03:05:22 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/07/2013 : 03:05:22 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/07/2013 : 03:06:45 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/07/2013 : 03:06:53 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/07/2013 : 03:06:53 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/07/2013 : 03:06:53 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/07/2013 : 03:08:24 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/07/2013 : 03:08:31 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/07/2013 : 03:08:31 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/07/2013 : 03:08:31 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/07/2013 : 03:11:05 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/07/2013 : 03:11:12 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/07/2013 : 03:11:14 UTC : Event: SMSESMSG, MsgType: REGREQTO, NewState: REGISTERING, Flag 0
01/07/2013 : 03:11:14 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/07/2013 : 03:11:14 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/07/2013 : 03:25:01 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/07/2013 : 03:25:08 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/07/2013 : 03:25:08 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/07/2013 : 03:25:08 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/07/2013 : 05:13:53 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/07/2013 : 05:14:00 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/07/2013 : 05:14:00 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/07/2013 : 05:14:00 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/07/2013 : 05:21:15 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/07/2013 : 05:21:22 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/07/2013 : 05:21:22 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/07/2013 : 05:21:22 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
01/08/2013 : 02:47:06 UTC : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 401
01/08/2013 : 02:47:13 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/08/2013 : 02:47:13 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 0
01/08/2013 : 02:47:13 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times

I’m wondering if anyone else has seen this issue, of if you have made any progress on it

hci · January 21, 2013, 7:14pm

So what does ‘NewState: OOSERVICE’ mean? And SMSESFAIL, SMVCERR?

admin_1 · February 14, 2013, 10:09pm

OOService = Out of Service
SMSESFAIL = SM Session Fail
SMVCERR = SM VC Error

Possible interference could cause this.
Try running a spectrum analyzer from the AP and see if this is the cause.

smwtech · March 4, 2013, 5:04pm

We ran the spectrum analyzer before and after changing the frequency in the AP, and didn’t see any interference but that must have been it because the customer hasn’t had any issues since we did it. I don’t think it was the SM, because it had been swapped out and other customers were also reporting similar issues.

Rapid_Tommy · November 23, 2015, 7:24pm

Ok so I have encountered the very same issue as well. And we have done spectrum analysis and shows nothing coming up to interefere. We have been told to adjust the contention slots and still no improvement. Client complains of latency and drops but is at -49/-59 in the SM and AP. Here is what the logs say… Cambium could we get a suggestion from you?? 11/17/2015 : 20:42:04 EDT : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0 11/17/2015 : 20:42:04 EDT : Event: SMSESINS, NewState: REGISTERED, Flag 15 11/17/2015 : 20:42:04 EDT : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0 repeated 2 times 11/18/2015 : 13:39:22 EDT : Event: SMSESFAIL, MsgType: OOS, NewState: OOSERVICE, Flag 0 11/18/2015 : 13:40:41 EDT : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0 11/18/2015 : 13:40:41 EDT : Event: SMSESINS, NewState: REGISTERED, Flag 16 11/18/2015 : 13:40:41 EDT : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0 repeated 2 times 11/19/2015 : 21:27:16 EDT : Event: SMSESFAIL, MsgType: OOS, NewState: OOSERVICE, Flag 0 11/19/2015 : 21:29:17 EDT : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0 11/19/2015 : 21:29:17 EDT : Event: SMSESINS, NewState: REGISTERED, Flag 14 11/19/2015 : 21:29:17 EDT : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0 repeated 2 times 11/23/2015 : 13:41:58 EDT : Event: SMSESFAIL, MsgType: OOS, NewState: OOSERVICE, Flag 0 11/23/2015 : 13:43:07 EDT : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0 11/23/2015 : 13:43:10 EDT : Event: SMSESMSG, MsgType: REGREQTO, NewState: REGISTERING, Flag 0 11/23/2015 : 13:43:10 EDT : Event: SMSESINS, NewState: REGISTERED, Flag 14 11/23/2015 : 13:43:10 EDT : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0 repeated 2 times 11/23/2015 : 13:45:01 EDT : Event: SMSESFAIL, MsgType: OOS, NewState: OOSERVICE, Flag 0 11/23/2015 : 13:46:17 EDT : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0 11/23/2015 : 13:46:20 EDT : Event: SMSESMSG, MsgType: REGREQTO, NewState: REGISTERING, Flag 0 11/23/2015 : 13:46:20 EDT : Event: SMSESINS, NewState: REGISTERED, Flag 14 11/23/2015 : 13:46:20 EDT : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0 repeated 2 times 11/23/2015 : 13:47:23 EDT : Event: SMSESFAIL, MsgType: OOS, NewState: OOSERVICE, Flag 0 11/23/2015 : 13:49:06 EDT : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0 11/23/2015 : 13:49:06 EDT : Event: SMSESINS, NewState: REGISTERED, Flag 14 11/23/2015 : 13:49:06 EDT : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0 repeated 2 times

Chitrang · November 24, 2015, 3:44am

Hi Tommy,
What software version of Canopy are you using, Also are you using RADIUS authentication for SM?

Ted_Stewart · November 25, 2015, 7:02pm

I've had tons of problems with customers' routers jamming out their 2.4 GHz SMs. It's very erratic, but it usually shows up as burst noise on the SM spectrums. We only have a handfull of 5 GHz SMs, but I would expect precisely the same problem when dealing with dual band routers.

I've gotten in the habit of asking if people have replaced their routers whenever I see any kind of noise. More often than not, that's the issue. Changing the new router to use a 20 MHz channel away from the SM frequency fixes it.

We had one customer with problems with what was obviously locally generated noise who for three months swore up and down they didn't change anything, and specifically did not have a new router. They refused to work with me when I called because they figured it had to be defective equipment on our part. Eventually, I was lucky enough to call when their son was there. The first thing out of his mouth: "The problem started right after we replaced the router. Could that be part of the problem?" *Facepalm*

MohawkOne · December 30, 2016, 6:27pm

Still no solution. Anyone resolve this yet?

Just wondering thanks.

@Ted Stewart wrote:
I've had tons of problems with customers' routers jamming out their 2.4 GHz SMs. It's very erratic, but it usually shows up as burst noise on the SM spectrums. We only have a handfull of 5 GHz SMs, but I would expect precisely the same problem when dealing with dual band routers.

I've gotten in the habit of asking if people have replaced their routers whenever I see any kind of noise. More often than not, that's the issue. Changing the new router to use a 20 MHz channel away from the SM frequency fixes it.

We had one customer with problems with what was obviously locally generated noise who for three months swore up and down they didn't change anything, and specifically did not have a new router. They refused to work with me when I called because they figured it had to be defective equipment on our part. Eventually, I was lucky enough to call when their son was there. The first thing out of his mouth: "The problem started right after we replaced the router. Could that be part of the problem?" *Facepalm*

MohawkOne · July 19, 2019, 12:59pm

Still none?

SBBinc · January 13, 2020, 4:55pm

We are seeing the same issue right now. Was there any resolution on this?

leon_rolls · October 17, 2021, 4:50pm

was this ever resolved having the sane issue

Steven · October 21, 2021, 2:33am

This thread was originally created discussing issues with the old Canopy PMP100 series 9 years ago.

I would recommend starting from scratch with a fresh thread with fresh details.

Unless you are still having trouble with PMP100 in which case I’d recommend… rip and replace!

But seriously “the same problem” might not be the same at all if you don’t provide details. There are many reasons sessions might drop.

CambiumMatt · October 21, 2021, 2:20pm

These are great points Steven. I would highly recommend a new thread with additional detail around your specific issue.

64spoons · January 31, 2024, 3:59pm

As usual, a valid problem with log entries gets no resolution and the inevitable response from Cambium… “Start a new thread”. I hope that Cambium realizes that this thread comes up on searches for people that are having the same issue.