Hey all, Here's my most recent experience with adding a new switch member to an existing stack. In my case, I added a MS210 to a switch stack in production. The switches were running the 12.x firmware and I followed these steps: Claimed new switch in Meraki Org Powered on new switch with an ethernet uplink inserted Made sure it checked into the Meraki dashboard and upgraded to the same firmware version as existing switch stack Powered off new switch member Broke the existing stack ring and re-cabled with new switch member Powered on new switch Once the new switch regain cloud connectivity, I manually added the switch to the stack, and I was done During my experience, I saw ~3 dropped ping packets when the new switch first powered on with the stack cables installed. I am sure everyones' experience is a little different depending on hardware models and firmware versions, but mine was very positive.
... View more
Hello all, I had a question regarding the default routing behavior of a MX. I have an environment where I would like to advertise the same subnet from two different VPN hubs. Hub 1 will act as the primary route to the network (10.150.0.0/16). Hub 2 will provide a backup route in an event where A) the 10.150.0.0/16 resource becomes unavailable or B) Hub 1 goes offline. Both Hubs advertise a local static route for the 10.150.0.0/16 into AutoVPN with route tracking enabled. In setting this up in an lab environment, I notice that with route tracking enabled Hub 1 continues to advertise the static route into AutoVPN. The two spokes continue to send their traffic destined to 10.150.0.0/16 to Hub 1 as a result. Hub 1 receives the packet, decrements the TTL on the IP packet, and then forwards it onto to Hub 2. My question for you all is this a routing behavior that we should expect to see in this type of scenario?
... View more