we have the following design.
VLAN 1 subnet 10.150.0.0/22
MS350 STACK With two switches
The switches are getting an DHCP lease from a DHCP server on VLAN1
Switch A 10.150.2.105 with Gateway 10.150.0.2
Switch B 10.150.2.106 with Gateway 10.150.0.2
The stack is also configured in DHCP & ROUTING
DHCP Settings: Off
OSPF Routing: Disabled
Multicast routing: Disabled
Also configured an static route
Name: default route
next hop ip: 10.150.0.1 (router to the internet)
In this situation the switches are not able to communicate to the cloud, and try to find a path over other configured vlan id.
I create a work-around for ( in my opinion ) this BUG
I found out that the switch was able to get an address but not able to route over the virtual interface (10.150.0.2) and follow the configured default route.
I created an reservation on the DHCP server and configured 10.150.0.1 as the router in this reservation.
possible to create a static IP configuration for this switch management address also with the 10.150.0.1 as gateway.
just use the gateway .1
when you have new switches or factory reset they dont have any vlan and routing configuration so it would not be able to contact the cloud.
you say this is a bug but what device has the 10.150.0.2 ip? (you say virtual ip?)
Is this the L3 interface?
Do you have a VLAN to route traffic back and forth between your firewall and switch stack?
And you can test your config by connecting a computer directly to the cable that is currently connected to the switch and setting it up with the same IP information to make sure you can ping the gateway and get to the internet. One thing worth mentioning is that the management IP really just needs to be an IP that the switches can use to get to the internet.
The device holding the 10.150.0.2 is the corestack interface for vlan 1
the two switches are member of this stack
This will work as other switches are also able to do this.
only the two switches in the same stack as the virtual interface are not able to do this.
The rest of the network is healthy.
here another topic relating to this with some info. https://community.meraki.com/t5/Switching/Management-VLAN/m-p/19025#M1520
you could make a support case and give it a try.
what is the reason you want to route to its own vlan?