cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
44204
Views
36
Helpful
31
Replies

Using AP2802I with POE-injector, Fails to bring up radios due to "not enough POE power"

Isak Asp
Level 1
Level 1

Hi.

We have 3 new 2802I that we can't get to work.

We're using a 3750 switch to power the other 2702 which works fine with our 2500series controller (version 8.3.112.0).

Since the 3750 can't provide enough power for the 2802 we bought a couple of D-link POE-injectors that support 802.3at(30W).

This is where the trouble starts.

Cisco installations guide for AP2800 says:

The AP can be powered through only Power-over-Ethernet (PoE), using:

• 802.3at Cisco Power Injector AIR-PWRINJ6=

• Any 802.3at (25.5 W) compliant switch port

Specification on AIR-PWRINJ6= says:

"The single-port PoE injector provides up to 30 Watts and is compliant with IEEE 802.3af (15.4 W) and IEEE 802.3at (30 W) systems."


AP2800 series should accordingly to documentation  "out of the box" with all features enabled consume 26W

The AP appears in the controller, but with all radios down. The LED indicates low power (flash green-blue-red).
Power Over Ethernet Settings says: POE Status: Medium Power (15.4W) and
Tx Power Level Assignment: Due to low PoE radio is transmitting at degraded power

If I disable the radio on the AP and then enable it the radio goes up. But the flashing led is still there.

Since I'm not a network-technician we called in a network consultant who said (after a troubleshooting) that we needed more power.
So we bought POE-injectors from Ubiquiti that provides 60W.  Still not working.

I've tried to enable Power Injector State and change Power Injector Selection to override. Still no luck.

Other things I've tried in desperation to find a solution is disable CDP, turned off POE for the interface in the 3750.

How am I supposed to move forward with the troubleshooting this?

(How)  Can I turn off the POE negotiation and force the AP to use full power mode?

Best Regards

Logg from the AP.

Jul 19 13:43:44 kernel: [*07/19/2017 13:43:44.2682] waiting for POE negotiation to complete
Jul 19 13:43:44 kernel: [*07/19/2017 13:43:44.2682]
Jul 19 13:43:47 kernel: [*07/19/2017 13:43:47.7955] waiting for POE negotiation to complete
Jul 19 13:43:47 kernel: [*07/19/2017 13:43:47.7955]
Jul 19 13:43:49 kernel: [*07/19/2017 13:43:49.2686] waiting for POE negotiation to complete
Jul 19 13:43:49 kernel: [*07/19/2017 13:43:49.2686]
Jul 19 13:43:52 kernel: [*07/19/2017 13:43:52.7959] waiting for POE negotiation to complete
Jul 19 13:43:52 kernel: [*07/19/2017 13:43:52.7959]
Jul 19 13:43:54 kernel: [*07/19/2017 13:43:54.2690] waiting for POE negotiation to complete
Jul 19 13:43:54 kernel: [*07/19/2017 13:43:54.2690]
Jul 19 13:43:57 kernel: [*07/19/2017 13:43:57.7964] waiting for POE negotiation to complete
Jul 19 13:43:57 kernel: [*07/19/2017 13:43:57.7964]
Jul 19 13:43:59 kernel: [*07/19/2017 13:43:59.2694] waiting for POE negotiation to complete
Jul 19 13:43:59 kernel: [*07/19/2017 13:43:59.2694]
Jul 19 13:44:02 kernel: [*07/19/2017 13:44:02.7968] waiting for POE negotiation to complete
Jul 19 13:44:02 kernel: [*07/19/2017 13:44:02.7968]
Jul 19 13:44:04 kernel: [*07/19/2017 13:44:04.2698] waiting for POE negotiation to complete
Jul 19 13:44:04 kernel: [*07/19/2017 13:44:04.2699]
Jul 19 13:44:07 kernel: [*07/19/2017 13:44:07.7972] waiting for POE negotiation to complete
Jul 19 13:44:07 kernel: [*07/19/2017 13:44:07.7972]
Jul 19 13:44:09 kernel: [*07/19/2017 13:44:09.2703] waiting for POE negotiation to complete
Jul 19 13:44:09 kernel: [*07/19/2017 13:44:09.2703]
Jul 19 13:44:12 kernel: [*07/19/2017 13:44:12.7977] waiting for POE negotiation to complete
Jul 19 13:44:12 kernel: [*07/19/2017 13:44:12.7977]
Jul 19 13:44:14 kernel: [*07/19/2017 13:44:14.2707] waiting for POE negotiation to complete
Jul 19 13:44:14 kernel: [*07/19/2017 13:44:14.2707]
Jul 19 13:44:17 kernel: [*07/19/2017 13:44:17.7981] waiting for POE negotiation to complete
Jul 19 13:44:17 kernel: [*07/19/2017 13:44:17.7981]
Jul 19 13:44:19 kernel: [*07/19/2017 13:44:19.2711] waiting for POE negotiation to complete
Jul 19 13:44:19 kernel: [*07/19/2017 13:44:19.2711]
Jul 19 13:44:19 FIPS[8444]: *** shell: FIPS Mode = disabled ***
Jul 19 13:44:22 kernel: [*07/19/2017 13:44:22.7986] waiting for POE negotiation to complete
Jul 19 13:44:22 kernel: [*07/19/2017 13:44:22.7986]
Jul 19 13:44:22 brain: CDP PoE negotiation FAILED !!
Jul 19 13:44:22 brain: LLDP PoE negotiation START
Jul 19 13:44:24 kernel: [*07/19/2017 13:44:24.2716] waiting for POE negotiation to complete
Jul 19 13:44:24 kernel: [*07/19/2017 13:44:24.2716]
Jul 19 13:44:27 kernel: [*07/19/2017 13:44:27.7990] waiting for POE negotiation to complete
Jul 19 13:44:27 kernel: [*07/19/2017 13:44:27.7990]
Jul 19 13:44:29 kernel: [*07/19/2017 13:44:29.2727] waiting for POE negotiation to complete
Jul 19 13:44:29 kernel: [*07/19/2017 13:44:29.2727]
Jul 19 13:44:32 kernel: [*07/19/2017 13:44:32.7995] waiting for POE negotiation to complete
Jul 19 13:44:32 kernel: [*07/19/2017 13:44:32.7995]
Jul 19 13:44:34 kernel: [*07/19/2017 13:44:34.2731] waiting for POE negotiation to complete
Jul 19 13:44:34 kernel: [*07/19/2017 13:44:34.2731]
Jul 19 13:44:37 kernel: [*07/19/2017 13:44:37.7999] waiting for POE negotiation to complete
Jul 19 13:44:37 kernel: [*07/19/2017 13:44:37.7999]
Jul 19 13:44:39 kernel: [*07/19/2017 13:44:39.2736] waiting for POE negotiation to complete
Jul 19 13:44:39 kernel: [*07/19/2017 13:44:39.2736]
Jul 19 13:44:42 kernel: [*07/19/2017 13:44:42.8004] waiting for POE negotiation to complete
Jul 19 13:44:42 kernel: [*07/19/2017 13:44:42.8004]
Jul 19 13:44:44 kernel: [*07/19/2017 13:44:44.2740] waiting for POE negotiation to complete
Jul 19 13:44:44 kernel: [*07/19/2017 13:44:44.2740]
Jul 19 13:44:47 kernel: [*07/19/2017 13:44:47.8008] waiting for POE negotiation to complete
Jul 19 13:44:47 kernel: [*07/19/2017 13:44:47.8008]
Jul 19 13:44:49 kernel: [*07/19/2017 13:44:49.2745] waiting for POE negotiation to complete
Jul 19 13:44:49 kernel: [*07/19/2017 13:44:49.2745]
Jul 19 13:44:52 kernel: [*07/19/2017 13:44:52.8012] waiting for POE negotiation to complete
Jul 19 13:44:52 kernel: [*07/19/2017 13:44:52.8013]
Jul 19 13:44:54 kernel: [*07/19/2017 13:44:54.2749] waiting for POE negotiation to complete
Jul 19 13:44:54 kernel: [*07/19/2017 13:44:54.2749]
Jul 19 13:44:54 brain: LLDP PoE negotiation FAILED !!
Jul 19 13:44:54 brain: Power mode: Degraded/Reduced Power, power_detection: DC_adapter(FALSE), 802.3AF_POE(TRUE)
Jul 19 13:44:54 kernel: [*07/19/2017 13:44:54.9240] SYS-COND: AP is in critical condition
Jul 19 13:44:55 syslog: +/usr/bin/cisco_core.sh
Jul 19 13:44:55 kernel: [*07/19/2017 13:44:55.3069] dtls_init: Use MIC device cert
Jul 19 13:44:55 kernel: [*07/19/2017 13:44:55.3072] dtls_init: Use MIC device cert private key
Jul 19 13:44:55 kernel: [*07/19/2017 13:44:55.3073]
Jul 19 13:44:55 kernel: [*07/19/2017 13:44:55.3073] CAPWAP State: Init
Jul 19 13:44:55 kernel: [*07/19/2017 13:44:55.3074]
Jul 19 13:44:55 kernel: [*07/19/2017 13:44:55.3074] PNP is not required, Starting CAPWAP discovery
Jul 19 13:44:55 kernel: [*07/19/2017 13:44:55.3074]
Jul 19 13:44:55 kernel: [*07/19/2017 13:44:55.3076]
Jul 19 13:44:55 kernel: [*07/19/2017 13:44:55.3076] CAPWAP State: Discovery
Jul 19 13:44:59 brain: Restart POE negotiation
Jul 19 13:45:00 brain: CDP PoE negotiation START
Jul 19 13:45:25 kernel: [*07/19/2017 13:45:25.3519] Discovery Request sent to 172.16.11.3, discovery type STATIC_CONFIG(1)
Jul 19 13:45:25 kernel: [*07/19/2017 13:45:25.3530] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
Jul 19 13:45:25 kernel: [*07/19/2017 13:45:25.3530]
Jul 19 13:45:25 kernel: [*07/19/2017 13:45:25.3530] CAPWAP State: Discovery
Jul 19 13:45:25 kernel: [*07/19/2017 13:45:25.3558] Discovery Response from 172.16.11.3
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.0003] Discovery Response from 172.16.11.3
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.0000]
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.0000] CAPWAP State: DTLS Setup
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.0886] dtls_load_ca_certs: LSC Root Certificate not present
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.0886]
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.1885]
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.1885] CAPWAP State: Join
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.1897] Sending Join request to 172.16.11.3 through port 5264
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.1920] Join Response from 172.16.11.3
Jul 19 13:46:17 syslog: +ifconfig wired0 promisc
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.2639] HW CAPWAP tunnel is ADDED
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.2773]
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.2773] CAPWAP State: Image Data
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.3071] do NO_UPGRADE, part2 is active part
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.3113]
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.3113] CAPWAP State: Configure
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.3165] NO-ENC-PROVIDER for DOT11R_WLC_MAC_IP_PAYLOAD
Jul 19 13:46:17 kernel: [*07/19/2017 13:46:17.8417] DOT11_DRV[0]: set_channel Channel set to 1
Jul 19 13:46:18 kernel: [*07/19/2017 13:46:18.1711] DOT11_DRV[0]: set_channel Channel set to 1
Jul 19 13:46:18 kernel: [*07/19/2017 13:46:18.6245] Radio1 not started, not enough POE power
Jul 19 13:46:18 kernel: [*07/19/2017 13:46:18.6468] DOT11_DRV[1]: set_channel Channel set to 36
Jul 19 13:46:18 kernel: [*07/19/2017 13:46:18.9817] DOT11_DRV[1]: set_channel Channel set to 36
Jul 19 13:46:19 kernel: [*07/19/2017 13:46:19.6325] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jul 19 13:46:19 kernel: [*07/19/2017 13:46:19.6326] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jul 19 13:46:19 kernel: [*07/19/2017 13:46:19.6326] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jul 19 13:46:19 kernel: [*07/19/2017 13:46:19.6327] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jul 19 13:46:19 kernel: [*07/19/2017 13:46:19.6879] Radio1 not started, not enough POE power
Jul 19 13:46:19 kernel: [*07/19/2017 13:46:19.6909] Radio1 not started, not enough POE power
Jul 19 13:46:19 kernel: [*07/19/2017 13:46:19.7133] DOT11_DRV[0]: set_channel Channel set to 1
Jul 19 13:46:20 kernel: [*07/19/2017 13:46:20.1342] Radio1 not started, not enough POE power
Jul 19 13:46:20 kernel: [*07/19/2017 13:46:20.1541] DOT11_DRV[1]: set_channel Channel set to 36
Jul 19 13:46:20 kernel: [*07/19/2017 13:46:20.5080] DOT11_DRV[1]: set_channel Channel set to 36
Jul 19 13:46:21 kernel: [*07/19/2017 13:46:21.0585]
Jul 19 13:46:21 kernel: [*07/19/2017 13:46:21.0585] CAPWAP State: Run
Jul 19 13:46:21 syslog: +ifconfig wired0 promisc
Jul 19 13:46:21 kernel: [*07/19/2017 13:46:21.0831] CAPWAP HW tunnel params changed, UPDATING the existing
Jul 19 13:46:21 kernel: [*07/19/2017 13:46:21.1362] AP has joined controller wlc01
Jul 19 13:46:21 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Jul 19 13:46:21 root: SYS-COND: Retrigger critical condition, 1 power
Jul 19 13:46:43 brain: CDP PoE negotiation FAILED !!
Jul 19 13:46:43 brain: LLDP PoE negotiation START
Jul 19 13:47:15 brain: LLDP PoE negotiation FAILED !!
Jul 19 13:47:15 brain: Power mode: Degraded/Reduced Power, power_detection: DC_adapter(FALSE), 802.3AF_POE(TRUE)
Jul 19 13:47:15 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Jul 19 13:47:15 root: SYS-COND: Retrigger critical condition, 1 power
Jul 19 13:47:20 brain: Restart POE negotiation
Jul 19 13:47:20 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Jul 19 13:47:20 root: SYS-COND: Retrigger critical condition, 1 power
Jul 19 13:47:21 brain: CDP PoE negotiation START
Jul 19 13:48:31 brain: CDP PoE negotiation FAILED !!
Jul 19 13:48:31 brain: LLDP PoE negotiation START
Jul 19 13:49:03 brain: LLDP PoE negotiation FAILED !!
Jul 19 13:49:03 brain: Power mode: Degraded/Reduced Power, power_detection: DC_adapter(FALSE), 802.3AF_POE(TRUE)
Jul 19 13:49:03 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Jul 19 13:49:03 root: SYS-COND: Retrigger critical condition, 1 power
Jul 19 13:49:08 brain: Restart POE negotiation
Jul 19 13:49:08 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Jul 19 13:49:08 root: SYS-COND: Retrigger critical condition, 1 power
Jul 19 13:49:09 brain: CDP PoE negotiation START

31 Replies 31

What if POE injector doesn't have any MAC address ?

What are you trying to solve? Injectors don’t need to have a MAC address entered to power up a device.
-Scott
*** Please rate helpful posts ***

Isak Asp
Level 1
Level 1

Does anyone have an idea on how to proceed troubleshooting this problem?

Best regards

So I found a solution to this problem - at least the problem we were having.

 

Injector : AIR-PWERINJ6

Accesspoint : AIR-AP2802I-E-K9

WLC 2504 Software : 8.3.122.0 (note we upgraded this to 8.5.103.0)

 

The issue was that the power negioation packets from the switch were overriding the injector, resulting in only 15.4W being supplied and the Annantae never being powered on due to low power.

 

A simple, quick solution, was to disconnect the 'data' port of the injector and reset the injector with only the AP connected.

Once the light changes from orange to green on the connector, connect the data uplink to the switch.

 

The AP then powers up as normal. - NOTE - if the light stays orange - it wont work.

 

This is a simple fix to confirm the problem, however a power outage will cause the problem to re-appear

 

So to properly fix the problem  - disable PoE on that port on the switch

 

 

Int Gig 1/0/5

shut

switchport

power inline never

no shut

end

 

wr

 

Once PoE is disabled on the port the injector works no matter which way you power up.

 

As part of our troubleshooting we upgraded to 8.5.103.0 - but I dont think this is necessary.

But im not going to downgrade to test it !!

 

Hope that works for you !

 

James

 

 

 

 

 

 

 

Update

 

We had to Downgrade the Controller to 8.3.122.0

This was due to a SHA1 issue / Certificates

This issue prevented our 4 X Aironet 1142N from working

 

All working now !

James,

 

Your suggestions work perfectly. I thought I had tried them but not in the exact sequence you noted. The POE negotiation confusion makes sense.

 

Thanks!

Leo Laohoo
Hall of Fame
Hall of Fame

Please post the complete output to the AP command "sh inventory".  I want to see the manufacturing date of the AP.  The AP could, potentially, be part of a bad batch. 

Read THIS.

Hi guys,

 

I am having the same problem with LLDP negotiations failing but the 3802i is connecting to a Nokia ONT which is capable of delivering 30W. The after the negotiations fail, the AP defaults to medium power 802.3af.

 

Does anyone know if it is possible to change the default behaviour to use 802.3at instead?

 

Thanks

usmcjohn
Level 1
Level 1

I had this problem today using POE+ injectors from fs.com. I was able to get around it by disabling CDP and LLDP on the switchport the AP was plugged into before plugging in the AP.  Note you don't have to disable CDP/LLDP on the AP or on the entire switchI itself, just the port the AP is plugged into.  If the AP is plugged in prior and negotiates power @ 15.4 watts, you will have to physically reset it.  Resetting it from the controller doesn't seem to force the AP to negotiate power again.  Was worried about it too cause we have a lot of these we have to get stood up over the next couple of weeks and have to use some of these POE injectors in places we have older switches.

