Do both stacks use the same vlan to uplink to the MX? What is you MX and MS version? ... View more

It sounds like it. What % of available bandwidth were you allowing to use multicast on the storm control settings? ... View more

@MRCUR- I had stacking issues with my MS350's. The root cause was just a simple nmap scan. I wonder if a device on your network is running some type of scan that is overwhelming the cpu??? I took my MS350 stacks to 10.14 a few weeks ago and that did resolve my issue, hopefully the 10.x train will do the same for you. ... View more

@AbhilashRN@MRCUR   I seem to have run into this same issue.   I want to make sure that i am understanding this correctly. I have a couple questions.   1. Before I start the vMX deployment i need to create a RG and a Vnet? 2. Your step 3 ) At this point select that Vnet. What about the subnet? Does that also need to be pre-created or can that be done during the deployment? Or do i just leave that as default? 3. If i want to have the vmX in a /24, but I also want several other /24's available for VM's how do I accomplish that?   Very new to Azure, any help would be greatly appreciated.     ... View more

Unfortunately 9.27 has not resolved the stacking issue I am having.    OSPF goes up then down and switches in the stack without their own uplink can fall out of stack.    I have a maintenance window scheduled for this weekend and will engage support so hopefully they can see this issue happen in real time.  ... View more

What version of firmware are you on?    I'm taking my entire environment to 9.27 this weekend.  ... View more

I have been on 9.26 for a few weeks now, I have had one issue.    The building had a power outage taking my 3 MS350 stacks down. 2 of the stacks came up without issue, 1 of the stacks had 2 switches that didn't join the stack. That stack had to be rebooted manually and then all switches came up in the stack.    I will be upgrading to 9.27 in the near future.      ... View more

It sounds like you need to turn the Auto VPN on at HQ and B5.    Then from the HQ location you need to advertise all networks you want to be reachable over the VPN. B5 will then route traffic destined to those networks to HQ and HQ will route them to the final destination.      ... View more

I think you can only use configuration sync if each network is a FW only site.    So any networks that are "combined networks" I don't believe you can use config synch tool.    I have ran into this issue in the past, and support was pushing my towards templates. But templates also have some unique challenges.  I got the impression that the config sync tool may be on the way out and they are focusing resources on templates.  ... View more

@BrandonN     Definitely wish the devices would show uptime!!!!   I search the logs for power supply inserted. That message appears upon bootup, so if I see that I know the switches rebooted.  ... View more

@JasonSnyder   I haven't used NAT mode yet, but one thing you probably want to test/check.    Does each AP create a separate NAT Network.    AP1 192.168.1.0/24 AP2 192.168.2.0/24 AP3 192.168.3.0/24   If that is what happens, roaming could get really ugly, because each roam will require the client to get a new IP and my guess is clients would be unhappy.    I'm not sure if it works that way or not, but probably worth testing before deploying.  ... View more

Upgrade is completed, ended up going to beta 9.26 instead of candidate release 9.19.    The tech I talked to tonight said that if you are below 9.2 and going to 9.19 then have had stacked switches hang, but that issue was fixed in 9.25, 9.26 has since been released to he advised to go to that to avoid any of the issues of the switches locking up.    When I started the upgrade all switches started flashing white on the front while they were downloading the image. After about 35 minutes of that they rebooted, the reboot was quick I would say the stacks were back up and passing traffic in about 3 minutes.    I hadn't seen this before, but I was able to watch the upgrade process until reboot on the http status page. I got a little nervous when for about 20-25 minutes all of the switches were hung at 66%. But eventually they jumped to 100% and rebooted.    I guess the real test will be over the next few days.  ... View more

Are you running NAT mode or concentrator?    How many remote sites do you have VPN'd in though the MX600?  ... View more

I haven't but I'm waiting from them to release the vMX100 in the Azure cloud. ... View more

I believe it's all switches on 8.10.    But it sounded like it only effects switches in the stack that don't have there own uplink. So in my case, I have 3 stacks of 6 switches, each stack has 2 switches with uplinks. The other 4 switches in the stacks don't have there own uplink, it only seems to affect the switches without uplinks.    They also mentioned that in general there are a lot of stacking bugs on 8.10.    One of the bugs is actually upgrading the switches! So instead of just scheduling the upgrade they have a very specific process they want me to follow for this upgrade.    1. Power down all but the primary uplink switch 2. Run the upgrade on the one powered on switch 3. boot up the remaining switches, I'm not sure if they meant all at once or one at a time.    But they mentioned they have had lots of issues when upgrading off 8.10 with stacked switches.      ... View more

