We have IPAM running as a module within the NPM.
IPAM is failing with SQL errors. Is it possible to re-configure the IPAM to access a different brand new database ?
Currently, the IPAM info tables are within the NPM database.
You'd have to break out IPAM I believe onto it's own server. There wouldn't be a way to configure it to another SQL server while still installed on the NPM server.
Can't I uninstall it and install it on the same server and point it to a new database. I don't mind redoing the whole IPAM setup again.
No on both. If you uinstall and reinstall it on the same server, it's going to simply add as a module. If you try on a separate server, it will be it's own app separate from the SolarWinds website. There's no way to integrate it without having it installed as a module using the same database.
The IPAM 4.2 is failing to after 67%, with the error,
An unexpected error has occurred when processing DHCP scopes results for server '1703'
Solarwinds support is pointing it Storage latency. the Database is on SSD and so far no issues we have seen
So, I thought it will be possible to move to another Database.
Any other ideas I can have ?
So why are they pointing to Storage latency? Did they give you a reason, or just that it has to be storage latency? How many scopes are on that server? What other modules do you have installed other than IPAM?
there is nothing really pointing to the latency.
from the IPM business layer log, this was seen,
2014-10-21 05:22:35,390  ERROR SolarWinds.IPAM.ScanningEngine.JobProcessor.JobProcessorBase`1 (null) - An unexpected error has occurred when processing scan results for subnetid '3409'
System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
There only NPM 11.0.1 ,NCM 7.3.2 and IPAM 4.2.
However the IPAM was working and some intermittent issues used to get reported, that used to vanish. A month ago it stopped working completely and then it was upgraded to fix. Since then it stopped working altogether.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.