Comments
-
So--- I just built a new instance for my company this one on 2019.4. I ran into the same issue. I would hope there is a better way to do this, but i will share what worked for me anyway. I went to Settings> all settings> virtualization settings>Virtualization global thresholds> I then (one by one) took note of the current…
-
I ended up doing an upgrade to the newest platform and the issue resolved itself. Sorry for the delayed response. I am now running NPM 12.5 and the issue has not reoccurred.
-
serena Thanks for the response. So that is what is so weird. The alert IS set to exclude powered off nodes. The VM is powered off, but still shows green in SolarWinds.
-
Thanks for the advice. I ended up having to kill IPAM all together, but once I removed my DNS and DHCP servers and all the scans cleared, I was able to ping and noticed my server performing operations much faster. I am planning a rebuild on Hyper-V in a few weeks, and I think i will just place IPAM on a separate server as…
-
Not sure if this is detailed enough, but here is part of how we group things. At a high level we group by location, then application. (using custom properties and dynamic queries to add things in the future automatically.) Then I have three groups under the "ApplicationName_Group" called "ApplicationName_NODES",…
-
I had this issue when upgrading my APE to (2019.2) NPM12.5. I never found the packagecleaner.exe so I ended up renaming my Repository folder to repository.old and copied the folder over from my primary server. Ran the configuration wizard again and it completed successfully. ( C\:\Program Files…
-
So... I have three networks and three instances of SolarWinds. On two of them, the servers seem to run fine with IPAM (v4.9) included with the primary. However, on my largest network, I discovered one day that I couldn't ping anything from that server. I found that other poeple had the same issue. I also noticed my website…
