Why does the ethernet-1 port of IAP-134/135 do not turn active?

Aruba Employee
Aruba Employee

Environment : This article applies to Aruba Instant AP-135 Access Point.



IAP-134 and IAP-135 feature dual 10/100/1000BASE-T Ethernet interfaces and operate from standard 802.3af and 802.3at Power-over-Ethernet (PoE) sources. The secondary Ethernet interface (eth-1) goes active only when POE+ (802.3at) or DC power is supplied to the access point.

Below observations are seen when eth-1 port is not active:



  •     Link lights on Eth-1 port of IAP-134/135 do not go up.
  •   Wired client connected to Eth-1 port not able to get IP address.


When an IAP-134/135 is powered with standard 802.3af PoE source, below message can be seen on the AP Console during boot:
rtaImage (1).jpg
Some POE switches requires LLDP by default to supply POE+ (802.3at) and Aruba supports that only on ArubaOS version 6.2, hence POE switch reverted to 802.3af which means AP135 disabled its eth1 port.  Issue can be resolved by disable the LLDP requirement per port on the vendor POE switch.

One can console into IAP and run the below command to know the ethernet port status:
rtaImage (2).jpg
Below are the Aruba Controllers that come with PoE ports:
rtaImage (3).jpg
If the IAP-134/135 is connected to one of the above controller ports that support PoE, then below CLI screenshots show us how to check if the PoE is enabeld on the port:
rtaImage (4).jpg


Version history
Revision #:
1 of 1
Last update:
‎06-27-2014 09:09 AM
Updated by:
Labels (1)

This post needs to be updated, see post



Upgrading the IAP to a newer firmware will allow ETH1 to work without poe+ power.

Search Airheads
Showing results for 
Search instead for 
Did you mean: