Comments
-
Andy, are you saying that there is no way the prevent a reset alert from firing under any circumstances? The logic is totally independent from the alert action triggering? I think most of us assume that a reset firing would be contingent on the trigger action firing, and that any reset delay is appended to the trigger…
-
Please send me the template also, Christine.
-
I had the same errors and resolved it by taking out the underscores_in_the_report names in the reports folder.
-
This is a way to disable it at a poller level. Go to the installation path, for example, C:\Program Files\SolarWinds\Orion and find the following file. SolarWinds.Orion.Core.BusinessLayer.dll.config Open the file with Notepad and set the property TopologyEnabled="False"
-
I know that this is not currently possible with the current version of NPM. Depending on what you need, you can create a Scheduled Task that runs a SQL query to update the Orion Node name with either the SysName or DNS name value.
-
I have tried about 10 different fixes already w/o any luck, but I am starting to think it may have to do with the re-partitioning of the drives. The software originally gets installed w/a key that I believe generates a serial # based on a hash of the HW and system, which may not match now due to the change. I wanted to…
-
The changes made to the organization of reports in v10 is a disaster and needs to be corrected so that we can supply the reports in a logical way to users.
-
Node caption is populated in the following priority during the node add: * sysName SNMP value returned (if SNMP responds) * Reverse DNS lookup * IP address Node Caption DOES NOT get updated automatically any time after the node loading and must be manually edited.
-
The LastError field in the AlertDefinitions table in the DB will show which Alerts are causing the errors. Disable and troubleshoot as needed.
-
Harold, I had a similar problem. In my case I needed to modify permissions on the web server. For whatever reason nobody at 1st level SW support offered a solution even though permissions is the obvious place to look. Add xxx\Domain Users to the following on your Primary Orion Web Server: * Add to the local system 'Users'…
-
We need enterprises.2197 for our RSA servers
-
I totally agree this is a gap that needs to be addressed. I have set up an alert based on the availability of one of core routers being UP which send me regular emails and writes to the NPM events so I can confirm the alerting service is working. In addition I have APM monitors/alerts for Netflow services along with file…