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

3832
Views
10
Helpful
7
Replies
Beginner

Cisco AIR-AP3802I-E-K9 not getting enough power WS-C3560X-48P IPBase

Hi all,

 

I do have 3 x AIR-AP3802I-E-K9 and a WS-C3560X-48P with a PS of 1100 W, capable of 802.3at.

I can get the APs on the WLC, but they're not broadcasting, and clean air is off.

 

After some troubleshooting, even if I configured the switch interface for max power (see below) the AP seems to suck no more than 15.4 W, which is...confusing, as on the WLC, it says Medium Power, but no alarms, though the LEDs are flashing in all colours.

 

The remaining power is over 600W on the switch so here we're fine.

 

See below the interface conf:

interface GigabitEthernet0/8
description *** Wireless AP ***
switchport trunk encapsulation dot1q
switchport trunk native vlan 40
switchport trunk allowed vlan 40,58
switchport mode trunk
load-interval 30
power inline port priority high
power inline static

 

See below the show power inline output showing the static power conf of 30 W per interface.

Available:847.0(w) Used:246.0(w) Remaining:601.0(w)

Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi0/4 static on 30.0 AIR-AP3802I-E-K9 4 30.0
Gi0/8 static on 30.0 AIR-AP3802I-E-K9 4 30.0

However, running show cdp nei on those interfaces is showing the APs are using 15.4 only:

 

Device ID: wap00cc-
Entry address(es):
IP address: 10.100.40.99
Platform: cisco AIR-AP3802I-E-K9, Capabilities: Router Trans-Bridge
Interface: GigabitEthernet0/8, Port ID (outgoing port): GigabitEthernet0
Holdtime : 179 sec

Version :
Cisco AP Software, ap3g3-k9w8 Version: 8.3.112.0
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2014-2015 by Cisco Systems, Inc.

advertisement version: 2
Duplex: full
Power drawn: 15.400 Watts
Power request id: 15763, Power management id: 1
Power request levels are:30000 15400 0 0 0
Management address(es):
IP address: 10.100.40.99

 

The switch is running: flash:/c3560e-ipbasek9-mz.122-55.SE6.bin

 

I also run show run conf all and there's no hidden commands sent on those interfaces.

Checking the log on the AP:

onfigure(8).
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.1008] Radio0 not started, not enough POE power
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.1011] Radio1 not started, not enough POE power
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.1017] Radio0 not started, not enough POE power
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.1020] Radio1 not started, not enough POE power
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.1086] Radio0 not started, not enough POE power
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.2184] Radio1 not started, not enough POE power
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.4653]
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.4654] CAPWAP State: Run
Sep 25 13:20:10 syslog: +ifconfig wired0 promisc
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.4906] CAPWAP HW tunnel params changed, UPDATING the existing
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.5447] AP has joined controller corwlc-01-gi-ldnedc
Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.5511] Flexconnect Switching to Connected Mode!

Sep 25 13:20:10 kernel: [*09/25/2017 13:20:10.9770] Password for 'IPGadmin' changed
Sep 25 13:20:10 FIPS[9357]: *** /usr/sbin/hostapd: FIPS Mode = disabled ***
Sep 25 13:20:10 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:20:11 FIPS[9367]: *** /usr/sbin/hostapd: FIPS Mode = disabled ***
Sep 25 13:21:05 brain: CDP PoE negotiation FAILED !!
Sep 25 13:21:05 brain: LLDP PoE negotiation START
Sep 25 13:21:37 brain: LLDP PoE negotiation FAILED !!
Sep 25 13:21:37 brain: Power mode: Degraded/Reduced Power, power_detection: DC_adapter(FALSE), 802.3AF_POE(TRUE)
Sep 25 13:21:37 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:21:37 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:21:42 brain: Restart POE negotiation
Sep 25 13:21:42 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:21:42 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:21:43 brain: CDP PoE negotiation START
Sep 25 13:22:53 brain: CDP PoE negotiation FAILED !!
Sep 25 13:22:53 brain: LLDP PoE negotiation START
Sep 25 13:23:25 brain: LLDP PoE negotiation FAILED !!
Sep 25 13:23:25 brain: Power mode: Degraded/Reduced Power, power_detection: DC_adapter(FALSE), 802.3AF_POE(TRUE)
Sep 25 13:23:25 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:23:25 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:23:30 brain: Restart POE negotiation
Sep 25 13:23:30 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:23:30 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:23:31 brain: CDP PoE negotiation START
Sep 25 13:24:31 brain: CDP PoE negotiation FAILED !!
Sep 25 13:24:31 brain: LLDP PoE negotiation START
Sep 25 13:25:03 brain: LLDP PoE negotiation FAILED !!
Sep 25 13:25:03 brain: Power mode: Degraded/Reduced Power, power_detection: DC_adapter(FALSE), 802.3AF_POE(TRUE)
Sep 25 13:25:03 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:25:03 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:25:08 brain: Restart POE negotiation
Sep 25 13:25:08 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:25:08 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:25:09 brain: CDP PoE negotiation START
Sep 25 13:26:09 brain: CDP PoE negotiation FAILED !!
Sep 25 13:26:09 brain: LLDP PoE negotiation START
Sep 25 13:26:41 brain: LLDP PoE negotiation FAILED !!
Sep 25 13:26:41 brain: Power mode: Degraded/Reduced Power, power_detection: DC_adapter(FALSE), 802.3AF_POE(TRUE)
Sep 25 13:26:41 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:26:41 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:26:46 brain: Restart POE negotiation
Sep 25 13:26:46 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:26:46 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:26:47 brain: CDP PoE negotiation START
Sep 25 13:27:47 brain: CDP PoE negotiation FAILED !!
Sep 25 13:27:47 brain: LLDP PoE negotiation START
Sep 25 13:28:19 brain: LLDP PoE negotiation FAILED !!
Sep 25 13:28:19 brain: Power mode: Degraded/Reduced Power, power_detection: DC_adapter(FALSE), 802.3AF_POE(TRUE)
Sep 25 13:28:19 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:28:19 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:28:24 brain: Restart POE negotiation
Sep 25 13:28:24 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:28:24 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:28:25 brain: CDP PoE negotiation START
Sep 25 13:29:25 brain: CDP PoE negotiation FAILED !!
Sep 25 13:29:25 brain: LLDP PoE negotiation START
Sep 25 13:29:57 brain: LLDP PoE negotiation FAILED !!
Sep 25 13:29:57 brain: Power mode: Degraded/Reduced Power, power_detection: DC_adapter(FALSE), 802.3AF_POE(TRUE)
Sep 25 13:29:57 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:29:57 root: SYS-COND: Retrigger critical condition, 1 power
Sep 25 13:30:02 brain: Restart POE negotiation
Sep 25 13:30:02 brain: Capwap Power-mode notify, power_consumption 15400, upoe 0
Sep 25 13:30:02 root: SYS-COND: Retrigger critical condition, 1 power

 

