You need to configure VLAN tagging in Dashboard (on the screen where you took the screenshot) as @PhilipDAth mentioned.    Your switch port config looks fine assuming you're using VLAN 55 for management and 20 for clients (once you configure this on the SSID).  ... View more

@bholmes12 I'll try to answer these as best I can from memory:   1) Before you deploy the vMX, you should have two resource groups. One of them should be for your servers, the other should only be for the vMX. You should also create the VNet you want the vMX to be in ahead of time and place this in the first resource group - NOT the RG that's only for the vMX.    2) Pick the VNet that is in the first RG. This will be the VNet that the vMX gets an IP from. I use a dedicated subnet in the VNet just for the vMX.    3) Add multiple subnets to the VNet. As an example, I use the 192.168.0.0/16 address space for my VNet. This is set on the "Address space" page under the VNet. Under the "Subnets" page, I then have multiple /24's defined (within the 192.168.X.X space). One of these I call vMX-Net and it is the /24 I use for the vMX and nothing else.    One other thing - when you create the route table for the vMX, you should create this in the RG that is only for the vMX. Don't create the route table in the RG you use for other servers. After you've deployed the vMX, don't add anything else to the vMX RG.  ... View more

This provides good instructions for Windows 7: https://documentation.meraki.com/MR/Encryption_and_Authentication/Configuring_Clients_for_802.1X_and_Meraki-hosted_RADIUS ... View more

This is a new issue that just started within a day or so.  ... View more

Ticket submission is definitely broken in Chrome.  ... View more

Until you have an order number for the trial, you can't add demo devices to Dashboard. You can use the demo networks that Meraki provides - see the link in @PhilipDAth post.  ... View more

Do you have the latest drivers installed from Intel (directly from Intel - not the machine OEM)?    Also, do you have 802.11r enabled or in adaptive mode (you want enabled)?  ... View more

Standard trial length is 30 days but can be extended if needed. As @Uberseehandel mentioned, your best bet is to join a webinar that gives free gear (including a 3-year license) so you can use it without worrying about the trial expiring.  ... View more

