ArubaOS and Controllers

Reply
Occasional Contributor II

Could have Mismatched SSID

I am having trouble finding the cause of the "trouble finding AP" error. Below is the Process Log.

Sep 22 07:47:06 sapd: <404052> |AP HNT3-4@10.128.0.147 sapd| AM 00:1a:1e:ac:1d:80: STA 00:24:36:91:94:8e has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:07 sapd: <404052> |AP FLT2-4@10.128.0.10 sapd| AM 00:1a:1e:a8:8c:40: STA 00:1f:3b:9a:d8:6f has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:07 sapd: <404052> |AP HLT3-5@10.128.0.156 sapd| AM 00:1a:1e:ac:05:20: STA 00:26:4a:6c:09:b2 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:08 sapd: <404075> |AP EMCS4-3@10.128.0.165 sapd| AM 00:1a:1e:a8:8a:40: ARM - decreasing power cov-index 13/0 tx-power 6 new_rra 10/4
Sep 22 07:47:09 sapd: <404052> |AP UC2-4@10.128.0.195 sapd| AM 00:1a:1e:ac:35:40: STA 00:1e:4c:78:03:f6 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:10 sapd: <404052> |AP HLT3-3@10.128.0.108 sapd| AM 00:1a:1e:9c:c4:20: STA c4:2c:03:ef:7d:a8 has trouble with AP 00:1a:1e:9c:c4:20. Reason code: 17. Reason: Association Denied; AP is resource constrained
Sep 22 07:47:11 sapd: <404052> |AP HLT3-5@10.128.0.156 sapd| AM 00:1a:1e:ac:05:20: STA c4:2c:03:ef:7d:a8 has trouble with AP 00:1a:1e:ac:05:20. Reason code: 17. Reason: Association Denied; AP is resource constrained
Sep 22 07:47:12 sapd: <404030> |AP LIB1-2@10.128.0.68 sapd| AM 00:1a:1e:ac:6e:60: Frame Retry Rate at 100 for STA 00:26:5e:ee:09:19 AP 00:1a:1e:ac:6e:60
Sep 22 07:47:12 sapd: <404052> |AP UC2-13@10.128.0.88 sapd| AM 00:24:6c:c5:cb:e0: STA 00:25:57:70:37:2d has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:12 sapd: <404052> |AP HNT1-3@10.128.0.125 sapd| AM 00:1a:1e:a1:99:a0: STA 00:1f:3b:c1:19:d7 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:12 sapd: <404052> |AP UC2-6@10.128.0.197 sapd| AM 00:1a:1e:ac:31:c0: STA 00:25:57:70:37:2d has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:13 sapd: <404052> |AP UC2-1@10.128.0.192 sapd| AM 00:1a:1e:ac:6e:20: STA 00:25:57:70:37:2d has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:14 sapd: <404052> |AP UC1-6@10.128.0.87 sapd| AM 00:24:6c:c5:c8:80: STA d4:e8:b2:02:e8:48 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:14 sapd: <404052> |AP FLT2-3@10.128.0.86 sapd| AM 00:1a:1e:ac:6b:c0: STA 00:26:4a:93:fa:45 has trouble with AP 00:1a:1e:ac:6b:c0. Reason code: 17. Reason: Association Denied; AP is resource constrained
Sep 22 07:47:14 sapd: <404052> |AP EMCS4-1@10.128.0.163 sapd| AM 00:1a:1e:a4:2c:e0: STA 00:25:4b:94:ad:f8 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:14 sapd: <404052> |AP EMCS3-4@10.128.0.171 sapd| AM 00:1a:1e:ac:41:60: STA 00:25:4b:94:ad:f8 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:14 fpcli: USER: admin has logged in from 172.28.1.17.
Sep 22 07:47:14 sapd: <404052> |AP FAC3-2@10.128.0.47 sapd| AM 00:1a:1e:9c:c9:00: STA 00:25:4b:94:ad:f8 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:14 fpcli: USER:admin@172.28.1.17 COMMAND: -- command executed successfully
Sep 22 07:47:14 sapd: <404052> |AP GRT1-5@10.128.1.50 sapd| AM 00:24:6c:b6:db:c0: STA d4:9a:20:3b:72:62 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:15 fpapps: PAPI RxPacket: Timer already removed - could be a duplicate ACK
Sep 22 07:47:15 fpcli: USER: admin connected from 172.28.1.17 has logged out.
Sep 22 07:47:15 fpapps: PAPI RxPacket: Timer already removed - could be a duplicate ACK
Sep 22 07:47:15 sapd: <404052> |AP GRT2-6@10.128.1.47 sapd| AM 00:24:6c:b6:dd:20: STA 00:26:37:74:3c:11 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:15 sapd: <404052> |AP EMCS4-2@10.128.0.162 sapd| AM 00:1a:1e:a8:8b:a0: STA 00:25:4b:94:ad:f8 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:27 sapd: <404052> |AP GRY2-3@10.128.0.141 sapd| AM 00:1a:1e:a4:31:a0: STA 90:84:0d:c6:e1:ae has trouble with AP 00:1a:1e:ac:5f:60. Reason code: 17. Reason: Association Denied; AP is resource constrained
Sep 22 07:47:27 sapd: <404052> |AP FLT3-1@10.128.0.19 sapd| AM 00:1a:1e:a1:90:c0: STA 5c:59:48:de:5c:bf has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:27 sapd: <404052> |AP FLT3-2@10.128.0.20 sapd| AM 00:1a:1e:a8:8c:80: STA 5c:59:48:de:5c:bf has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:27 sapd: <404052> |AP FLT1-1@10.128.0.13 sapd| AM 00:1a:1e:9c:ce:80: STA 5c:59:48:de:5c:bf has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:27 sapd: <404052> |AP FLT2-5@10.128.0.11 sapd| AM 00:1a:1e:ac:6c:40: STA 5c:59:48:de:5c:bf has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:27 sapd: <404003> |AP FLT4-2@10.128.0.26 sapd| AM 00:1a:1e:ac:65:a0: Interfering AP detected with SSID hpsetup and BSSID 96:23:7d:b1:b2:f0
Sep 22 07:47:27 sapd: <404052> |AP LIB2-1@10.128.0.69 sapd| AM 00:1a:1e:ac:60:40: STA 90:84:0d:c6:e1:ae has trouble with AP 00:1a:1e:ac:5f:60. Reason code: 17. Reason: Association Denied; AP is resource constrained
Sep 22 07:47:27 sapd: <404052> |AP LIB1-3@10.128.0.254 sapd| AM 00:1a:1e:a8:8f:c0: STA 90:84:0d:c6:e1:ae has trouble with AP 00:1a:1e:ac:5f:60. Reason code: 17. Reason: Association Denied; AP is resource constrained
Sep 22 07:47:28 sapd: <404052> |AP FAC3-5@10.128.1.2 sapd| AM 00:1a:1e:ac:66:e0: STA 00:26:08:f4:da:e1 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:28 sapd: <404052> |AP FAC1-3@10.128.0.255 sapd| AM 00:1a:1e:a8:8d:c0: STA 00:26:08:f4:da:e1 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:28 sapd: <404003> |AP FND1-2@10.128.0.50 sapd| AM 00:1a:1e:ac:06:80: Interfering AP detected with SSID ctfpWireless and BSSID 00:0e:d7:52:42:41
Sep 22 07:47:29 sapd: <404052> |AP BRK4-3@10.128.0.161 sapd| AM 00:1a:1e:ac:67:60: STA 00:1e:c2:c3:ef:c0 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:29 sapd: <404042> |AP LIB2-4@10.128.0.78 sapd| AM 00:1a:1e:ac:5f:60: Frame Retry Rate at 92 for Channel 7
Sep 22 07:47:29 sapd: <404029> |AP LIB2-4@10.128.0.78 sapd| AM 00:1a:1e:ac:5f:60: Frame Retry Rate at 92 for AP 00:24:6c:c5:cb:e0
Sep 22 07:47:30 sapd: <404052> |AP GRT1-3@10.128.1.48 sapd| AM 00:24:6c:b6:dc:10: STA 00:21:00:36:7c:94 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:30 sapd: <404052> |AP LIB1-3@10.128.0.254 sapd| AM 00:1a:1e:a8:8f:c0: STA 30:7c:30:01:4f:e2 has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:31 sapd: <404042> |AP FAC3-1@10.128.0.46 sapd| AM 00:1a:1e:ac:2d:40: Frame Retry Rate at 86 for Channel 9
Sep 22 07:47:31 sapd: <404029> |AP FAC3-1@10.128.0.46 sapd| AM 00:1a:1e:ac:2d:40: Frame Retry Rate at 86 for AP 00:1a:1e:9c:c9:00
Sep 22 07:47:31 sapd: <404052> |AP FAC2-1@10.128.0.211 sapd| AM 00:1a:1e:ac:67:00: STA 00:23:12:19:26:1a has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:32 sapd: <404042> |AP BRK2-3@10.128.0.116 sapd| AM 00:1a:1e:a2:fa:00: Frame Retry Rate at 92 for Channel 8
Sep 22 07:47:32 sapd: <404029> |AP BRK2-3@10.128.0.116 sapd| AM 00:1a:1e:a2:fa:00: Frame Retry Rate at 92 for AP 00:24:6c:c5:cb:e0
Sep 22 07:47:32 sapd: <404003> |AP HNT3-1@10.128.0.121 sapd| AM 00:1a:1e:a2:f6:80: Interfering AP detected with SSID hpsetup and BSSID 96:23:7d:b1:b2:f0
Sep 22 07:47:32 sapd: <404052> |AP FLT4-1@10.128.0.25 sapd| AM 00:1a:1e:9c:cc:a0: STA 00:22:fb:bb:a5:9a has trouble finding AP : Could have mismatched SSID
Sep 22 07:47:32 sapd: <404052> |AP EMCS4-1@10.128.0.163 sapd| AM 00:1a:1e:a4:2c:e0: STA 00:23:14:04:ae:88 has trouble finding AP : Could have mismatched SSID

