@kevinl wrote: @Adam, curious about the exact mechanism that you use for the per-VLAN traffic shaping. Is that done by Group Policies, and Bandwidth -> Custom Bandwidth Limit? Then you use the Addressing & VLANs page on the MX to tie each VLAN to the relevant Group Policy? (I was thinking this might be a good answer to clients who complain that unlike classic Cisco Cats, the MS series switches do not have built-in bandwidth limiters so they can't shape bandwidth to what the tenant has paid for) Thanks, Kevin Hey Kevin, Here is the exact steps we use to setup a new tenant. 1. Security Appliance>Addressing & VLANs and we setup a /24 VLAN. For simplicity I try to make the third octet match the VLAN number. Example 10.17.2.0/24 for VLAN 2. MX IP 10.17.2.1 2. Security Appliance>DHCP, I turn on DHCP and I usually set .1-.50 as reserved so they could assign any static IPs they need. 3. Security Appliance>Firewall, I setup rules to block their subnet from talking to any other tenants. You can supernet this depending on how your subnets are configured 4. Security Appliance>Traffic Shaping, I setup a traffic shaping rule to limit their subnet to the bandwidth they subscribed to. You can do this by setting custom expression "localnet:10.17.2.0/24" without the quotes and then specify the bandwidth We now have Meraki APs in the building so next I go to Wireless>SSIDs and I configure an SSID and do bridge mode and tag it with their VLAN. Lastly I setup a physical port on the switch as access VLAN x. This is the port going to their tenant suite(s). From there they can connect a switch and hookup whatever ports needed and they'll get DHCP from the MX.
... View more