Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

AP135 shuts down eth1 due to insufficient POE voltage [power profile 2]

This thread has been viewed 2 times

  • 1.  AP135 shuts down eth1 due to insufficient POE voltage [power profile 2]

    Posted May 09, 2013 11:31 AM

    AP135 is plugged into Cisco 3560x switch and lldp is enabled as well. But it shuts down eth1 port due to insufficient power.

     

    Any ideas?



  • 2.  RE: AP135 shuts down eth1 due to insufficient POE voltage [power profile 2]

    Posted May 09, 2013 01:22 PM

     

    You need 802.11at in order to get power on e1 and the 3560 supports 802.11af instead.

     

     



  • 3.  RE: AP135 shuts down eth1 due to insufficient POE voltage [power profile 2]

    EMPLOYEE
    Posted May 09, 2013 01:32 PM

    What code are you running? This behavior has been changing a bit in recent releases.

     

    Prior to 6.2, only layer 1 negotiation for 802.3at POE was supported. With 6.2, LLDP can be used to identify an 802.3at source.

     

    /Onno Harms, Aruba



  • 4.  RE: AP135 shuts down eth1 due to insufficient POE voltage [power profile 2]

    Posted May 09, 2013 01:42 PM

    @vfabian - 3560X supports POE+

     

    The code is 6.1.3.8. This means I need to use a POE injector for the AP?



  • 5.  RE: AP135 shuts down eth1 due to insufficient POE voltage [power profile 2]
    Best Answer

    EMPLOYEE
    Posted May 09, 2013 01:51 PM

    If you need the second ethernet port, you should either use an 802.3at midspan, or upgrade to 6.2.



  • 6.  RE: AP135 shuts down eth1 due to insufficient POE voltage [power profile 2]

    Posted May 10, 2013 03:23 PM

    I also had to upgrade the IOS image on Cisco 3560X to get it working. (12.2 => 15.0)



  • 7.  RE: AP135 shuts down eth1 due to insufficient POE voltage [power profile 2]

    Posted May 09, 2013 01:54 PM

    missed the "x"