@Asavoy Good point. Didn't remember that one. Clearly there's some need for naming convention standards on the MS team (I'm guessing it's called uplink on all the local UI's across product lines actually).  ... View more

@PhilipDAth wrote: @Adam, OM3 is orange.  OM4 is raspberry pink.  I tend to use OM4 these days as it has better 10Gb/s support.  And if someone is putting in cabling I also recommend using OM4 even if they are using Gigabit so then can upgrade to 10Gbe in the future. OM3 is meant to be aqua. I've also seen aqua continue to be used for OM4, at least in the US, but it is meant to be pink.  ... View more

Try creating a manual connection to the network and deselect the option to verify the certificates under "Settings" on the security tab of the connection.  ... View more

I don't think there's anything SM can control on macOS for this. Have you considered enabling fast user switching as a workaround?  ... View more

@CarolineS Awesome! Thanks Caroline! ... View more

 Rocket ship news!     Founding astronauts (I mean members)!  ... View more

I'm also having this issue with an Android 5.1 device. I installed the SM app via ADB and set the owner to SM with the Meraki provided ADB command from here: https://documentation.meraki.com/SM/Device_Enrollment/Enabling_Device_Owner_Mode_using_Android_Debug_Bridge_(ADB)   The devices enrolls correctly but never asks for authentication. I also cannot select the Meraki managed AfW Gmail account as the owner for the device in Dashboard. Support says that without an AfW account on the device, Sentry WiFi won't work (which is really the only reason I'm trying to get this device enrolled).    ... View more

@Asavoy You can see the dedicated management port here: https://documentation.meraki.com/MS/Installation_Guides/MS350_Series_Installation_Guide   The up arrow in Dashboard on a port indicates it's the port that is being used for Dashboard traffic. I agree with you it's reasonable to call this the uplink, my previous point was that Meraki does not ask you to configure an "uplink" interface anywhere in the UI.  ... View more

Given your current Comcast handoff setup, you'd need to put a switch in front of the MXen as mentioned by @PhilipDAth. I don't think you'll ever talk Comcast into setting up a second port on the Ciena in the same VLAN as your current handoff port. I've never seen them do this and they're particular about standardization on EDI handoffs.    If you do put a switch in front of the MXen, you will need a /29 handoff from Comcast so each MX can have an IP and you can have a third IP to act as the WAN VIP. This is also something I've never seen Comcast do for EDI... ... View more

@Asavoy wrote: Does the MS350 have a dedicated management port?  From what I see of the specifications, it doesn't.... not like a MS410 has.   Yes, the MS350 has a dedicated management port. It's important to keep in mind that MS devices with a dedicated management port cannot use this port for Dashboard connectivity. The port is ONLY used for access to the local UI when the switch doesn't have an Internet connection. You cannot set an IP on this physical interface.    But anyhow, like I've said in my post about my MS320s, Meraki has got to fix their terminology in this regard.  They use the terms Management, LAN IP, and Uplink interchangebly, and if you're not familiar with Meraki equipment you can get very confused.   The management port is the physical port on the switch (if it's equipped with one). The LAN IP and Uplink are references to Dashboard uplink. The LAN IP you set for the switch is what's going to be used for Dashboard connectivity. By default all MS devices will try DHCP to get Dashboard connectivity. The management VLAN setting at the network level (more below) is also describing the VLAN the MS device will use to get Internet/Dashboard connectivity.    It's also confusing that you can set Management VLAN in the Configure>Switches section, but then bypass that by specifying a different VLAN ID in the LAN IP, AKA, 'Uplink configuration', AKA, 'Uplink Internet Connection'.   The management VLAN is a network level default. You can override this setting on an individual switch basis if you need it to be different on a specific switch. If all the switches in a Dashboard network are meant to use the same management VLAN for Dashboard connectivity, then you should change the Management VLAN option and not set this on each individual switch.    The actual Uplink Interface is located in the Configure>Routing and DHCP section.  That's where you specify the Uplink Interface, it's gateway, and VLAN.  That CAN absolutely be in the same address range as your Management VLAN.   These are layer 3 interfaces. I'm not sure that "uplink" is mentioned anywhere on these pages. You don't need to create a L3 interface for an MS device to get Internet connectivity/Dashboard connectivity. You only need to create L3 interfaces if you want the MS device to do routing.    Also it's important to note that it is NOT currently supported for an MS device to use a L3 configured interface as its own management (Dashboard uplink) interface. It sometimes works, but it's not supported.      ... View more

@Asavoy I know it works - sometimes. What I'm saying, and what I think @PhilipDAth is saying, is that you should really plan to move to the Meraki supported setup and go from there. I absolutely want the MS line to support the setup you are using officially. It would save me VLAN's and IP space, but for now I have it running in a supported setup. The Dashboard uplink has its own VLAN/subnet that's tagged on the uplink port. The VLAN I run OSPF on is untagged on this same port back to the core the MS L3 switches uplink to.  ... View more

What you're seeing is the kind of behavior that happens with this (as @PhilipDAth mentioned) invalid config. A L3 interface configured on the MS cannot be used as its Dashboard uplink. You need to separate the VLAN's used for Dashboard uplink and routing.    Yes, this is a pain and doesn't make sense if you've come from a non-MS background.  ... View more

Open a case with Support. They can see which units have thrown the critical temp alarm (this isn't visible to users in Dashboard) - it may be multiple units as well.  ... View more

The arrow indicates that the interface is being used for the uplink to Dashboard. It is not an indicator of STP status.  ... View more

@lfischer-gcpl Agreed on Chromebit for a video wall - definitely not a suitable device for more than 1 or 2 cameras. I'm specifically trying to stream just one camera (it's a front door monitor for an office that cannot physically see the front door) which works fine on a Chromebit.    At this point we are probably going to deploy a Chromebit doing an RSTP stream from a Ubiquiti camera as the delay on MV streams is causing issues at the building. Hopefully Meraki has some better solutions for permanent monitor arrangements and lower latency streams soon.  ... View more

Correct. If you set the MS to use VLAN 11 for management, it will acquire an IP from VLAN 11 and will tag packets for this traffic.  ... View more