Controllerless Networks

last person joined: 21 hours ago 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Expand all | Collapse all

AP-105 requesting to much power over PoE and switch shuts down port.

This thread has been viewed 0 times
  • 1.  AP-105 requesting to much power over PoE and switch shuts down port.

    Posted Jan 23, 2014 05:24 PM

    We're seeing a very odd issue at a school where AP-105s are pulling more power than the port allows and so the switch shuts down the port.

     

    Has anyone else experienced this issue? It just started on a handful of APs and I'm pretty sure it's an issue with the APs and not the switch.

     

    Thanks,



  • 2.  RE: AP-105 requesting to much power over PoE and switch shuts down port.

    EMPLOYEE
    Posted Jan 23, 2014 07:42 PM

    Make sure hybrid spectrum analysis is not enabled in the radio profile.



  • 3.  RE: AP-105 requesting to much power over PoE and switch shuts down port.

    Posted Jan 24, 2014 11:51 AM


  • 4.  RE: AP-105 requesting to much power over PoE and switch shuts down port.

    Posted May 13, 2016 09:16 AM

    I am encountering this issue on a 3200 controller. We have with multiple AP-105's, and the controller is running code version 6.3.1.2. AP-mode is activated on all APs with no spectrum analysis. Only 1 of the AP-105's is affected. It is trying to draw a lot of power and the switch has shut down the port. Any advice as to why this is happening?



  • 5.  RE: AP-105 requesting to much power over PoE and switch shuts down port.

    EMPLOYEE
    Posted May 13, 2016 09:46 AM

    What kind of switch and how many APs do you have on it?



  • 6.  RE: AP-105 requesting to much power over PoE and switch shuts down port.

    Posted May 13, 2016 09:57 AM

    The switch is a Cisco 4507. We have 8 APs on the switch - 7x AP-105s, 1x AP-104.



  • 7.  RE: AP-105 requesting to much power over PoE and switch shuts down port.

    EMPLOYEE
    Posted May 13, 2016 10:01 AM

    We need more details:

     

    How much does each AP consume?

    What is the total?

    Do you have hybrid spectrum analysis enabled?

     



  • 8.  RE: AP-105 requesting to much power over PoE and switch shuts down port.

    Posted May 13, 2016 10:20 AM

    The APs consume 15.4W each. 7 x 15.4 = 107.8W.

     

    We do not have hybrid spectrum analysis enabled.



  • 9.  RE: AP-105 requesting to much power over PoE and switch shuts down port.

    EMPLOYEE
    Posted May 13, 2016 10:50 AM

    Do you have the output of "show power inline" from the switch?

    Are these Instant APs or controller-based APs?

    What version of Aruba Instant or Controller-based code is this?



  • 10.  RE: AP-105 requesting to much power over PoE and switch shuts down port.

    Posted May 31, 2016 05:05 AM

    @cjoseph wrote:

    Do you have the output of "show power inline" from the switch?

    Are these Instant APs or controller-based APs?

    What version of Aruba Instant or Controller-based code is this?


    It's a 3200 controller running code version 6.3.1.2.

    All APs are campus APs.

     

    Show power inline output on the port:

     

    sw-4.#sh power inline gi7/26
    Available:4800(w) Used:1174(w) Remaining:3626(w)

    Interface   Admin   Oper             Power(Watts)               Device          Class
                                                       From PS   To Device
    -----------   ------     -----------------  ----------     --------------   ----------------- -------

    Gi7/26     auto      on                  16.6          15.4             Ieee PD         3

     

    Interface   AdminPowerMax    AdminConsumption
                    (Watts)                    (Watts)
    ----------    ------------------------   -----------------------

    Gi7/26     30.0                        15.4

     

    Below is the error we get from the switch on the port the AP is on:

     

    051703: May 12 03:49:10.568 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051704: May 12 03:50:39.550 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051705: May 12 03:52:08.673 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051706: May 12 03:53:12.595 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051707: May 12 03:54:42.994 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051708: May 12 03:55:43.277 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051709: May 12 03:57:11.702 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051710: May 12 03:58:39.897 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051711: May 12 03:59:57.314 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051712: May 12 04:01:03.213 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051713: May 12 04:02:15.925 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.
    051714: May 12 04:03:28.962 UTC: %C4K_ETHPORTMAN-3-INLINEPOWEROVERDRAWN: Inline powered device connected on port Gi7/26 exceeded its hardware protection threshold.