SMs are dropping Wireless Session often

Products ePMP
1

Hi everyone,

Hope you are well.

After investigation of intermittent connection of one of our customers, we found this in the backlog:
Sep 1 00:00:27 jerusalemcroft snmpd[2639]: DFS status: N/A
Sep 1 00:00:45 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Sep 1 00:01:53 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Sep 1 00:01:55 jerusalemcroft kernel: [ 119.610000] SM associated with AP[00:04:56:d8:11:30]
Sep 1 00:02:02 jerusalemcroft DEVICE-AGENT[2876]: SessionID unavailable, regenerating
Jun 8 06:32:02 jerusalemcroft kernel: [28454.300000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 33 (GPFs MISS)
Jun 8 06:32:05 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 8 06:35:46 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 8 06:37:03 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 8 06:37:34 jerusalemcroft kernel: [28786.040000] SM associated with AP[00:04:56:d8:11:30]
Jun 8 06:40:20 jerusalemcroft DEVICE-AGENT[2876]: send_lldp: SIOCG-IF-INDEX failed for eth1
Jun 9 08:44:29 jerusalemcroft kernel: [122801.110000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 48 (COMMUNICATION LOST)
Jun 9 08:44:45 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 08:45:15 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 08:46:32 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 08:50:02 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 08:50:48 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 08:51:49 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 08:55:48 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 08:57:03 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 08:58:01 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 09:00:34 jerusalemcroft kernel: [123765.850000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 32 (NO ALLOCATION ON AP)
Jun 9 09:00:51 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:01:37 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:02:31 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 09:06:32 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:07:02 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:08:31 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 09:09:27 jerusalemcroft kernel: [124298.360000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 33 (GPFs MISS)
Jun 9 09:09:32 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:10:01 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:11:04 jerusalemcroft kernel: [124396.320000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 33 (GPFs MISS)
Jun 9 09:11:17 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:19:48 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:21:02 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 09:23:02 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:23:04 jerusalemcroft kernel: [125116.120000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 49 (INVALID SECURITY KEY)
Jun 9 09:23:50 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:25:02 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 09:26:28 jerusalemcroft kernel: [125319.450000] SM associated with AP[00:04:56:d8:11:30]
Jun 9 09:26:36 jerusalemcroft kernel: [125327.860000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 49 (INVALID SECURITY KEY)
Jun 9 09:26:37 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:27:23 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:27:45 jerusalemcroft kernel: [125396.700000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 33 (GPFs MISS)
Jun 9 09:27:53 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:31:33 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:32:32 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 09:33:07 jerusalemcroft kernel: [125718.440000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 33 (GPFs MISS)
Jun 9 09:33:18 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:33:48 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:33:53 jerusalemcroft kernel: [125764.800000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 33 (GPFs MISS)
Jun 9 09:34:02 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:43:50 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:44:43 jerusalemcroft kernel: [126414.960000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 33 (GPFs MISS)
Jun 9 09:44:47 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:50:32 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:51:33 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 09:54:28 jerusalemcroft kernel: [126999.620000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 48 (COMMUNICATION LOST)
Jun 9 09:54:32 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 09:55:18 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 09:56:32 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 10:00:32 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 10:01:49 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 10:03:03 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 10:06:47 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 10:08:31 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 10:09:17 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 10:13:02 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 10:14:16 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 10:15:16 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 10:17:32 jerusalemcroft kernel: [128383.890000] SM associated with AP[00:04:56:d8:11:30]
Jun 9 10:20:29 jerusalemcroft DEVICE-AGENT[2876]: send_lldp: SIOCG-IF-INDEX failed for eth1
Jun 9 11:29:13 jerusalemcroft kernel: [132685.040000] SM disassociated from AP[00:04:56:d8:11:30] F=5735 11naht40plus. Reason: 32 (NO ALLOCATION ON AP)
Jun 9 11:29:39 jerusalemcroft snmpd[2639]: DFS status: N/A
Jun 9 11:30:01 jerusalemcroft snmpd[2639]: DFS status: Channel Availability Check at 0 MHz, band = -1 MHz
Jun 9 11:31:02 jerusalemcroft snmpd[2639]: DFS status: In-Service Monitoring
Jun 9 11:31:14 jerusalemcroft kernel: [132805.370000] SM associated with AP[00:04:56:d8:11:30]

There are various different error codes, so I just wanted to know, what does it mean?

Many thanks
David Riedl
Lothian Broadband

2

thats a nice log but what is the rssi and snr history like?
reason 48 literally means signal lost/can not decode session sync messages. check your signal and the snr in monitor-wireless and maybe use the e-align to see what is happening with the signal in real time

3

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.