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

Running vs Startup not accurate

I am using "since last update" and it is showing that I have one config that isn't right. 1 device out of 7 total and the percentage on graph shows 25%. The real kicker is that I removed all startup configs from the device and no longer back up startup configs. The device still shows as not matching. How do I clear this alarm mode out and why does the percentage not seem accurate based on the number of nodes?

Find more posts tagged with

since_last_update

Accepted answers

All comments

chris.lapoint

Can you try downloading the running config on your devices to update the comparison cache and see what happens?

brian_duvall

I have but the issue remains. As if it still thinks there is a startup config for that device even though it was previously deleted.

brian_duvall

I ended up clearing all configs for device...attempting to pull down running config. This didn't resolve it so I set the "saved" config pull as the same command for running config to get it to clear the alarm. Then deleted the saved config and all is well now. Seems like alarm will only clear once you pull saved and running and they match. Seems obvious but if you stopped pulling saved configs its a problem.