Meraki

MRCUR · ‎Sep 21 2018

Have you actually created a stack in Dashboard? Did you set the ports you're using to run as stacking ports?

MRCUR · ‎Sep 21 2018

Apple defines what the restriction payloads can do, not Meraki. You should submit this feedback to Apple directly.

MRCUR · ‎Sep 21 2018

I don't think so. The delay date is set based off of "release date" which is 9/17/18.

MRCUR · ‎Sep 19 2018

@cta102 The AP's don't tag their management traffic if the VLAN box is left blank on the AP LAN IP config (MS switches do from what I've seen).

MRCUR · ‎Sep 19 2018

You might be able to get away with setting the "All other AP's" to VLAN 1 or 0. Give it a try in a test network.

MRCUR · ‎Sep 17 2018

This is not possible with the MX as the redundancy (warm spare) is an active-passive design. All traffic is handled by the active MX unless there is a failover event and then all traffic is handled by the second MX until the primary MX comes back online.

MRCUR · ‎Sep 14 2018

I don't think @GeorgeB is a huge PTZ fan. They're expensive, there are lots of components that can fail and they don't give you constant coverage of a given area. We've found that it's been easier to simply add additional cameras to cover a whole area (the MV12W provides a very wide angle view) than what was previously being done with PTZ's. This isn't to say Meraki won't eventually release something to compete with a PTZ, but for now it's a non-issue for us.

MRCUR · ‎Sep 13 2018

@PhilipDAth It's just the URL of an individual camera page that you can see today.

MRCUR · ‎Sep 12 2018

This is awesome! Thanks for the update @GeorgeB.

MRCUR · ‎Sep 11 2018

We monitor the WAN IP's of each MX and the shared virtual IP with simple ICMP ping.

MRCUR · ‎Sep 11 2018

@aws_architect If you don't want to continue using MR 26.X, ask Support to revert the network(s) to the previous 25.X build. If you want to test the Umbrella integration, you will have to run 26.X.

MRCUR · ‎Sep 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 · ‎Sep 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 · ‎Sep 9 2018

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

MRCUR · ‎Sep 4 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 · ‎Aug 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 · ‎Aug 28 2018

@redsector The fixed switches will be available in October.

MRCUR · ‎Aug 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 · ‎Aug 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 · ‎Aug 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 · ‎Aug 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 · ‎Aug 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 · ‎Aug 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 · ‎Aug 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 · ‎Aug 23 2018

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

About MRCUR

MRCUR

Community Record

Badges