Can SNMPv3 write to config or only to the MIB & running config?

Question

We have configured SNMPv3 with the write views to be able to write the cisco device, but we do not see the config manager accounting for the changes since the changes are not being saved to NVRAM. The changes do appear on the running config but not on the startup config. What step are we missing to get this to behave like a CLI change that any one person does. Much help is appreciated. Thank you.

FormerMember · Answer

I think what amondol is asking is if IPMonitor can have a "copy running-config startup-config" command added to save the current running configuration to the startup configuration file in NVRAM.

JasonFerree · Answer

I'm not sure I 100% understand your question.  IP SLA manager will write to the running config.  That is how the operation will then start performing its polling.  It will not write to the start up config.  NCM should also show when any config changes are made to the running config.  With NCM if you are always downloading the startup config you will not see the operations added.  If you download the running configs then you will see when the operations are added.  If you look at the NCM start vs run config report you should also see the difference.

amondol · Answer

Can IP SLA manager be made to write to write the config? Otherwise there is not that checks and balances since config manager will not pickup on an operation that might have been put in place. Thank you a head of time for your reply.