cloud managed c9300 and stack renumbering question

[Greg Locke]

I have a few c9300's converted to cloud managed running 17.18.1

I've been playing around in my dev environment by adding, subtracting to a stack or two. Switching from 8 in a stack to 4 in 2 stacks etc.

I've noticed that the switches are still numbered 1-4 and 5-8 when I've split them apart creating 2 stacks.

I'm wondering what will happen if I have another switch stack that also has former members of a stack that have the same number will behaive when I add to another existing stack when cloud managed.

Will it be handled without issue?

[aleabrahao]

Member IDs are not globally unique across all stacks; they only matter within a single stack. When you add a switch to a different stack, Meraki Cloud re-provisions it based on the new stack configuration. The previous member ID is discarded during the join process. The cloud uses the switch’s serial number as the unique identifier for management, not the stack number.

Getting started: Cisco Catalyst 9300 Management with Meraki Dashboard - Cisco Meraki Documentation

[Greg Locke]

Good. I'm just noticing that the new 2nd switch stack I created from the larger stack I split, has the switch port numbers in it's config as 5/0/1 for example instead of 1/0/1.

So when I look for them in the list they show up not exactly the way I would have expected.

In locally managed config, I would do a stack renumber command to get switch 1 to show up as 1 etc. in the new stack.

[joey.debra]

I'm not sure how 17.18 handles it but in 17.15 the Meraki numbering is totally disconnected from the Cisco numbering. So you could have switch 1 be switch 4 in IOS-XE. In that version at least you can't renumber your switches on the Cisco side so I'm not sure how it will handle the modification.