INAC Miss Timeout

[Devlin_Hendry]

Hi,

I trust you all are well,

I do see there was a thread that was closed due to no replies or responses, but we are experiencing the same issues. Once the Sector and the SM are rebooted then it seems to connect. We have checked on the same settings to be applied on the secor and the SM but with no success we receive this error message still. We also get invalid security key, INAC Miss timeout, SM disassociated, Connection lost. Has anyone experieinced these issues and gotten it right?

Seemingly random "SM Disassociated" messages on AP for new 2.4 Force 200 install, SM not registering

Hi there, Recently out in the field we’ve had a few cases where an SM will show great signal levels to an AP in the AP scan, but the technician cannot get the SM to actually register and stay connected to the AP. The SM shows a check mark next to “Meets Reg Criteria” but the registration status is “Unknown”. When this happens, we also see a lot of seemingly random “SM Disassociated” messages in the AP’s log for the SM that is trying to connect. It is usually some combination of “Communicatio…

[Devlin_Hendry]

Just want to ask:

We had a user setup the field
Subscriber Module Target Receive Level at -45 but we never got many SMs connected at this level. Could this the reason it causes all the errors such as INAC Miss timeout, SM deregistered, Connection Lost ect?

[Eric_Ozrelic]

Why is your SM target receive level at -45dBm? By default this is typically -60dBm. The reason why you’re probably not seeing SM’s uplink RSSI at -45 is because this is a very high power level and the SM’s would have to be quite close to the AP. You really don’t want SM’s blasting at -45 at the AP though… as mentioned before the default and recommended power level is -60dBm.

[Devlin_Hendry]

Yes, this is what I thought as well. This has greatly improved my logs and SMs are connecting seemlessly. I also made some adjustments to dbi and dbm. Magic spot found. Thank you Eric