Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Select all devices with config mismatch and execute script?

Is there away to select all devices that have a config mismatch so I can quickly push out a copy-run-start command to all of them at once? When I click on the devices with config mismatches my only options that I see are to download the config, which isn't going to solve the problem.

Find more posts tagged with

Accepted answers

All comments

christopher.a.thornton

Hi enderaz,

I was looking through my NCM instance and I think I see what you are talking about. That area is not talking about a config mismatch on the device itself, though there may be one. What the graph and list are saying is that there are difference between the last downloaded running configuration and the last downloaded startup configuration. Those configurations could be months apart actual as is the case with some of my devices. I am not sure if you are backing up the running configuration and startup configuration every night, but if so then those mismatches are true. But if not you may want to download a fresh copy of the startup config from the devices in violation and see where they stand at that point. Hope this helps a bit.

Chris

enderaz

We are doing an initial setup of Solarwinds. These look to be actual mismatches between the running config and startup config from when our previous config manager (Prime) didn't write to startup config. I was looking to push out a write script to all of these devices, but I see no easy way to select all of my devices with a configuration conflict and run this script.

christopher.a.thornton

Ok I get what you are saying now. I am not sure of an easy way to select just the nodes that have a configuration mismatch to perform a write on them. If it were me I would just make a job to write the config and push it out to all of the devices so that way I know all of them were good. Not sure if that is something you would be wanting to do though.