Controller-less WLANs

Why does not an AP 135's eth1 port coming up?

Environment : AP 135 connected to 802.3ad power source, DC power source and 802.3at power source

 

AP 135 requires either 802.3at (Poe+) or DC power to bring the eth1 port Up.

With normal POE (802.3af) below output can be seen in the APboot up sequence.

########################
APBoot 1.2.6.7 (build 30025)
Built: 2011-08-30 at 17:41:16

Model: AP-13x
CPU:   88F6560 A0 (DDR3)
Clock: CPU 1600MHz, L2 533MHz, SysClock 533MHz, TClock 200MHz
DRAM:  256MB
POST1: passed
Flash: 16 MB
Power: 802.3af POE  <<<<<<<<<<<<<<<<<<<
LAN:   done
PHY:   done

.
.
.
Shutting down eth1 due to insufficient POE voltage [power profile 2] <<<<<<<<<<<<<<<<<<<
wifi0: Base BSSID d8:c7:c8:3d:3e:10, 16 available BSSID(s)

d8:c7:c8:cb:d3:e0# sho port status
Port Status
-----------
Port  Type  Admin-State  Oper-State
-----------------------------------
eth0    GE           up          up
eth1    GE           up        down <<<<<<<<<<<<<<<<<<< Operational status remains down
########################

With POE+ or 802.3at

########################
APBoot 1.2.6.7 (build 30025)
Built: 2011-08-30 at 17:41:16

Model: AP-13x
CPU:   88F6560 A0 (DDR3)
Clock: CPU 1600MHz, L2 533MHz, SysClock 533MHz, TClock 200MHz
DRAM:  256MB
POST1: passed
Flash: 16 MB
Power: 802.3at POE  <<<<<<<<<<<<<<<<<<
LAN:   done
PHY:   done
.
.
.
d8:c7:c8:cb:d3:e0# sho port status
Port Status
-----------
Port  Type  Admin-State  Oper-State
-----------------------------------
eth0    GE           up          up
eth1    GE           up          up
d8:c7:c8:cb:d3:e0#

Version History
Revision #:
2 of 2
Last update:
‎07-03-2014 08:42 AM
Updated by:
 
Labels (1)
Comments
Plsamuel53
I ran into this problem about a year ago. what version of software are you running on your controller

Default power requirement for AP 134/135:

 

For Aruba OS version 6.1.1.0 onwards:

 

48 volts DC 802.3af power over Ethernet (PoE) or 802.3at PoE+

 

- Note: when using 802.3af POE, the second Ethernet port is disabled. It is enabled when using an 802.3at POE power source (or direct DC power).

...

eth1: link down

ADDRCONF(NETDEV_UP): eth1: link is not ready

eth1: link down

bonding: bond0: enslaving eth1 as a backup interface with a down link.

 

PoE+ is not 802.3at

 

AOS6.2.0.2 and further supports power negotiation via LLDP,

 

Then in the AP boot up you would see something like;

...

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

Enabling eth1 due to LLDP power grant [power profile 1]

eth1: link up, full duplex, speed 1 Gbps

bonding: bond0: link status definitely up for interface eth1.

 

Thanks,

Anshul Bharthan

Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.