cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3589
Views
5
Helpful
4
Replies
Participant

AIR-AP3802I-B-K9 Power Requirements

Hi,

just connected a AIR-AP3802I-B-K9 AP to the network. The AP seems to be stuck in a boot cycle. In this doc you can see that the AP requires uPOE. Is this my issue?

Thank you

http://www.cisco.com/c/dam/en/us/td/i/400001-500000/410001-420000/412001-413000/412746.tif/_jcr_content/renditions/412746.jpg

I will be able to ping the AP for a short period...then, it goes down again. Also, I dont see it registering on the Controller either (5508 running version 8.2.100.0)

Reply from 10.20.4.55: bytes=32 time=1ms TTL=64
Reply from 10.20.4.55: bytes=32 time=1ms TTL=64
Reply from 10.20.4.55: bytes=32 time=1ms TTL=64
Reply from 10.20.4.55: bytes=32 time=1ms TTL=64
Reply from 10.20.4.55: bytes=32 time=8ms TTL=64
Reply from 10.20.4.55: bytes=32 time=1ms TTL=64

I see the device on the switch using CDP:

Device ID: AP0042.68C6.0F3A
Entry address(es):
  IP address: 10.20.4.55
Platform: AIR-AP3802I-B-K9,  Capabilities: Router Trans-Bridge
Interface: GigabitEthernet1/0/47,  Port ID (outgoing port): GigabitEthernet0
Holdtime : 133 sec

Version :
Cisco AP Software, AIR-AP3802I-B-K9 Version: 8.2.20.16
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2014-2015 by Cisco Systems, Inc.

advertisement version: 2
Power drawn: 30.000 Watts
Power request id: 2456, Power management id: 2
Power request levels are:30000 0 0 0 0


Total cdp entries displayed : 1

The switch model is:

NAME: "c38xx Stack", DESCR: "c38xx Stack"
PID: WS-C3850-48P      , VID: V02  , SN: FOC1746X0B1

Show power inline output...notice the last port...that is the AP in question:

sho power inline

Module   Available     Used     Remaining
          (Watts)     (Watts)    (Watts)
------   ---------   --------   ---------
1           390.0      119.4       270.6
Interface Admin  Oper       Power   Device              Class Max
                            (Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/1   auto   off        0.0     n/a                 n/a   30.0
Gi1/0/2   auto   off        0.0     n/a                 n/a   30.0
Gi1/0/3   auto   off        0.0     n/a                 n/a   30.0
Gi1/0/4   auto   off        0.0     n/a                 n/a   30.0
Gi1/0/5   auto   off        0.0     n/a                 n/a   30.0
Gi1/0/6   auto   on         9.5     IP Phone 8961       4     30.0
Gi1/0/7   auto   on         3.8     IP Phone 6945       1     30.0
Gi1/0/8   auto   off        0.0     n/a                 n/a   30.0
Gi1/0/9   auto   off        0.0     n/a                 n/a   30.0
Gi1/0/10  auto   on         9.5     IP Phone 8961       4     30.0
Gi1/0/11  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/12  auto   on         3.8     IP Phone 6945       1     30.0
Gi1/0/13  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/14  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/15  auto   on         3.8     IP Phone 6945       1     30.0
Gi1/0/16  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/17  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/18  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/19  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/20  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/21  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/22  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/23  auto   on         15.4    Ieee PD             0     30.0
Gi1/0/24  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/25  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/26  auto   on         3.8     IP Phone 6945       1     30.0
Gi1/0/27  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/28  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/29  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/30  auto   on         9.5     IP Phone 8961       4     30.0
Gi1/0/31  auto   on         3.8     IP Phone 6945       1     30.0
Gi1/0/32  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/33  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/34  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/35  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/36  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/37  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/38  auto   off        0.0     n/a                 n/a   30.0
Interface Admin  Oper       Power   Device              Class Max
                            (Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/39  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/40  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/41  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/42  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/43  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/44  auto   on         16.8    AIR-CAP3702I-A-K9   4     30.0
Gi1/0/45  auto   off        0.0     n/a                 n/a   30.0
Gi1/0/46  auto   on         9.5     IP Phone 8961       4     30.0
Gi1/0/47  auto   on         30.0    AIR-AP3802I-B-K9    4     30.0

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
VIP Mentor

I will be able to ping the AP

I will be able to ping the AP for a short period...then, it goes down again. Also, I dont see it registering on the Controller either (5508 running version 8.2.100.0)

8.2.100.0 is not support 3800 series AP. Minimum code is 8.2.110.0 (refer table 2 of this doc)

http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html#56735

Upgrade your controller to 8.2MR1 (8.2.111.0). Here is the release note of that code

http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn82mr1.html

HTH

Rasika

*** Pls rate all useful responses ***

4 REPLIES

hi,

hi,

i don't think is a poe problem, this behavior is typical when it fails to join the controller

if it's possible check the output on console port of the ap

i see on the release that there is a bug for dns discovery:

If you are using Cisco 1800, 2800, or 3800 Series APs, and want to enable the DNS Discovery for CAPWAP Join feature, we recommend that you upgrade to Release 8.2.111.0. If you do not want to enable this feature, you do not have to upgrade, and can continue to use Release 8.2.110.0.

Regards.

VIP Mentor

I will be able to ping the AP

I will be able to ping the AP for a short period...then, it goes down again. Also, I dont see it registering on the Controller either (5508 running version 8.2.100.0)

8.2.100.0 is not support 3800 series AP. Minimum code is 8.2.110.0 (refer table 2 of this doc)

http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html#56735

Upgrade your controller to 8.2MR1 (8.2.111.0). Here is the release note of that code

http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn82mr1.html

HTH

Rasika

*** Pls rate all useful responses ***

Participant

Thanks Rasik - I didnt even

Thanks Rasik - I didnt even think about an upgrade as our current code is so recent.

Beginner

Understand this particular

Understand this particular issue was code related but we do have a power issue which is why I'm responding on this thread.

We're looking at inline POE (802.3at) injector rather than individual 'injector blocks' for each AP.  I've seen some posts stating that for at least the 3700's, there's issues where the AP does not recognize the available 802.3at wattage and goes in to this low-power mode.  Has anyone used a third-party power-injector for the 3800's rather than the Cisco branded injector-blocks?

CreatePlease to create content