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

revert changes when one of the script commands failed

jacobco

so if one of the commands was not recognized it would not skip on it and marked it as a success

it could be fatal if you're trying to configure tacacs and one of the commands failed but the auth still changed

Find more posts tagged with

Status: None

Comments

rschroeder

I like your idea, but I can see cases where reverting wouldn't be possible--particularly regarding security like TACACS. If you change the IP addresses of TACACS servers, or their PSK's, or other AAA settings in a Cisco device, from that point onward NCM (and YOU) will be unable to make corrections to role back mistakes.

There are other, similar changes that wouldn't be able to be rolled back (you changed the node's IP address, mask, gateway, certain ACL's, etc.).

Of course, it all relies on us making the right changes, avoiding typos, knowing what we're doing, knowing the results of the changes we apply before we make them.

If we're only talking of being able to roll back changes that don't isolate the equipment from us, I support your request 100%.

Swift Packets!

Rick Schroeder