R720 slow speed issue, under 100Mbit, Unleashed version 200.15.6.212.20

[bartman2468]

I bought 2 r720 off eBay. 

One of them was inaccessible after reset and I had to flash the firmware via uart console, successfully. 

I got both of them updated to the latest Unleashed version that shows support for r720. Everything seemed fine. Unleashed version 200.15.6.212.20

Except when I put it in place I get speeds under 100 on 5ghz down and up

I have separate ssid for 5 and 2.4, both give low speeds under 100

It’s like it’s capped at 100 down but I check the port info under ap status and it says 1000 full auto. Which checks out on my switch as well.

PoE injector is 90w Poe++, I found I had to set the power to bt manually in ap settings to get rid of that warning about low power.

That didn’t change anything same exact speeds as it was when it was set to af and drawing 15w…..

I’m very confused by this. Is there something I’m doing wrong?

Both of these r720 exhibit the same behavior and same speeds.

So I’m less inclined to believe it’s a hardware issue but who knows.

Is the latest Unleashed version for these not good, if so can someone recommend best version for an r720.

I’m at a loss any info and guidance would be greatly appreciated. Thanks everyone.

[Kiran_Raval · Accepted solution]

Hi Bartman,

Please follow these recommendations to optimize performance:

• Update the AP to the latest firmware version v200.15.6.212.27. You can download it from the following link: 

• Ensure the AP is operating on a clear channel with a channel width of 40 MHz or 80 MHz, depending on availability of a clear 80 MHz channel.

• Position the client device close to the AP to maintain a strong and stable signal connection.

• Connect an 802.11ac-compatible client device and perform a speed test to verify throughput.

Regards,

Kiran Raval

[bartman2468]

Thank you for the reply. I mistakenly forgot to check wired connection on other devices, I actually had an issue with ISP connection at the fiber ONT, power cycled and all back to normal. 

The local network speed test that everyone was mentioning would’ve shown this, so now I can add that to the list of troubleshooting steps for instances like this. 

Thanks.