Meraki API problems

Anyone else had issues with Meraki API since last Windows update?

Our monitoring stopped working at 4am on Monday coinciding with our patching. This will also be the first reboot since installing latest Solarwinds versions too. Since then all Meraki AP's and the orchestrator were showing offline in Orion and getting "Failed to get list of organizations" when clicking to get organizations.

Running a test from the 'proxy setting' page in Orion the api was reporting a TLS issue. I ran tests from the server in powershell and determined the issue was with TLS1.2 not being allowed. I set TLS1.2 to enabled in the 3 place of the registry I think is required and after changing the .net key the Powershell tests were succeeding.

I am now getting a response from the 'proxy setting' page to the api (albeit a 401 due to me not being able to send the key at this point) but it is obviously hitting the endpoint however the node is still reporting "Failed to get list of organizations".

I notice that no matter which poller I assign the node to I still only get entries in the logs on the main poller. In there I can see the latest module is loading in:
"*** Assembly SolarWinds.Orion.Orchestrators.Meraki.Common, Version=2023.1.0.0, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***"

I have deleted the node but now unable to add back due to this error.

Find more posts tagged with

meraki

tls1.2

Accepted answers

All comments

victorg89

I'm facing the same issue.
Even after removing windows update is still reporting "Failed to get list of organizations"

bmrad

Haven't seen this before, go ahead an open a support ticket, upload diagnostics and post the ID back here.

osborne_graham

Thanks both. I logged ticket last week (Case # - 01297645). one person confirmed the cert errors from the diagnostics and said tls is configured on the server not solarwinds (which I know however there are a number of different places where it can be set - i would have thought orion would be using the .net keys which i can confirm work fine through powershell from the poller locally) and another sent me the initial configuration instructions and asked me to double check the key is correct, possibly missing my note about it working fine through powershell nd has been fine for 18 months+ with no config changes. I've been out of the of the office so not replied to the last one yet but if anyone has any ideas in the meantime I'd be very interested to know.

RAJPAD

Im having a similar but not exact issue on my side. Orchestrator stays online for a few days and then completely node down, 100% packet loss.

response frrom support case [tag:01287450]

In HCO (Hybrid Cloud Observability) we do not use PING (ICMP) requests for Response Time measurement like it was in NPM.
Instead, we use [HTTP GET request] to the Meraki API server which usually takes longer as it is bigger and contains some payload.

Based on the information you provided, to overcome the problem you may edit node settings and change default Response Time thresholds. For example, 10000ms for Warning and 20000 ms for Critical.