Meraki

CptnCrnch · ‎Nov 23 2019

Great to have you with us @KRobert! 👍🏻

CptnCrnch · ‎Nov 22 2019

Update: I just called support (which is possibly what I should have done in the first place) and they were very helpful (as always). It seems to be only a cosmetic issue within Dashboard that is currently known and will be fixed soon automatically. Just leaving this here in case somebody else is also running into this.

CptnCrnch · ‎Nov 22 2019

That‘s what the documentation clearly states: „Only one license is required for an HA pair. The warm spare unit does not require a separate license. Alerts for Warm spare failover can be configured on the Alerts and Administration page.“ https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair „Do I need duplicate licenses to cover my security appliance in a warm spare configuration? A: No, if two security appliances are in a warm spare/HA configuration licensing is only required for one of the two devices. The only additional cost of a warm spare configuration is the redundant hardware.“ https://documentation.meraki.com/zGeneral_Administration/Licensing/Meraki_Licensing_FAQs

CptnCrnch · ‎Nov 22 2019

Licensing has not been an issue with the old model because of the warm spare configuration. Looks like that‘s not the case anymore.

CptnCrnch · ‎Nov 22 2019

Has somebody already tried to convert to the new licensing model in an org that has MX‘s in a warm spare environment? I just did and Dashboard is yelling at me because I seem to have an unlicensed device: my primary MX from that warm spare (interestingly enough, because this one has always been licensed). The documentation and FAQ still clearly state: Do I need duplicate licenses to cover my security appliance in a warm spare configuration? A: No, if two security appliances are in a warm spare/HA configuration licensing is only required for one of the two devices. The only additional cost of a warm spare configuration is the redundant hardware. I guess / hope that this is just something that hasn‘t come up yet but something seems to be utterly wrong in this case.

CptnCrnch · ‎Nov 22 2019

From what I heard, the feature should now be available and can be activated when you open a support case for it. At least I opened such a case earlier today and pretty curious if it'll be fulfilled. Will keep you posted.

CptnCrnch · ‎Nov 21 2019

You simply make use of Layer 7 rules, there's a special category for these kind of services. You'll need the advanced license for that though.

CptnCrnch · ‎Nov 12 2019

Integration is (and will still be) the magic word for me from a security perspective: especially Umbrella is perfectly complementing MR and MX.

CptnCrnch · ‎Nov 4 2019

From a technical point of view, there's nothing that would prevent you to use an MX for a bank or ATM. Guess it'll boil down to many more factors we unfortunately don't know (yet). 😉

CptnCrnch · ‎Nov 2 2019

Perhaps I‘m missing something but from my point of view this should be rather trivial: Each VRF needs to have its own transfer net to a specific VLAN interface on your MX pair and point its default route to the MX. Everything inside the specific VRF will stay inside its own routing table, inter-VRF traffic and everything going to the „outside world“ will then be routed via your MX pair. Of course, you‘ll have to set up routing on the MX side accordingly. Overlapping IP spaces are an obvious no-go in this scenario

CptnCrnch · ‎Nov 2 2019

Well, Netflow would make perfect sense even or especially on MS thinking about Stealthwatch. Guess integration has not gotten that far within the Meraki PM team (unfortunately).

CptnCrnch · ‎Nov 1 2019

Dream team strikes again. Congrats guys! 🙂

CptnCrnch · ‎Oct 31 2019

I've heard of two "rumors" lately, at least one them will make me very happy 😎

CptnCrnch · ‎Oct 22 2019

Devices going up or down could be handled via standard alerting. The monitoring system would either be able to receive email alerts or Webhooks. On the other hand, internals systems would be able to ping your Meraki devices and provide you with reachability information. That would of course be the most simple use case though.

CptnCrnch · ‎Oct 22 2019

Does https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Configuring_Network_Alerts_in_Dashboard help?

CptnCrnch · ‎Oct 22 2019

Well, what exactly do you want to monitor? Reachability „only“? Interface utilization? CPU? Please take a look at https://documentation.meraki.com/zGeneral_Administration/Monitoring_and_Reporting/Meraki_Device_Reporting_-_Syslog%2C_SNMP_and_API

CptnCrnch · ‎Oct 21 2019

Thanks so much guys! For whatever reason, I‘m unable to give Kudos here. 🤔

CptnCrnch · ‎Oct 17 2019

Wow! Guess this day will be my own „Meraki day“ From now on: earlier today I had the chance to take the CMNA class / lab and coming home I find myself featured here. Thanks a million for the having me! 🙂

CptnCrnch · ‎Oct 17 2019

It's documented on https://developer.cisco.com/meraki/api/#/rest/api-endpoints/admins/create-organization-admin

CptnCrnch · ‎Oct 16 2019

Silly question: have you rebooted the MX?

CptnCrnch · ‎Oct 16 2019

You don‘t have to specify a VLAN. Just create a group policy including the QoS settings and assign it to the specified client.

CptnCrnch · ‎Oct 13 2019

Having a similar setup myself...even without a business behind it, I‘d say that‘s a pretty great line of defense. Levering Umbrella, I‘ve seen many things in the meantime, I didn‘t even think I‘d ever see in my own environment. Not only here but especially in client environments. It really adds a huge amount of security. After all, you‘ll receive a huge👍. 😎

CptnCrnch · ‎Oct 10 2019

The document states: „Dashboard branding options are only available to qualified Managed Service Providers. Please contact Cisco Meraki Support to check eligibility“

CptnCrnch · ‎Oct 7 2019

Could you please gibe a little more details about what the question is or what your goals are?

CptnCrnch · ‎Oct 5 2019

Please see above, my post was edited: using another SSID, everything worked out of the box. Great stuff! 😎 Thanks a lot for your help! 👍 MS gnome and MV gnome were here — they've been safely returned home!

About CptnCrnch

CptnCrnch

Chris

Community Record

Badges