cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1343
Views
0
Helpful
10
Replies

WLAN connectivity

TECH-JEFF
Level 1
Level 1

Hi, I'm new to WLAN of Cisco, our company has purchased Cisco WLAN Controller 2504 with 10 Aironet license(AP). I was able to configure the controller and the AP's and wireless has been working fine but for some reason, users have experienced intermittent connectivity at some point in time of usage.

What are some of the things I need to check to ensure that they're going to have a smooth/consistent WLAN connectivity?

Thanks

Jeff

Jefferson Co
10 Replies 10

Sandeep Choudhary
VIP Alumni
VIP Alumni

can you paste some logs from cisco WLC/AP.

 

Like:

debug client <mac address>

 

Regards

Hi Sandeep,

These are some of the logs inside the WLC:

*Dot1x_NW_MsgTask_4: Jun 18 05:00:26.446: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:ea:67:f4
*Dot1x_NW_MsgTask_4: Jun 18 05:00:25.399: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:ea:67:f4
*Dot1x_NW_MsgTask_4: Jun 18 04:59:36.577: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:ec:0c
*Dot1x_NW_MsgTask_4: Jun 18 04:59:35.328: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:ec:0c
*Dot1x_NW_MsgTask_6: Jun 18 04:59:33.245: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:e6:4e
*Dot1x_NW_MsgTask_6: Jun 18 04:59:32.090: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:e6:4e
*Dot1x_NW_MsgTask_0: Jun 18 04:59:06.954: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f3:09:88
*Dot1x_NW_MsgTask_0: Jun 18 04:59:05.908: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f3:09:88
*Dot1x_NW_MsgTask_6: Jun 18 04:58:46.350: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:26:c6:71:97:ae
*Dot1x_NW_MsgTask_6: Jun 18 04:58:45.299: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:26:c6:71:97:ae
*Dot1x_NW_MsgTask_2: Jun 18 04:58:43.550: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:26:c6:72:b9:b2
*Dot1x_NW_MsgTask_0: Jun 18 04:58:42.558: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:38:59:98
*Dot1x_NW_MsgTask_2: Jun 18 04:58:42.382: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:26:c6:72:b9:b2
*Dot1x_NW_MsgTask_0: Jun 18 04:58:41.559: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:38:59:98
*osapiBsnTimer: Jun 18 04:58:24.344: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:e5:c6
*Dot1x_NW_MsgTask_6: Jun 18 04:58:21.250: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:e5:c6
*Dot1x_NW_MsgTask_0: Jun 18 04:57:33.151: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:70:a8
*Dot1x_NW_MsgTask_0: Jun 18 04:57:32.123: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:70:a8
*Dot1x_NW_MsgTask_6: Jun 18 04:57:13.449: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:73:66
*Dot1x_NW_MsgTask_6: Jun 18 04:57:11.848: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:73:66
*Dot1x_NW_MsgTask_2: Jun 18 04:57:05.948: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:6f:ba
*Dot1x_NW_MsgTask_2: Jun 18 04:57:04.758: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:6f:ba
*osapiBsnTimer: Jun 18 04:56:49.528: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:e6:49:d8
*Dot1x_NW_MsgTask_0: Jun 18 04:56:39.733: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:e6:49:d8
*Dot1x_NW_MsgTask_4: Jun 18 04:56:15.415: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8a:5f:3c
*Dot1x_NW_MsgTask_4: Jun 18 04:56:14.276: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8a:5f:3c
*Dot1x_NW_MsgTask_4: Jun 18 04:55:37.956: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e6:6b:7c
*Dot1x_NW_MsgTask_4: Jun 18 04:55:36.934: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e6:6b:7c
*Dot1x_NW_MsgTask_2: Jun 18 04:55:21.921: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:6f:d2
*Dot1x_NW_MsgTask_2: Jun 18 04:55:20.814: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:6f:d2
*Dot1x_NW_MsgTask_5: Jun 18 04:55:11.760: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:72:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:55:10.455: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:72:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:54:50.914: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:8b:f5:50
*Dot1x_NW_MsgTask_0: Jun 18 04:54:49.916: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:48:ce:98
*Dot1x_NW_MsgTask_0: Jun 18 04:54:49.730: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:8b:f5:50
*Dot1x_NW_MsgTask_0: Jun 18 04:54:48.743: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:48:ce:98
*Dot1x_NW_MsgTask_0: Jun 18 04:54:42.728: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:7c:a1:38
*Dot1x_NW_MsgTask_0: Jun 18 04:54:41.666: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:7c:a1:38
*Dot1x_NW_MsgTask_0: Jun 18 04:54:35.723: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 08:11:96:08:0f:c0
*Dot1x_NW_MsgTask_0: Jun 18 04:54:34.709: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 08:11:96:08:0f:c0
*apfReceiveTask: Jun 18 04:54:07.708: #APF-1-ADD_TO_BLACKLIST_FAILED: apf_ms.c:5580 Unable to create exclusion-list entry for mobile 40:b3:95:48:84:e1
*Dot1x_NW_MsgTask_0: Jun 18 04:54:02.136: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:81:64:d0
*Dot1x_NW_MsgTask_0: Jun 18 04:54:01.092: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:81:64:d0
*Dot1x_NW_MsgTask_4: Jun 18 04:53:58.809: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e9:d7:34
*Dot1x_NW_MsgTask_4: Jun 18 04:53:57.761: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e9:d7:34
*Dot1x_NW_MsgTask_4: Jun 18 04:53:55.805: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:26:c6:71:96:4c
*Dot1x_NW_MsgTask_4: Jun 18 04:53:54.757: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:26:c6:71:96:4c
*Dot1x_NW_MsgTask_4: Jun 18 04:53:54.697: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e9:bb:04
*Dot1x_NW_MsgTask_4: Jun 18 04:53:51.062: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e9:bb:04
*Dot1x_NW_MsgTask_0: Jun 18 04:53:32.533: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:82:3a:d8
*Dot1x_NW_MsgTask_0: Jun 18 04:53:31.375: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:82:3a:d8
*Dot1x_NW_MsgTask_0: Jun 18 04:53:25.712: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:08:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:53:24.586: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:08:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:53:22.510: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:79:0b:18
*Dot1x_NW_MsgTask_0: Jun 18 04:53:21.457: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:79:0b:18
*Dot1x_NW_MsgTask_0: Jun 18 04:53:18.616: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:0e:38
*Dot1x_NW_MsgTask_0: Jun 18 04:53:17.571: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:0e:38
*Dot1x_NW_MsgTask_0: Jun 18 04:53:10.313: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:72:08
*Dot1x_NW_MsgTask_0: Jun 18 04:53:09.296: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:72:08
*Dot1x_NW_MsgTask_4: Jun 18 04:52:56.314: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:14:38:5a:a4
*Dot1x_NW_MsgTask_4: Jun 18 04:52:55.233: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:14:38:5a:a4
*Dot1x_NW_MsgTask_0: Jun 18 04:52:10.424: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4f:40
*Dot1x_NW_MsgTask_0: Jun 18 04:52:09.222: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4f:40
*Dot1x_NW_MsgTask_0: Jun 18 04:51:42.093: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:89:d3:88
*Dot1x_NW_MsgTask_0: Jun 18 04:51:40.931: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:89:d3:88
*Dot1x_NW_MsgTask_4: Jun 18 04:51:37.395: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:a9:04
*Dot1x_NW_MsgTask_4: Jun 18 04:51:36.145: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:a9:04
*Dot1x_NW_MsgTask_2: Jun 18 04:51:27.814: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:74:8a
*Dot1x_NW_MsgTask_2: Jun 18 04:51:26.662: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:74:8a
*Dot1x_NW_MsgTask_4: Jun 18 04:50:58.088: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:88:9b:64
*Dot1x_NW_MsgTask_0: Jun 18 04:50:57.088: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:14:a3:f7:98
*Dot1x_NW_MsgTask_4: Jun 18 04:50:57.075: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:88:9b:64
*Dot1x_NW_MsgTask_0: Jun 18 04:50:56.010: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:14:a3:f7:98
*Dot1x_NW_MsgTask_4: Jun 18 04:50:53.313: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8a:68:0c
*Dot1x_NW_MsgTask_4: Jun 18 04:50:53.313: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:80:b4
*Dot1x_NW_MsgTask_4: Jun 18 04:50:52.338: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:80:b4
*Dot1x_NW_MsgTask_4: Jun 18 04:50:52.200: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8a:68:0c
*Dot1x_NW_MsgTask_4: Jun 18 04:50:03.565: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:f3:cc
*Dot1x_NW_MsgTask_4: Jun 18 04:50:02.520: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:f3:cc
*Dot1x_NW_MsgTask_0: Jun 18 04:50:00.126: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:81:ef:18
*Dot1x_NW_MsgTask_0: Jun 18 04:49:58.969: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:81:ef:18
*Dot1x_NW_MsgTask_4: Jun 18 04:49:37.690: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:f1:2c
*Dot1x_NW_MsgTask_4: Jun 18 04:49:36.666: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:f1:2c
*Dot1x_NW_MsgTask_0: Jun 18 04:49:21.295: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:0d:70
*Dot1x_NW_MsgTask_0: Jun 18 04:49:20.123: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:0d:70
*Dot1x_NW_MsgTask_4: Jun 18 04:48:23.928: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:c1:b7:ac
*Dot1x_NW_MsgTask_4: Jun 18 04:48:22.818: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:c1:b7:ac
*Dot1x_NW_MsgTask_6: Jun 18 04:48:15.680: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:e5:06
*Dot1x_NW_MsgTask_6: Jun 18 04:48:14.620: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:e5:06
*Dot1x_NW_MsgTask_2: Jun 18 04:46:49.083: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4d:ba
*Dot1x_NW_MsgTask_4: Jun 18 04:46:48.539: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 08:11:96:07:db:3c
*Dot1x_NW_MsgTask_2: Jun 18 04:46:48.015: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4d:ba
*Dot1x_NW_MsgTask_4: Jun 18 04:46:47.497: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 08:11:96:07:db:3c
*Dot1x_NW_MsgTask_4: Jun 18 04:46:30.072: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f2:f1:e4
*Dot1x_NW_MsgTask_4: Jun 18 04:46:28.928: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f2:f1:e4
*Dot1x_NW_MsgTask_4: Jun 18 04:46:24.274: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:82:25:c4
*Dot1x_NW_MsgTask_4: Jun 18 04:46:23.260: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:82:25:c4
*Dot1x_NW_MsgTask_0: Jun 18 04:46:15.297: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:7b:f0:18
*Dot1x_NW_MsgTask_0: Jun 18 04:46:14.201: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:7b:f0:18
*Dot1x_NW_MsgTask_4: Jun 18 04:46:02.311: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e7:8f:ac
*Dot1x_NW_MsgTask_4: Jun 18 04:46:01.161: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e7:8f:ac
*Dot1x_NW_MsgTask_4: Jun 18 04:45:52.789: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:f2:e4
*Dot1x_NW_MsgTask_4: Jun 18 04:45:51.485: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:f2:e4
*Dot1x_NW_MsgTask_4: Jun 18 04:45:30.075: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:88:ad:74
*Dot1x_NW_MsgTask_4: Jun 18 04:45:28.930: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:88:ad:74
*Dot1x_NW_MsgTask_0: Jun 18 04:45:24.340: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:a3:e0:70
*Dot1x_NW_MsgTask_0: Jun 18 04:45:23.191: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:a3:e0:70
*Dot1x_NW_MsgTask_0: Jun 18 04:45:18.908: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:e9:c9:b8
*Dot1x_NW_MsgTask_0: Jun 18 04:45:17.748: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:e9:c9:b8
*Dot1x_NW_MsgTask_0: Jun 18 04:45:08.072: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:10:80
*Dot1x_NW_MsgTask_0: Jun 18 04:45:06.901: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:10:80
*Dot1x_NW_MsgTask_0: Jun 18 04:45:05.910: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:f0:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:45:04.868: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:f0:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:44:49.888: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:c1:e5:f0
*Dot1x_NW_MsgTask_0: Jun 18 04:44:48.857: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:c1:e5:f0
*Dot1x_NW_MsgTask_4: Jun 18 04:44:30.469: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4f:54
*Dot1x_NW_MsgTask_4: Jun 18 04:44:29.444: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4f:54
*Dot1x_NW_MsgTask_0: Jun 18 04:44:26.956: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:82:6b:40
*Dot1x_NW_MsgTask_0: Jun 18 04:44:25.809: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:82:6b:40
*Dot1x_NW_MsgTask_0: Jun 18 04:44:10.111: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:18:12:c8
*Dot1x_NW_MsgTask_0: Jun 18 04:44:08.970: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:18:12:c8
*Dot1x_NW_MsgTask_0: Jun 18 04:43:25.655: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:52:a8
*Dot1x_NW_MsgTask_0: Jun 18 04:43:24.610: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:52:a8
*apfReceiveTask: Jun 18 04:43:05.652: #APF-1-ADD_TO_BLACKLIST_FAILED: apf_ms.c:5580 Unable to create exclusion-list entry for mobile cc:78:5f:02:aa:7b
*apfReceiveTask: Jun 18 04:42:03.448: #APF-1-ADD_TO_BLACKLIST_FAILED: apf_ms.c:5580 Unable to create exclusion-list entry for mobile 38:48:4c:25:73:2d
*Dot1x_NW_MsgTask_4: Jun 18 04:41:23.949: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8f:1d:9c
*Dot1x_NW_MsgTask_4: Jun 18 04:41:22.905: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8f:1d:9c
*apfMsConnTask_5: Jun 18 04:41:09.281: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4f:3a
*Dot1x_NW_MsgTask_2: Jun 18 04:41:03.961: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4f:3a
*Dot1x_NW_MsgTask_4: Jun 18 04:40:51.697: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 56, Key type 1, client 00:23:4d:8b:82:b4
*Dot1x_NW_MsgTask_4: Jun 18 04:40:50.599: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 56, Key type 1, client 00:23:4d:8b:82:b4
*Dot1x_NW_MsgTask_4: Jun 18 04:40:35.527: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 72, Key type 1, client 00:24:2c:e5:3e:94
*Dot1x_NW_MsgTask_4: Jun 18 04:40:34.323: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 72, Key type 1, client 00:24:2c:e5:3e:94
*Dot1x_NW_MsgTask_4: Jun 18 04:39:57.313: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:7c:9e:b4
*Dot1x_NW_MsgTask_4: Jun 18 04:39:56.223: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:7c:9e:b4
*Dot1x_NW_MsgTask_0: Jun 18 04:39:47.583: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e9:e5:90
*Dot1x_NW_MsgTask_0: Jun 18 04:39:46.539: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e9:e5:90
*Dot1x_NW_MsgTask_0: Jun 18 04:39:45.261: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f2:ea:b0
*Dot1x_NW_MsgTask_0: Jun 18 04:39:44.192: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f2:ea:b0
*Dot1x_NW_MsgTask_0: Jun 18 04:38:29.646: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:b4:98
*Dot1x_NW_MsgTask_0: Jun 18 04:38:28.492: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:b4:98
*Dot1x_NW_MsgTask_6: Jun 18 04:38:25.847: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:72:4e
*Dot1x_NW_MsgTask_6: Jun 18 04:38:24.781: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:72:4e
*Dot1x_NW_MsgTask_0: Jun 18 04:38:08.221: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 84:3a:4b:10:53:98
*Dot1x_NW_MsgTask_0: Jun 18 04:38:06.965: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 84:3a:4b:10:53:98
*Dot1x_NW_MsgTask_0: Jun 18 04:37:37.058: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:14:37:6a:50
*Dot1x_NW_MsgTask_0: Jun 18 04:37:36.014: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:14:37:6a:50
*Dot1x_NW_MsgTask_4: Jun 18 04:37:34.644: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:6f:dc
*Dot1x_NW_MsgTask_4: Jun 18 04:37:33.627: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:6f:dc
*Dot1x_NW_MsgTask_2: Jun 18 04:37:17.641: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:71:62
*Dot1x_NW_MsgTask_2: Jun 18 04:37:16.469: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:71:62
*Dot1x_NW_MsgTask_2: Jun 18 04:37:10.441: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:71:c2
*Dot1x_NW_MsgTask_2: Jun 18 04:37:09.441: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:71:c2
*Dot1x_NW_MsgTask_4: Jun 18 04:36:26.431: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:f2:54
*Dot1x_NW_MsgTask_4: Jun 18 04:36:25.338: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:f2:54
*Dot1x_NW_MsgTask_4: Jun 18 04:35:53.283: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:7c:90:9c
*Dot1x_NW_MsgTask_4: Jun 18 04:35:52.150: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:7c:90:9c
*Dot1x_NW_MsgTask_4: Jun 18 04:35:49.230: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e7:80:6c
*Dot1x_NW_MsgTask_4: Jun 18 04:35:48.109: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e7:80:6c
*Dot1x_NW_MsgTask_0: Jun 18 04:35:29.233: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:83:78
*Dot1x_NW_MsgTask_0: Jun 18 04:35:28.117: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:83:78
*Dot1x_NW_MsgTask_4: Jun 18 04:34:57.434: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8f:22:7c
*Dot1x_NW_MsgTask_4: Jun 18 04:34:56.338: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8f:22:7c
*Dot1x_NW_MsgTask_4: Jun 18 04:34:28.036: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:7c:a0:5c
*Dot1x_NW_MsgTask_4: Jun 18 04:34:26.865: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:7c:a0:5c
*Dot1x_NW_MsgTask_4: Jun 18 04:34:10.918: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8f:6c:64
*Dot1x_NW_MsgTask_4: Jun 18 04:34:09.873: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8f:6c:64
*Dot1x_NW_MsgTask_0: Jun 18 04:33:54.913: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:fd:18
*Dot1x_NW_MsgTask_0: Jun 18 04:33:53.860: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:fd:18
*Dot1x_NW_MsgTask_0: Jun 18 04:33:52.820: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:8f:4d:b8
*Dot1x_NW_MsgTask_0: Jun 18 04:33:52.818: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:4d:8b:89:08
*Dot1x_NW_MsgTask_0: Jun 18 04:33:51.775: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:8f:4d:b8
*Dot1x_NW_MsgTask_0: Jun 18 04:33:51.705: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:4d:8b:89:08
*Dot1x_NW_MsgTask_4: Jun 18 04:33:22.617: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:a3:fc:2c
*Dot1x_NW_MsgTask_4: Jun 18 04:33:21.597: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:a3:fc:2c
*Dot1x_NW_MsgTask_0: Jun 18 04:33:19.109: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f2:f3:b0
*Dot1x_NW_MsgTask_0: Jun 18 04:33:17.969: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f2:f3:b0
*apfMsConnTask_7: Jun 18 04:32:58.281: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f2:e7:e0
*Dot1x_NW_MsgTask_0: Jun 18 04:32:56.791: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f2:e7:e0
*Dot1x_NW_MsgTask_0: Jun 18 04:32:55.730: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:e9:d1:58
*Dot1x_NW_MsgTask_0: Jun 18 04:32:54.580: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:e9:d1:58
*Dot1x_NW_MsgTask_1: Jun 18 04:32:35.619: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 72, Key type 1, client 00:24:2c:e5:3e:e9
*Dot1x_NW_MsgTask_1: Jun 18 04:32:34.440: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 72, Key type 1, client 00:24:2c:e5:3e:e9
*Dot1x_NW_MsgTask_0: Jun 18 04:31:18.231: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:a4:07:90
*Dot1x_NW_MsgTask_0: Jun 18 04:31:17.049: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:a4:07:90
*Dot1x_NW_MsgTask_4: Jun 18 04:31:09.564: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 6c:88:14:bb:be:dc
*Dot1x_NW_MsgTask_4: Jun 18 04:31:08.518: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 6c:88:14:bb:be:dc
*Dot1x_NW_MsgTask_4: Jun 18 04:31:07.251: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:8b:a0:b4
*Dot1x_NW_MsgTask_4: Jun 18 04:31:06.206: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:8b:a0:b4
*Dot1x_NW_MsgTask_0: Jun 18 04:31:02.012: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:7c:a5:18
*Dot1x_NW_MsgTask_0: Jun 18 04:31:01.008: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:7c:a5:18
*osapiBsnTimer: Jun 18 04:30:52.404: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:ea:67:f4
*Dot1x_NW_MsgTask_4: Jun 18 04:30:23.311: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:ea:67:f4
*Dot1x_NW_MsgTask_6: Jun 18 04:29:42.729: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:e6:4e
*Dot1x_NW_MsgTask_6: Jun 18 04:29:41.071: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:e6:4e
*Dot1x_NW_MsgTask_4: Jun 18 04:29:25.499: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:ec:0c
*Dot1x_NW_MsgTask_4: Jun 18 04:29:24.356: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:ec:0c
*Dot1x_NW_MsgTask_0: Jun 18 04:29:16.793: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f3:09:88
*Dot1x_NW_MsgTask_0: Jun 18 04:29:15.657: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f3:09:88
*apfReceiveTask: Jun 18 04:29:05.588: #APF-1-ADD_TO_BLACKLIST_FAILED: apf_ms.c:5580 Unable to create exclusion-list entry for mobile 88:53:95:77:63:4e
*Dot1x_NW_MsgTask_2: Jun 18 04:28:56.590: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:26:c6:72:b9:b2
*Dot1x_NW_MsgTask_2: Jun 18 04:28:55.583: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:26:c6:72:b9:b2
*Dot1x_NW_MsgTask_0: Jun 18 04:28:35.014: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:38:59:98
*Dot1x_NW_MsgTask_2: Jun 18 04:28:09.612: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:6f:b2
*Dot1x_NW_MsgTask_2: Jun 18 04:28:08.464: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:6f:b2
*Dot1x_NW_MsgTask_2: Jun 18 04:27:26.209: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:6f:ba
*Dot1x_NW_MsgTask_2: Jun 18 04:27:25.156: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:6f:ba
*Dot1x_NW_MsgTask_0: Jun 18 04:27:22.193: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:70:a8
*Dot1x_NW_MsgTask_0: Jun 18 04:27:21.126: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:70:a8
*Dot1x_NW_MsgTask_6: Jun 18 04:27:13.204: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:73:66
*Dot1x_NW_MsgTask_6: Jun 18 04:27:12.082: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:73:66
*Dot1x_NW_MsgTask_4: Jun 18 04:27:00.199: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:8b:fa:1c
*Dot1x_NW_MsgTask_4: Jun 18 04:26:59.118: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:8b:fa:1c
*Dot1x_NW_MsgTask_4: Jun 18 04:26:09.251: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8a:5f:3c
*Dot1x_NW_MsgTask_0: Jun 18 04:26:08.217: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 84:3a:4b:10:4f:38
*Dot1x_NW_MsgTask_4: Jun 18 04:26:08.207: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8a:5f:3c
*Dot1x_NW_MsgTask_0: Jun 18 04:26:07.073: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 84:3a:4b:10:4f:38
*Dot1x_NW_MsgTask_4: Jun 18 04:25:59.273: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e6:6b:7c
*Dot1x_NW_MsgTask_4: Jun 18 04:25:58.133: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e6:6b:7c
*Dot1x_NW_MsgTask_2: Jun 18 04:25:11.773: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:6f:d2
*Dot1x_NW_MsgTask_2: Jun 18 04:25:10.615: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:6f:d2
*Dot1x_NW_MsgTask_0: Jun 18 04:24:54.782: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:72:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:24:53.790: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:8b:f5:50
*Dot1x_NW_MsgTask_0: Jun 18 04:24:53.740: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:72:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:24:52.687: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:8b:f5:50
*Dot1x_NW_MsgTask_0: Jun 18 04:24:25.582: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:48:ce:98
*Dot1x_NW_MsgTask_0: Jun 18 04:24:24.423: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:48:ce:98
*Dot1x_NW_MsgTask_0: Jun 18 04:24:14.371: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:7c:a1:38
*Dot1x_NW_MsgTask_0: Jun 18 04:24:13.341: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:7c:a1:38
*Dot1x_NW_MsgTask_1: Jun 18 04:24:03.330: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e9:d7:34
*Dot1x_NW_MsgTask_4: Jun 18 04:24:00.684: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e9:d7:34
*Dot1x_NW_MsgTask_4: Jun 18 04:23:54.854: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:26:c6:71:96:4c
*Dot1x_NW_MsgTask_4: Jun 18 04:23:53.614: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:26:c6:71:96:4c
*Dot1x_NW_MsgTask_0: Jun 18 04:23:51.794: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:81:64:d0
*Dot1x_NW_MsgTask_0: Jun 18 04:23:50.647: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:27:10:81:64:d0
*Dot1x_NW_MsgTask_4: Jun 18 04:23:45.195: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e9:bb:04
*Dot1x_NW_MsgTask_4: Jun 18 04:23:44.097: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e9:bb:04
*Dot1x_NW_MsgTask_0: Jun 18 04:23:19.549: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:0e:38
*Dot1x_NW_MsgTask_0: Jun 18 04:23:18.465: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:0e:38
*Dot1x_NW_MsgTask_4: Jun 18 04:23:09.967: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:14:38:5a:a4
*Dot1x_NW_MsgTask_4: Jun 18 04:23:09.456: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:6f:7c
*Dot1x_NW_MsgTask_4: Jun 18 04:23:08.461: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:14:38:5a:a4
*Dot1x_NW_MsgTask_4: Jun 18 04:23:08.202: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:6f:7c
*Dot1x_NW_MsgTask_0: Jun 18 04:23:05.265: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:79:0b:18
*Dot1x_NW_MsgTask_0: Jun 18 04:23:04.117: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:79:0b:18
*Dot1x_NW_MsgTask_0: Jun 18 04:23:02.169: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:82:3a:d8
*Dot1x_NW_MsgTask_0: Jun 18 04:23:01.155: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:82:3a:d8
*Dot1x_NW_MsgTask_0: Jun 18 04:22:56.269: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:08:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:22:54.702: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:08:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:22:20.420: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4f:40
*Dot1x_NW_MsgTask_0: Jun 18 04:22:19.378: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4f:40
*Dot1x_NW_MsgTask_0: Jun 18 04:21:42.742: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:89:d3:88
*Dot1x_NW_MsgTask_0: Jun 18 04:21:41.387: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:89:d3:88
*Dot1x_NW_MsgTask_4: Jun 18 04:21:40.212: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:a9:04
*Dot1x_NW_MsgTask_4: Jun 18 04:21:39.170: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:a9:04
*Dot1x_NW_MsgTask_0: Jun 18 04:21:18.991: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:14:a3:f7:98
*Dot1x_NW_MsgTask_0: Jun 18 04:21:17.795: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:23:14:a3:f7:98
*Dot1x_NW_MsgTask_4: Jun 18 04:21:09.142: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:80:b4
*Dot1x_NW_MsgTask_4: Jun 18 04:21:07.883: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:88:9b:64
*Dot1x_NW_MsgTask_4: Jun 18 04:21:07.838: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:80:b4
*Dot1x_NW_MsgTask_4: Jun 18 04:21:06.612: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:88:9b:64
*Dot1x_NW_MsgTask_2: Jun 18 04:20:57.514: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:74:8a
*Dot1x_NW_MsgTask_4: Jun 18 04:20:56.987: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8a:68:0c
*Dot1x_NW_MsgTask_2: Jun 18 04:20:56.262: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:78:74:8a
*Dot1x_NW_MsgTask_4: Jun 18 04:20:55.842: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8a:68:0c
*Dot1x_NW_MsgTask_6: Jun 18 04:20:26.395: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client 60:67:20:78:e6:4e - got 00 00 00 00 00 00 00 11, expected 00 00 00 00 00 00 00 12
*Dot1x_NW_MsgTask_6: Jun 18 04:20:26.392: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client 60:67:20:78:e6:4e - got 00 00 00 00 00 00 00 10, expected 00 00 00 00 00 00 00 12
*Dot1x_NW_MsgTask_4: Jun 18 04:20:25.392: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client 10:0b:a9:ea:67:f4 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_4: Jun 18 04:20:25.252: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client 60:67:20:f2:ec:0c - got 00 00 00 00 00 00 00 05, expected 00 00 00 00 00 00 00 06
*Dot1x_NW_MsgTask_0: Jun 18 04:20:25.239: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client 84:3a:4b:10:4f:38 - got 00 00 00 00 00 00 00 09, expected 00 00 00 00 00 00 00 0a
*Dot1x_NW_MsgTask_0: Jun 18 04:20:25.159: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client 84:3a:4b:10:53:98 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Jun 18 04:19:42.337: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:81:ef:18
*Dot1x_NW_MsgTask_0: Jun 18 04:19:41.290: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:81:ef:18
*Dot1x_NW_MsgTask_4: Jun 18 04:19:35.621: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:f1:2c
*Dot1x_NW_MsgTask_4: Jun 18 04:19:34.468: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:f1:2c
*Dot1x_NW_MsgTask_4: Jun 18 04:19:34.389: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:f3:cc
*Dot1x_NW_MsgTask_4: Jun 18 04:19:30.865: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:f3:cc
*Dot1x_NW_MsgTask_0: Jun 18 04:19:28.338: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:0d:70
*Dot1x_NW_MsgTask_0: Jun 18 04:19:27.275: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f3:0d:70
*Dot1x_NW_MsgTask_0: Jun 18 04:19:27.269: #LOG-3-Q_IND: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8f:22:dc
*Dot1x_NW_MsgTask_4: Jun 18 04:19:25.068: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8f:22:dc
*Dot1x_NW_MsgTask_0: Jun 18 04:18:59.387: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 08:11:96:08:09:38
*Dot1x_NW_MsgTask_0: Jun 18 04:18:58.248: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 08:11:96:08:09:38
*Dot1x_NW_MsgTask_4: Jun 18 04:18:28.131: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 08:11:96:0a:e2:2c
*Dot1x_NW_MsgTask_4: Jun 18 04:18:26.974: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 08:11:96:0a:e2:2c
*Dot1x_NW_MsgTask_4: Jun 18 04:18:24.133: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:c1:b7:ac
*Dot1x_NW_MsgTask_6: Jun 18 04:18:23.135: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:e5:06
*Dot1x_NW_MsgTask_4: Jun 18 04:18:22.951: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 00:27:10:c1:b7:ac
*Dot1x_NW_MsgTask_6: Jun 18 04:18:21.935: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:78:e5:06
*Dot1x_NW_MsgTask_2: Jun 18 04:16:22.523: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4d:ba
*Dot1x_NW_MsgTask_2: Jun 18 04:16:21.471: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 84:3a:4b:10:4d:ba
*Dot1x_NW_MsgTask_4: Jun 18 04:16:13.446: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 60:67:20:f2:f1:e4
*apfReceiveTask: Jun 18 04:16:09.108: #APF-1-ADD_TO_BLACKLIST_FAILED: apf_ms.c:5580 Unable to create exclusion-list entry for mobile 00:f4:b9:d0:8e:61
*Dot1x_NW_MsgTask_4: Jun 18 04:16:07.625: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e7:8f:ac
*Dot1x_NW_MsgTask_4: Jun 18 04:16:06.686: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 10:0b:a9:e7:8f:ac
*Dot1x_NW_MsgTask_4: Jun 18 04:15:58.140: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:f2:e4
*Dot1x_NW_MsgTask_4: Jun 18 04:15:57.093: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f2:f2:e4
*Dot1x_NW_MsgTask_4: Jun 18 04:15:39.316: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:88:ad:74
*Dot1x_NW_MsgTask_4: Jun 18 04:15:38.246: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:88:ad:74
*Dot1x_NW_MsgTask_0: Jun 18 04:15:10.758: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:a3:e0:70
*Dot1x_NW_MsgTask_0: Jun 18 04:15:10.319: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f3:10:80
*apfReceiveTask: Jun 18 04:15:10.308: #APF-1-ADD_TO_BLACKLIST_FAILED: apf_ms.c:5580 Unable to create exclusion-list entry for mobile 40:b3:95:48:84:e1
*Dot1x_NW_MsgTask_0: Jun 18 04:15:09.818: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 00:23:14:a3:e0:70
*Dot1x_NW_MsgTask_0: Jun 18 04:15:09.307: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client 60:67:20:f3:10:80
*Dot1x_NW_MsgTask_0: Jun 18 04:15:03.299: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:e9:c9:b8
*Dot1x_NW_MsgTask_0: Jun 18 04:15:02.186: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client 10:0b:a9:e9:c9:b8
*Dot1x_NW_MsgTask_0: Jun 18 04:14:57.447: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:f0:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:14:56.310: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 24, Key type 1, client a4:4e:31:8b:f0:f8
*Dot1x_NW_MsgTask_0: Jun 18 04:14:36.745: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:18:12:c8


