Odd issue with a Cisco phone.

Dustin Anderson — Thu, 24 May 2018 21:42:02 GMT

I don't think this is an ISE issue, but wanted to ask in case I'm missing something.

So, we are changing over from an Avaya to Cisco phone system using ISE for authentication to the network.

So far all is going well until we tried a CP-8832 conference phone. The issue I am having is it is retrying 802.1x over and over without success. But, I have other models on the same switch that have worked fine.

What's really odd is the phone works at the facility here, but fails at our remote facility. We send a second down and that one doesn't work either.

This is the debug on the switch. Has anyone had a similar issue they were able to fix?

May 24 15:14:54.087: %AUTHMGR-5-START: Starting 'dot1x' for client (f87b.2088.9c2a) on Interface Gi3/0/22 AuditSessionID C0A8FB06000979A458CBDF97

May 24 20:14:54.112: EAPOL pak dump Tx

May 24 20:14:54.112: EAPOL Version: 0x3 type: 0x0 length: 0x0006

May 24 20:14:54.112: EAP code: 0x1 id: 0x70 length: 0x0006 type: 0xD

May 24 20:14:54.112: dot1x-packet(Gi3/0/22): EAPOL packet sent to client 0xFA000562 (f87b.2088.9c2a)

May 24 20:15:24.085: EAPOL pak dump Tx

May 24 20:15:24.085: EAPOL Version: 0x3 type: 0x0 length: 0x0006

May 24 20:15:24.085: EAP code: 0x1 id: 0x70 length: 0x0006 type: 0xD

May 24 20:15:24.085: dot1x-packet(Gi3/0/22): EAPOL packet sent to client 0xFA000562 (f87b.2088.9c2a)

May 24 20:15:24.110: dot1x-packet(Gi3/0/22): queuing an EAPOL pkt on Auth Q

May 24 20:15:24.110: dot1x-packet(Gi3/0/22): Received an EAPOL frame

May 24 20:15:24.110: dot1x-packet(Gi3/0/22): Received an EAPOL-Start packet

May 24 20:15:24.110: EAPOL pak dump rx

May 24 20:15:24.110: EAPOL Version: 0x1 type: 0x1 length: 0x0000

May 24 20:15:24.110: EAPOL pak dump Tx

May 24 20:15:24.110: EAPOL Version: 0x3 type: 0x0 length: 0x0005

May 24 20:15:24.110: EAP code: 0x1 id: 0x1 length: 0x0005 type: 0x1

May 24 20:15:24.110: dot1x-packet(Gi3/0/22): EAPOL packet sent to client 0xFA000562 (f87b.2088.9c2a)

May 24 20:15:54.133: dot1x-packet(Gi3/0/22): queuing an EAPOL pkt on Auth Q

May 24 20:15:54.133: dot1x-packet(Gi3/0/22): Received an EAPOL frame

May 24 20:15:54.133: dot1x-packet(Gi3/0/22): Received an EAPOL-Start packet

May 24 20:15:54.133: EAPOL pak dump rx

May 24 20:15:54.133: EAPOL Version: 0x1 type: 0x1 length: 0x0000

May 24 20:15:54.133: EAPOL pak dump Tx

May 24 20:15:54.133: EAPOL Version: 0x3 type: 0x0 length: 0x0004

May 24 20:15:54.133: EAP code: 0x4 id: 0x1 length: 0x0004

May 24 20:15:54.133: dot1x-packet(Gi3/0/22): dot1x_auth_txCannedStatus: EAPOL packet sent to client 0xFA000562 (f87b.2088.9c2a)

May 24 20:15:54.334: EAPOL pak dump Tx

May 24 20:15:54.334: EAPOL Version: 0x3 type: 0x0 length: 0x0005

May 24 20:15:54.334: EAP code: 0x1 id: 0x1 length: 0x0005 type: 0x1

May 24 20:15:54.334: dot1x-packet(Gi3/0/22): EAPOL packet sent to client 0x2F000C27 (0000.0000.0000)

May 24 20:15:54.343: dot1x-packet(Gi3/0/22): Queuing an EAPOL pkt on Authenticator Q

May 24 20:15:54.343: dot1x-packet(Gi3/0/22): Received an EAPOL frame

May 24 20:15:54.343: dot1x-packet(Gi3/0/22): Received an EAP packet

May 24 20:15:54.343: EAPOL pak dump rx

May 24 20:15:54.343: EAPOL Version: 0x1 type: 0x0 length: 0x001C

May 24 20:15:54.343: dot1x-packet(Gi3/0/22): Received an EAP packet from f87b.2088.9c2a

