Hi @MerakiMed , believe this is currently on Beta 16.x.   With regards what’s needed at the backend....an MX 😁   I would expect a separate Anyconnect subscription is also required. ... View more

do you have any firewall rules setup for the cellular interface which could be blocking the vpn? ... View more

Hi @NDIAYE , that should come up automatically, well, within a few seconds of failing over.  How long are you leaving it whilst testing the failover? ... View more

Really excited for this one. GO TEAM EMEA 😁 ... View more

Welcome to the board @gadda      ... View more

@Memonic - sock wall?   Please tell me they’re clean? ... View more

Hooray. More socks. My others have holes in them.       ... View more

Hi @ChristopherC , which test have you passed? ... View more

Hi @redsector , sure you’re aware but Meraki have their MT Sensors:   https://meraki.cisco.com/products/sensors/ What are you looking to achieve? ... View more

Hi @Zeeshan786  yes you can.  Section on Non-Meraki VPN Peers     https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-site_VPN_Settings   Non-Meraki VPN peers You can create Site-to-site VPN tunnels between a Security Appliance or a Teleworker Gateway and a Non-Meraki VPN endpoint device under the Non-Meraki VPN peers section on the Security & SD-WAN > Configure > Site-to-site VPN page. Simply click "Add a peer" and enter the following information: A name for the remote device or VPN tunnel. What IKE version to use (IKEv1 or IKEv2)* The public IP address of the remote device. The Remote ID of the remote peer. This is an optional configuration and can be configured to the remote peer’s UserFQDN (e.g. user@domain.com), FQDN (e.g. www.example.com) or IPv4 address as needed. Which of these values you use is dependent upon your remote device. Please consult its documentation to learn what values it is capable of specifying as its remote ID, and how to configure them (e.g. crypto isakmp identity for ASA firewalls) The subnets behind the third-party device that you wish to connect to over the VPN. 0.0.0.0/0 can also be specified to define a default route to this peer. Note that if an MX-Z device is configured with a default route (0.0.0.0/0) to a Non-Meraki VPN peer, traffic will not fail over to the WAN, even if the connection goes down. The IPsec policy to use. The preshared secret key (PSK). Availability settings to determine which appliances in your Dashboard Organization will connect to the peer.   ... View more

oh that elusive ECMS training...... ... View more

welcome @Nung    Very dry.  Love the fact that it also states "Conversationalist" after your name 😂 ... View more

👍 @trunolimit  ... View more

VRRP is there to ascertain the keep alive between both boxes.  i.e Primary MX are you there > no reply received > OK secondary your turn.  If both WAN1 and WAN2 already have ccts terminated in them on the Primary MX then this setup should be replicated across onto the secondary.  What Bruce was eluding to was placing the connection from your MG21E into a port on the secondary MX and letting that be your WAN connection should the primary MX fail.  It just won't work like that. ... View more

By all means test but I don't believe that setup will work.  With your primary mx setup with WAN1 and WAN2 configured that configuration is sat on the secondary waiting to jump into action.  Once the primary fails the WAN port with your MG21 shouldn't work as it'll have the configuration from primary WAN connection pre-defined. ... View more

Fraid not   https://documentation.meraki.com/MG/MG21%2F%2F21E_Datasheet   Use Cases Note that the following use-cases refer to using a Meraki MX appliance with the MG21 as a WAN uplink. However, the use-cases can also apply to non-Meraki devices. Antenna placement where cellular coverage is best  Signal strength is key for cellular performance. The MG21 makes cellular a viable option in situations where the best location for the MX is not necessarily the best location  for a strong cellular signal. The separation of cellular antenna and MX expands cellular options for all networks, particularly for mid-range MXs mounted in a data center. Primary WAN In areas where wired internet services are not available, the MG21 provides a simple, viable option for wireless WAN connectivity. Secondary WAN for Failover An MX's secondary WAN interface connected to an MG21 may use the cellular network in the event of a primary uplink failure. Secondary WAN for SD-WAN An MX with an MG21 as a secondary WAN uplink may use the cellular network to establish VPNs for SD-WAN. High Availability Uplink The MG21 can be used as either a primary or secondary internet uplink for MX HA topologies. Its two LAN ports allow the MXs to share access to the same cellular network. Your other option is to use the 3G/4G failover port in the MX. ... View more

Hi @trunolimit , you’ll find that the whole Mx Series only have two WAN ports. ... View more

Hahahaha, I use that very same reasoning  ... View more

Did you not make it to bed last night Charles? ... View more

More than likely your ISP if the device suddenly unregisters and alerts. ... View more