What is our primary use case?
It's for IP address management. It has been more than 12 years since I have been using SolarWinds products in this firm. We are using seven to eight models of SolarWinds, such as SAM, IPAM, Virtualization Manager, UDT, and NPM. Over these years, we have done customizations and created so many dashboards and alerts that it's quite difficult for us to switch to a different application because we would have to do that customization again. If I bring new applications to my firm, I would need almost two years to make that equivalent to what we have now with Solarwinds.
How has it helped my organization?
We have an on-prem environment where we keep on deploying servers, etc. So, we need a tool like this to keep track of the static IPs. This is the only application that we use, and we are happy with this.
What is most valuable?
Its setup is simple. Its interface is simple. It's very easy to manage.
What needs improvement?
My understanding is that IPAM cannot be used for the AWS environment. I might be wrong, but that's what I believe it cannot do. On AWS, SolarWinds IPAM cannot do what it does on the on-prem side. They should explore how to make IPAM capable and scalable on AWS and Azure environments.
For how long have I used the solution?
It has been more than 12 years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
It's not about scalability. It's about IPAM's capability. IPAM is not capable enough to manage the IP address on AWS. I can scale it to AWS, but it's not going to perform how it's performing in the on-prem environment.
In terms of the number of users, SolarWind IPAM is completely administered by my team. We are 18 in number. We are using it very frequently. It's almost on a daily basis.
How are customer service and support?
About 10 years ago, support was very good, but in the last two to three years, we are observing that the support quality has degraded in terms of knowledge and responsiveness.
In some cases, we had to escalate to the account manager or territory manager, and even then, I didn't find them helpful. This is the level of support that we are getting. It's because of the number of SolarWinds users they have now. Sometimes, they take a long time to receive our call. Sometimes, even when they receive our call, if we are looking for some urgent solution from them, they download files and ask us to give them some time to get back. They might take half an hour, or they might take one, two, or three hours. During that duration, my system is down. They're not able to provide quick responses nowadays.
How would you rate customer service and support?
How was the initial setup?
It's very easy. I would rate it a five out of five in terms of the ease of the setup. We are not just using IPAM. We're using multiple modules of SolarWinds, and in a single day, I can bring up my entire SolarWinds setup. It's very simple.
What's my experience with pricing, setup cost, and licensing?
It's on the costlier side. It's expensive.
I haven't explored other applications in the market. I have seen a couple of open-source ones, which are comparatively low in price but they can't be exactly compared to SolarWinds. IPAM is an expensive solution for any firm to adopt.
What other advice do I have?
It's on the costlier side. If you can afford it, I would definitely recommend going for SolarWinds because it's simple and easy to manage. It depends on how much you want to spend on an IPAM tool. If you do not have a very big environment, then you can also manage IP addresses in a simple Excel sheet, but for a very big environment, you would need an IPAM tool.
Because I'm still not able to utilize my IPAM on the AWS cloud environment, I would rate it a 7 out of 10, but I'm happy with it on the on-prem side.