Changing Client Tracking to Unique Identifier means we lose ability to track clients on network

[SimonReach]

We've changed over from the MAC address client tracking to Unique Client Identifier, to look at resolving the issues we're having with the 17.x and 18.x firmware slowing down our internet connection, but when the change was made, we lose the ability to identify which switch port clients are plugged in.

Our network is setup as 2x MX100s > 2x MS250s teamed together > MS210s teamed together.  Servers are plugged into the MS250s and the clients are plugged into the MS210s.

In the clients screen on MAC address client tracking, we can view the switch port a client is plugged into on the MS210s.  With the Unique Client Identifier, all the clients state that they're plugged into the aggregated switch ports that connected the MS250s to the MS210.

[alemabrahao]

What problem are you facing that makes it necessary to change the client tracking?

[SimonReach]

When we update the MX100 at our headoffice from firmware 16.x to 17.x or 18.x, the internet at the site slows right down and a lot of websites will time out the first time you use it and then works fine when you refresh.

This is a well documented problem in the forums, a lot of people are stating that the issue is resolved by changing the tracking to the Unique Client Identifier if you have MXs with Meraki level 3 switches underneath them.

[alemabrahao]

I'm not sure if  it will solve the issue, I suggest you open a support case.

[PhilipDAth]

That is not the expected behaviour.  That is a bug.

Make sure the MS are running current stable firmware or better.  If they are, then open a support case.