Controller-less WLANs

 View Only
last person joined: one year ago 

Articles relating to existing and legacy HPE Aruba Networking products and solutions including IAP, Central / HPE Aruba Networking Central, MSR, and Outdoor Mesh

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

Jun 28, 2014 10:19 AM

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#

Statistics
0 Favorited
2 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.