Hi @DR1  I had the case last year, we set up a remote stacking between MS425 using MA-QSFP-40G-CSR4 and MPO12   Some former topics say that this is not supported by Meraki but here the details provided by my Cisco Solution engineer implying it is supported as their DAC / Stack cables are standard.   SR4 and CSR4 are both MPO interfaces. My recommendation would be that you will be ok with the MPO12 The document shows this but Channel Pairs (Ethernet link Tx and Rx): 1 and 12 (Tx1 and Rx1) 2 and 11 (Tx2 and Rx2) 3 and 10 (Tx3 and Rx3) 4 and 9 (Tx4 and Rx4) Channels 5, 6, 7 and 8 are unused     I drafted quick specs after ends based on this first experience To note, I didn't follow up this project from start to end but they follow my initial recommendations and it ends up working fine. Cisco Spec slide about their QSFP-40G-SR   I hope it helps. I'm pretty sure the same could be done with QSFP28.  A similar discussion from last week https://community.meraki.com/t5/Managed-Services/MS355-long-distance-stacking/m-p/102794#M392   If you have access to a Cisco Solution engineer, you may ask him the fiber breakout specifications for MA-CBL-100G / 100GQSFP28 https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/transceiver-modules/data_sheet_c78-660083.html https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/transceiver-modules/datasheet-c78-736282.html  https://meraki.cisco.com/lib/pdf/meraki_datasheet_sfp.pdf     Edit: To confirm, MS425 Stack ports have been set to "stacking" so technically no different than a stack dedicated port on other series.   ... View more

Hi @JeremyBrainard  That's the endpoint "claim network devices" where you set networkID in the URL and serial Number in the request body It will add the listed devices to the network   https://developer.cisco.com/meraki/api-v1/#!claim-network-devices     The other endpoint to claim order/devices into Organization dashboard is "Claim into Organization", which indeed claim the devices the first time into your dashboard https://developer.cisco.com/meraki/api-v1/#!claim-into-organization ... View more

I got the same message on all my networks with MR74, simply solved by settings the external currently installed on them   By default Meraki leaves it configured with MA-ANT-23 but seems to show the alert until you manually set the proper one as there are few possibilities   Note you have to do it on both radios.       ... View more

Hi @GaryShainberg  I think you will need to set WAN2 as primary link to do so.   ... View more

Hi @nikmagashi    Indeed you figured it out: Shared secret field: it the shared secret to be configured on Windows VPN Client as well Secret field in Radius section: it the PSK/Secret to configure with Radius client on NPS server   Regarding the IP Address to associate with the Radius Client on NPS Side, this meraki KB is really helpful and explains the different cases https://documentation.meraki.com/MX/Client_VPN/Configuring_RADIUS_Authentication_with_Client_VPN#Add_MX_Security_Appliance_as_RADIUS_clients_on_the_NPS_server   On an intranet, If your MX uses a static route to reach out the NPS Server, you will have to use MX IP of network segment used by this route. If your MX relies on VPN tunnel to reach out NPS, use the MX IP of the highest-numbered VLAN Interface set "in VPN"   I hope it helps ... View more

If I remember correctly, the behavior is to pick the interface with the highest VLAN for radius trafic   I remember I used to configure a dummy VLAN 1000 for this purpose ... View more

When I was playing with MX68CW and Verizon SIM Card a while ago, I was able to make it work using Verizon APN "vzwinternet"   As far as I remember, it was the only one stricly requiring an APN to make it work  ... View more