With the $base_uri = "https://api.meraki.com/api/v1/organizations/12345/" - 12345 being the org_id displayed at the bottom of my meraki dashboard page in Web_UI , I run the command as .\MerakiPSKTool.ps1 -site <sitename> -ssid <ssidName> -action Display The errors are : === Displaying Wifi details Network Name : NetworkName id : Network_Id Type : Invoke-WebRequest : Page not found The page you are looking for may have been moved or does not exist. To log in to the Cisco Meraki Dashboard, go to https://dashboard.meraki.com.© 2024 Cisco Systems, Inc. At D:\scripts\amagi\MerakiPSKTool.ps1:90 char:14 + ... $r = Invoke-WebRequest $request_uri -Method:Get -Headers @{"X- ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand ConvertFrom-Json : Cannot bind argument to parameter 'InputObject' because it is null. At D:\scripts\amagi\MerakiPSKTool.ps1:92 char:19 + $z = $r | ConvertFrom-Json + ~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidData: (:) [ConvertFrom-Json], ParameterBindingValidationException + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.ConvertFromJsonCommand === ... View more

PPPoE sorted at least. Turns out there is a bug which was fixed in 18.107.3 which causes the WAN port to be disabled when the PPPoE credentials are set. The challenge with that is you have to re-enable within the dashboard but unless you connect up a second (direct) WAN connection you cannot connect the device to the cloud.   All good now but we have to upgrade the firmware of all of our boxed new MXs using a direct connection prior to deploying them to site with PPPoE.     Now just waiting on a fix for the custom APN but for which we do at least have a workaround.    ... View more

Hi @SimonT    We have been experiencing this very same issue at one of our sites. Symptoms are identical, both the MX and Cisco switch are set to auto duplex/speed and the port will not come up. Plug a laptop into either the MX or the switch and the port comes straight up. Often then plugging the MX back to the switch and it will then work. Once up it will work without issue until the unit is powered down for maintenance. We also had a very similar experience where the port would not come up and then over a weekend after leaving the devices connected we found the port had come up.   As has been mentioned seemed to be some strange negotiation issue, we assume a bug but unsure if the bug sits on the MX or switch side.   We have a Meraki MX84 (ver. 15.44) and a Cisco C2960X (ver. 12.2(2)E8), out of interest what are you running in your environment?   We have yet to try fixing the port speeds/duplex on both sides or upgrading the switch IOS. The issue is once the port comes back up the device is then in use so we don't get the chance to troubleshoot.   Interested to hear if any others experience similar issues. @Meraki2 Any other reports you have seen of this on your side?   Jason ... View more

Did you ever find a solution to the lack of manual network selection. We have started using the MG21Es with mutli/world SIMs and also find the auto network selection to not be optimal. Sometimes results in the unit connecting via 3G when a perfectly good 4G signal is available on another network. Our sites often run on temporary generator power which is shut down overnight so it might work one day and then the next day we end up with a different carrier.    Manual network selection options are needed, have this on a 'basic' brand 4G modem/router which is also a quarter of the price. Also any manual APN settings have to be done locally on the device and cannot be set via the Meraki dashboard. Nice idea having the management all in one place but not sure these units are quite up to scratch yet.   Just seen a MG41E is about to launch, perhaps this may improve on this.  ... View more