Meraki Community

SuperDanza · ‎Apr 18 2024

That's a fine thought. I can work anytime after midnight. We are a small community and it's pretty quiet at night. I can keep a 3750 trunked back to the core that keeps key connections up while I rip out the rest of the switches. Downtime would be minimal. It's the core that concerns me. Thinking about it I can replace three of the distribution switches in that stack ahead of time and just have to deal with replacing the remaining layer 3 switch with the layer 2 MS410. I am probably making this more complicated in my head than it is. But measure 15 times, cut once...

SuperDanza · ‎Apr 18 2024

Thank you for verifying the routing question. Doing a rip and replace was my original plan. However this work involved a police department and downtime needs to be kept at a minimum. I also had a flashback of being 8 years old and taking my sound effects machine apart and then sitting on the floor looking at all of the pieces forgetting how it all went together. On paper this is a very simple network. My plan is to replace the edge switches, including the five at the PD, and then do a rip/replace of the Core stack on a Friday night. I appreciate the time you took to read and comment on my post. I feel better moving forward with this plan. Thank you.

SuperDanza · ‎Apr 18 2024

Hello, I recently asked a question about connecting MS210s to my existing Cisco 3750 network. Thanks to the support here I was able to successfully add six of those switches to my network. The next step for me is to figure out what steps to take to replace my 3750 core. The core is running EIGRP but that is a legacy configuration due to some old T1 and T3 links to sites. Everything is now connected via layer 2 point to point fiber. There is no routing on the far end sites. Just 3750 switches running at layer 2. I am thinking that I really can exist in a layer 2 world going forward. Here is what my network is going to look like: The VLANs exist for management purposes. There are some cases where I need ACLs to prevent a VLAN from accessing another VLAN. That seems pretty straightforward. My questions are: 1. Can I really exist in the layer 2 world with no routing. My network is a true hub/spoke with all far end connections landing on the MS410. Do I need routing? I set this up in a lab and was able to ping from VLAN to VLAN. configure ACLs to limit traffic to certain VLANs and all VLANs were able to access the internet. 2. As asked in the previous post, my plan is to do a shutdown on VLAN 110 on the 3750 stack and then configure that VLAN on the MS410. I am expecting some traffic issues while the new route is learned. I will repeat the steps for the rest of the VLANS. I tested this in a lab with only a few machines and it worked. But lab and real world are two different animals. 3. 192.168.0.1 is currently an old Cisco 2611. This equipment was in service when there were T1 and T3 serial connections. The ONLY work it is doing now is serving as the gateway for VLAN 1. This address is the VLAN 1 address of the MS410. I am thinking I can just disconnect the 2611, connect the MS410 and traffic to 192.168.0.1 will eventually route through the MS410. I can clear the arp cache on the 3750 core to speed things up. THIS WILL NEED TO BE THE FIRST THING I DO WHEN I INTRODUCE THE MS410 TO THE NETWORK. I can move the other connections over time. I still have about 15 more switches to deploy and then I am ready to cutover. I am looking for any input that would be helpful. As I stated, the last post got my MS210s integrated with the Catalysts (pruning VLANS! Yes! Thank you!). My next step is to remove the 3750 core, replacing it with the MS410. Thanks in advance!! I am sure I have missed something 🙂 (And I know there is no link to my WatchGuard Access Points - I know I need one, just threw the drawing together quickly. They will connect to MS210s trunked with a native VLAN of 110 and allowed 110 and 85)

SuperDanza · ‎Apr 3 2024

Thank you for responding and for that information. One question - is this in reference to the MS210 access switches, the MS410 layer 3 switch or just in general for all switches? I am still kicking around the best path forward here. Thankfully I have maintenance windows on Sundays. I am seeing that the first thing I need to address is vlan1. On my MS410 the gateway is 192.168.0.1. That address also exists on a legacy Cisco 2611. I am thinking I can trunk the MS410 to my 3750 stack and shutdown interface on the 2611, which is configured as follows: interface FastEthernet0/0 description connected to EthernetLAN ip address 192.168.0.1 255.255.255.0 duplex auto speed auto no mop enabled The MS410 *should* then route traffic for 192.168.0.1 to the next hop which is the WatchGuard. The WG will either route the traffic to the internet or back to the 3750 core stack which is configured as follows: interface Vlan1 ip address 192.168.253.1 255.255.255.0 secondary ip address 192.168.0.243 255.255.255.0 192.168.0.243 is the next hop back to the network from the WG. Once all of this is done, the hop back to the internal network will be 192.168.0.1 on the WG. I don't see where I can have a secondary interface on vlan1 on the Meraki. I have inherited a bit of a mess due to the legacy routed network that was never cleaned up. The network now is flat. All remote sites are connected via fiber to the core. There are ACLs in place to prevent public traffic (library and community center wifi) from seeing private, but everything else is wide open between subnets. I appreciate the time you took to respond to this 🙂

SuperDanza · ‎Apr 2 2024

Thank you for your reply. The spanning tree info is helpful. I am going to have to draw this solution out to make sure I don't introduce any issues. I have the MS410 and five MS210s in a lab connected to a VMWare server with copies of the Domain Controllers/DHCP and DNS servers with a WatchGuard firewall as the gateway on a separate WAN link. Everything works. What I don't have is a 3750 with the routing protocols in the middle. What I might do is remove all VLANS from the MS410 and put the MS410 in production and trunk it to the 3750 stack. Create a new VLAN on the 3750 stack, trunk it to a MS210, test connectivity and then create that VLAN on the MS410 (shutting down the VLAN on the 3750) and move that MS210 link to the MS410 and see what happens. I need to keep an eye out for IP address conflicts. But that seems like a good production test. I'd rather spend some time on the front end rather than rip/replace and run out of time because I missed something. I'll be glad when this is done.

SuperDanza · ‎Apr 2 2024

Hello, I have been tasked with replacing a Cisco 3750 core stack and 22 access switches with Meraki MS gear. In my inventory I have a MS410 to handle the layer 3 traffic and 21 MS210 access layer switches. We are a hub and spoke environment with all remote sites landing on the 3750 stack. We have 12 VLANs with all gateway addresses handled by the 3750 stack. There are some odd configurations that are left over from some legacy T1 links (such as the vlan1 gateway existing on a Cisco 2611 router) and EIGRP AND OSPF running on the 3750 stack. We really don't have a need for IP routing protocols as all sites are direct connected to the 3750 (soon to be replaced by the MS410). All traffic reaches the internet through a WatchGuard firewall. My thought is to one by one shutdown the vlan interface for each remote site on the 3750 stack and move the physical connection for that site to the MS410. The MS410 will be trunked to the 3750. The remote sites will have to learn a new route (I think/guess). If I can keep downtime to less than five minutes per site that would be ideal. If this isn't going to work, my plan is to replace the far end 3750 access switches with the MS210s, trunked to the 3750 core, and then do a rip and replace of that core over a weekend. We are a small local government with five sites and about 250 endpoints. This seems like it should be rather easy to do. But I've been doing this long enough to know that easy is a four letter word. I am looking for suggestions, warnings, etc. Thanks in advance.

Meraki Community

About SuperDanza

SuperDanza

Community Record

Badges

Re: Network Topology

Re: Network Topology

Network Topology

Re: Steps To Replace Cisco 3750 Environment

Re: Steps To Replace Cisco 3750 Environment

Steps To Replace Cisco 3750 Environment

Re: Network Topology

Re: Network Topology