This is a small portion of the process log. Anybody have an idea?


Specs:
A6000 - SupI
AOS 3.4.1.0
Regular Contributor I

Re: Could have Mismatched SSID

I, too, would like a definitive response to this issue. We see "Could have mismatched SSID" logs filling up our external syslog disks.

-Mike
Version 3.4.3.0 M3K


Sep 28 09:26:08 2010 sapd: <404052> |AP LGRC-A147-1@172.22.1.49 sapd| AM 00:1a:1e:54:5c:80: STA 00:17:f2:ec:0e:cc has trouble finding AP : Could have mismatched SSID
Sep 28 09:26:09 2010 sapd: <404052> |AP ARND-210-1@172.22.3.217 sapd| AM 00:1a:1e:a3:93:00: STA 00:17:f2:ec:0e:cc has trouble finding AP : Could have mismatched SSID
Sep 28 09:26:09 2010 sapd: <404052> |AP ARND-301-1@172.22.3.189 sapd| AM 00:1a:1e:a3:5d:80: STA 00:17:f2:ec:0e:cc has trouble finding AP : Could have mismatched SSID
Sep 28 09:26:09 2010 sapd: <404052> |AP LGRC-A117-1@172.22.1.241 sapd| AM 00:0b:86:99:8a:80: STA 00:17:f2:ec:0e:cc has trouble with AP 00:0b:86:99:7d:41. Reason code: 17. Reason: Association Denied; AP is resource constrained
Sep 28 09:26:10 2010 sapd: <404052> |AP LGRC-A209E-1@172.22.1.239 sapd| AM 00:0b:86:99:7d:48: STA 00:17:f2:ec:0e:cc has trouble with AP 00:0b:86:99:7d:41. Reason code: 17. Reason: Association Denied; AP is resource constrained
Sep 28 09:26:10 2010 sapd: <404052> |AP LGRC-A201-1@172.22.1.123 sapd| AM 00:0b:86:99:83:e0: STA 00:17:f2:ec:0e:cc has trouble with AP 00:0b:86:99:7d:41. Reason code: 17. Reason: Association Denied; AP is resource constrained
Sep 28 09:26:10 2010 sapd: <404052> |AP HAML-407-1@172.22.3.161 sapd| AM 00:1a:1e:53:0c:60: STA 00:17:f2:ec:0e:cc has trouble finding AP : Could have mismatched SSID
Sep 28 09:26:11 2010 sapd: <404052> |AP HAML-303-1@172.22.2.24 sapd| AM 00:24:6c:bf:82:00: STA 00:17:f2:ec:0e:cc has trouble finding AP : Could have mismatched SSID
Sep 28 09:26:12 2010 sapd: <404052> |AP LGRC-A107-1@172.22.0.244 sapd| AM 00:0b:86:99:ac:a0: STA 00:17:f2:ec:0e:cc has trouble with AP 00:0b:86:99:7d:41. Reason code: 17. Reason: Association Denied; AP is resource constrained
Sep 28 09:27:16 2010 sapd: <404052> |AP LEWS-217-1@172.22.3.175 sapd| AM 00:24:6c:bf:7d:e0: STA 00:17:f2:ec:0e:cc has trouble finding AP : Could have mismatched SSID
Sep 28 09:27:17 2010 sapd: <404052> |AP LGRC-A19-1@172.22.1.125 sapd| AM 00:0b:86:99:7b:60: STA 00:17:f2:ec:0e:cc has trouble finding AP : Could have mismatched SSID
Sep 28 09:27:18 2010 sapd: <404052> |AP ARND-313-1@172.22.3.199 sapd| AM 00:1a:1e:a3:5d:c0: STA 00:17:f2:ec:0e:cc has trouble finding AP : Could have mismatched SSID
Sep 28 09:27:18 2010 sapd: <404052> |AP ARND-104-1@172.22.3.234 sapd| AM 00:1a:1e:a4:21:c0: STA 00:17:f2:ec:0e:cc has trouble finding AP : Could have mismatched SSID
Sep 28 09:27:20 2010 sapd: <404052> |AP TOTM-9-1@172.22.1.141 sapd| AM 00:1a:1e:cd:27:60: STA 00:17:f2:ec:0e:cc has trouble finding AP : Could have mismatched SSID
Guru Elite

Could have mismatched SSID

According to engineering: "If we saw a station but did not see it associate to any AP within 60
seconds, we will print this log. This station would be found in the
"potential client" list, until it is aged out after 120 secs."


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: