12-07-2023 05:48 AM
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?
Solved! Go to Solution.
12-15-2023 08:01 AM
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.
12-07-2023 06:25 AM
One question, is it possible to share a topology with us? Just to check other possibilities.
12-07-2023 06:47 AM
One small detail, you need to tag the VLANs in the trunk. I believe you did this correctly?
12-07-2023 08:48 AM
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?
12-07-2023 08:51 AM
Hi,
I'm talking about tag the VLAN on trunk port between MX and the MS(Allowed VLANs).
12-07-2023 10:02 AM
Understood. Here is the configuration of the port that connects the switch to the MX.
12-07-2023 10:06 AM
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.
12-15-2023 08:01 AM
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.
12-13-2023 03:30 PM
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide