Link negotiation

Solved
rvalencia87
Here to help

Link negotiation

Is there a way to configure the negotiation manually in an AP??? I have 4 AP that have speed degraded, so I configure the switch port to force the speed negotiation to 1Gbps, but when I do that, the AP doesn't work, then I want to know if there is a way to configure the ethernet port in the AP to force to negotiate to 1Gbps.

1 Accepted Solution
rvalencia87
Here to help

Yes, I solved the problem, it was generated because of the RJ45, I replaced it, after that the AP start to work to 1Gbps. 

So in my case the problem was something physical.

View solution in original post

12 Replies 12
alemabrahao
Kind of a big deal
Kind of a big deal

No, you cannot manually configure speed or duplex settings on Meraki APs. Meraki APs always rely on auto-negotiation for link speed and duplex. 

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
rvalencia87
Here to help

I asked because in my case, the port 3 of the switch is forced to 1Gbps, but if I forced the negotiation, the AP doesn't work, and if I configure the port as automatic negotiation, the AP work in deprecated speed to 100MB, and I want to recover the speed of 1Gbps. 

 

rvalencia87_0-1752013658863.png

 

PhilipDAth
Kind of a big deal
Kind of a big deal

Going sideways;

 

Thirty years ago, forcing the speed/duplex was a semi-common issue.  But that problem no longer exists today.  You have a deeper underlying issue if you are having negotiation issues, and at best, forcing the speed/duplex might mask it.  Or worse still, hide the problem.

 

Before forcing the configuration, did the switch port and AP report that they had negotiated the same speed/duplex (such as 1Gb/s, 2.5Gb/s, etc)?

If so, were you getting anything reported like CRC errors, to give any indication there was a link issue?

 

If so, forcing the speed/duplex will have no impact on the issue.  The issue is far more likely to like on the RF side, or with client drivers.

 

One of the most common issues I encounter with companies that have multiple APs is that they have not configured an RF profile.  They left all the RF settings on their default settings.  If you are not using a profile, try configuring one first and wait 24 hours to verify whether the issue persists or changes.

https://documentation.meraki.com/MR/Radio_Settings/RF_Profiles

 

While you are there, make sure you have enabled AI channel planning.

PhilipDAth_0-1752013523659.png

 

Also, check out Wireless Health and Overview to see if it is identifying any issues.

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Meraki_Health_Overvie...

PhilipDAth_1-1752013569810.png

 

Having 2.4Ghz enabled is also a VERY common issue for performance problems.  Try disabling it so that only 5Ghz is enabled.

 

The Learning Hub also includes an advanced training course (free) for WiFi.  Modules 1, 2 and 3 are all about troubleshooting WiFi issues.

https://community.meraki.com/t5/Wireless-Advanced-Operations/ct-p/mroperations

 

rvalencia87
Here to help

In my case, the AP's works with a SSID which is public and other SSID that are only for employee, that's the reason because we can't turn off the 2.4GHZ band because customers who visit the bussines use old cel phones or devices. 

 

Also, I already use a RF Profile, it's the basic Indoor Profile, We have around 30 AP's but only 4 AP's has the speed of negotiation reduced, I already try to cycle the switch port, reboot the AP, run the cable test, and force the speed, but the issue still persist. 

PhilipDAth
Kind of a big deal
Kind of a big deal

Don't use the "Basic Indoor Profile" - that is the one with the default settings, primarily designed for customers with a single AP.

 

Use the option to create a new profile and choose the option that best describes your environment.

PhilipDAth_0-1752015269795.png

 

What do you mean when you say "speed of negotiation reduced"?  Is the AP and switch port set to auto/auto, and if so, what speed do they report they are negotiating?

rvalencia87
Here to help

The AP is running to 100MB instead 1Gbps, and I try that the AP works to 1Gbps, but if I forced the speed negotiation to 1Gbps the AP doesn't work. 

 

I already made all the suggestion that dashboard suggest me but the problem still persist.
The suggerence are:

- Run cable test. 

- Update link negotation. 

- Cycle port on switch. 

 

rvalencia87_0-1752015494125.png

 

PhilipDAth
Kind of a big deal
Kind of a big deal

And this plugs into a Meraki switch?

 

If you unplug the AP, and then run a cable test, how long does it report the cable is?  We want it to be under 100m (including the length of any patch leads in use), 90m otherwise.

rvalencia87
Here to help

Yes, it's a full Meraki solution, MX, Switch and AP's, there are 30 AP's but only 4 are affected by the "ethernet uplink speed degraded" error, the meassure I already made in one of them by the feature of measure in Meraki and gives me 41 mts.  

 

In my list of AP in the dashboard appears me like that, the one with alert are the AP's that are running to 100MB instead of 1Gbps.

 

rvalencia87_0-1752017181851.png

 

Mloraditch
Kind of a big deal
Kind of a big deal

The cable test didn't report any errors? If so if you dismount a problem AP and plug it directly into the switch do you still have the same error? If so you've narrowed it down to a bad AP or a bad switch port and you will need support to RMA one of these items probably. If not you have a cabling issue that that test isn't picking up and will need to repair or replace the drop most likely

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
dlee
Comes here often

Hi did you fix the problem? I have same issue here

rvalencia87
Here to help

Yes, I solved the problem, it was generated because of the RJ45, I replaced it, after that the AP start to work to 1Gbps. 

So in my case the problem was something physical.

dlee
Comes here often

Thanks to let me know I'll try replaced the cable.

 

Get notified when there are additional replies to this discussion.