Administration network VLAN 1

Solved
GaelGiraud
Comes here often

Administration network VLAN 1

Hi,

I have a question regarding the equipment management network and potential interference with Layer 3 of the switching infrastructure.

At Site 1, I have an MX server that broadcasts DHCP on VLAN 1. It uses a 4G network.

This internet access is solely for retrieving configurations from Cisco Meraki.

Connected to this MX server is a Catalyst C9300-24Y that retrieves its configuration via the 4G network.

This Catalyst is also connected via a dark fiber cable to a second Catalyst server located 2 km away.

 

Site 2 is the main site, and Site 1 is a new extension.

On the Catalyst at Site 1, I created five Layer 3 interfaces, and I would like the default route for all these interfaces to go to the Catalyst at Site 2 while still retrieving configurations via 4G internet.

Eventually, I plan to upgrade these Catalysts and use the routed IOS ports. VLAN 1 does not flow between Sites 1 and 2.

 

Can I configure the default route of the switching section at Site 1 to the Catalyst at Site 2 without losing access to VLAN 1 so I can continue to manage my equipment at Site 1 in the dashboard?

 

To summarize, all my business traffic goes to the Catalyst at Site 2, and dashboard traffic continues to be routed to VLAN 1 as advertised by the MX record.

 

Best regards,

 

Gael

1 Accepted Solution
alemabrahao
Kind of a big deal
Kind of a big deal

Yes, you can configure the Catalyst at Site1 to have a default route pointing to the Catalyst at Site2, keeping VLAN1 local and never forwarding it over dark fiber.

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.

View solution in original post

2 Replies 2
alemabrahao
Kind of a big deal
Kind of a big deal

  • Default gateway: When creating the first IPv4 interface on a switch, you will be prompted to enter a default gateway address. This is the next hop IPv4 address of another device on the network, used for any traffic that isn't going to a directly connected subnet or over a static route. This IP address must exist in a subnet with a L3 interface, and will be used for the default route next hop IP address.

 

https://documentation.meraki.com/Switching/MS_-_Switches/Design_and_Configure/Configuration_Guides/L...

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

Yes, you can configure the Catalyst at Site1 to have a default route pointing to the Catalyst at Site2, keeping VLAN1 local and never forwarding it over dark fiber.

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.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.
Labels