May 24 15:15:54.343: %AUTHMGR-5-START: Starting 'dot1x' for client (f87b.2088.9c2a) on Interface Gi3/0/22 AuditSessionID C0A8FB06000979A558CCCAEE

May 24 20:15:54.368: EAPOL pak dump Tx

May 24 20:15:54.368: EAPOL Version: 0x3 type: 0x0 length: 0x0006

May 24 20:15:54.368: EAP code: 0x1 id: 0xD3 length: 0x0006 type: 0xD

May 24 20:15:54.368: dot1x-packet(Gi3/0/22): EAPOL packet sent to client 0x2F000C27 (f87b.2088.9c2a)

May 24 20:16:24.366: dot1x-packet(Gi3/0/22): queuing an EAPOL pkt on Auth Q

May 24 20:16:24.366: dot1x-packet(Gi3/0/22): Received an EAPOL frame

May 24 20:16:24.366: dot1x-packet(Gi3/0/22): Received an EAPOL-Start packet

May 24 20:16:24.366: EAPOL pak dump rx

May 24 20:16:24.366: EAPOL Version: 0x1 type: 0x1 length: 0x0000

May 24 20:16:24.366: EAPOL pak dump Tx

May 24 20:16:24.366: EAPOL Version: 0x3 type: 0x0 length: 0x0005

May 24 20:16:24.366: EAP code: 0x1 id: 0x1 length: 0x0005 type: 0x1

May 24 20:16:24.366: dot1x-packet(Gi3/0/22): EAPOL packet sent to client 0x2F000C27 (f87b.2088.9c2a)

May 24 20:16:54.389: dot1x-packet(Gi3/0/22): queuing an EAPOL pkt on Auth Q

May 24 20:16:54.389: dot1x-packet(Gi3/0/22): Received an EAPOL frame

May 24 20:16:54.389: dot1x-packet(Gi3/0/22): Received an EAPOL-Start packet

May 24 20:16:54.398: EAPOL pak dump rx

May 24 20:16:54.398: EAPOL Version: 0x1 type: 0x1 length: 0x0000

May 24 20:16:54.398: EAPOL pak dump Tx

May 24 20:16:54.398: EAPOL Version: 0x3 type: 0x0 length: 0x0004

May 24 20:16:54.398: EAP code: 0x4 id: 0x1 length: 0x0004

May 24 20:16:54.398: dot1x-packet(Gi3/0/22): dot1x_auth_txCannedStatus: EAPOL packet sent to client 0x2F000C27 (f87b.2088.9c2a)

May 24 20:16:54.599: EAPOL pak dump Tx

May 24 20:16:54.599: EAPOL Version: 0x3 type: 0x0 length: 0x0005

May 24 20:16:54.599: EAP code: 0x1 id: 0x1 length: 0x0005 type: 0x1

May 24 20:16:54.599: dot1x-packet(Gi3/0/22): EAPOL packet sent to client 0x9E000687 (0000.0000.0000)

May 24 20:16:54.599: dot1x-packet(Gi3/0/22): Queuing an EAPOL pkt on Authenticator Q

May 24 20:16:54.599: dot1x-packet(Gi3/0/22): Received an EAPOL frame

May 24 20:16:54.599: dot1x-packet(Gi3/0/22): Received an EAP packet

May 24 20:16:54.599: EAPOL pak dump rx

May 24 20:16:54.599: EAPOL Version: 0x1 type: 0x0 length: 0x001C

May 24 20:16:54.607: dot1x-packet(Gi3/0/22): Received an EAP packet from f87b.2088.9c2a

May 24 15:16:54.607: %AUTHMGR-5-START: Starting 'dot1x' for client (f87b.2088.9c2a) on Interface Gi3/0/22 AuditSessionID C0A8FB06000979A658CDB656

May 24 20:16:54.624: EAPOL pak dump Tx

May 24 20:16:54.624: EAPOL Version: 0x3 type: 0x0 length: 0x0006

May 24 20:16:54.624: EAP code: 0x1 id: 0xDA length: 0x0006 type: 0xD

May 24 20:16:54.624: dot1x-packet(Gi3/0/22): EAPOL packet sent to client 0x9E000687 (f87b.2088.9c2a)

Re: Odd issue with a Cisco phone.

kthiruve — Thu, 24 May 2018 22:01:16 GMT

Dustin,

802.1x is getting stuck there. I checked the datasheet and it mentioned 802.1x.

If other models are working except for this, try upgrading the software and see if it resolves it.

You can reset/reboot the phone and take a debug as well. Not sure what is going on there.

-Krishnan

topic Odd issue with a Cisco phone. in Network Access Control

Odd issue with a Cisco phone.

Re: Odd issue with a Cisco phone.