Per Port VLAN Settings

Solved
drestle
Conversationalist

Per Port VLAN Settings

We have VLANs 1 and 21 configured on our network. The MX runs DHCP for VLAN 1 (192.168.1.1/24) and a Windows server runs DHCP for VLAN 21 (221.21.21.1/24). Our switches are downstream port 3 on the MX which is configured to trunk with a native VLAN of 21.

 

Our end goal is to migrate all clients to the VLAN 1 subnet. We would like to do this incrementally if possible. When configuring a switch port with settings for VLAN 1, the connected client is not able to get an IP address on the 192.168.1.1/24 network even if the IP settings are statically configured on the device. The only method I found for devices to get IP addresses on VLAN 1 would be to update the native VLAN on the MX port to 1, but that migrates the entire switch to VLAN 1 which is not what we want.

 

Is what we are trying to accomplish possible and what would the best method be for migrating devices connected to individual switch ports to this subnet?

1 Accepted Solution

Hello. I was not able to get this functional even after working with support. My resolution ended up being to configure one switch for VLAN 1 and the other for VLAN 21. Then move devices from VLAN 21 to 1 by physically moving the cables over one at a time as needed. Thank you for your assistance.

View solution in original post

8 Replies 8
alemabrahao
Kind of a big deal
Kind of a big deal

One question, is it possible to share a topology with us? Just to check other possibilities.

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.
alemabrahao
Kind of a big deal
Kind of a big deal

One small detail, you need to tag the VLANs in the trunk. I believe you did this correctly?

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.

Good question. I am not sure if I need to be adding tags in the port settings. I did try it with and without the tag and got the same results. Or is there another way I should be tagging traffic?

 

Tags.png

alemabrahao
Kind of a big deal
Kind of a big deal

Hi,

 

I'm talking about tag the VLAN on trunk port between MX and the MS(Allowed VLANs).

alemabrahao_0-1701967875168.png

 

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.

Understood. Here is the configuration of the port that connects the switch to the MX.

 

Uplink.png

alemabrahao
Kind of a big deal
Kind of a big deal

What about the switch? Apparently everything is ok, so I don't see any configuration problems on the MX side, even if you put a native VLAN as 21.

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.

Hello. I was not able to get this functional even after working with support. My resolution ended up being to configure one switch for VLAN 1 and the other for VLAN 21. Then move devices from VLAN 21 to 1 by physically moving the cables over one at a time as needed. Thank you for your assistance.

cmr
Kind of a big deal
Kind of a big deal

As an aside, it would be better not to move everything to VLAN 1, at least pick a different number and secondly you would be better not using 192.168.1.0/24 as that is the most common home network.  Ideally pick something in the 172.x.x.x private ranges, or the 10.x.x.x ranges.

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.