Network Configuration Manager is well suited for backing up configurations of all your devices. It also has a great comparison tool for seeing only the differences in config. Another great feature is it's ability to push a script to any number of devices. This is very handy for pushing changes to one, 10 or multiple devices. There are also some great reports that you can run against the devices in inventory
On its own, it's a solid choice for an SMB or Mid-size Enterprise if you're price sensitive and looking primarily for core functionality. SolarWinds has a large family of products that can also be leveraged in conjunction with SWNDM. Turning the product loose on a very large environment for discovery and mapping should be done with care and concern for a number of reasons but including the performance of the product for this task. If you're looking for an all-in-one product with some presumed supporting features built in (config manager, etc.) you'll need to look elsewhere.
For our use case, it does everything great and some of the features we underutilize but I would like to be able to set a configuration baseline when initially adding a node instead of after the configuration is pulled but it's not a particularly big deal to let it pull the configuration then set it as the baseline.
Medium complexity to set up in the beginning if using any non-standard devices or configurations, else fairly easy (e.g. Cisco Nexus or IOS-based devices). Reports are fairly straightforward to set up. Updates to the platform are fairly straightforward and don't take a major effort. Easy to add or remove devices.
The user interface is lacking. It is difficult to navigate at times and things can be done multiple ways. Quite often I am confused by how their notification structure works. It is not very intuitive. They do offer a free Academy. They also offer a community of other technical folks. I have enjoyed both.
To be fair, I have not had to involve Support in a number of years, but when I did, I was greeted with enthusiastic engineers who wanted to understand and solve the issue. It was a fairly complex scenario and I have discovered in my most recent implementation that engineering included that option as a standard now.
Solarwinds has actually produced new training since I last used it that is available on their site at any time. Their previous training was more than enough to get us started but now there is significantly more content. Since I'm comfortable with the Orion platform and the products we use I haven't checked the new training out yet but we have new staff go through portions of that training and they always come away with an understanding of the platform and ready to use it
it was a fairly easy implementation and everything was pretty straightforward. only challenge we had was getting all the snmp communities updated on the networking equipment
At the time SolarWinds was the biggest player in the space and their whole portfolio was very comprehensive. As time progressed and newer technologies came about (i.e. SDWAN) their products couldn't keep up with the consumer demands and changing market. Security became such a big focus that once Solarwinds got hacked we had to remove all their products from our environment
MS is meant for windows monitoring and up/down for mostly everything else. Moved away from MS System Center. Now we have better visibility and management can get reports. The other teams have added Linux to Solarwinds and also see improvements in monitoring. Whether you use snmp (v3), wmi or some other credentials to connect to you system, Solarwinds will more than likely be able to manage and monitor it.
Saves 100s of hours a year in man hours over manual configuration.
Saved easily 50k in lost revenue when a switch rebooted with months old unsaved configuration. NCM let us quickly restore a snapshot of the running config from the previous day.
Saves us several man hours per week of config auditing by reducing all changes to a summary email.
