cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
18021
Views
10
Helpful
25
Replies

POE issue on cat 3550

kmoshayedi
Level 1
Level 1

01:12:51: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/7

: Power given, but link is not up

I have connected a voip phone and ip camera getting the same error.. any idea ?

25 Replies 25

yes cisco IP phone or AP work fine.. .. I tested the camera and other Snom IP phone with a netgear POE switch and worked fine..guess we are going to dump our POS 3550 and get something that can do the job .. we have over 30 phone IP phones and I am not about to connect an injector in. .. POE ..

cat 3550 inline power POE = POS lol

according to the specs this unit is

IEEE 802.3af Power over Ethernet (PoE) Standard Compliant; 8 x  

SO the answe is NO .. EXPERTS

Q. Does the Catalyst 3550-24 PWR switch support the upcoming 802.3af inline power standard?

A. This switch will support the Cisco inline power implementation and 15.4W/port on all 24 ports. 802.3af

compliance cannot be claimed due to the current status of the proposed standard (draft form) and litigation involving

an alleged patent violation for the power disconnect portion of this standard. Full 802.3af compliance is dependent

on the outcome of this litigation. Vendors claiming current support for this standard should also inform their

customers of the risk associated with draft standard claims. The 802.3af standard is expected to be ratified Q2CY03.

Backward compatibility will ensure that previously sold Cisco IP phones and wireless access points will be compatible

with the new Catalyst 3550 inline power switch. Development of an 802.3af inline power Catalyst 3550 switch has

been difficult because of the uncertainty that has existed in the formation of the final IEEE standard.

fyi:

http://www.cisco.com/global/AP/switching/product/3550/c3550_qp.pdf

big no

amikat
Level 7
Level 7

Hi,

Will you please make sure you have "spanning-tree portfast" settings on the interaces. You can also try to extend the initial power shutdown delay to e.g. 90 seconds via the interface command "power inline delay shutdown 20 initial 90" or even further (to its maximum 300). To get more information about the PoE problem will you please set "debug ilpower controller" and do "shut/no shut" of the interface and post the output of the debug.

Thanks & Regards,

Antonin

set the timer to 20 /90

and here is the debug

Switch#debug ilpower coln

Switch#debug ilpower con

Switch#debug ilpower controller

ILPOWER controller debugging is on

Switch#conf

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_PWR_GOOD_USE_LINK_DISC_S,  Event=

BAD_LINK_TIMER_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = F

1d14h: Reg 0x10 = 22

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = F

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Off at ( Fa0/2 ) Okay

1d14h: ILP After Power Off at ( Fa0/2 ), port re-config  Okay

1d14h: ILP Power Accounting RELEASE_PWR ( Fa0/2 ) Okay, pwr_used= 0

1d14h: ILP Power problem detected ( Fa0/2 )

1d14h: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/2: P

ower given, but link is not up

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_WAIT_S,  Event= TWTI_PWR_GOOD_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = F

1d14h: Reg 0x10 = 22

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = F

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Off at ( Fa0/2 ) Okay

1d14h: ILP After Power Off at ( Fa0/2 ), port re-config  Okay

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_WAIT_S,  Event= BAD_PWR_TIMER_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = D

1d14h: Reg 0x10 = 0

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = D

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Off at ( Fa0/2 ) Okay

1d14h: ILP After Power Off at ( Fa0/2 ), port re-config  Okay

1d14h: ILP Start Power Controller phone detection ( Fa0/2 ) Okay

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_DETECTING_S,  Event= TWTI_PWR_GOOD

_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = F

1d14h: Reg 0x10 = 22

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = F

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Accounting REQ_PWR ( Fa0/2 ) Okay

Configuring from terminal, memory, or network [terminal]?

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_PWR_GOOD_USE_LINK_DISC_S,  Event=

BAD_LINK_TIMER_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = F

1d14h: Reg 0x10 = 22

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = F

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Off at ( Fa0/2 ) Okay

1d14h: ILP After Power Off at ( Fa0/2 ), port re-config  Okay

1d14h: ILP Power Accounting RELEASE_PWR ( Fa0/2 ) Okay, pwr_used= 0

1d14h: ILP Power problem detected ( Fa0/2 )

1d14h: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/2: P

ower given, but link is not up

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_WAIT_S,  Event= TWTI_PWR_GOOD_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = F

1d14h: Reg 0x10 = 22

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = F

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Off at ( Fa0/2 ) Okay

1d14h: ILP After Power Off at ( Fa0/2 ), port re-config  Okay

Enter configuration commands, one per line.  End with CNTL/Z.

Switch(config)#

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_WAIT_S,  Event= BAD_PWR_TIMER_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = D

1d14h: Reg 0x10 = 0

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = D

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Off at ( Fa0/2 ) Okay

