Abnormal log messages and SM dropping regularly each evening

Hi all,

We’ve had one customer on an F300 that is dropping every day, accompanied by some interesting log events that we have not seen before. The SM is running on 4.6.2STA, using an STA frequency. Spectrum analyzer doesn’t show anything else on that frequency at either the AP or SM end. The ICMP monitoring for this device shows that in the evening, the latency spikes real high and eventually the SM drops completely. Usually the consistent latency issues in the evenings would indicate the connection or the AP itself is being maxed out, but the AP seems to be running at less than 75% capacity at peak, and the customer rarely comes close to maxing out her own connection. Congestion also wouldn’t explain why it loses the wireless link at this time. Here are the messages in the log (it pretty much looks the same every day, sanitized for security):

Aug 31 23:06:54 Cust-Radio kernel: [34331.670147] SM associated with AP[xx:xx:xx:xx:xx:xx]
Aug 31 23:06:21 Cust-Radio kernel: [34298.558941] SM cannot be associated on AP[xx:xx:xx:xx:xx:xx] F=5860 11acvht40plus. Reason: 16 (INA RETRIES EXHAUSTED)
Aug 31 23:06:21 Cust-Radio kernel: [34298.558094] SM cannot be associated on AP[xx:xx:xx:xx:xx:xx] F=5860 11acvht40plus. Reason: 24 (LOST INAR)
Aug 31 23:05:56 Cust-Radio kernel: [34274.324181] SM disassociated from AP[xx:xx:xx:xx:xx:xx] F=5860 11acvht40plus. Reason: 49 (INVALID SECURITY KEY)
Aug 31 23:05:52 Cust-Radio kernel: [34269.532980] SM associated with AP[xx:xx:xx:xx:xx:xx]
Aug 31 23:04:47 Cust-Radio kernel: [34204.719992] SM disassociated from AP[xx:xx:xx:xx:xx:xx] F=5860 11acvht40plus. Reason: 32 (NO ALLOCATION ON AP)
Aug 31 23:03:44 Cust-Radio kernel: [34142.121591] SM associated with AP[xx:xx:xx:xx:xx:xx]
Aug 31 23:02:43 Cust-Radio kernel: [34080.638087] SM cannot be associated on AP[xx:xx:xx:xx:xx:xx] F=5860 11acvht40plus. Reason: 19 (LOST AID)
Aug 31 23:01:03 Cust-Radio kernel: [33980.812496] SM disassociated from AP[xx:xx:xx:xx:xx:xx] F=5860 11acvht40plus. Reason: 32 (NO ALLOCATION ON AP)
Aug 31 22:55:36 Cust-Radio kernel: [33654.413124] SM associated with AP[xx:xx:xx:xx:xx:xx]
Aug 31 22:54:29 Cust-Radio kernel: [33586.988983] SM cannot be associated on AP[xx:xx:xx:xx:xx:xx] F=5860 11acvht40plus. Reason: 16 (INA RETRIES EXHAUSTED)
Aug 31 22:54:29 Cust-Radio kernel: [33586.988087] SM cannot be associated on AP[xx:xx:xx:xx:xx:xx] F=5860 11acvht40plus. Reason: 24 (LOST INAR)
Aug 31 22:52:38 Cust-Radio kernel: [33475.623377] SM disassociated from AP[xx:xx:xx:xx:xx:xx] F=5860 11acvht40plus. Reason: 32 (NO ALLOCATION ON AP)
Aug 31 14:06:06 Cust-Radio kernel: [ 1883.618218] SM associated with AP[xx:xx:xx:xx:xx:xx]
Aug 31 14:05:27 Cust-Radio kernel: [ 1845.143094] SM disassociated from AP[xx:xx:xx:xx:xx:xx] F=5860 11acvht40plus. Reason: 32 (NO ALLOCATION ON AP)

about to open a support ticket, but thought we would ask around here to see if anybody else has had this combination of log events before.

The Invalid Security Key log event usually indicates interference if the key is actually set properly in the SM, so that may just be what we are dealing with here, but whatever it is doesn’t seem to show up on spectrum, at least not during office hours.

This is not true. It could be a problem with signal quality. Check Line of Sight and RSSI.

It has been in our experience. We’ve had high levels of interference cause SMs to fail to connect with the Invalid Security Key message in the logs. The line of sight and signal quality are quite good, -60 RSSI.

Did u test other channel ?

I have forwarded this to our support team.
Ray

Hello @SBBinc,

did you have a chance to raise a support ticket? If yes, PM me the number please!

Which exactly F300 is it?
Why don’t you upgrade to 4.7.0.1?

It can be a bad signal or just failed radio. Will it be the same if you swap the radio?

Is 4.7.0.1 the recommended version? I thought that it was 4.6.2 or 4.7.1 and to avoid 4.7.0.1 (I thought?). I was told that 4.7.1 fixed all the issues with 4.7.0.1?

Anyway, I don’t have anything useful to add to this thread… just surprised at that advice :slight_smile: