Go to the 17:30 minute mark for the POE discussion.
PoE Switches negotiate PoE power after identifying other end devices such as AP, Cameras using LLDP-MED.
if you are using ICX Switches:
By default, LLDP is disabled in ICX 7450 switch. To enable it, the following global command has to be issued:
ICX7450-48P Router(config)#lldp run
The switch will have to advertise power via LLDP and the following commands have to be issued either for the specific port e.g. port 1/1/5,
ICX7450-48P Router(config-if-e1000-1/1/5)#lldp advertise power-via-mdi ports ethernet 1/1/5
or if all ports have to be configured identically
ICX7450-48P Router(config-if-e1000-1/1/5)#lldp advertise power-via-mdi ports all
Also verify on Ruckus Unleashed AP if LLDP enabled
ruckus# show ap mac
If not enabled
ruckus(config-ap)# lldp enable
I have several R710 and R610 in my house
My POE+ 802.11at switches are Netgear gs108epp and Zyxel GS1200-8pV2.
Both supports 802.11at, but my ruckus AP connects only at 802.11af with limited perfomance
Q: Is it possible to managed my switch/ruckus to work correctly?
If not -what is the best price recommended switch with 8 ethernet + minimum 2 POE out to work with ruckus?
I've had exactly the same problem as well since upgrading to 200.8. I only have a single R720 to test with (along with several H510s, which don't require 802.11at), but I have tested with multiple ports, multiple cables, and two separate Netgear MS510TXPP switches, all with the same result.
The switches autodetect class 4 (802.3at) PoE for all my Ruckus APs, so I can't find anything wrong on that end.
I'll also note that I doubt the workaround provided above is actually doing anything. Yes, if I manually override the PoE setting on the R720 to 802.3at, it will show "802.3at" on the status page, but I also still get the warning about power. I really can't imagine this option allows the AP to draw more power than it believes the switch can provide (which sounds like a great way to damage some hardware) vs. operating in a lower power mode than the current PoE source can support.
Seeing the same issue—port 2 being an R710 and port 3 an R610. The R710 doesn’t appear to be doing LLDP by default. What my switch sees is below and this remains unchanged even after enabling lldp on the R710 as noted in another post here. The switch settings are the same for both ports.
switch(config)# sh lldp info remote-device 2
LLDP Remote Device Information Detail
switch(config)# sh lldp info remote-device 3
LLDP Remote Device Information Detail
Local Port : 3
ChassisType : mac-address
ChassisId : ...
PortType : mac-address
PortId : ...
SysName : R610
System Descr : Ruckus R610 Multimedia Hotzone Wireless AP/SW Version: 20...
PortDescr : eth0
System Capabilities Supported : bridge, wlan-access-point, router
System Capabilities Enabled : bridge, wlan-access-point
Remote Management Address
Type : ipv4
Address : ...
Poe Plus Information Detail
Poe Device Type : Type2 PD
Power Source : Only PSE
Power Priority : Unknown
Requested Power Value : 25.0 Watts
Actual Power Value : 25.0 Watts
As far as I can tell, LLDP (and LLDP-MED) are fully enabled on both the AP and switch. "get lldp" on the AP does indicate everything is enabled there. "get lldp neighbors" does also display the correct information for my switch, though the only entry I see related to PoE is "UPOE: 0". Hopefully the AP is checking for more than just UPoE.
On the switch, LLDP is enabled globally and in "Tx & Rx" mode for all ports (which is the default, and fully enabled). LLDP-MED is also enabled for all ports. Pulling up the information for the port the AP is connected to, though, it doesn't look like the AP is transmitting any MED properties. All MED details are blank ("N/A"), though standard LLDP details are all there and correct.
I'll reiterate that I did try to force the AP to 802.11at, and this appeared to have no effect. Do I need to do something other than changing the setting in the UI? (The CLI setting just seems to follow the UI.)
Considering that this seemed to be working prior to an AP firmware update, this certainly sounds like an issue with the Ruckus firmware. I am currently running the latest firmware from 6/10 (18.104.22.168.278), so no fixes so far on that end.
Interestingly after a couple minutes the alert went away after i had logged out of the web interface and logged back in.
Can confirm the second wired ethernet jack is working as well. I assume the error will come if I power cycle AP as it came back repeatedly.
Seems to me the handshake is taking a long time