Meraki

AnthonyN

Hey Alex If your also getting the same errors on other AP's then it is likely a client side issue. Have you updated your wireless drivers to the latest firmware? Might be worth raising a ticket with your vendor.

AnthonyN

Hey there, Does a nslookup return anything? You can try toggling the hostname (just add a character and revert it back after about 15 minutes) to see if this helps. Other wise I'd suggest raising a ticket with support to see why the MX isn't reporting its hostname.

AnthonyN

Hey there, The INVALID_ID_INFORMATION error means that the traffic selectors (subnets) did not match. Is one more specific than the other? The VPN status is showing green because Phase 1 is up, this does not take into account of phase 2 unfortunately. If the traffic selectors match exactly then I'd suggest raising a ticket with the NMVPN vendor and Meraki support to see if there's anything weird going on.

AnthonyN

+1 to this Unfortunately, there is no way to recover the access. You will have to get the old provider to remove the devices from their dashboard so you can claim them into your own. Support cannot assist in this due to our policy so you may have to get some legal assistance.

AnthonyN

Hey there, Are you using Client VPN or Anyconnect to connect your devices to the MX105? Client VPN uses L2TP and Anyconnect uses Cisco Proprietory VPN protocols (TLS/DTLS) so neither use IPSEC VPN. I know that newer versions of Android (13+) no longer have L2TP support. If your using Android 10 and still cant connect through ClientVPN then I would suggest going through this KB, then opening a ticket if your still having issues. https://documentation.meraki.com/MX/Client_VPN/Guided_Client_VPN_Troubleshooting

AnthonyN

Hey there, +1 to Raphael Meraki devices use Meraki/public NTP servers, this is not configurable. If you can confirm this traffic is indeed being sent by the MVs to your private server then I would suggest opening a ticket with support.

AnthonyN

+1 on cmr's comment Your Ubuntu/Linux box needs to run LACP. MS/Catalyst running Meraki mode use LACP for link aggregation. If the switch does not receive a reply to its LACP negotiation packets then it will block the port as "....LACP has disabled this port". Is this the error you are seeing on your switchport? See these KB's below for more info https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Switch_Ports#Link_Aggregation https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Link_Aggregation_and_Load_Balancing Any doubts, you can raise a ticket with support to see why the aggregation is not forming correctly.

Meraki

Community

About AnthonyN

AnthonyN

Community Record

Badges

Re: Association errors

Re: Meraki VPN host name not resolving

Re: Non-Meraki Peer to vMX Site to Site VPN

Re: Recover Dashboard Admin

Re: IPSEC VPN is not working in Android

Re: NTP requests being sent to 192.168.1.100 from all new cameras; this is ...

Re: Bonded LAN ports on Ubuntu causing port flapping on C9300X

Re: Bonded LAN ports on Ubuntu causing port flapping on C9300X

Re: Non-Meraki Peer to vMX Site to Site VPN

Re: NTP requests being sent to 192.168.1.100 from all new cameras; this is ...

Re: Bonded LAN ports on Ubuntu causing port flapping on C9300X