1d14h: ILP After Power Off at ( Fa0/2 ), port re-config  Okay

1d14h: ILP Start Power Controller phone

Switch(config)#detection ( Fa0/2 ) Okay

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_DETECTING_S,  Event= TWTI_PWR_GOOD

_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = F

1d14h: Reg 0x10 = 22

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = F

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Accounting REQ_PWR ( Fa0/2 ) Okay

Switch(config)#int fa0/2

Switch(config-if)#shju

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_PWR_GOOD_USE_LINK_DISC_S,  Event=

BAD_LINK_TIMER_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = F

1d14h: Reg 0x10 = 22

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = F

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Off at ( Fa0/2 ) Okay

1d14h: ILP After Power Off at ( Fa0/2 ), port re-config  Okay

1d14h: ILP Power Aounting RELEASE_PWR ( Fa0/2 ) Okay, pwr_used= 0

1d14h: ILP Power problem detected ( Fa0/2 )

1d14h: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/2: P

ower given, but link is not

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_WAIT_S,  Event= TWTI_PWR_GOOD_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = F

1d14h: Reg 0x10 = 22

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = F

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Off at ( Fa0/2 ) Okay

1d14h: ILP After Power Off at ( Fa0/2 ), port re-config  Okay

Switch(config-if)#shut

Switch(config-if)#

1d14h: ILP CLI 'shut' handling ( Fa0/2 ) Okay

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_WAIT_S,  Event= GO_SHUT_OFF_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = D

1d14h: Reg 0x10 = 0

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = D

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Stop Power Controller detection ( Fa0/2 ) Okay

1d14h: ILP Shut off ILP detection ( Fa0no /2 )

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_SHUT_OFF_S,  Event= BAD_PWR_TIMER_

EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = D

1d14h: Reg 0x10 = 0

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = D

1d14h: Reg 0x17 = 80

1d14h: *************************************

shut

Switch(config-if)#

1d14h: %LINK-5-CHANGED: Interface FastEthernet0/2, changed state to administrati

vely down

1d14h: ILP CLI 'no shut' handling ( Fa0/2 ) Okay

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_SHUT_OFF_S,  Event= CLI_START_DETE

CT_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = D

1d14h: Reg 0x10 = 0

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = D

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Off at ( Fa0/2 ) Okay

1d14h: ILP After Power Off at ( Fa0/2 ), port re-config  Okay

1d14h: ILP Start Power Controller phone detection ( Fa0/2 ) Okay

1d14h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2, changed

state to down

1d14h: ILP State_Machine( Fa0/2 ): State= ILP_DETECTING_S,  Event= TWTI_PWR_GOOD

_EV

1d14h: ****Power controller address 0x20****

1d14h: Reg 0x0  = 8

1d14h: Reg 0x1  = E6

1d14h: Reg 0x2  = 0

1d14h: Reg 0x4  = F

1d14h: Reg 0x10 = 22

1d14h: Reg 0x12 = FF

1d14h: Reg 0x13 = 0

1d14h: Reg 0x14 = F

1d14h: Reg 0x17 = 80

1d14h: *************************************

1d14h: ILP Power Accounting REQ_PWR ( Fa0/2 ) Okay

1d14h: %LINK-3-UPDOWN: Interface FastEthernet0/2, changed state to down

Switch(config-if)#no shut

Switch(config-if)#end

Switch#

1d14h: %SYS-5-CONFIG_I: Configured from console by console

is  802.3af support class 3 or 1

Hi,

Which Snom IP phone you are trying to connect? Majority of Snom models are 802.3af Power Class 1 or 2, but there are also models which use non-standard PoE solution.

Best regards,

Antonin

I have tried snom 360 and 320 ..  also a IP camera

Hi,

Both these IP Phones are of 802.3af Class 1, ie. requiring very low power. I try to find out if there are any specific requirements for these models, hope to came back soon.

Best regards,

Antonin

amikat
Level 7
Level 7

Hi,

I have tried to get detailed information about the 802.3af poe support for both the Cat3550-PWR switch and Snom IP Phones and failed. The information provided is rather ambiguous and I have not this setup in my lab. While your posted "sh power inline" output clearly indicates that Snom phone has been detected via Fa0/7 interface I also found the Cisco document saying that this switch does not support 802.3af at all:

http://www.cisco.com/warp/public/cc/pd/si/casi/ca6000/prodlit/psnap_br.pdf

The only other attempt I would try is to take the Snom Phone directly to the switch (provided you have an access) and connect it via short patchcord (to eliminate RF noice and possible cabling issues). BTW I hope you are using straight and not crossover cable.

I am planning to get the equipment and try locally in my lab, but it may take weeks or months to fulfil. I am sorry I cannot provide more help at the moment.

Best regards,

Antonin

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:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco