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
Store

IPLSA not writing changes to memory

I had to make some changes to IPSLA tests and noticed that the new changes are in the running config but not start up. IS this a bug or something? These changes should be written to memory after they are made.

Find more posts tagged with

Accepted answers

All comments

mcbridea

IP SLAM does not write to start up config. If a device reboots IP SLAM sees the missing config and replaces it. This is only true if the IP SLA operation was created in IP SLAM.

BryanBecker

Ok...however this is causing a problem with our backup system saying there is a discrepancy between running and start-up configurations. If IPSLA is writing to the config can you make it write to memory?

BB

mcbridea

I see. IP SLAM won't write them to startup but I'll let the PM know you are interested in this. Is it possible to make an exception for IP SLA configs discrepancies or manually copy run to start? Once you have your configs set they shouldn't change, so it's not something you'ld probably have to do very often.

BryanBecker

Making an exception would be somewhat hard to code (not using NCM) and we could run a write mem job but if IPSLA is making a change I think it would be best that i t also write it to memory.