Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Closey1200
Community Record
5
Posts
0
Kudos
0
Solutions
Badges
Jul 25 2024
1:37 AM
Thank you GldenJoe, you've been very helpful with your responses. This now makes sense. Thanks again for your help and have a great day.
... View more
Jul 24 2024
6:13 AM
The .253 & .254 are part of a larger /24 subnet so no need to create a separate subnet on the firewall. All other switches have their management IP in this same subnet also, but their gateway is pointing to .254 So to be clear, this is all done whilst both connections are still in place. Would i put the management IP on the new core pointing to the .253 as its gateway? I can then start by removing the .254 SVI from the old switch and adding it to the new? Thanks,
... View more
Jul 24 2024
2:14 AM
Hi GIdenJoe. Thank you for your detailed response. I truly appreciate the clarity you've provided. I'd like to offer some additional context about our current setup to give you a more comprehensive view of our goals. This should help us refine our approach and ensure we're on the right path. I apologize if this leads to any repetition from your previous answers, but I want to make sure I fully understand the situation. Here’s a simplified version of our topology… As mentioned earlier, our plan is to replace the old Catalyst 3560 switch and designate the Meraki MS250 as the core switch in stack 1, handling all IP routing and inter-VLAN routing. Our goal is to replicate the functionality of the Catalyst 3560 as closely as possible with the MS250. Since Meraki devices don't use a CLI, I'm trying to understand the first steps for configuring the MS250 with all the necessary SVIs and routing. Should I first disconnect the Catalyst 3560 and connect directly to the MS250 via its configuration port? Then, do I assign it an IP address that allows for internet connectivity to bring the switch online in the Meraki Dashboard? After connecting the firewall link to the switch, can I proceed with the configuration through the dashboard? I'm just a bit unsure about this initial setup phase. Please be aware downtime for a few hours is ok. Many Thanks.
... View more
Jul 22 2024
12:34 PM
Noted! I’ll give this a try. Thank you Darren
... View more
Jul 22 2024
5:35 AM
Hi All, Real apologies for such a noob question, but here goes.... in our small office environment we have a very old Catalyst 3560 acting as a layer 3 core switch with a few SVI's set up for each subnet (doing all our inter-vlan'ing) and some static routes. This is directly connected to our firewall. We've recently been slowly upgrading everything below the 3560 with our new MS250 and MS225's switches in layer 2 distribution/access setup in preparation. The plan over one weekend is to unplug the old 3560 and to make the MS250 as the new layer 3 core switch replicating all rules etc from the old switch..... Silly question time... how am i supposed to configure the MS250 as a layer 3 creating the same settings once we've unplugged the 3560, can i still get onto the cloud and configure the 250 if i statically assign the management IP in the same subnet as the firewall and connect the old wired connection into the new switch? Once I'm on the switch with all the settings at my disposal i should be ok, its just that first initial bit. I've looked at the local settings page (http://switch.meraki.com/) but this seems restricted to just a small subset of options. Hope that makes sense. 🙃
... View more
Labels:
- Labels:
-
Layer 3
© 2024 Cisco Systems, Inc.