Ticking the checkbox for "Pre-standard 802.3af switches" is not a solution, as I know this AP needs more than that. I've done this anyway, the radios will be on, clean air off and wont broadcast the ssid.

What intrigues me is why is not getting more than 15.4 W of power, since 30 W are provided?

Another strange thing is that on the WLC it says connected with medium power, and not indication of low power here (only on the APs logs).

 

Any thoughts ?

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Beginner

Re: Cisco AIR-AP3802I-E-K9 not getting enough power WS-C3560X-48P IPBase

You are very correct.

That would be my next step in troubleshooting this problem.

 

Unfortunately I can't update the code at this moment. 

I was just looking to find out if there are any other people that faced the same problem and what steps they followed.

 

After more research, I realised the switch will need one more power supply in order to work under the 802.3at standard. I did not test as we bought the righ power injectors, but I assume for a 3560x-48 I will need 2 PS:

Setup1 - 1 x 1100 W and 1 x 750 W

Setup 2 - 2 x 1100 W

 

Otherwise the switch will be just 802.3af.

 

Found this in their documentation. Not that happy, as Cisco is advertising the sw as POE+. I had to go through all their documentation to find this bit. I wonder how the switch will perform with a new code.

 

 

7 REPLIES 7
Beginner

Re: Cisco AIR-AP3802I-E-K9 not getting enough power WS-C3560X-48P IPBase

Do you have CDP disabled globally or disabled on the switch ports by chance?  I didn't see it specifically disabled on the port configuration you provided, but perhaps it's disabled globally?

 

CDP is required for power negotiation.

 

-Derrick

Beginner

Re: Cisco AIR-AP3802I-E-K9 not getting enough power WS-C3560X-48P IPBase

Hi @Derrick Hurley,

 

The CDP is enabled.

 

Kind regards,

Neo

Beginner

Re: Cisco AIR-AP3802I-E-K9 not getting enough power WS-C3560X-48P IPBase

Any chance of updating the software on the switch and putting the port back to non static POE?

 

The current software is over 5 years old.

 

-Derrick

Highlighted
Beginner

Re: Cisco AIR-AP3802I-E-K9 not getting enough power WS-C3560X-48P IPBase

You are very correct.

That would be my next step in troubleshooting this problem.

 

Unfortunately I can't update the code at this moment. 

I was just looking to find out if there are any other people that faced the same problem and what steps they followed.

 

After more research, I realised the switch will need one more power supply in order to work under the 802.3at standard. I did not test as we bought the righ power injectors, but I assume for a 3560x-48 I will need 2 PS:

Setup1 - 1 x 1100 W and 1 x 750 W

Setup 2 - 2 x 1100 W

 

Otherwise the switch will be just 802.3af.

 

Found this in their documentation. Not that happy, as Cisco is advertising the sw as POE+. I had to go through all their documentation to find this bit. I wonder how the switch will perform with a new code.

 

 

Enthusiast

Re: Cisco AIR-AP3802I-E-K9 not getting enough power WS-C3560X-48P IPBase

What power does the 3560x provide?  Remember there are multiple versions of PoE; and the 3802's need the full 30 watts to operate.

 

(PoE, PoE+, and uPoE.  Not sure which is which at the moment.)

I think the PoE+ is needed for 3702's that like about 18 watts; and uPoE for 3802 ?

Enthusiast

Re: Cisco AIR-AP3802I-E-K9 not getting enough power WS-C3560X-48P IPBase

PoE gives 15.4 watts, PoE+ gives 30W, and uPoE can give 60W

 

Turns out the 3802 WITHOUT an installed module needs 30W, so PoE+ is fine.

 

3702's would run on PoE with some capabilities limited and some radios disabled.  3802 needs PoE+ or upoe.

Beginner

Re: Cisco AIR-AP3802I-E-K9 not getting enough power WS-C3560X-48P IPBase

Hey,

 

My problem is solved. 

The answers for your both posts are in my first post describing my problem.

 

Thank you for your time and intention.

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