Hi Everyone,
We have a hub and spoke WAN. I am doing a full conversion over to Meraki with a combination of 425s, 350s and 225s.
A 425 stack is installed at the “hub” and is basically the core of the network. The 425 stack connects to our firewalls via a trunk. The management IPs of the 425s are in the 172.20.254.0/24 network and the gateway of this vlan is the IP of the firewall. The 350s are the core of the “spoke” and will connect to our 425s via a trunk and ospf will be enabled on both the 425s and 350s. I have a transit vlan setup on both the 425s and the 350s that will be used for ospf.
I am having a problem with the management IPs on the 350s. It appears that the only way the 350s can get out to the internet is if they get an IP from the 172.20.254.0/24 network. I would like the 350s to get an IP from the 172.19.254.0/24 network that is defined on the 350s. That second octet is how I define what building the devices are in. Is it possible to set up the management IPs on the 350s this way?
Thanks for your help.
Meraki switches dont like to get a management ip from its own svi/vlan.
That gateway ip for that vlan should be on the ms425 or on the firewall and then l2 to the ms425-ms350
Upvote for @ww . Meraki switches don’t respond well when the mgmt vlan resides on itself. Learnt this the hard way.
Youll have to use an upstream device.
I will add that this is noted in the documentation:
With Meraki you have an organisation that is subdivided into networks. If you use the networks as sites or buildings then you don't need to worry about IP ranges to know where a switch is.
For example an alert for one of our switches would say something like:
The following settings have changed on the sitename - switch network.
@mcbrown a few answers: