Can't avoid.  they are what we have, so we'll have to see how it goes and make the best of it.  I have been going over the current core config with a fine-toothed comb, so I can replicate as much as possible on the Meraki stack. The only issue is the difference in terminology between the two sometimes make it confusing in translation. ... View more

In our current 3850 stack, we have a number of VLANs defined, login to the stack is via RSA(my understanding is that on Meraki, we need to use Duo), have a number of Port-channels defined as links to wiring closets, has some static routes defined, and access lists to some VLANs and some by protocol.   I have never set up a core switch before, and this new Meraki stack will replace the 3850 stack.  I'm trying to verify if this is a feasible switch, and how to do it properly.  Currently I'm waiting for my secondary power supplies, stacking and power stacking cables to be able to create the stack.  Then I need to nail down the steps to take to switch over, and some way to test without breaking the network. Up till now, I've only deployed layer 2 switches, so this is all new to me. ... View more

I also found it:   The Start date is from date of delivery (co-term) or up to 90 days after delivery (per-device), but no later than the claim date  All licenses expire at the same time as opposed to unique license periods/device ... View more

So, for example, I have 3 VLANS called VLAN 100, 140 & 150, with IP addresses of 172.28.100.x, 172.28.140.x & 172.28.150.x.  My DHCP server is in VLAN 51 at 172.28.51.x, and the switch is on mgmt VLAN 31 or 172.28.31.x.  For the Routing and DHCP, do I create in interface in each of the vlans, so like 172.28.100.5, 172.28.140.5 & 172.28.150.5 for example pointing to my DHCP server, or would I just use 1 IP for all interfaces in the switch's VLAN 31, forwarding DHCP requests tagged with the VLAN ID to the DHCP server? ... View more

But do you need to enter in an interface IP and, if so what exactly is it looking for?   ... View more