Hello,
We have an Orion IPAM instance that is running as a module on our Orion NPM server, along with SEUM, UDT, SAM, NTA and the IPSLA Manager. We have received quite a bit of complaints about the Orion site being too slow. Our users also complain about frequent downtime, which happens every time we upgrade or during troubleshooting NPM or any of the modules on it . So, we are consdering the option of moving IPAM to a standalone VM server instance. However, before we attempt this, we would like to truly understand all the pros and cons for this potential IPAM move. We already know that we would have to use the Import feature, which is not ideal, since we have to import subnets on an individual basis. That won't be much fun at all, and would prefer to see the IPAM developers offer a fool-proof way to import and export ALL of the IPAM data.
Anyway, back to the original issue at hand. I searched the SolarWinds website and also the Thwack forum. However, I could not find any specific postings listing pros and cons for running IPAM as standalone vs. as a module. So, I would like to know...
- Besides the issue of having to import individual subnets, and having to support a separate server and DB.., what are the drawbacks for running IPAM as standalone?
- Besides a faster application performance and smaller database, what are the benefits of running IPAM on standalone?
- Also, about running IPAM as a module? What are the pros and cons for this?
Thanks in advance!!!