Meraki

yaypingworks

This was it, we found that we were publishing the record for some reason. Thanks for the pointer!

TyShawn

Thanks for your time in responding to this post. Sorry for the typos I was working on a small fire when I saw you replied and I wanted to respond quickly :). I don't want to turn this into the me show, so if any of the other forum members would want to share their thoughts please do :).

yaypingworks

Input those addresses in firefox and it will bring you to your concentrator local page. We recently ran into the same deal. Meraki shenanigans

PhilipDAth · ‎Nov 17 2024

In your environment it might be more appropriate to disable the local status page (you'll need to make this decision). https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#Disabling_the_Local_Status_Page

RoshanS · ‎Oct 31 2024

Greetings, It is possible that some existing traffic hasn't failed over solely with the configuration changes. Some traffic, especially sensitive traffic like voice/video calls or some streaming services for example, might not failover since that would break the connection completely. I would suggest testing with a new client, or at least a client that has been disconnected for at least five minutes from the network and then testing again. After that, if possible, I would physically disconnect WAN 1 to force the traffic to failover. If some IPv4 traffic still egresses from WAN 1 - I would suggest contacting support and opening a case so that we can investigate further. Immediate failover/failback is also an option but we should troubleshoot prior to enabling that option. https://documentation.meraki.com/General_Administration/Support/Contacting_Support https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Connection_Monitoring_for_WAN_Failover#.E2.80.9CImmediate.E2.80.9D

DC5 · ‎Oct 30 2024

The solution ended up not being Meraki-related, but I'd like to include it in case anyone in the future comes looking for help: Temporarily, to get the APs to communicate on the proper VLAN and DHCP scope, I set up DHCP reservations and then assigned a static IP in Meraki Dashboard to each AP matching the reservation. I was then able to untag the ports with the proper VLAN and have it all work. This gave me a working network while I figured out the actual cause. When I plugged in a laptop to a port on the WiFi VLAN, I got a 10.x.x.x/8 address with a gateway of 10.128.128.128. This is a Meraki Cloud DHCP, so this indicated that the VLAN was not communicating at all with the DHCP it was supposed to be. Said DHCP server is offsite; the culprit ended up being the DHCP relay in our firewall. Once I rebooted that and made sure that the switch the firewall was wired to had OSPF "redistribute connected. restrict [our DHCP IP and subnet mask]" and VLAN [WiFi] IP address [Our DHCP IP and subnet mask], I was able to remove the DHCP reservations and set the APs back to DHCP in Meraki Dashboard. Hopefully this helps some folks in the future, and thanks everyone who replied for your suggestions! The key troubleshoot that led to the breakthrough was the suggestion of using a laptop to connect to the VLAN/DHCP.

GIdenJoe · ‎Oct 29 2024

If you are sure your routing is ok and you did the capture correctly and not see anything on UDP port 1812 leaving the switch, then you should capture the EAPoL frames on the port. Your supplicant might not be sending EAPoL frames to the switch.

wial · ‎Oct 27 2024

Thank you, Sir. it works on this plan. Now I want to have to enable IGMP into the specific VLAN on SSID. Been followed this doc: https://documentation.meraki.com/General_Administration/Other_Topics/Multicast_support#IGMP_Support_on_the_Cisco_Meraki_Switch But I want to know how to test the IGMP works. Since my AV vendor keeps saying to enable IGMP on AP.

GreenMan · ‎Oct 23 2024

The risks of continuing to use an End of Life device are generally one or all of these: You can no longer get a replacement device via Meraki Support, if the hardware fails. You will no longer receive firmware updates or fixes, lincluding for bugs and/or security fixes. Meraki Support will no longer provide substantial support in the event that you have a problem with the device. Remember too that, in order to keep the device working, you do still need to ensure the license is kept up. So; the relative value received from that license drops significantly. In most cases, any residual value for remaining license time on a device you want to replace will (or can) be retained for a new Meraki device, deployed in its place.

Adrian4 · ‎Oct 23 2024

hmmm, i may have to resort to that, thanks!

yaypingworks · ‎Oct 22 2024

For BYOD, I recommend 802.1X where your employees will connect to Wi-Fi and enter their work credentials. You can have radius assign them into a VLAN that can't access internal resources, and once the employee leaves the organization they won't be able to use their login anymore

PhilipDAth · ‎Aug 20 2024

In the earlier days of iPSK without RADIUS I used to have to reboot the APs from time to time. I presume it was a problem with the downloaded list like @GIdenJoe mentioned. It has been rock solid reliable for a long time now. I would try giving an affected AP a reboot and see if it makes any difference.

ww · ‎Aug 10 2024

Looks like the z3 can do a bit more from fw 18.2.

Meraki

Community

About yaypingworks

yaypingworks

Community Record

Badges

Re: How is Google is resolving my intranet IP...?

Re: Disabling IPV6 on WAN

Re: Is Meraki VPN traffic monitored by USA government? :D

Re: MX Concentrator had a public IP to get to local status page...?

Re: Failover not working as expected

Re: APs connecting on one port-based VLAN but not another

Re: 802.1x over Ethernet EAP-TLS

Re: VLAN and Multicast on MS and MR Device

Re: Can someone explain end of support for meraki devices?

Re: weird connection issue

Re: Best practice for guest users and IOT wireless environment.

Re: Identity PSK VLAN assignment bug on MR42 30.7?

Re: VPN throughput question

Re: How is Google is resolving my intranet IP...?

Re: Best practice for guest users and IOT wireless environment.

Re: weird connection issue