Automatically Recovering Corrupt Configuration Files - Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual

JUNOSe 11.1.x System Basics Configuration Guide
that you run the manual command to check the file system before you enable HA
or perform any unified ISSU-related operations
service check-config
service config-monitor-periodicity
show service config-monitor-periodicity

Automatically Recovering Corrupt Configuration Files

You can automatically recover corrupted CFG files detected in the running
configuration.
272
Monitoring the Current Configuration
Use to detect corruption of running configuration files and CNF files on the
primary SRP and the standby SRP when it is due to a fatal duplicate key error.
You cannot monitor CNF files on the standby SRP.
Auto mode checks the running configuration at regular intervals; auto mode
cannot be used for CNF files.
Use the default version to restore the default setting, manual detection.
Example
host1(config)#service check-config auto
Use the no version to restore the default action, manual detection.
See service check-config.
Use to set the time for background monitoring of the active and standby SRP.
By default, background monitoring is not running. For corruption detection of
the CNF files, you must use manual mode.
Auto mode checks the running configuration at regular intervals; auto mode
cannot be used for CNF files.
Use the default version to restore the default setting, manual detection.
Example
host1(config)#service config-monitor-periodicity 2000
There is no no version.
See service config-monitor-periodicity.
Use to display the time of the monitoring task for detecting corruption of a
running configuration on both the primary SRP and the standby SRP.
Example
host1#show service config-monitor-periodicity
config-monitor-periodicity = 2000
See show service config-monitor-periodicity.