Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- About jimmyt234
Community Record
15
Posts
26
Kudos
3
Solutions
Badges
a week ago
3 Kudos
I think you'll struggle / experience weird things if you try to have 2 Azure VPN tunnels to the same remote subnet. What you can do, and we have done a lot of, is peer the Azure VPN to the MX's DDNS hostname. This will resolve to the primary uplink IP during normal operation and then if WAN failure it will update and the Azure VPN should re-establish to the other WAN IP. This will be a lot slower and is less elegant and flexible than deploying a vMX, however.
... View more
3 weeks ago
In your diagram the offices are connected to the same switches in Area 1 and 2, does that mean they are in the same layer 2 broadcast domain and share the same LAN subnets? If so, you could run the MX105 firewalls in HA, with the one with 2 WAN connections being the primary unit and the other the spare.
... View more
3 weeks ago
Are the switches still online in the dashboard with the same LAN IP? DHCP or static?
... View more
3 weeks ago
3 Kudos
You can achieve this with group policy rules against the client, best implementation is done via AnyConnect with RADIUS auth: https://documentation.meraki.com/MX/Client_VPN/AnyConnect_on_the_MX_Appliance#Group_Policies
... View more
3 weeks ago
6 Kudos
Yes, traffic should automatically fail back to WAN 1 when it is up. You may need to change WAN failover behaviour to Immediate rather than Graceful (Connection Monitoring for WAN Failover - Cisco Meraki) Other that that, reach out to support as you have already suggested. No show tech required, just give them a ring and they will troubleshoot with you!
... View more
3 weeks ago
Yep - learnt about this the hard why like you did by having routing issues and Meraki support informing me of this secret back end route summarisation configuration that was enabled, issue was resolved after them disabling.
... View more
4 weeks ago
2 Kudos
No, but I am sure any SNMP platform of your choosing could easily do this job.
... View more
a month ago
2 Kudos
Yes, you can configure non-Meraki VPN peers on a vMX in concentrator mode.
... View more
a month ago
2 Kudos
No, but... For non-Meraki VPN peers you could leverage the tag feature to remove the VPN from that network, then add it back in. For AutoVPN you could turn off the site-to-site VPN setting and then turn it back on. Or, reboot the MX.
... View more
a month ago
2 Kudos
Not that I am aware of. If you're trying to maintain the same content filtering settings across multiple networks then a few choices that I see are: Templates Configuration sync (only works for non-combined networks) API
... View more
08-09-2023
02:05 AM
Same! Updated existing support case we had for not being able to upgrade to .3 either...
... View more
08-02-2023
03:54 AM
Same - ticket has been opened
... View more
06-14-2023
08:58 AM
Azure does support FQDN, sometimes it will error when you try to create in the GUI about it being an invalid FQDN, this is a GUI bug and if you create via Azure CLI it will work.
... View more
06-14-2023
08:55 AM
Configure your Azure connection to the Dynamic DNS hostname of the MX, this will auto-failover, albeit rather slowly. The real, elegant solution is to deploy a vMX in Azure.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 197 | a week ago | |
| 172 | a month ago | |
| 199 | a month ago |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 6 | 66 | |
| 6 | 141 | |
| 3 | 197 | |
| 3 | 143 | |
| 2 | 526 |
