Do I need to enable inter-VLAN routing on Catalyst 9200L?

[JamesEdmondsAspall]

Hi,

I am using a 9200L stack as our main root switch in a small network.

I know that DNA Essentials license provides some basic L3 functionality including inter-VLAN routing, but I am wondering if I need to do anything to enable this, or if I simply need to create the SVIs on each VLAN?

Do I perhaps also need to add routes for each VLAN subnet pointing to the appropriate SVI IP address?

Additionally, can I do any control over what VLANs can/cannot access each other, or will it only do "Allow All"?

Thanks

James

[Reza Sharifi · Accepted solution]

Hi,

If you already have the license, then you simply create the SVI you need.

config t

interface vlan x

ip address x.x.x.x

Also, you don't need to do anything besides enabling "ip routing" on the switch for SVIs to communicate with each other(inter-vlan routing). If you want to block communication between SVIs, you would need to use ACLs.

HTH

[Joseph W. Doherty]

In addition to what Reza already noted, don't forget your VLAN hosts, generally, should have their VLAN's SVI's IP configured as their gateway IP.  (Also, if using DHCP, exclude the VLAN's SVI from the allocation pool.)

I don't know the routing restrictions, if any, for a 9200L switch, but often such "low end" switches are sold for, mostly, for L2 usage.  I.e. L3 features, like routing, can be very limited.

If you need to route to other devices, then you'll need to also configure static route statements and/or a dynamic routing protocol.  (Again, such is where something like a 9200L might have very limited features.)  For routing, on the same switch, between VLANs, and their SVIs defined on the switch, it's as simple as Reza described.

[JamesEdmondsAspall]

Thanks guys.

We are quite budget restricted, as I'd love to have gone with a 9300 series for some more oomph/features, but at the moment the actual network requirements are pretty simple.

We have a small handful of VLANs, so only want to allow some communication between them, and then we will have one static route for internet access pointing to a Meraki firewall.

Noted on points around gateways and DHCP, and these are on my lists of items to sort when deploying

I'll enable ip routing to do what I need, then investigate ACL setup.

Thanks very much!

James

[Reza Sharifi]

Good Luck, James!

[JamesEdmondsAspall]

Appreciate it!

You guys in this forum are acting as my mini CCNA tutors haha!