By default integrated LTE would be the path of last resort. Meaning only active when WAN 1 & 2 fail. However, you can override this behavior by enabling "Cellular active uplink" on the Security & SD-WAN > SD-WAN & traffic shaping page. This makes WAN 1 & cellular the active uplinks (instead of WAN 2).   https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/Meraki_SD-WAN#SD-WAN_over_Cellular_Active_Uplink ... View more

It would make more sense to have the same fast circuit for both MX'es WAN1 and the same slow circuit for both MX'es WAN2 and then use the mobile backup as Cellular failover link (you can deploy the failover WAN3 option on the newer MX models). This way if WAN1 fails, it will fail for both MX'es and you have a more determinate failover scenario. However if circuit 2 is too slow then it would make no sense to use it.  If your mobile service is faster I would use that as WAN2 then but also on both MX'es. ... View more

I havent done it yet, but it seems simple enough, just go to ekahau.cloud, go to your project inslight, click export and enter Meraki API key     ... View more

There's no published API call for this.   There are two early-access API calls that can be used to calculate availability (not differentiated between device/ISP failure, but probability is that mostly it'll be ISP failure rather than device failure)...   Currently we calculate availability across multiple organizations by using this call to log status every 5 minutes, then use the date to calculate availability across the SLA period... https://developer.cisco.com/meraki/api-v1/api-reference-early-access-api-platform-monitor-devices-statuses-get-organization-devices-statuses/     There is a potentially more efficient way using the newer call (I'm not migrating to it unless/until it goes general release)... https://developer.cisco.com/meraki/api-v1/api-reference-early-access-api-platform-monitor-devices-availabilities-changehistory-get-organization-devices-availabilities-change-history/   ... View more

Hi @Vbardy , it’s only the management IP so wouldn’t panic too much especially if the device is registered to the cloud and the network functioning.  Change the IP out of hours  ... View more

The best place to see firmware changes is under Organization/Firmware upgrades.   It doesn't tell you the prior firmware, but if it was a recent change you can click the "rollback" button to revert the change.   Errors should appear in the event log - but I would hope that they are a rare event.   ... View more

Hi Blake,  The person requesting this wants the 8 switches onsite to have the ips assigned in top down order in that management vlan scope.  We use templates so not sure if the local admin page for the switches would be an option.   So my plan to do this by adding the reservations one at a time and rebooting the switches sounds like a reasonable approach? Can you please let me know your thoughts.   Thank you.   Rgds, Vicky ... View more

yeah but cat5e is soooo much better then the cat3 or pots quad that is likely hanging off the 6P2C RJ11...   The devil is in the details about the actual cable and  how it was really ran and terminated.... Likely ran by an electrician... YUCK!☹️   The person asking this question about RJ11 to 45 is likely in way over their head.   best scenario is all  home runs, not on 66 blocks, runs are <=90m AND its cat5 or cat5e with the blue pair terminated and the other three pairs wrapped or clipped on at least 18 inches of service loop of inches of slack cable.   Worst case is complete raw sewage show ... View more

Yes a long as you create the VLAN on the SB switches you are fine. I have done exactly what you are trying to do at home with my MX and MS and a small business 10 port switch in my garage.   It wouldn't be much of a home network with VLANS 😂 ... View more