HP Comware 5 Debug Manual Vol 1

*Mar 28 09:52:58:860 2008 Sysname LS/7/EVENT:

EAP_Type: 1

// The EAP server received a response of the ID type.

*Mar 28 09:52:59:313 2008 Sysname LS/7/EVENT:

EAP_Type: 4

// The EAP server received a response of the type MD5 challenge.

*Mar 28 09:52:59:313 2008 Sysname LS/7/EVENT:

EAP_MD5 passwords matched

// The password for EAP_MD5 authentication was matched.

# Enable local server packet debugging. Output similar to the following example is generated when an

802.1X client initiates an authentication process under the following conditions:

•

Local EAP authentication is enabled on the device.

•

EAP-MD5 is specified as the EAP authentication method on the local server.

<Sysname> debugging local-server packet

*Mar 28 08:45:15:253 2008 Sysname LS/7/PACKET:

EAP Server received an eap packet:

*Mar 28 08:45:15:260 2008 Sysname LS/7/PACKET:

02 01 00 0d 01 63 61 69 7a 69 62 69 6e

// The EAP server received a response of the ID type and including the username.

*Mar 28 08:45:15:270 2008 Sysname LS/7/PACKET:

MD5 challenge:

*Mar 28 08:45:15:280 2008 Sysname LS/7/PACKET:

c2 a5 3a eb 40 bb 46 a6 d9 21 7d 61 b8 65 57 a8

// The MD5 module generated an MD5 challenge.

*Mar 28 08:45:15:290 2008 Sysname LS/7/PACKET:

EAP Server replied an eap packet:

*Mar 28 08:45:15:300 2008 Sysname LS/7/PACKET:

01 02 00 16 04 10 c2 a5 3a eb 40 bb 46 a6 d9 21

7d 61 b8 65 57 a8

// The EAP server sent an MD5 challenge request.

*Mar 28 08:45:15:310 2008 Sysname LS/7/PACKET:

EAP Server received an eap packet:

*Mar 28 08:45:15:320 2008 Sysname LS/7/PACKET:

02 02 00 1e 04 10 3d 1e 81 b5 56 3d 18 ee 4d a9

4c ec 0b 24 85 b2 63 61 69 7a 69 62 69 6e

// The EAP server received an MD5 challenge response.

*Mar 28 08:45:15:330 2008 Sysname LS/7/PACKET:

EAP Server replied an eap packet:

*Mar 28 08:45:15:340 2008 Sysname LS/7/PACKET:

03 02 00 04

// The EAP server sent an authentication acknowledgement packet.