Thanks

Jeff

Jefferson Co

Hi,

*Dot1x_NW_MsgTask_0: Jun 18 04:14:36.745: #DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:864 Received invalid EAPOL-key M2 msg in START  state - invalid secure bit; KeyLen 40, Key type 1, client a4:4e:31:18:12:c8

 

This error stats: The client tried to send a key, when the PEM state on the WLC was START.  More than likely the client thought it could roam, but the WLC thought differently.

question:

1. Only this client have problem or many others??

2. If only one then please update the driver of the device.

Can you please post the log from WLC.

To find out the exact cause please paste the output of this command.

debug client <mac address>

Also post your show WLAN <id>

 

Regards

Hi Sandeep,

Please see response below:

1. Only this client have problem or many others??

Ans. random/many others and random part of the office, one instance is that a user is connected visually with the icon below with full strength signal but user is wondering why it takes too long to process a file share then signal bars will suddenly appear an exclamation icon on the signal bars, meaning "limited access". Remedy would be discon/recon to the SSID

2. If only one then please update the driver of the device.

Ans. n/a since this happens in random laptops. FYI: we have almost 500-600 laptops

Once it happens again in a laptop, that's the best time I can perform debug client<mac address>

attached below is my WLAN ID

 

Regards,

Jeff

Jefferson Co

