cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
728
Views
0
Helpful
7
Replies
Beginner

POE issue on cisco phone?

Hi there,

Went to connect a 6921 phone and nothing was happening.  Power inline was set to auto, and it was showing as on when the phone was connected, but the phone wasn't powering up.  Moved it to another port and it came up.

 

Having a look at the ports, and for the port that didn't come up I was getting this:

Nov 29 10:16:16.760: %ILPOWER-7-DETECT: Interface Fa1/0/14: Power Device detected: Cisco PD
Nov 29 10:16:17.154: %ILPOWER-5-POWER_GRANTED: Interface Fa1/0/14: Power granted
Nov 29 10:16:18.170: %ILPOWER-5-IEEE_DISCONNECT: Interface Fa1/0/14: PD removed

 

For the port it came up on I was getting this:

Nov 29 10:23:30.362: %ILPOWER-7-DETECT: Interface Fa1/0/27: Power Device detected: IEEE PD
Nov 29 10:23:31.352: %ILPOWER-5-POWER_GRANTED: Interface Fa1/0/27: Power granted

 

So it seems like different ports are recognising it as different devices.

 

Anyone any ideas?  Problem with the POE controller?  Port gone bad?

 

Many thanks, Al.

 

 

7 REPLIES 7
Beginner

Re: POE issue on cisco phone?

I have seen this issue caused by bad POE controllers, bad phones, and bad patch cables. If you really want to get into it, it looks like you may want to do some troubleshooting such as trying different phones on the same ports, changing out patch cables, and more detailed POE debugs.

 

Here is some good Cisco POE troubleshooting documentation to start with. It is from the cisco 3750 catalyst documentation but should be good information if you are on other models either way:

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750/software/troubleshooting/g_power_over_ethernet.html#wp1015060

Beginner

Re: POE issue on cisco phone?

Hi there,

 

Thanks for the reply.  Yeah, I read through that before I posted here.  I haven't run any debugs yet; which ones would you suggest?

 

I'm kind of ruling out patch cables and phones, as they both work fine on other ports; the problem seems to stay with the port not move with the poe device...

 

To me, the way its being detected as a cisco device on one port and an IEEE device on the other, it feels like there's some confusion about which standard is being detected and supplied....  But that's as far as my understanding of POE takes me....

 

Al.

Hall of Fame Community Legend

Re: POE issue on cisco phone?

What is the exact model of this switch?
Post the complete output to the command "sh interface Fa1/0/27 controll".
Beginner

Re: POE issue on cisco phone?

Hi Leo,

 

Many thanks for the reply.

 

Its a 3750V2-48PS-E.

 

I've included the output from port 1/0/14 (where it wouldn't connect) and 2/0/14 (where I now have it connected).

 

Cheers, Al.

 

# sh int fa 1/0/14 contr
FastEthernet1/0/14 is down, line protocol is down (notconnect)
Hardware is Fast Ethernet, address is 34a8.4e16.2090 (bia 34a8.4e16.2090)
Description: 01-14 
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 4w2d, output 4w2d, output hang never
Last clearing of "show interface" counters 19w6d
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1402720 packets input, 184518381 bytes, 0 no buffer
Received 317416 broadcasts (313489 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 313489 multicast, 0 pause input
0 input packets with dribble condition detected
13431513 packets output, 1086365452 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out

Transmit FastEthernet1/0/14 Receive
3247101487 Bytes 2285424828 Bytes
29866922 Unicast frames 12360538 Unicast frames
104703298 Multicast frames 3027345 Multicast frames
8380168 Broadcast frames 38122 Broadcast frames
0 Too old frames 1537074938 Unicast bytes
0 Deferred frames 696276130 Multicast bytes
0 MTU exceeded frames 2477994 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 0 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 0 Undersize frames
0 5 collision frames 0 Collision fragments
0 6 collision frames
0 7 collision frames 0 Minimum size frames
0 8 collision frames 7748039 65 to 127 byte frames
0 9 collision frames 6159990 128 to 255 byte frames
0 10 collision frames 1515419 256 to 511 byte frames
0 11 collision frames 2458 512 to 1023 byte frames
0 12 collision frames 101 1024 to 1518 byte frames
0 13 collision frames 0 Overrun frames
0 14 collision frames 0 Pause frames
0 15 collision frames
0 Excessive collisions 3 Symbol error frames
0 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 0 Valid frames, too large
0 Excess defer frames 1 Invalid frames, too small
16736761 64 byte frames 0 Valid frames, too small
116441664 127 byte frames
7926075 255 byte frames 0 Too old frames
1802330 511 byte frames 0 Valid oversize frames
37894 1023 byte frames 0 System FCS error frames
5664 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames

 

 

# sh int fa 2/0/14 contr

FastEthernet2/0/14 is up, line protocol is up (connected)
Hardware is Fast Ethernet, address is 34a8.4e16.5b10 (bia 34a8.4e16.5b10)
Description: 
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:38, output 00:00:38, output hang never
Last clearing of "show interface" counters 19w6d
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
10502 packets input, 1324103 bytes, 0 no buffer
Received 2713 broadcasts (2661 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 2661 multicast, 0 pause input
0 input packets with dribble condition detected
122294 packets output, 10303973 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out

Transmit FastEthernet2/0/14 Receive
10304113 Bytes 1324103 Bytes
18018 Unicast frames 7789 Unicast frames
95798 Multicast frames 2661 Multicast frames
8480 Broadcast frames 52 Broadcast frames
0 Too old frames 676901 Unicast bytes
0 Deferred frames 610246 Multicast bytes
0 MTU exceeded frames 5548 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 0 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 0 Undersize frames
0 5 collision frames 0 Collision fragments
0 6 collision frames
0 7 collision frames 0 Minimum size frames
0 8 collision frames 6856 65 to 127 byte frames
0 9 collision frames 2314 128 to 255 byte frames
0 10 collision frames 1329 256 to 511 byte frames
0 11 collision frames 1 512 to 1023 byte frames
0 12 collision frames 2 1024 to 1518 byte frames
0 13 collision frames 0 Overrun frames
0 14 collision frames 0 Pause frames
0 15 collision frames
0 Excessive collisions 0 Symbol error frames
0 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 0 Valid frames, too large
0 Excess defer frames 0 Invalid frames, too small
12844 64 byte frames 0 Valid frames, too small
102310 127 byte frames
5222 255 byte frames 0 Too old frames
1680 511 byte frames 0 Valid oversize frames
34 1023 byte frames 0 System FCS error frames
206 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames

 

Beginner

Re: POE issue on cisco phone?

"Last input 4w2d, output 4w2d, output hang never
Last clearing of "show interface" counters 19w6d"

 

That does not bode well for the interface. 4 weeks since last detected input & output?

I would be interested to see if other ports on the same controller give you the same problem. I am rusty on 3750's but I think the command "show platform pm platform-block"will tell you what controller your ports are controlled by so you can identify another port to test on.

 

 

Beginner

Re: POE issue on cisco phone?

I wouldn't read too much into that, its a phone that hardly gets used except in an emergency.

 

Anyway, I ran a couple of debugs, and, for the same phone, this is what happened on a port the phone works on:

 

Nov 30 14:49:49.163: ilpower_hwif_comingup: Fa2/0/14
Nov 30 14:49:49.163: ilpower_powerman_power_available_tlv: about sending patlv on Fa2/0/14
Nov 30 14:49:49.163: req id 2415, man id 3, pwr avail 6000, pwr man 6000
Nov 30 14:49:49.163: ilpower_if_statechange_complete: Fa2/0/14
Nov 30 14:49:49.565: ilpower_powerallocation_change( Fa2/0/14 ) power: 7000
Nov 30 14:49:49.565: ilpower_get_admin_state( Fa2/0/14 )
Nov 30 14:49:49.565: ilpower_get_admin_state( Fa2/0/14 )
Nov 30 14:49:49.565: ilpower_pd_power_statechange(Fa2/0/14) pd_power_state: 0
Nov 30 14:49:49.565: ilpower_powerallocation_change( Fa2/0/14 ) power: 7000
Nov 30 14:49:49.565: ilpower_get_admin_state( Fa2/0/14 )
Nov 30 14:49:49.565: ilpower_get_admin_state( Fa2/0/14 )
Nov 30 14:49:49.565: ilpower_pd_power_statechange(Fa2/0/14) pd_power_state: 1
Nov 30 14:49:49.574: ilpower_pd_statechange( Fa2/0/14 ) pd_class: 5, Ieee class: 2
Nov 30 14:49:49.574: ilpower_pd_device_typechange( Fa2/0/14 ) pd_device: 3
Nov 30 14:49:49.565: %ILPOWER-7-DETECT: Interface Fa2/0/14: Power Device detected: IEEE PD (ellac-ec-p20-st07-2)
Nov 30 14:49:50.622: ilpower_power_assgn_handle_event: event 0, pwr assign is done by proto CDP

 

and this is what I get on the port that the phone's not coming up on:

 

Nov 30 14:21:23.435: ILP State_Machine ( Fa1/0/14 ): State= ILP_DETECTING_S, Event= PHY_CSCO_DETECTED_EV
Nov 30 14:21:23.435: **** Instance 0 : Sub Address 0 *****
Nov 30 14:21:23.435: ***************************************

Nov 30 14:21:23.435: ILP uses DC Disconnect(Fa1/0/14): state= ILP_DETECTING_S, event= PHY_CSCO_DETECTED_EV
Nov 30 14:21:23.435: ilpower_get_admin_state( Fa1/0/14 )
Nov 30 14:21:27.437: ILP State_Machine ( Fa1/0/14 ): State= ILP_DETECTING_S, Event= WAIT_IEEE_DETECT_TIMER_EV
Nov 30 14:21:27.437: **** Instance 0 : Sub Address 0 *****
Nov 30 14:21:27.437: ***************************************

Nov 30 14:21:27.437: ILP uses DC Disconnect(Fa1/0/14): state= ILP_DETECTING_S, event= WAIT_IEEE_DETECT_TIMER_EV
Nov 30 14:21:27.437: %ILPOWER-7-DETECT: Interface Fa1/0/14: Power Device detected: Cisco PD
Nov 30 14:21:27.437: Ilpower PD device 1 class 2 from interface (Fa1/0/14)
Nov 30 14:21:27.437: ilpower new power from pd discovery Fa1/0/14, power_status ok
Nov 30 14:21:27.437: Ilpower interface (Fa1/0/14) power status change, allocated power 15400
Nov 30 14:21:27.445: ilpower_notify_lldp_tlv: lldp power class tlv:
Nov 30 14:21:27.445: (curr/prev) pwr value 15400/0
Nov 30 14:21:27.445: ilpower_get_admin_state( Fa1/0/14 )
Nov 30 14:21:27.445: ilpower_pd_power_statechange(Fa1/0/14) pd_power_state: 0
Nov 30 14:21:27.445: ilpower_get_admin_state( Fa1/0/14 )
Nov 30 14:21:27.445: ilpower_get_admin_state( Fa1/0/14 )
Nov 30 14:21:27.445: ilpower_notify_lldp_power_via_mdi_tlv Fa1/0/14 pwr alloc 15400
Nov 30 14:21:27.445: Fa1/0/14 AUTO PORT PWR Alloc 130 Request 130
Nov 30 14:21:27.445: Fa1/0/14: LLDP NOTIFY TLV:
(curr/prev) PSE Allocation: 13000/0
(curr/prev) PD Request : 13000/0
(curr/prev) PD Class : 1/0
(curr/prev) PD Priority : 3/0
(curr/prev Power Type : 2/0
(curr/prev) mdi_pwr_support: 1/0
(curr/prev Power Pair) : 1/0
(curr/prev) PSE Pwr Source : 1/0
Nov 30 14:21:27.445: ilpower_pd_power_statechange(Fa1/0/14) pd_power_state: 1
Nov 30 14:21:27.454: ILP Power apply to ( Fa1/0/14 ) Okay
Nov 30 14:21:27.454: ILP Power Accounting REQ_PWR ( Fa1/0/14 ) Okay sys_used=60400
Nov 30 14:21:27.454: ilpower_pd_statechange( Fa1/0/14 ) pd_class: 2, Ieee class: n/a
Nov 30 14:21:27.454: ilpower_pd_device_typechange( Fa1/0/14 ) pd_device: 1
Nov 30 14:21:27.999: ILP State_Machine ( Fa1/0/14 ): State= ILP_PD_DETECTED_S, Event= IEEE_PD_REMOVAL_EV
Nov 30 14:21:27.999: **** Instance 0 : Sub Address 0 *****
Nov 30 14:21:27.999: ***************************************

Nov 30 14:21:27.999: ILP uses DC Disconnect(Fa1/0/14): state= ILP_PD_DETECTED_S, event= IEEE_PD_REMOVAL_EV
Nov 30 14:21:27.999: ilpower delete power from pd linkdown Fa1/0/14
Nov 30 14:21:27.999: Ilpower interface (Fa1/0/14), delete allocated power 15400
Nov 30 14:21:27.999: ilpower_notify_lldp_power_via_mdi_tlv Fa1/0/14 pwr alloc 0
Nov 30 14:21:27.999: Fa1/0/14 AUTO PORT PWR Alloc 130 Request 130
Nov 30 14:21:27.999: Fa1/0/14: LLDP NOTIFY TLV:
(curr/prev) PSE Allocation: 13000/0

 

and it then just goes into a loop of power granted, power deleted.....

 

Heres the output; which one shows me the poe module?

ellac-ec-p20-st07#sh platform pm platform-block

interface gid gpn lpn asic hw-i flags sp dp bundle vlan mvid mac so_di i_vlan
-----------------------------------------------------------------------------
Fa1/0/1 3 3 1 1 2 D 1 2 no 0 0 0 61443 0
Fa1/0/2 4 4 2 1 3 D 2 2 no 0 0 0 61444 0

 

Cheers, Al.

 

 

Beginner

Re: POE issue on cisco phone?

"Heres the output; which one shows me the poe module?

ellac-ec-p20-st07#sh platform pm platform-block

interface gid gpn lpn asic hw-i flags sp dp bundle vlan mvid mac so_di i_vlan
-----------------------------------------------------------------------------
Fa1/0/1 3 3 1 1 2 D 1 2 no 0 0 0 61443 0
Fa1/0/2 4 4 2 1 3 D 2 2 no 0 0 0 61444 0"

 

The asic is your controller.

 

 

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards