Seek advice on automating (scheduling) detection of unsaved configs. Say, running config is archive is > 24h old and it is still different to startup config. Is there a way to get an alert for similar condition with PI 3.1 ?
Essentially, the purpose is to tackle risk of device (router or switch) restart using an out-dated config.
The plan B is to schedule daily 'copy run sta' across the board, but it does not look pretty and might interfere with config management history.