WAP4410N will not stay powered on a 3550 PoE

[jrockett1]

Greetings. I have a WAP4410N new out of the box will not stay powered on any of our three 3550 24 port PoE switches running 12.2(25) ipservicesk9-M EMI. The WAP4410N is running the 2.0.3.3 firmware. Unfortunately the AP is the only PoE device I have at my disposal. The device will power on, the link will come up on the switch but after ~5 seconds the power light then the PoE light on the WAP4410N turns off and the device reboots and continues this cycle. The WAP4410N operates normally when plugged in with the included power adapter, but I need to use this as a PoE device. Thanks for any help.

[davbarre]

Hi,

Can you please outline if you are using the same port on the 3350 when attempting PoE as well as using the included power supply?  I'd like to eliminate as many variables as possible.

We would also like to see if you can try another PoE device to make sure the switch is acting correctly.

Thanks!

Dave

[jrockett1]

I plugged the AP in with the power cable and connected it to the same port (fa0/22) on the 3550. The AP remains powered and the PoE light on the AP is solid green and I am able to access the web gui for the AP. A "sh power inline" displays the below info on the port:

Interface Admin  Oper       Power   Device              Class Max
                                      (Watts)

Fa0/22    auto   on             15.4    Ieee PD                   15.4

I was able to find a VoIP phone (non-Cisco sadly) but it is PoE and keeps a connection on the switch on the same switchport. The settings on fa0/22 are as follows:

interface FastEthernet0/22
switchport mode access
spanning-tree portfast

I've hooked both powered devices to several ports on two identical 3550s and receive the same result.  Thanks for your help in this matter.

[jrockett1]

Below is the debug ilpower event output when I plug the AP into the switch. Thanks.

1d02h: ILP uses Link Disconnect(Fa0/22): state= ILP_LINK_UP_S, event= PHY_LINK_DOWN_EV
3550-24-Ins1#
1d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
3550-24-Ins1#
1d02h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to down
3550-24-Ins1#
1d02h: ILP uses Link Disconnect(Fa0/22): state= ILP_DETECTING_S, event= TWTI_PWR_GOOD_EV
1d02h: ILP disable DTE detection X seconds (Fa0/22)
3550-24-Ins1#
1d02h: ILP uses Link Disconnect(Fa0/22): state= ILP_PWR_GOOD_USE_LINK_DISC_S, event= PHY_LINK_UP_EV
3550-24-Ins1#
1d02h: ILP uses Link Disconnect(Fa0/22): state= ILP_LINK_UP_S, event= DISABLE_DTE_TIMER_EV
3550-24-Ins1#
1d02h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed
state to up
3550-24-Ins1#
1d02h: ILP uses Link Disconnect(Fa0/22): state= ILP_LINK_UP_S, event= PHY_LINK_DOWN_EV
3550-24-Ins1#
1d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
3550-24-Ins1#
1d02h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to down
3550-24-Ins1#
1d02h: ILP uses Link Disconnect(Fa0/22): state= ILP_DETECTING_S, event= TWTI_PWR_GOOD_EV
3550-24-Ins1#
1d02h: ILP uses Link Disconnect(Fa0/22): state= ILP_PWR_GOOD_USE_LINK_DISC_S, event= PHY_LINK_UP_EV
3550-24-Ins1#
1d02h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed
state to up
3550-24-Ins1#
1d02h: ILP uses Link Disconnect(Fa0/22): state= ILP_LINK_UP_S, event= PHY_LINK_DOWN_EV
3550-24-Ins1#
1d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
3550-24-Ins1#
1d02h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to down
3550-24-Ins1#

[jrockett1]

Today I was able to keep the AP powered on the switch with only the eth cable by powering the AP with the power adapter. After the power light was solid I disconnected the power adapter and the device continues to pull power from the switch. Could it be a faulty AP?

[David Carr]

It could be faulty, however it could be the length of the cable your using plays a big factor.  Poe deteriates the further the cable is.  You might have to adjust the poe settings on the switch to send maximum power to the Access point.

[Marko Pribanic · Accepted solution]

Hi,

This setup will not work, because the 3550PoE supports only Cisco Pre-standard PoE and the WAP4410N supports only IEEE 802.3af standard.

More here:

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

http://www.cisco.com/en/US/docs/wireless/access_point/csbap/wap4410n/administration/guide/WAP4410N_Admin_Guide.pdf

[jrockett1]

Well that stinks.

Thanks for the info, I'll store this away for future use. At least I can power it up via the adapter then remove said adapter to use the PoE function if needed. Funny thing is I had already sent it back to Cisco to be replaced.

[bts.forklift]

Maybe something like this will help you?

http://www.panoptictechnology.com/network-smart-adapters/

[Eric Moyers]

Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center.

Currently there is no Cisco certified POE injector for use with any of our Access Points. While there are several out in the market, none of them have been verified by Cisco to work with our equipment completely. Doing so, could do damage to your Access Point. Currently our best reccommendation would be to plug them into a POE switch that supports IEEE 802.3af standard. If you currently do not have one, We have several small inexpensive unmanaged POE switches that would surfice for this.

Eric Moyers
Cisco Network Support Engineer
1-866-606-1866