We at testing with cradlepoint and so far it's going really well.    Had active VOIP calls running over VPN and failed over to the Verizon 4G and the calls stayed active, it was pretty impressive.    https://cradlepoint.com/products/arc-cba850     ... View more

During my initial troubles with stacks I also had that same realization. And you are right, it felt very strange to run switches without static IP's. But I figured it works with dhcp's and because I am not SSH'ing into switches and they just need internet access it doesn't really matter if they are static. So since then I have been deploying all my MS switches stacks or not using DHCP.    A couple things that have made me nervous with this are DHCP snooping, and if our DHCP server has any issues, but so far so good.    ... View more

@Dave@NFL0NR @BHC_RESORTS   Ok so today again I had the some of the switches fall out of the stacks, but I think we have been able to track down the issue.    Our security team was running ping sweeps across our network. When the sweep got to the MS stack closets for some reason it took down the OSPF neighbor relationship from the MS 350's to the 9k's.    When the OSPF neighbors went down and then came up the MS switches hit a bug. Based on what Meraki support is saying there is a bug when the uplink goes down other switches in the stack fall over the stack.    Tonight I am upgrading to 9.19 and Meraki support believes the stacking bugs are fixed in this release.  ... View more

@BHC_RESORTSYeah talking about physical stacking.    Nothing in the logs, just all of a sudden certain switches were no longer seen as in the stacks.    We probably have 30+ stacks hanging off the 9k's the MS350's were the only ones that had any issues.   It did get me wondering if Meraki pushes out patches to switches outside of just standard firmware upgrades?????? ... View more

One of the other things I ran into when first stacking was realizing that all of the Meraki switches in the stack need there own MGT IP.    Coming from Cisco stacks, I always viewed a stack as 1 logical device with x physical switches.    Meraki doesn't seem to view it that way. With Meraki it seems to be 5 switches and 5 logical devices, they just happen to have  40Gbps (I think its 40) links between them, they are still 5 managed as 5 different devices. Yes they can share the same SVI's, routing table, etc but you manage each switch in the stack from its MGT IP.    A cisco stack would have 1 MGT IP for all 5 switches in a stack. In a Meraki stack all 5 switches will need there own MGT IP. The first time I stacked with Meraki this though me off and I had issues with that stack until I realized they all need MGT Ip's.        ... View more

Started a separate thread on this and then saw your post, but I think this is relevant here as well.    Version:1.0 StartHTML:000000234 EndHTML:000018730 StartFragment:000016376 EndFragment:000018569 StartSelection:000016605 EndSelection:000018553 SourceURL:https://community.meraki.com/t5/Switching/MS350-Stacking-Issues/m-p/528MS350 Stacking Issues - The Meraki Community MS350 Stacking Issues I have 3 MS350 stacks, 6 switches in each stack, running on 8.10 software.    All stacks have been up and running without issue for the past month or so. No changes have been made on the Meraki switches or the Cisco Nexus 9k's that are upstream.    This morning within an hour all 3 stacks had switches that removed themselves from the stack and stopped forwarding traffic.    Stack 1 - 1 switch disappeared from the stack and stopped forwarding traffic - Did not come online until after a reboot. Uplink port was not on this switch.    Stack 2 - 1 switch disappeared from the stack and stopped forwarding traffic - Did not come online until after a reboot. Uplink port was not on this switch.    Stack 3 - 5 of the switches disappeared from the stack - 1 of the uplinks was on one of the switches that disappeared from the stack. After rebooting the switch with the uplink the 5 switches rejoined the stack. 1 switch in this stack stayed online, that switch has an uplink to the core.    It seems really strange that 3 stacks had the same issue within an hour, Meraki support suggested we hit a bug (8.10) and have requested I upgrade to 9.19.    Has anyone else been having stacking issues?    I typically put in Cisco 4500's or 3850's and these are my first 3 MS350 stack closets. This obviously isn't giving me a very warm and fuzzy feeling to have a failure like this after a month or so.    Curious what other users experiences  have been when using MS350 stacks ??? ... View more