cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

10296
Views
30
Helpful
28
Replies
Beginner

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

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

28 REPLIES 28
Hall of Fame Community Legend

If the AP has joined the

If the AP has joined the controller, go to the controller: 

  1. Monitor > AP Summary > All APs > Detail;
  2. Click on the AP of concern;
  3. Go to Advanced tab; 
  4. Power over Ethernet Settings > click Power Injector State > enter the MAC address of the injector.
  5. Click Apply
Beginner

Hi,

Hi,

thank you for your reply.

The AP has joined the controller. I've tried to set the Power Injector Selection to override, but that did not work. I tried to restart the AP.

Ubiquiti POE injector don't (as far as i can see,) have there own mac-address. Not that I can find from checking arp-table at AP and switch.

Best regards

Participant

Can you put more details

Can you put more details about the PoE injectors you are using?  You mentioned D-Link PoE adaptors, then Ubiquity adaptors.  Model numbers would be useful.

The problem is most likely due to something with the PoE injectors (not necessarily faulty - just not quite interoperable) however it could be related to the PoE negotiation.  It might also be worth opening a TAC case about it as I don't know if the Wireless team test the 2800s with third party PoE adapters.

I have tested and ran 2800s successfully with the AIR-PWRINJ6= - so it definitely does work with those ones but they are Cisco - not third party units.

Incidentally you can use Cisco Small Business Gig PoE adapters as well (SKU: SB-PWR-INJ2), they look and work identically, are much cheaper and have the identical OEM part number but with a different sticker/logo :-)

Beginner

Hi.

Hi.

The D-link injector is a DPE-301GI,
and the Ubiquity POE-50-60W.

Since the documentation says "Any 802.3at (25.5 W) compliant switch port". I thought it would be the same with POE-injectors.

Best regards

Participant

Those PoE injectors certainly

Those PoE injectors certainly look good enough to me.

One last thing - can you confirm the specifications of the cables?  Have you tried swapping them over with new Cat5e or better grade to rule that out?

If you have and it still doesn't work then it is probably time to raise a TAC case.  Either the documentation is incorrect or there is a bug of some sort.

Enthusiast

I know they don't work from

I know they don't work from pwrinj4's which are 56v/.55a or 30.8w.   They do not attach to the wlc, but work fine with the generic PSM60U supply for the br1410's.

Beginner

Have changed the cables,

Have changed the cables, still no improvement.

Hall of Fame Community Legend

Can you enable LLDP on the

Can you enable LLDP on the switch?

Highlighted
Beginner

Re: Hi.

I have the same problem with Startech POEINJ4G 4-port injector. It is able to provide 30W to all four ports but with the two 2802is I have connected they only draw AF power and will not turn on the radios. I have tried Injector Override and turning on and off CDP and LLDP on the individual ports.

I get the same logs from the AP which seems to indicate it only want's to negotiate AT power with an AT compliant device that can do CDP/LLDP and indicate adequate power. 

 

Does anyone have these APs working at full power with ANY 3rd party injector or switch?

Cisco Employee

Re: Hi.

Please use AIR-PWRINJ-6 provided by Cisco.
Beginner

Re: Hi.

I consider this a non-reply reply from Cisco. Obviously it's going to work with the manufacturer suggested device produced by the manufacturer. The question being asked in this whole thread is, why is the AP incapable of working with a different 802.3at compliant injector or device?

 

This relevant section from the device data sheet seems uneccessarily ambiguous in hindsight but it's very easy to interpret it as meaning that the AP can be powered by an 802.3AT injector *such-as* the (AIR-PWRINJ-6):

 

●  802.3at PoE+, Cisco Universal PoE (Cisco UPOE®)
●  802.3at power injector (AIR-PWRINJ6=)
 
It's not clear that Cisco's meaning is *ONLY* the Cisco AIR-PWRINJ6=, MSRP $139.
 
Perhaps Cisco could update the data sheet to be more explicit about the interoperability of it's device, or provide more detailed information about what technical constraints built into the device make it picky about which 802.3at power injectors or switches it will function with.
 
This misleading/incomplete information is wasting mine and obviously other folks time and money.
Beginner

Re: Hi.

Did you end up getting these units working with the Ubiquiti POE-50-60W?

 

I have a 3802i with Mobility Express loaded on it - but I'm getting the same issue:

 

Aug 10 02:16:50 brain: Power mode: Degraded/Reduced Power, power_detection: DC_adapter(FALSE), 802.3AF_POE(TRUE)
Aug 10 02:16:55 brain: Restart POE negotiation
Aug 10 02:16:56 brain: CDP PoE negotiation START
Aug 10 02:17:57 brain: CDP PoE negotiation FAILED !!
Aug 10 02:17:57 brain: LLDP PoE negotiation START
Aug 10 02:18:29 brain: LLDP PoE negotiation FAILED !!

In this mode, I can't bring up any of the radios, although I can SSH / browse / console into the device fine.

 

I'm just trying to use these with a dumb switch (no LLDP or CDP support), and the power injector to give the thing PoE.

 

I've also tried:

(Cisco Controller) >config ap power injector enable all override
Hall of Fame Community Legend

Re: Hi.

What firmware version is the AP running on?
Beginner

Re: Hi.

I am using 'AIR-AP3800-K9-ME-8-5-135-0.tar' with the unit in Mobility Express mode.

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