Symptom
Startup-config is not saved to stby-nvram filesystem on system that require configuration sync when utilizing CISCO-CONFIG-COPY-MIB. Examples of impacted devices include switch stacks or switch/routers with redundant supervisors/route-processors.
Conditions
Use CISCO-CONFIG-COPY-MIB to copy running configuration to startup configuration.
Executed on system that had redundant filesystem.
Further Problem Description
+ To save running configuration to startup configuration, utilize similar commands to the following:
snmpset -v3 -l authNoPriv -u -a SHA -A '' -m CISCO-CONFIG-COPY-MIB .1.3.6.1.4.1.9.9.96.1.1.1.1.14.{job_id_integer} integer 6 <- Delete Existing Job
snmpset -v3 -l authNoPriv -u -a SHA -A '' -m CISCO-CONFIG-COPY-MIB .1.3.6.1.4.1.9.9.96.1.1.1.1.3.{job_id_integer} integer 4 <- Copy Run
snmpset -v3 -l authNoPriv -u -a SHA -A '' -m CISCO-CONFIG-COPY-MIB .1.3.6.1.4.1.9.9.96.1.1.1.1.4.{job_id_integer} integer 3 <- To Start
snmpset -v3 -l authNoPriv -u -a SHA -A '' -m CISCO-CONFIG-COPY-MIB .1.3.6.1.4.1.9.9.96.1.1.1.1.14.{job_id_integer} integer 1 <- Execute
snmpwalk -v3 -l authNoPriv -u -a SHA -A '' -m CISCO-CONFIG-COPY-MIB ccCopyState <- View Job Status
+ Once complete, validate issue by runnning:
more stby-nvram:startup-config | include {command that was changed}
