Meraki

MRCUR · ‎May 29 2018

@lauraCanadaIT There is no way to customize the DHCP options for the client VPN subnet that I'm aware of. If you issue a mobile config profile to your iOS users to set up the VPN, perhaps you can supply the DNS suffix with that config.

MRCUR · ‎May 28 2018

The L3 roaming option is only needed if your clients are going to roam between different subnets. It sounds like you can make the wireless VLAN you'd like the clients to be in available at all of the AP's, so you can simply use regular bridge mode and tag the appropriate VLAN you'd like to use.

MRCUR · ‎May 23 2018

I think your proposed solution will work well @CarolineS! There should definitely be some "value" to the solutions for the leaderboards as posting solutions is important, especially as the community grows and people come here to search for exact issues and their solutions. I do agree with @Mr_IT_Guy that sometimes the "solutions" selected by OP's are a bit dubious, but this isn't a big deal for now as the community is still rather small.

MRCUR · ‎May 18 2018

Keep in mind that you cannot actually set the uplink speed in Dashboard higher than the MX is configured to work with. An MX64 for instance will not let you set it to higher than 250Mbps while an MX450 will not let you set it to higher than 6Gbps.

MRCUR · ‎May 17 2018

You'll need to create a Systems Manager network. See here: https://documentation.meraki.com/SM/Systems_Manager_Quick_Start

MRCUR · ‎May 16 2018

I don't. It seems like it's in the core 802.11 standard as it's part of the 802.11 frame. Google is probably your best friend here.

MRCUR · ‎May 16 2018

"All Meraki Access Points support PS-Poll." - this typically means it's enabled by default and cannot be disabled. The client will need to support PS-Poll.

MRCUR · ‎May 15 2018

I'd suggest to submit this feedback through your Meraki sales partner so they can create/add to existing feature requests. This could potentially be solved with an MV API that does not currently exist.

MRCUR · ‎May 11 2018

This is definitely an oddity of Meraki MS devices currently. As @PhilipDAth points out, you cannot use a L3 interface you've created on the stack as the stack's Dashboard uplink (management). While some people have reported this works, it is NOT supported so you're better off using the link between the stack and your firewall as the management interface.

MRCUR · ‎May 10 2018

@Bovie2K The Z3 spec sheet is quite clear on its throughput - 100Mb and a further limit of 50Mb for VPN.

MRCUR · ‎May 3 2018

Not a bad idea! (I have to get to 50 characters apparently...)

MRCUR · ‎May 3 2018

See previous discussion here: https://community.meraki.com/t5/Security-SD-WAN/Blocking-WhatsApp-Traffic-Using-MX84/m-p/12796 The search box at the top is very handy. 😄

MRCUR · ‎May 3 2018

@PhilipDAth wrote: The MX100 does not have an SFP+ port. I don't know how you are even plugging it in. I imagine he's plugging it into one of the SFP ports on the MX. SFP+ will physically fit, it just won't work.

MRCUR · ‎May 1 2018

@WDW I don't think it matters that your peers are non-Meraki. I have MXen with non-Meraki VPN peers and saw this issue previously. It might be worth reaching out to your Meraki sales rep/SE and ask them to get the case in front of their managers and the product team if possible. You can always call Support and ask to speak with a manager as well, or ask any engineer if they could ask the product team if they know about this issue (they're all in the same office).

MRCUR · ‎May 1 2018

Thanks for the kudos everyone! I have no doubt you will make it to 12 months @PhilipDAth. Maybe that achievement should bring something extra special with it, like lunch with @tnight. As always - thanks to @CarolineS for keeping the rocket ship in order!

MRCUR · ‎May 1 2018

There was previously a known issue on earlier 14.2X firmware builds where devices would reboot when S2S/AutoVPN was enabled. This is what was very likely happening to the people who posted in the thread you linked to (myself included). Even though the devices are logging power events, S2S was the real issue previously. While I am no longer seeing reboots on 14.25 with S2S tunnels, these did not immediately stop after upgrading to 14.25 which leads me to believe the root issue has not yet been corrected. Have you considered trying to 15.X firmware? It has been in development long enough now that it's probably relatively stable, but if you go this route I would ask for the known issues on the current build to be sure none of them directly impact you.

MRCUR · ‎Apr 24 2018

See the very end of this doc for splitting networks: https://documentation.meraki.com/zGeneral_Administration/Organizations_and_Networks/Combined_Dashboard_Networks You can then rename the network to the desired name.

MRCUR · ‎Apr 23 2018

Is the Owatonna network combined or MX only?

MRCUR · ‎Apr 23 2018

If you run non-combined networks they will be named exactly what you name them.

MRCUR · ‎Apr 23 2018

If you are using combined networks (multiple Meraki product types in the same network), then each network "type" actually gets a - (product) appended to the name. "Wired" is the name for MX, "switch" is the name for MS and "wireless" is the name for MR. You'll see this in the Dashboard URL when you're in each product config area.

MRCUR · ‎Apr 23 2018

@Uberseehandel FYI - the UniFi model of the EdgeRouter Infinity is available now: http://www.doubleradius.com/Manufacturers/New-Ubiquiti/ubiquiti-unifi-8-xg-gateway-router.html It's a bit pricier than I expected.

MRCUR · ‎Apr 23 2018

@Adam It's still a "beta" release so you probably need betas enabled on the network or ask Support to apply it.

MRCUR · ‎Apr 23 2018

@svk253 If you're not using a device anymore, you need to remove it from whatever Dashboard network it's in. You don't need to remove it from your org inventory, but if a device is in a network, then it will consume a license.

MRCUR · ‎Apr 20 2018

MV 3.6 firmware is available with additional MV12 fixes.

MRCUR · ‎Apr 20 2018

@CraigCummings wrote: In any event...there is absolutely no valid reason to disable the ENTIRE org over one measly Z1 license. Cisco could easily just disable the one Z1. Again, heavy-handed is a radical understatement. This isn't about a "measly" Z1 compared to your other products. Meraki licenses everything at the org level. There is ONE expiration date for the entire org. There would've been a red license warning button displaying in your Dashboard for the entire time you were out of license compliance. Is this a different licensing approach than most tech companies? Yes, but Meraki has a different approach to tech than most companies. Understanding how the licensing works is part of being a Meraki admin.

About MRCUR

MRCUR

Community Record

Badges