We're have a Meraki mx64 connected to a cellular network. We have a best effort LTE service that may itself have bandwidth congestion. Behind the Meraki, we have priority users (the bill payer) and regular users. Let's say we have a 10M down, 5M up service. I'm mainly interested in prioritizing who gets bandwidth in bound from the non-vpn Internet. I suspect the primary application that's in contention is Netflix. Rules are in place. I don't believe that the people that wrote these rules really understand what they're getting and neither am I. Can someone clarify? Wan 1 is set with 10 dn X 5up. Per client limit is 5M We have three rules 1. Priority user vlan gets ignore network per client limit ie unlimited and high priority 2. Regular user vlan gets obey network per client limit ie 5dnX5up and normal priority 3. Video, music, and p2p get 2M limit with low priority 1 First regular and priority users are both running Netflix. Is that rule 3 or rules 1 and 2? 2 Just considering rule 1, with no contention, priority users get 10M per client up to 10M total, right? 3 Just considering rule 2, with no contention, regular users get 5M per client up to 10M total, right? 4 With contention between rules 1&2, priority clients get 4/7*10M or 5.7M in total right? 5 With contention between rules 1&2, regular clients get 2/7*10M or 2.9M in total right? 6 video, music, and P2P get 2M total and up to 1/7*10 or 1.4M in contention right? 7 Is rule three a per client limit or a total limit?
... View more
I want to use WAN1 and WAN2 with separate LTE radios. The purpose is that the two LTE APNs are set up for different class of service, guaranteed vs best effort. We've been using two Meraki's and two radios, I want to use just one Meraki with two WAN ports. The problem is that if WAN2 fails, it looks like all the traffic goes over WAN1. Then when WAN2 comes back up, it looks like flows that got mapped to WAN1 during the failure stay mapped to WAN1, even though WAN2 has come back up. Neither of those traits are very desirable for my application. If WAN2 goes down, I really don't think I want it to failover. It might be OK, but if it does failover, I definitely don't want it to stay mapped to WAN1 indefinitely. This is a corporate type connection on WAN1 and personal use on WAN2. It might be ok to flood Netflix users on to the corporate link during an outage, although probably not. If WAN2 comes back up, definitely not. Can anyone clarify that yes indeed flows already mapped to WAN1 won't route back after the failure? Is there any other means to accomplish what I want?
... View more