If you were talking to someone whose organization is considering SolarWinds Network Configuration Manager, what would you say?
How would you rate it and why? Any other tips or advice?
Just make sure you only put the nodes that you need to monitor and make sure whoever needs to have nodes in SolarWinds, keep the people besides your team or your group, who want their own nodes there. Make sure you set up the right rules and the standards and the thresholds where you need to get communication for error messages or CPU alerts or power heat or any type of alerts. The alerts, they need to be very clearly addressed in order for you to monitor your devices. We have faced some problems in the past that the alerts are not really set up properly. We have to randomly change the thresholds and the numbers and the ranges. I would recommend that you make sure you monitor only what you need to monitor. Make sure if you need to trigger those alerts, make sure that you have somebody or a team to respond. And, they can have a group responsible for whatever they need to troubleshoot. I would rate it at a seven out of ten.
We are using version 7.9 of the solution. We migrated from 7.7 to 7.9 about three years ago. We use both the cloud and on-premises deployment models. We had production on the on-premises model in 2016. I'm an implementation engineer for SolarWinds so I'm not using the NCM devices any longer. I'd advise others who may be installing the solution for the first time to just use the 7.9 version of the solution. It's the latest version. If you are using FortiGate you'll be able to configure everything and have a backup and be able to use the data. I'd rate the solution eight out of ten.
We use the on-premises deployment model. We're a SolarWinds distributor. I'd rate the solution nine out of ten.