Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About JasonM_PDX
JasonM_PDX
Here to help
Member since Apr 9, 2018
Apr 30 2020
Community Record
5
Posts
1
Kudos
1
Solution
Badges
Mar 14 2020
2:46 PM
1 Kudo
Update: Switching to a non-wildcard cert fixed it. I replaced the wildcart cert that was in place previously with a single domain cert through Let's Encrypt as a test. Once the new cert was in place, I was able to see the Dashboard servers hitting my webserver again and actually showing up in the access log.
... View more
Jan 15 2020
12:30 PM
The webserver does have a publicly issued valid certificate. The certificate is a wildcard, but that was previously working. I have tried removing and re-adding, but maybe I missed a network as not all of our networks are on our primary template. So, I'll try that again. Thanks for the suggestion.
... View more
Jan 14 2020
5:27 PM
I've been encountering an issue with using the webhooks. I had a webhook set up and working great for several months on two of our organizations, but then I stopped getting any requests from the Dashboard to my webserver. I can intentionally generate a down or up event that would previously hit the webhook, but I won't ever see a request in the Apache logs. If I use the "Test" button in the Dashboard Alerts page, I get an error back and still no request. I have confirmed that the webhook script is otherwise accessible from external services, it is HTTPS enabled with a valid (wildcard) certificate, and all other requests show up properly in the webserver logs. An interesting thing I found is in the following snippet of webhook logs requested from the Dashboard API: { "organizationId": "XXXXXX", "networkId": "N_XXXXXX", "sentAt": "2019-12-04T07:37:35.993999Z", "loggedAt": "2019-12-04T07:37:36.118000Z", "url": "https://webhooks.example.com/alertHook.php", "alertType": "Cellular went down", "responseCode": -1, "responseDuration": 122 }, { "organizationId": "XXXXXX", "networkId": "N_XXXXXX", "sentAt": "2019-12-04T07:37:41.061000Z", "loggedAt": "2019-12-04T07:37:41.181999Z", "url": "https://webhooks.example.com/alertHook.php", "alertType": "Cellular went down", "responseCode": -1, "responseDuration": 120 }, { "organizationId": "XXXXXX", "networkId": "L_XXXXXX", "sentAt": "2019-12-04T07:48:25.513000Z", "loggedAt": "2019-12-04T07:48:25.727999Z", "url": "https://webhooks.example.com/alertHook.php", "alertType": "APs went down", "responseCode": -1, "responseDuration": 214 } All the request logs indicate a responseCode of -1, but unfortunately, I'm unable to find any documentation (like almost all of the API) indicating what that return value means. I would obviously expect it to be the HTTP response code, but since it never hits the server, it makes sense it doesn't have one. I'm hoping that someone else has seen similar and can suggest what might be causing this. My assumption is that it is an issue with the config in the Dashboard, but I've tried removing/re-adding it, changing it, and otherwise tweaking with it while maintaining the key pieces with no luck. Thank you in advance for any help/suggestions.
... View more
Labels:
- Labels:
-
Dashboard API
-
Webhooks
Nov 30 2018
5:36 PM
Yeah, that's the conclusion I've come to as well. I'd have to make the AP networks separately and then manually do the combine action. And yeah, adding an additional device type to the network converts it to a combined network with no issue at all, when done from the Dashboard. When attempted from the API, it gives an error. I'm only trying to change the network type ahead of time in order to be able to add APs to the networks. If there was a way to add the APs via the API and have it automatically change the network type, I'd be very much down with that too.
... View more
Nov 30 2018
1:03 PM
I'm working on automating a wireless deployment. We currently have each of our branches using an MX appliance, and have set each network up as an appliance or wired network, rather than combined, so that configuration sync would work. Now however, we're adding AP(s) to each branch. When trying to add an MR device to the network via the API, I get an error that I "Cannot add devices of wireless to a wired network". Alright, that's fair. I'll just change the type of the network to combined first. But, there's apparently no option to change the type on an existing network. I found that the network creation call has an option to define the type, but the update call does not. I also looked to see if the Dashboard interface itself has an easy way to bulk convert networks from appliance to combined, but that doesn't seem to be possible either. I considered creating each wireless network as its own network, and then combining them into the appliance networks, but there doesn't appear to be a programmatic way to combine networks either. While manually combining the two networks for 250 branches would be do-able, and still an improvement over no automation, it's not ideal. So, my question, is anyone aware of an effective way to change network types via the API? Or is there a better way to achieve the goal of adding an AP to an existing appliance network? Any help/ideas are appreciated. Thank you.
... View more
Labels:
- Labels:
-
Dashboard API
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 2546 | Mar 14 2020 2:46 PM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 1 | 2546 |
© 2024 Cisco Systems, Inc.
