Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About HDupuis
Community Record
9
Posts
0
Kudos
0
Solutions
Badges
Aug 30 2023
11:46 AM
I finally got it to work. I had a typo in the static routes. However, I had to connect a VLAN1 direct link between the MXes in order for the MX64 to see the devices in the 10.3.0.0/24 range (red square in picture) Here is the final diagram. I'm sure there are optimizations to be done however this design seem to work so far.
... View more
Aug 30 2023
10:14 AM
I tried it this morning, like this: I was able to sucessfully ping 10.0.3.1 from the server, but not from PC2 to 10.17.6.96. Is the design ok? I can redo a test.
... View more
Aug 30 2023
9:17 AM
Hi @GIdenJoe I checked the ARP on all devices and the entries were all present. I think I pinpointed the problem, I have an error showing in the switch as soon as I plug the VLAN 55 access link When I saw that, I disallowed the VLAN55 in the uplink (to prevent having 2 simultaneous links), that did not solve the problem. My conclusion is that this configuration creates a loop within the router (between the VLANs) and that there is no other solution than to migrate physically the end devices from on VLAN to the other. Is my understanding right?
... View more
Aug 29 2023
10:05 AM
Yes that's the case and yes I see the devices on the client tab.
... View more
Aug 29 2023
10:03 AM
I already have a Layer 2 switch (MS120). This configuration works already, what I am trying to avoid is to physically reconnect the devices to the switch. To answer your question, I have approximately 200 devices on the network.
... View more
Aug 29 2023
10:00 AM
Hi. So I tried this configuration, here how it goes: I ran a continuous ping to google.com on the server and PC2. It looks like they are fighting each other: When one PC2 gains connectivity the server loses it and so on. It goes flip-flopping like this forever. If I put the server port in the switch to Access VLAN 55, everything is fine, however I would like to avoid as this implies to physically reconnect devices to the right ports. Any ideas?
... View more
Aug 27 2023
8:06 AM
My bad, did not revise before posting. Here is the updated topology:
... View more
Aug 27 2023
6:35 AM
Thanks all for you answers. Yes I thought about swapping the new MX configured exactly like the other on a flat network, it does not solve the next step which is to gradually migrate the devices to the new subnet (10.17.6.0/24 ->10.3.0.0/23) @GIdenJoe That's exactly what I was trying to achieve yesterday, however, I wasn't using this port configuration (I tried almost everything BUT this), I ended up making loops (I presume) that would crash the whole network. I will try your configuration ASAP, and let you know: I summarize it as this, is my understanding ok? And no the MX84 isn't new, and I'm aware that at some point, lots of traffic will be going thru the temporary link. I'll let you know the results.
... View more
Aug 27 2023
12:37 AM
Hi, Long time lurker, first time poster. I’m managing a site where I need to decommission an old router and migrate to a new network. Here is the situation. The router to remove is a Cisco 800 that is not owned by our organisation. Since it’s not owned by us, we cannot modify its configuration. Here is the actual and desired situations: Actual: Cisco 800 No VLAN Subnet 10.17.6.0/24 GW: 10.17.6.30 Desired: Meraki MX84 VLAN 1 Subnet: 10.3.0.1/23 GW: 10.3.0.1 I want to do the migration gradually and ideally in production because there are many services that have hard coded IP addresses that I’m not necessarily aware of. In case one service fails, I want to be able to roll back that particular service to the old address instantly. I would also like to avoid to physically reconnect devices to specific ports as there are many unmanaged switches spread around the building. My first idea was to create a second gateway handled by the new router in the old range, to do the routing between subnets, as depicted below. However, I can’t figure out how to properly do the routing between subnets, as Meraki does not allow multiple subnets in the same VLAN. To circumvent this, I thought about putting a temporary router and put static routes between the two, without success. My 3 questions are: Is this the best way to do the migration? If so, how can I configure the routes between the 2 merakis? Would my life be easier if I had a layer 3 switch? Many thanks in advance.
... View more
© 2024 Cisco Systems, Inc.
