Only way i've managed to force these to remove reservations is to set a static reservation against the mac address of the switch within my dhcp server, manually deleting all of the other reservations the switch has, configuring the static to be correct within the dashboard then hitting the manual reset button and forcing the switch to factory reset & pull its dashboard config again. Seems to clear the reservations & fix the leasing issue, but you will ofcourse suffer downtime!  ... View more

I mirror the sentiments of @Purroy , give up on using 2.4Ghz and disable it.  Only use 5Ghz or 6Ghz (if you have WiFi 6E kit). ... View more

I'm not sure if that voice auth checkbox means you can just have a phone on the port without authenticating.  I believe it is to signal that you have a phone possibility on the port and can have the Radius attribute sent for voice domain authorization. The documentation also says in most host modes every client needs to be authenticated including the phone. If your radius server supports MAB you could just have the MAC addresses of the phones in there to authenticate against. ... View more

at the moment we could solve the problem by using these configuration below :   Management IP Old MS410 Switch : 192.168.1.2/24 Management IP New MS410 Switch : 192.168.1.4/24 SVI Stack Switch as p2p to FW : 192.168.1.3/24 IP p2p on FW side : 192.168.1.1/24   we decide to differ the SVI and Management IP Old MS410 Switch, so far there are no further issue, but another question is :   should we use different subnet between SVI and P2P IP addressing? or we could run with our current configuration right now, by using different SVI and P2P IP addressing on the same subnet?   cheers ... View more

i don't know it's still be a problem with you or not, but recently we faced the same problem, when we added the new switch that has lower mac address and create stack the existing switch as a stack together, the newer one become active role due to lower mac address   our approach is rebooted the newer one, and the active role move to the existing/older one.. referred to this documentation    https://documentation.meraki.com/MS/Stacking/Switch_Stacks#Configuring_a_Physical_Switch_Stack     ... View more

This will get you the primary device inventory... https://developer.cisco.com/meraki/api-v1/get-organization-inventory-devices/   Where supported, you can get PSUs with... https://developer.cisco.com/meraki/api-v1/get-organization-devices-power-modules-statuses-by-device/   For SFPs it gets fiddlier, try these for switches... https://developer.cisco.com/meraki/api-v1/get-device-switch-ports/   https://developer.cisco.com/meraki/api-v1/get-organization-switch-ports-transceivers-readings-history-by-switch/   ...I don't recall anything for MX SFPs. ... View more

What @Brash said above. You’ll need to contact Meraki support. This is likely a feature that could be enabled in the future as this has been widely requested here in the community. ... View more

@meraki-newbie please give kudos to the people who you felt helped you with upgrading to 30.7 to fix the issue. ... View more

Nice!!!!! Well done!. ... View more

Run a cable test on the MS125 on the port going to the AP. https://documentation.meraki.com/MS/Monitoring_and_Reporting/Using_the_Cable_Test_Live_tool    99% this is a cabling issue.   Another option, bring the AP to the switch and plug it in using a patch cable (so all existing cabling is eliminated) - does it work properly now? ... View more

did you just allow vlan 1 as native? or just allow vlan 1 on the vlan list with another native vlan? ... View more

well this is worked, connecting my laptop to LAN and set static IP 1.1.1.99 /24 and having gateway 1.1.1.100    thank you ... View more

thank you victor for your response.. just another suggestion, after re-schedule performed, the newly date of firmware upgrade date could popped up and renew/refresh the old one. Due to the popped up notification could be seen once we access the dashboard and potentially be a misleading information.. cheers  ... View more

If a shared IP is used it would be expected to the use that IP, depending on which interfaces is active/primary for VPNs would determine which of the potentially 2 VIPs to use.  ... View more

Your spare MX is not connected to the switch.  So it does not receive any VRRP messages from the primary MX and assumes it is dead.  So yes in this setup it is normal to have a dual active scenario. If your downstream switches are not stacked make sure your link between the switches are a lower number than the uplinks to the MX'es and uplink both switches to both MX'es. ... View more

If you don't already have one, you need a static route on the MX for 192.168.65.0/24 with next hop of 192.168.255.1. You'll also need a static route on the Fortinet for 10.10.10.0/24 with next hop of 192.168.255.2. Assuming you have that, you'll then need to look at the firewall rules on the Fortinet and MX to ensure they're configured correctly. Given you've got 2 security appliances there, I'd use the packet capture functionality on them to see where the packets are getting stuck. ... View more

I believe because of the special architecture of chassis based switches it is more difficult to get it into the dashboard.  So they could potentially come to dashboard but they will take the longest. ... View more

I would't say easier, it's different. 😃 When you configure a regular IPsec peer you won't have a redundancy when using physical WAN addresses. When you use the VIP the IPsec tunnel can move to the secondary MX. ... View more

Flow preferences can only use IP addresses or subnets for the destination. There are more routing features available such as application based routing with the SD-WAN plus MX license. However I believe it still does not support FQDN. ... View more

thank you for your feedbacks @Ryan_Miles , this will help me a lot.. 🤝 ... View more

The Client Balancing  will not solve your problem. The use of channels depends on several factors, the number of connected clients, the amount of data being transmitted at the same time, the number of neighboring APs.   The best thing would be to carry out a site survey to try to find the source of the problem. ... View more

This is a bit off topic but is there likely to be SSO supported for vision.meraki.com in the future?  Currently users have to access it via the dashboard and it would be a much nicer experience if users were able to login directly to the vision port via SSO. ... View more

Yes  - remember that those credentials are used to verify your IDP, not the individual user;   that IDP will separately have to authenticate each user. ... View more

You can only configure the MGMT IP address (or DHCP if preferred) and the MGMT vlan of the MS410 via the local status page. Essentially the bare minimum to get it connected to the dashboard where it will pull all of the rest of the config. ... View more