No, the maximum runnable firmware for MR32's is version 26. If you have newer AP's in the same network and apply the 28 firmware upgrade, the newer AP's will run 28 while the MR32's will remain on 26   https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Product_Firmware_Version_Restrictions#MR ... View more

Basically all RMA's need to be issued by support. If you can't open a case via the portal, you can call up Meraki support via phone.   In some exceptional circumstances, your Meraki rep may also be able to assist.   https://documentation.meraki.com/General_Administration/Support/Contacting_Support#Online   Is there a reason you can't open a case with Meraki support via the dashboard to request troubleshooting and an RMA? ... View more

Meraki SFP's are fully supported with Meraki Go - https://community.meraki.com/t5/Questions-and-Answers/SFPs/m-p/100004#M428   I don't have experience with Meraki Go equipment but it seems like supported SFP's for GS switches align with the MS equivalent. https://community.meraki.com/t5/Questions-and-Answers/GS110-SFP-ports/m-p/138809   From the above thread, It seems that similar to MS switches, only Meraki SFP's are supported but other branded SFP's will work. ... View more

You can logically group networks with network tags. They're somewhat useful by themselves but are especially person when played with the API   https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Organization_Menu/Manage_Tags#Creating_Network_tags ... View more

The image you provided is for creating a routed vlan interface (or SVI) on a Meraki Switch. MS120's are layer 2 switches only. They do not support the creation of virtual interfaces.   For your design, you would need to trunk both VLAN 100 and VLAN 300 up to the MX65W and have the VLAN interfaces created on there. The configuration for the VLAN interfaces is configured under "Security & SD-WAN" -> "Addresses and VLANs". Once they're created, you then need to ensure that the ports connecting between the MX and the MS are trunking the VLANs and you should be good.   Be aware though that if you're trying to push a lot of traffic between the two VLAN's, the MX may struggle from a performance perspective. If you find that this is the case, you may want to swap the MS120 for an MS2xx which supports the VLAN interfaces to be present on the switch, and will offload the inter-vlan routing from the MX down to the MS. You would then configure a point-to-point link between the MS and the MX for internet traffic as you originally had. ... View more

Clients connecting to the AP can be authenticated by RADIUS, but the AP's themselves are authenticated to the organisation and configured when connecting to the Meraki cloud.   That said, if you're looking to authenticate Meraki devices on the network, you can look at enabling Secure Connect. SecureConnect - Cisco Meraki ... View more

Similar questions have been asked previously. I suggest checking out the following threads.   https://community.meraki.com/t5/Security-SD-WAN/Migrating-rules-from-Sonicwall-TZ215-to-Meraki-MX64/m-p/46855   https://community.meraki.com/t5/Security-SD-WAN/Migration-from-Sonicwall-TZ-400-to-a-Meraki-MX67/m-p/135186   The short answer is that there's no tool or documented method. You essentially just need to copy and paste the values into their appropriate places. ... View more

The same document also says the following   "Expected behavior. If the MX losses connectivity to the VPN registry, peer information gets purged over time but not immediately. Connectivity to the registry matters when a node changes its contact information after losing connectivity to the VPN registry.   Both the hub and spoke will still be able to form the tunnel if the contact information remains the same, and they lost registry connectivity. Peer information will purge after a few hours causing the tunnel to be marked down."   It sounds like there is a timeout where the peer info gets purged and connectivity to the VPN registry is required for the tunnel to remain established. That said, I've never seen this occur.  For the exact length of time the tunnels remain up for, you'd probably need to ask Meraki support. ... View more

Sounds like the previous admin has made bulk overrides to the RF settings for your AP's.   Under wireless -> RF settings you can see/change the profile used by your AP's. You. An also override some of these settings by selecting the AP's and clicking "Edit Settings" -> "Bulk edit settings..."   My guess is that they've manually overridden channel assignment or power. 90% of the time these settings take care of themselves on auto but in some circumstances these can be manually tuned for better performance.   You can clear overrides by re-assigning the profile to the AP. Select the AP -> edit settings -> assign profile, select the profile and on the next page, check the boxes for clear overrides. The review page that follows it will then tell you the changes it's about to make. ... View more

You can do routed mode with No NAT, but it requires Meraki support to enable it on your dashboard. Once the feature is enabled on the dashboard, NAT bypass can be enabled on a per WAN interface or per vlan basis. ... View more

They will work in the same way as if they were connected to any other noon Cisco switch - the Meraki switch will provide backend networking and POE. However they will not integrate to the Meraki dashboard and as @MarcP said, you will still need a Cisco WLC in the network to manage and configure them. ... View more