Avaya WLAN Security Switch 2300 Series, Troubleshooting And Debug Manual, Page: 43 / 74

43
Avaya WLAN Security Switch 2300 Series Troubleshooting and Debug Guide
DOT1X Apr 11 20:45:37.697034 DEBUG DOT1X-CLIENT: retransmit packet to 00:0d:54:98:99:6d
We’re retransmitting the previous packet (the EAP Identity Request).
DOT1X Apr 11 20:45:37.746255 DEBUG DOT1X-PACKET: EAPoL EAP packet, id 1, len 17, received from
00:0d:54:98:99:6d
We’ve received a response to the EAP request with id 1 (in this case that’s the EAP Identity
request we just sent).
DOT1X Apr 11 20:45:37.746285 DEBUG DOT1X-PACKET: Cancelling retrans timer for 00:0d:54:98:99:6d
DOT1X Apr 11 20:45:37.746360 DEBUG DOT1X-CLIENT: glob '**' matches 'AVAYA\tash', ssid 'slipshod-
tkip' matches 'slipshod-tkip': eap_type=25
At this point the WSS knows the outer username of the client, and begins to compare this
username to the userwildcards on the “set authentication dot1x…” rules. This
configuration is very simple so it matches the first one. If there were additional
authentication rules in front of this one, they would be displayed in order you would see
“does not match” instead of “matches”. The eap_type field is an internal number indicating
which EAP type is configured on network access rule. Eap_type 25 is PEAP-MSCHAPv2,
254 is “pass-through”, ??? is EAP-TLS.
DOT1X Apr 11 20:45:37.746385 DEBUG DOT1X-CLIENT: EAP-ID resp for AVAYA\tash at
00:0d:54:98:99:6d doing PEAP
AAA has decided to do PEAP for this user based on the network access rule.
DOT1X Apr 11 20:45:37.746682 DEBUG DOT1X-STATE: 00:0d:54:98:99:6d transition from
CONNECTING to AUTHENTICATING
DOT1X Apr 11 20:45:37.746705 DEBUG DOT1X-STATS: 00:0d:54:98:99:6d enters authenticating --> 11
DOT1X Apr 11 20:45:37.746788 DEBUG DOT1X-PACKET: EAPoL EAP packet of 10 bytes w/id 2 (with
retransmit set) sent to 00:0d:54:98:99:6d
Sending the next EAP packet (which is the EAP-type negotiation).