Comments
-
Your jobEngineservice looks to be high. The easiest way to address this issue is to open a support ticket so we can take a closer look at your environment. Thanks, David
-
I don't have an answer for you, but I would like clarification... "Whenever I change the port description".... Are you changing it via Orion, or via the MRV? I assume via the MRV, and when the device is rediscovered, it's marked as unknown.. correct?
-
Exit my shot in the dark, I'll try and verify for you tomorrow.
-
I'll take a shot in the dark and say it's because those VM's have SNMP enabled?
-
Mromeo, As you are certified; I'll start a little higher up the troublshooting chart. First of all, are you getting these errors for all Alerts that are triggered? The error message is self-explanatory in a sense - that the service timed out. However digging into the "why" it timed out can sometimes be a task. I've found…
-
The best thing to do is to go into the Solarwinds Syslog Viewer and set the "retention time" to a lower limit... My guess is you are at 180 days, and unless you find that information useful, I would lower it to 7-21 days. In order to clean your database out, I would recommend truncating the syslog table (you will lose all…
