Meraki

MRCUR · ‎Nov 5 2017

@MerakiDave Are you Dave S. who works with Matt S.?

MRCUR · ‎Nov 4 2017

@Mr_IT_Guy I'm not involved enough with it to speak to it unfortunately. We're very likely using it differently from use so I suspect that's where the different requirements are coming into play.

MRCUR · ‎Nov 4 2017

@Mr_IT_Guy We actually FTP files to them.

MRCUR · ‎Nov 1 2017

Do you have a custom password set at Network Wide - General - Device configuration?

MRCUR · ‎Nov 1 2017

@KarbonX1 Definitely submit a case about that. It shouldn't actually try to run the lower firmware than is required, even if you configure it on the network. It should just say it's up to date on the version you configure but continue running its minimum version silently.

MRCUR · ‎Oct 31 2017

@Asavoy Follow the recommendation from @PhilipDAth. That way you can ensure all of the necessary rules are in place.

MRCUR · ‎Oct 31 2017

Man you guys must be really excited for this launch. I was going to say it's only early afternoon at Meraki's HQ. They must've finished up lunch and clicked the right buttons to make it live.

MRCUR · ‎Oct 29 2017

@Asavoy FYI - not every address in the new range is being used yet. They're just now beginning to migrate shards over to the new space - https://bgp.he.net/net/209.206.48.0/24#_dns

MRCUR · ‎Oct 29 2017

We use FiServ for something with payroll and have an MX providing Internet. No complaints from FiServ on this setup. As others have pointed out, Meraki is PCI compliant so I'm not sure what the issue would be. You're not sending user traffic to Meraki at any point.

MRCUR · ‎Oct 29 2017

@WadeAlsup This is definitely the closest you'll get for historical average use, but they definitely filter out peak usage in that chart. The chart for one of my MXen shows a peak of about 600Mbps. This may well be the "average" for that MX of the time period, but it regularly goes above 1Gbps and sometimes much higher (upwards of 2.5Gbps).

MRCUR · ‎Oct 28 2017

The recommendation is typically to create a network per location. To keep the configs all in line, you can create an MR template and then bind the template to each of the individual networks. The only networks I use that are not specifically tied to individual locations are Systems Manager network (typically one per org) and MX networks that serve entire orgs (aggregated Internet for entire school district for example).

MRCUR · ‎Oct 28 2017

@Reinout I'm a bit confused by your post. The vMX license is one price - it doesn't matter if you run it on AWS or Azure. But the costs to running on AWS or Azure are of course different as they aren't set by Meraki. Meraki is just setting the type of VM hardware you need to supply for the vMX as it's a managed appliance on each service.

MRCUR · ‎Oct 27 2017

@techmoc wrote: Late October is turning into November Tuesday is still October...

MRCUR · ‎Oct 27 2017

@BklynITGuy That's not a public setup guide...

MRCUR · ‎Oct 27 2017

@BklynITGuy I don't actually see it listed. I'd suggest trying it again next week though, perhaps sometime after Tuesday.

MRCUR · ‎Oct 26 2017

Open a support case. That's why it's flashing - it's trying to update the firmware. The Dashboard firmware status changes immediately after an update - it's not accurate to what the device is actually doing.

MRCUR · ‎Oct 26 2017

If you go to the local status page, does it say there is an upgrade in progress?

MRCUR · ‎Oct 26 2017

@Adam Same as the MS - no uptime available besides the 30 day connectivity history. I believe Support has access to actual uptime though.

MRCUR · ‎Oct 26 2017

This is a known issue with Sentry policies. I've had a case open on this since June 2016 with no resolution to date.

MRCUR · ‎Oct 26 2017

You'd probably be better off posting in the TechNet forums - https://social.technet.microsoft.com/Forums/en-US/home

MRCUR · ‎Oct 26 2017

You can see release dates for the stable builds.

MRCUR · ‎Oct 17 2017

First step is to configure any local settings on the MX like static IP (if required). You can then either clone the existing MX network, or remove the existing MX64 from its network and then add the new 84 to that network. The network retains all the config info. If you use site-to-site VPN, you'll need to re-enable that feature (all settings will be retained) after the swap.

MRCUR · ‎Oct 17 2017

@MikeFromHAVEN I would force the issue then. I'm not sure why they're saying a fan that isn't operating is okay. By the time the switch throws a temp alert, it's too late. I had multiple already dead at that point.

MRCUR · ‎Oct 17 2017

@MikeFromHAVEN If the fan is not operating then the switch absolutely needs replaced. I'd recommend calling Support and requesting an RMA ASAP.

MRCUR · ‎Oct 17 2017

@MikeFromHAVEN I would recommend replacing any switch that isn't running the fan at very close to full speed. If you have any that are cycling between slow/fast, I've seen that become a failure within a week or so.

About MRCUR

MRCUR

Community Record

Badges