I believe the proper way to do this would be to put a splash page login on the SSID, and give your allowed clients a policy that allows them to bypass the splash page. ... View more

Hi @whistleblower, here’s my take on your questions based on experience. Happy for others to advise if they’ve had different outcomes.   1. Yes, local configuration overrides network-wide configuration, but I’ve never seen a warning message if the two don’t match. I’ve only seen warning messages if there is a communication issue with the Meraki cloud.   2. There is no automatic tagging for the management VLAN across the network. You have to get the traffic to/from the switch. Based on this I always find it easiest to have the management VLAN set as the native on all trunks that are uplinks.   3. Imagine the management address as an access port on the switch. It doesn’t care which VLAN it is, only if there in a path to a DHCP server on that VLAN. Since it’s an ‘access port’ it’s always untagged, whether it’s tagged or not on another port depends on that port’s configuration.   4. The definition of a safe configuration is a few paragraphs further up in that document, “Safe configuration means that ‘the device has connectivity to cloud and hasn't rebooted for 30 minutes following a configuration change.’ That is, the safe configuration is the last configuration the device received from the cloud that was not followed by a reboot within 30 minutes.” A ‘not safe configuration’ is just the reverse - I.e. one where no connectivity to the cloud has been achieved. ... View more

Hey Nedy, So just bring the switch online and add it to the dashboard network. Make sure you don't couple it to the other switch yet. Then wait until the switch has the same firmware as the other future stackmember. When that is done, power down both switches.  Cable them up (stack cables)  don't forget to cross them.  So stack port 1 on the first switch connects to stack port 2 on the second and vice versa. Then power them back up and wait a few minutes before going into the dashboard and then click in switch->switch stacks. In that menu you'll see possible stackmembers where both switches will be on one line and then just click provision and give the stack a name. Example:  first switch is SW-CORE1-01 and second switch is SW-CORE1-02 and then the stack is named SW-CORE1 ... View more

Sorry for my answer after a lot of days. Thank you for your help! ... View more

There could be any number of things that might constitute "poor cloud connectivity" so instead of pinging you with a bunch of questions (which might go slowly over an online forum) it might be fastest to open a case with Meraki Support.  They will be able to see if and how your MS350 switches are communicating with Dashboard. Are the M350 devices physically stacked, and if so, there is a specific sequence of steps, did you follow the correct procedure to create that stack?  Are the switches showing up in Dashboard at all with a green or amber status, or only as red offline?   It could be an upstream firewall issue for example, if you have a restrictive Internet firewall in the outbound direction, you'll need to make sure a handful of ports are allowed out (such as UDP/7351 for primary Dashboard communications) and you can see the full list in Dashboard by going to Help > Firewall Info.  If you are behind a web proxy, you may need to leverage the local status page via the MS350 management port to put in a proxy configuration.  In fact, you can connect into the management port and perhaps see if the local status page offers a clue about why it doesn't have full connectivity to Dashboard.   If you're brand new to this, and since it could be many things, might be fastest to work with Meraki Support, but let us know if we can also help.     ... View more

With switches all the packet forwarding is done by the silicon.  The CPU and memory are used by things like dynamic routing protocol updates, spanning tree calculations, and the like.   Unless you have at least 10,000 layer 3 routes in your network you probably don't have to worry about CPU or memory.   Throughput can be gauaged from the Network-Wide/Clients view.  If you are only using the Gigabit ports, then your maximum throughout would be 2 x 24 Gb/s, or 48Gb/s.  So if you don't see the graph getting close to this you don't have an issue. And even then, you could then consider using the 10Gbe ports for high traffic generators/sinks.   ... View more

Thank you! I think your answer is the best option for mi. Thank you! ... View more

Set the native vlan on Meraki side trunk to the VLAN you want the IP from. ... View more