Meraki

jdsilva · ‎Dec 11 2018

I'm not sure there's an "easy" way here. I'd suggest that you connect up the MX to the cloud, and then run the Mgmt interface of the MS to the MX so you have a stable control plane to work with here. And then as you say, just migrate the L3 interfaces one at a time. Moving DHCP is going to be a pain. I would suggest ahead of time you shorten the lease time on the MS down to something really short (1 hour? 30 minutes?) and let all your clients get the new short leases. This will ensure the clients re-dhcp to the MX within a reasonable period.

SeanFFC · ‎Dec 10 2018

Where would be a good place to suggest this as an addition to the API?

CarolineS · ‎Dec 10 2018

@jdsilva that's a nice swag museum in the background 🙂

jdsilva · ‎Nov 30 2018

@Adoos This is what failed means: https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Connection_Monitoring_for_WAN_Failover

NolanHerring · ‎Nov 28 2018

Oh I am. Good point 😃

MManolli · ‎Nov 23 2018

Hi Nolan, Thank you for your help. Key regenerated Mauro

rhbirkelund · ‎Nov 23 2018

I am currently deploying this network topology, although with a single ISP only. Using multiple switches in the WAN breakout network (VLAN) you need to keep an eye on your STP. Because I am basically implementing multiple tiered network loop, I having a problem net STP actually doing its job, and thus blocking all WAN links to my Warm Spare MX. In order to keep my secondary MX online, I have to disable RSTP on one port, so as it doesn't go into a blocking state.

MacuserJim · ‎Nov 20 2018

Ah, yeah the network should revert back to the config it had right before it was bound to the template.

jdsilva · ‎Nov 19 2018

Meraki wrote: The type of the new network. Valid types are 'wireless' (for MR), 'switch' (for MS), 'appliance' (for MX, Z-Series), 'phone' (for MC), or a space-separated list of those for a combined network. https://api.meraki.com/api_docs#create-a-network

jdsilva · ‎Nov 14 2018

No problem! Good luck with your config 🙂

mat1458 · ‎Nov 14 2018

Hi jdsilva Thanks for your reply and sorry for my late reply. That's indeed the way to go, L2TPv3 Tunnels or EoGRE would be others but due to technical restrictions I'll continue with your idea. Cheers mat

CML_Todd · ‎Nov 13 2018

Thanks for the heads ups Zilla! I definitely plan on getting a demo.

sschiang · ‎Nov 9 2018

Hi, sorry for the late reply. I did a port scan on the Windows system (it does have Windows Firewall on). It appears that it is rejecting access to most ports. I've tried to enable various Windows Services that I think are relevant but no luck yet. It now appears your suggestion that this is a Firewall problem is correct. Thanks for the help.

PhilipDAth · ‎Nov 7 2018

Hahahahaha. OMG.

jdsilva · ‎Nov 7 2018

Yup, you're safe.

jdsilva · ‎Nov 5 2018

Oh... Hah! I forgot that was hidden behind an NFO. We have it enabled on all our Orgs so I always just see it. Nice catch.

aalex01 · ‎Nov 5 2018

All these "tips" actually work,many thanks. I can't believe I have to "cheat" for that and just cannot disabled all SSID. Alexandre.

jdsilva · ‎Nov 3 2018

Another solution could be to use the API to do this. https://api.meraki.com/api_docs#update-the-attributes-of-an-ssid It wouldn't be too difficult to set up a weekly cron job that updates the key and emails you the value once a week.

jdsilva · ‎Oct 31 2018

Hi @Homerdan, Yes, you need Meraki at all locations you wish to deploy SD-WAN at. That is the same for every vendor's SD-WAN product out there. Not a single one has any interoperability with another. If you place both MX64's at one location then all you can leverage is Warm Spare and failover between ISPs,

Pugmiester · ‎Oct 31 2018

Hi @jdsilva Thanks for the pointer. I hadn't realised the best practice guide had been updated. I've stripped out the HA dedicated patch cable and together with dual connections from each MX to each switch, everything is looking rock solid. I think we have a winner.

jdsilva · ‎Oct 30 2018

Yup, this would work just fine. The caveat would be that is WAN2 fails you won't be able to stop your specific VLAN from using WAN1 in the event that WAN2 fails.

jdsilva · ‎Oct 29 2018

@PhilipDAth wrote: You could possibly use the GPDR data privacy feature. https://documentation.meraki.com/zGeneral_Administration/Privacy_and_Security/Meraki_Data_Privacy_and_Protection_Features Hey, that's a neat idea. I might have to try that.

jdsilva · ‎Oct 28 2018

Nope. It can do port forwarding via its WAN IP, a 1:1 NAT, or a 1:Many NAT, but it doesn't actually proxy those connections.

AdanC · ‎Oct 28 2018

Thank you!!

fidel · ‎Oct 27 2018

I have tried all the javascript code snippets from postman but still not working yet i get a good result from postman software itself. I have actually written my entire codes in javascript hence would not like to switch to any other language. Is there any help

About jdsilva

jdsilva

Community Record

Badges