Meraki

jimmyt234 · ‎Aug 12 2024

Thanks @AmyReyes and congrats to all the other winners!

jimmyt234 · ‎Aug 12 2024

Yes

jimmyt234 · ‎Jul 23 2024

The device/firewall on the other end of the non-Meraki VPN needs to have your client VPN subnet configured to route down the tunnel, so it knows how to route back to you.

jimmyt234 · ‎Jul 23 2024

1) Make sure you have VPN Mode = Enabled on your Client VPN subnet on the MX 2) Make sure the remote end includes your VPN subnet in their remote encryption domain

jimmyt234 · ‎Jul 23 2024

If you want the SSID to work on the APs native VLAN then you need to remove the VLAN tag on the SSID. So set this to Disabled:

jimmyt234 · ‎Jul 18 2024

Yes! But for an OSPF enabled network it is just telling me that BGP isn't running:

jimmyt234 · ‎Jul 16 2024

You should be able to copy the link of the application from the myapps page, add this to your bookmarks toolbar and then you're only a button press away from logging in 😊

jimmyt234 · ‎Jul 16 2024

Re-IP your local network to avoid the subnet clash... or ask them politely again to review if they can do a NAT on the tunnel on their FortiGate as they should be able to, having personally done so in the past on those firewalls.

jimmyt234 · ‎Jul 16 2024

Not that it helps much, but for the 1 customer who currently has cloud monitored C9200 and C9300 switches we only see the list of tabs you get (ie. I don't see a Power tab either).

jimmyt234 · ‎Jul 16 2024

Ah, in that case yes I see what you are doing and would agree with @ConnorLeedy that I would be deploying it in one-arm mode. Although personally I would be deploying a vMX in Azure any letting all my branches talk to it directly - but I presume you have your reasons to not do this!

jimmyt234 · ‎Jul 16 2024

If you happened to have inbound NAT/PAT rules configured with any source allowed then I would use the Layer 7 firewall to block Remote IP Range, this should block those IP's coming in on your NAT rules.

jimmyt234 · ‎Jul 16 2024

+1, I get the same as @GIdenJoe and @Michael_Pry for Orgs with the 'find in menu' option (doesn't seem to appear everywhere yet).

jimmyt234 · ‎Jul 16 2024

We have a single enterprise app in Entra and then use the same certificate fingerprint configured in all our customer Meraki orgs - this allows IdP initiated login for us as the MSP to all. We have two roles, one for read only and one for full. The customer can then optionally setup their own alongside this.

jimmyt234 · ‎Jul 15 2024

I was more thinking what is the point in the MX85 at all, can the MX450 not support your VPN requirements..?

jimmyt234 · ‎Jul 12 2024

Get Network Events - Meraki Dashboard API v1 - Cisco Meraki Developer Hub You don't need the [] for productType, so this URL should work: https://api.meraki.com/api/v1/networks/{networkId}/events?productType=wireless&perPage=30

jimmyt234 · ‎Jul 10 2024

Could try Layer 7 rule blocking HTTP hostname of linkedin.com as well?

jimmyt234 · ‎Jul 10 2024

We will still maintain a non-SAML full admin account in all customer Orgs, access to which is restricted to certain staff so that everyone else has to use their SAML access. This non-SAML account will have an API key that we can then use to mass-update things like the SAML thumbprint as you have mentioned.

jimmyt234 · ‎Jul 9 2024

How would you represent it differently in the API documentation than it already is?

jimmyt234 · ‎Jul 8 2024

Nice find @PhilipDAth, I will try to remember this for the future if a customer requires a no-NAT scenario due to having public IP subnet on a VLAN!

jimmyt234 · ‎Jul 4 2024

What about the bit below where you are specifying the trunk allowed/native VLANs, etc? At first glance you have different VLANs on the MX to the switch...

jimmyt234 · ‎Jul 4 2024

What is the configuration of the LAN port on the MX?

jimmyt234 · ‎Jul 4 2024

What do you mean by: "the new implementation of the New MX 3 inbound FW rules" ? Can you link the documentation describing this, please.

jimmyt234 · ‎Jul 4 2024

If you're using method 1 quick swap from this document then the hostname will stay the same: MX Cold Swap - Replacing an Existing MX with a Different MX - Cisco Meraki Documentation

jimmyt234 · ‎Jul 2 2024

"Cisco Meraki MS switches must be deployed in the network for the Network-wide > Topology option to be available." https://documentation.meraki.com/MS/Monitoring_and_Reporting/Network_Topology

jimmyt234 · ‎Jun 27 2024

It's on the bit to the left of where your screenshot shows, here:

About jimmyt234

jimmyt234

Community Record

Badges