About MRCUR

MRCUR · ‎09-11-2018

Unfortunately the CCX changes in 25.12 did not resolve the issue for us. We also tried completely disabling CCX/Fastlane which did not resolve the issues either. We've now modified the min. bitrate for our primary SSID to see if that helps (no complaints so far).

MRCUR · ‎09-10-2018

This was an issue with the firmware the MR42 originally shipped with. The LLDP negotiation for power didn't work correctly so you had to manually set it on the switch port. This has been working for quite a while though. Are you on a current MR firmware build? What OS build are you running on the switches? I have a 2530 sitting on my desk running 16.05.0003 and it's negotiating PoE+ correctly with MR42's and 52's.

MRCUR · ‎09-09-2018

@aws_architect This typically happens when there are other items in the firmware which are not yet public.

MRCUR · ‎09-04-2018

You'll be offered a 250 replacement (including entire stack if you have 210/225's stacked) if you have a switch experiencing the issue today and need a replacement today. Otherwise the tool will order you 210/225's once they start shipping next month. As @MerakiDave said - just keep in mind that the MS250's are gigantic switches.

MRCUR · ‎08-30-2018

When you restore the backup, you restore the supervision state (in this case you are restoring an unsupervised state). The workaround in the Jamf thread (and discussed here previously if you do a search), is to restore the backup to a *different* device. If you need the same device to be returned to a user, you could then do a backup of the different device and then restore it to the original device (which would retain the now supervised state).

MRCUR · ‎08-28-2018

@redsector The fixed switches will be available in October.

MRCUR · ‎08-27-2018

I have seen an MX250 go offline following a firmware update which was resolved with a power cycle. I have not had a complete failure after updating firmware.

MRCUR · ‎08-27-2018

@Jmezo Since you can reproduce this pretty consistently, I'd recommend contacting Support and asking them to disable CCX completely on the SSID you're having issues with while still on 25.12 firmware. The thought is CCX has been causing these issues. Part of it was disabled in 25.12, but perhaps not enough to fix this completely. If you do this and have a case number, feel free to message it to me and I will make sure it gets in front of the product team.

MRCUR · ‎08-26-2018

What you have planned is a very standard deployment of MS425's at the core and MS225's at the edge. I would stack the 425's with QSFP and then create LAG's to the 225 stacks with a link going to each of the 425's.

MRCUR · ‎08-23-2018

@jwoodok I agree there needs to be a better PVM solution. I know @GeorgeB has mentioned they are looking at better solutions.

MRCUR · ‎08-23-2018

@GaryM You would see the AP log clients leaving because your clients are disconnecting from (leaving) the AP. But since you are seeing the client side WiFi adapter reset at the request of the driver, it seems like a client side driver issue. We never saw the client driver request a reset throughout this issue. It wouldn't hurt to move to 25.12 firmware since it is the stable release candidate and will likely become the stable release shortly.

MRCUR · ‎08-23-2018

@GaryM wrote: The network interface "Intel(R) Dual Band Wireless-AC 8260" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver requested that it be reset. You should update the driver directly from Intel. What you're seeing is very likely a driver issue and unrelated to what is being discussed in this thread.

MRCUR · ‎08-23-2018

@Krewal wrote: Keep in mind you can only revert firmware for 1 week, if I remember correctly. This is becoming ridiculous by now. half of the year yet they could not address it? Support can modify firmware version on the network at any time. The issue being discussed in this thread is believed to be resolved in 25.12.

MRCUR · ‎08-23-2018

@rdunlap Perhaps @CarolineS has protected the employee accounts from receiving messages?

MRCUR · ‎08-23-2018

There have not been any changes since the previous thread you saw. This is still not possible through a native solution. You could potentially have something like Chrome launch on login and have the homepage set to a specific video wall, but there is a also a global Dashboard forced logout setting which may eventually kick this out.

MRCUR · ‎08-23-2018

@Ben See here: https://documentation.meraki.com/MR/Other_Topics/Integrating_Cisco_Umbrella_with_Meraki_MR_Networks "Please contact Meraki Support to have this feature enabled."

MRCUR · ‎08-22-2018

What's the name of the profile this is coming from? Is it the Meraki enrollment profile?

MRCUR · ‎08-22-2018

I have 25.12 running on ~1,400 AP's and so far have not had any complaints of random disconnects. This is only the second day with teachers back in the district however. Hopefully it's really fixed.

MRCUR · ‎08-20-2018

Ask the engineer assigned to check with the SM dev team. They have the ability to do this easily so it shouldn't be a problem.

MRCUR · ‎08-20-2018

@Adam You can use this in place of the NAT mode content filtering. Another big benefit is the AP's enforcing the DNS traffic going to Umbrella and encrypting that traffic. Even if someone configures alternate DNS servers locally, it won't matter as the AP is going to send it all to Umbrella.

MRCUR · ‎08-20-2018

This seems like a bug since valicert.com doesn't have a valid cert. It is a very old root CA that (I think) GoDaddy purchased at one point, but it's not used anymore. Perhaps @Melissa can check with the engineering team on this.

MRCUR · ‎08-20-2018

Meraki SM alone will not accomplish what you are looking for. SM does not have the ability to schedule tasks like this or set up login/logout scripts. You could do what @PhilipDAth is suggesting by using cron to schedule the execution of the script at regular intervals however. This is unfortunately not nearly as simple as Task Scheduler in Windows.

MRCUR · ‎08-20-2018

It sounds like this may be an issue with the specific network/SSID that was removed. Do you have a case open with Support on this? You may need to get SM engineering involved to have it removed.

MRCUR · ‎08-18-2018

You'll need to include a telltale in the script, like a dummy app to be "installed" into /Applications. Otherwise SM does not know if the script has been installed or not. See here for documentation on this: https://documentation.meraki.com/SM/Apps_and_Software/Deploying_Scripts_in_Systems_Manager_using_Software_Installer

MRCUR · ‎08-18-2018

For your first issue, are you 100% positive this old SSID is not still configured anywhere in your Dashboard org? Typically the old Meraki WiFi profile should be removed when the old SSID is removed or changed to a non-Sentry auth type. I'd love to hear feedback from the SM team on your other questions as I also see the same (odd) behavior.

MRCUR

Community Record

Badges