Comments
-
I did select 2 answers, I just thought it was strange it said, the 4th answer was not part of the Secure by Design, or maybe it is and I missed it?
-
May 20th question. - I think I answered this right, but it popped up and said, the 4th answer is not part of the Secure by Design - but I did not select that option. I have a screen shot. thanks
-
Side note - We noticed that if we are in Aruba Orchestrator modifying settings, SolarWinds starts to report nodes are down. Packet Loss. Really strange. Resets fine once we are done working in Orchestrator.
-
We modified the following to 30 seconds, and we are not getting the constant SDWAN Down alerts. Seems to have fixed it but still monitoring. * RequestsLimitationPeriod: The limitation period. By default, this is set to 00:00:05 (five seconds). Make the limitation period longer to reduce the number of API requests.
-
Finally got an error from the SW side of things when SW loses connection to the orchestrator - "Polling stopped because the orchestrator API token has expired. Provide a new API token in the Edit Node view". We waited like 10 minutes, and it came back on its own. Still troubleshooting....
-
I have started to make small changes, and it does seem to help but I am still testing. I will report back on how this works.
-
We are using the out-of-the-box alert for Node is down. There is also a "SD-WAN Edge is Down" boxed alert, but it does not seem to work. SolarWinds sends an alert of node is down when I know it is not. When you visit the Orchestrator Device or Edge device page, it shows 100% packet loss. We are monitoring the Orchestrator…
-
Your right. I just took a quick look and yes, we have most of our servers being monitored via SAM. They are on negotiate. Thanks for the info!
-
Anyone having issues installing the Agent using the token? When I enter the token info it says it cannot be verified at this time and asked if I would like to continue. I click continue and the install fails to install the agent after 3 attempts. Just curious if anyone else having this issue.
-
Ok, still working this issue. Support has sent me a couple of fixes, one of which the instructions didn't match my install for some reason. Then I was escalated and told to Perform a fresh Orion installation (uninstall and reinstall) on the same Windows server. This did not resolve my issue. Anyone else see an error like…
