Meraki

AnthonyN · ‎Dec 18 2024

If the MPLS is your primary then it is expected behavior for the MX to try and attempt to form a tunnel over it. I don't believe there will be an option to disable autoVPN tunnel over a Primary uplink. You can enable Active-Active to have a "quicker" failover behavior but I'd start with the KB I previously linked 🙂

AnthonyN · ‎Dec 18 2024

Hey there, Is your MPLS link your primary or secondary uplink for the MX? And do you have Active-Active Enabled? That may explain the behavior your seeing. If you'd like to have a failover scenario, then follow this KB https://documentation.meraki.com/MX/Deployment_Guides/MPLS_Failover_to_Meraki_Auto_VPN

AnthonyN · ‎Dec 17 2024

If the AP the laptop is connected to, is on the same switch the TV is connected to, then you wont need the snooping config. However, you mentioned you have multiple switches in your network so you will need to have the snooping config. What IP address is the laptop and TV in your screenshot? The only other traffic I see there is NBNS (NetBIOS Name Service) between .1 and .255 which is essentially like DNS.

AnthonyN · ‎Dec 15 2024

You can see the device 192.168.137.1 is trying to Join a multicast group using IGMPv3 If the traffic goes from one switch to another, you need to have an IGMP snooping querier configured on one of your switches. Review this doco here for more info about multicast https://documentation.meraki.com/MS/Other_Topics/Multicast_Overview%2C_Configurations_and_Best_Practices

AnthonyN · ‎Dec 12 2024

Do you have multiple switches in your network? Does Miracast work if the clients are connected to an AP that's connected to the same switch the TV's AP is, but not if its a different switch? In that case, you may need to enable an IGMP snooping querier on one of your switches.

AnthonyN · ‎Dec 12 2024

Hey @AYEN +1 to the other responses here, the spanning tree events are just a response to the physical port flaps. ie when a port goes down, spanning tree state moves to disabled, when port comes up it moves to designated/root state https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Spanning_Tree_Protocol_(STP)_Overview#STP_Port_Roles I agree, run some cable tests to ensure the cable is good, remove the AP and plug it directly into the switchport with a known working cable to see if you get the same issues. The port flapping events is purely based on Layer 1 (whether the interface is up or down), nothing to do with software.

AnthonyN · ‎Dec 12 2024

+1 to @DarrenOC's comment https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/MR_Firewall_Rules You will be able to block certain apps/websites through the MRs firewall page

AnthonyN · ‎Dec 12 2024

For historical traffic logs, you will need to configure a syslog server https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Syslog_Server_Overview_and_Configuration https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Syslog_Event_Types_and_Log_Samples

AnthonyN · ‎Dec 9 2024

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 · ‎Dec 9 2024

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 · ‎Dec 9 2024

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 · ‎Dec 9 2024

+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 · ‎Dec 9 2024

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 · ‎Dec 9 2024

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 · ‎Dec 5 2024

+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: VPN connectivity change

Re: VPN connectivity change

Re: Miracast Issue For Laptop

Re: Miracast Issue For Laptop

Re: Miracast Issue For Laptop

Re: Spanning Tree always noticed on event log

Re: Web Content Filtering

Re: Web Content Filtering

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: VPN connectivity change

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

Re: VPN connectivity change

Re: Miracast Issue For Laptop