HI Jeff,

I don't see any problem with config. M not sure but may be this can be issue of  brodcast key intervel. It's 3600 seconds by default.  But you can force the broadcast key to rotate

config advanced eap bcast-key-interval  ?

      Enter the number of seconds between 120 and 86400

 

which software you are running on wlc?

 

Regards

 

 

Hi Sandeep,

Apologies, accidentally clicked on "Report" button, haha,

Anyway, the software version I'm using is: 7.5.102.0

If ever I need to play around with the key interval, in your experience what would be the best values for this?

Regards,

Jeff

Jefferson Co

HI Jeff,

First of all 7.5.102.0 deferred from cisco so you must go with either 7.4.121.0 or 7.6.120.0.

try to use 86400(max 24hrs) (but may be in night or in evening), may it can affect user. So test in a maintenance window. It keeps the key from expiring when a client gets disconnected

 

Regards

Hi Sandeep,

Apologies for the late updates, I was offline for quite some time in obeservance of the stability of the WLAN, I've noticed that it became more stable as of the moment. I'll take your advice if the connectivty is intermittent again.

Thanks and have a great day ahead.

Jeff

Jefferson Co

Abha Jha
Cisco Employee
Cisco Employee
Error Message    %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: Received invalid [chars] msg in 
[chars] state - [chars]; len [int], key type [int], client 
[hex]:[hex]:[hex]:[hex]:[hex]:[hex] 

Explanation    Client authentication failed because of an authentication protocol error between the client and access point.

Recommended Action    If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity.

Also

It is possible that some SSID is configured with WPA  TKIP Cipher and WPA2 AES Cipher, you can try to configure the SSID only with WPA2 AES Cipher or only with WPA  TKIP Cipher,
sometimes when you configure both we see those messages that you are seeing.


The most common root cause for that is a incorrectly configured PSK on the client.

Check if that client  has wrong PSK  (4c:e6:76:6a:b8:de)


If this is for 802.1x enabled WLAN (not PSK), this could be client bug.

 

 

 

Actually our authentication is not PSK, our method of authentication is certificate base via radius server.

Thanks

Jeff

Jefferson Co
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: