L3 routing setup

New here

L3 routing setup

I've tried to figure out the L3 routing config on my own, but it's just not clicking in my head.  Most of the help leads to the same Meraki documentation page (https://documentation.meraki.com/MS/Layer_3_Switching/MS_Layer_3_Switching_and_Routing) and I guess I need it spelled out a little more, or explained differently. 


Situation, I'm replacing 3 stacked Catalyst 3750s as my core with stacked MS390s.  I have the 390s stacked, firmware updated and online.  I'll be changing them out next week on our shutdown week. I'm pre-configuring as much as I can, without creating IP conflicts.


My existing catalyst has a default gateway of (IPs changed to protect the innocent) and a route of configured.  In addition, vlan interfaces are configured (vlan20 - management vlan, vlan 60 - voice, etc) with helper-address for DHCP requests.


When I look at creating the first L3 interface on my 390 stack, I get confused. I've got

Name- "Uplink"

Subnet - ""

Interface IP - <This is my question>

Default Gateway - 

Multicast -  Disabled

VLAN - 20?


Then, I create my other interfaces.

Name - Voice

Subnet -

Interface IP -

VLAN - 60

Multicast - Disabled

Client addressing - Relay to another Server

DHCP Server IPs -



I may have answered my own question typing this out. lol

Creating the initial default gateway also creates the interface for my vlan 20 (with IP 1010.20.1), correct? Then I don't need to create vlan20 in later steps. 

Kind of a big deal
Kind of a big deal

Interface IP - <This is my question>  I supose you mean but thats currently in use at your core.


That is a ip thats not in subnet





To start using layer 3 routing, navigate to the switch details page by going to Switch > Monitor > Switches and clicking on the switch to be configured. Under Status > L3 routing status, click Configure layer 3 settings.



The window that appears will allow the configuring of the first routed interface and a default route. It is recommended that the uplink VLAN be configured first


The default route will be pointing to the default gateway adress of you first interface




Ugh, yeah, my bad.  I meant  Yes, that is currently in use at my core. Thanks.


Okay, so that confirms my understanding. I see where it says that now in the documentation.  Guess I glazed over that.



Next question is a chicken/egg situation.


If I configure the interfaces on the Meraki stack while online, there will be IP conflicts with the existing Cisco stack.  I can configure them offline, but then if I take the Cisco stack out and replace it with the Meraki, it will not be able to get to the cloud to update the config since the Cisco is the gateway.


I suppose at cutover time I bring the Meraki online, let them update the config and have conflicts, then take the Cisco stack down and make the change over. Right?

Kind of a big deal

I'm not familiar with MS390, but with all the other MS switches ...


The ultimate default gateway is usually a firewall or some path to the Internet.  You need to put the switch management IP addresses all in this same VLAN, and the default route for them needs to point to that firewall.  They CAN NOT point to any L3 interface on the switch itself.  The switch management system does not use the primary routing table.

As you mentioned, it won't be able to get its config as it would need its config to get to the Internet.


Then you create the layer 3 interfaces.  These are separate different IP addresses from the management interfaces.  And these have their own [primary] routing table.


Whether this also applies to the MS390 I don't know.

@PhilipDAth so are we putting the same gateway for all of the interfaces?


e.g. I have 10 x VLANs I need to create but the switches will be getting their internet access from an ISP router.

Do I point them all to the router?



Kind of a big deal

For the switch management - yes.

Thank you.

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