Aftab Alam
Level 1
Level 1

Hi All,

 

I was having the same issue and was getting low power over POE, enabled the cdp advertisement-v2 at switch where APs were connected and it started to drawing the full power ,fixed the issue.

 

sw1(config)#cdp advertise-v2

 

sw1(config)#cdp advertise-v2

sw1#show power inline

able     Used     Remaining

ts)     (Watts)    (Watts)

----   --------   ---------

0.0      499.4      1300.6

n  Oper       Power   Device              Class Max

              (Watts)                            

-- ---------- ------- ------------------- ----- ----

   off        0.0     n/a                 n/a   60.0

   off        0.0     n/a                 n/a   60.0

   off        0.0     n/a                 n/a   60.0

   off        0.0     n/a                 n/a   60.0

   off        0.0     n/a                 n/a   60.0

   off        0.0     n/a                 n/a   60.0

   off        0.0     n/a                 n/a   60.0

   off        0.0     n/a                 n/a   60.0

   on         15.4    AIR-AP3802I-E-K9    4     60.0

   on         30.0    AIR-AP3802I-E-K9    4     60.0

   on         30.0    AIR-AP3802I-E-K9    4     60.0

   on         15.4    AIR-AP3802I-E-K9    4     60.0

   on         30.0    AIR-AP3802I-E-K9    4     60.0

   on         30.0    AIR-AP3802I-E-K9    4     60.0

   on         30.0    AIR-AP3802I-E-K9    4     60.0

   on         30.0    AIR-AP3802I-E-K9    4     60.0

   on         30.0    AIR-AP3802I-E-K9    4     60.0

   on         15.4    AIR-AP3802I-E-K9    4     60.0

   on         30.0    AIR-AP3802I-E-K9    4     60.0

   on         15.4    AIR-AP3802I-E-K9    4     60.0

 

 Thanks,

Aftab Alam

rg6211
Level 1
Level 1

I had this problem looking for compatible inexpensive 3rd party POE+ injectors and POE+ switches, until I discovered:

• Trendnet TPE-115GI POE+ injector

• Zyxel GS1900 POE+ switches 

 

These work fine with the AP2802i, hope this saves some of you time and headache!

 

Certain other vendors with this issue listened to feedback and added an option in the GUI to select the power source type manually, Cisco might take note.

 

While we are resurrecting the old thread, one other thing. If you attach the AP to an old Switch with offers PoE 802.11af, you must turn it off on the switch. Otherwise the AP might negotiate PoE with the switch, which tells him he will only get 15.4 W, which will cause the AP to shutdown it's radios.

The manufacturer of Cisco-branded power injector is Phihong USA.

As an update to this problem, my company is deploying a bunch of 2802i access points and I have been doing some testing between Cisco POE switches and PowerDsine POE injectors.  It seems so far that 2802i V03 access points work fine on the 9000 series PowerDsine POE injectors (802.3at) but V01 and V02 do not.  Have not tried to confirm this with Cisco support but that is what I have so far.  Running 8.3.150.0 on the controller.

 

Oddly enough, the V01 and V02 seem to come up full power on the single port un-managed PowerDsine but not on the managed multi-port PowerDsine POE injectors.

Thanks for testing. That really sound a case for TAC. You probably can/should replace all your V01/V02 models.
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: