Onboarding Catalyst switches and Unique client identifier

Solved
Einstein
Getting noticed

Onboarding Catalyst switches and Unique client identifier

We currently have our Meraki layer 3 network set on MAC address in Addressing and VLAN's for device identification. We have always had some misreporting with this, but nothing I couldn't work through. We are onboarding some new 9000 Catalyst switches, and I see when we do this it will force our network onto "Unique Client Identifier". 

 

I have seen several posts here on the forums going both ways, some saying don't use unique client identifier, and some saying don't use MAC address.  If onboarding Catalyst switches AUTOMATICALLY set it to unique client identifier, I just want an idea of what I may expect with this. 

 

Has anyone gone through this? 

Thank you in advance everyone!

1 Accepted Solution
cmr
Kind of a big deal
Kind of a big deal

Yes it does, no choice of anything else!

If my answer solves your problem please click Accept as Solution so others can benefit from it.

View solution in original post

4 Replies 4
cmr
Kind of a big deal
Kind of a big deal

I have used unique client identifier most of the time recently and found it to work okay.

If my answer solves your problem please click Accept as Solution so others can benefit from it.
Einstein
Getting noticed

Thank you for the input. Guess my main question is does onboarding Catalyst switches into a Meraki network automatically set your network to unique client identifier, not giving you any choice. 

cmr
Kind of a big deal
Kind of a big deal

Yes it does, no choice of anything else!

If my answer solves your problem please click Accept as Solution so others can benefit from it.
Einstein
Getting noticed

Thank you. I appreciate it!

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.
Labels