L3 Routing Setup on MS and Catalyst Switches

pBrain
Here to help

L3 Routing Setup on MS and Catalyst Switches

When setting up L3 routing on MS / Catalyst (Meraki) Switches with an MX, I am setting up 2 SVI's on the switch to start.

 

1 NET Management SVI for Management and 1 TRANSIT SVI for Inter VLAN Traffic and communicating with the Uplink MX.

 

Which of these two SVI's should be set up as the "Default Uplink"?

11 Replies 11
RWelch
Kind of a big deal
Kind of a big deal

The transit VLAN.

MS Layer 3 Switching and Routing 

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
pBrain
Here to help

Thanks.  I am running into an issue where my L3 switches are displaying their IP addresses from the transit VLAN, and not from the management VLAN.


Is this by design?

RWelch
Kind of a big deal
Kind of a big deal

Here are a couple of other reference documents if interested with L3 setups.

Layer 3 Switch Example 

Hybrid Campus LAN Design Guide (CVD) 

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
RWelch
Kind of a big deal
Kind of a big deal

The Hybrid Campus LAN Design Guide (CVD) has two design options for your consideration:

Design and Configuration Guidelines

Option 1 -  STP Based Convergence with Native VLAN 1

Option 2 -  STP Based Convergence without Native VLAN 1

I typically choose to use Option 2 when deploying L3 interfaces but both options are there for your consideration.

I am running MS425s and keep the MTU at 9394 so your default MTU of 9198 should be ok.

 

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
pBrain
Here to help

Also, the document states, "SVI MTU size is 1500".  Does this mean that I have to set the MTU for that whole L3 switch to 1500?  Currently our switches have a default MTU of 9198.

alemabrahao
Kind of a big deal
Kind of a big deal

When creating the first IPv4 interface on a switch, you will be prompted to enter a default gateway address. This is the next hop IPv4 address of another device on the network, used for any traffic that isn't going to a directly connected subnet or over a static route. This IP address must exist in a subnet with a L3 interface, and will be used for the default route next hop IP address.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
pBrain
Here to help

The reason I bring this up is because I have a Network management VLAN, that all other switches get their IP addresses from, but the core l3 switches are using the TRANSIT VLAN SVI IP Address instead.

 

I read somewhere that in the Meraki ecosystem, the management and transit VLAN's must be different.  Is that still the case?

alemabrahao
Kind of a big deal
Kind of a big deal

Can you share the document?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
pBrain
Here to help

While watching some Youtube videos on the subject and reading through the community posts.  This one in particular:

 

Solved: Separate VLAN for Transit VLAN versus Meraki Core switches management inte... - The Meraki C...

alemabrahao
Kind of a big deal
Kind of a big deal

Yes, that statement is correct.

 

You should use a VLAN that is not the default gateway for management.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
pBrain
Here to help

It's odd, because on one of the switch stacks, it takes the transit VLAN as the switch IP address, but on all the others it uses the Net Management VLAN.

Get notified when there are additional replies to this discussion.