service check-config
Copyright © 2010, Juniper Networks, Inc.
When duplicate key corruption is detected in either the active or standby SRP:
File synchronization between the active and standby SRP occurs when HA is enabled.
Configuration files are not synchronized to the standby SRP when corruption is detected
and the auto-recovery option is disabled. You can restart file synchronization of
configuration files only when you reinitialize the flash file system on the corrupted SRP.
If HA is disabled, you cannot enable HA until you reinitialize the flash file system on the
corrupted system. HA is disabled because of the redundancy corruption criteria. HA
cannot be reenabled until the flash file system is reinitialized on the corrupted system.
You cannot initialize unified ISSU until you reinitialize the flash file system on the
corrupted system. If the corruption is detected after unified ISSU is initialized, HA is
disabled, which then sets a redundancy criteria for corruption that prevents unified
ISSU from starting.
If monitoring is configured to run in auto mode when unified ISSU starts, monitoring
reverts back to manual mode to prevent monitoring during a unified ISSU upgrade.
After a successful unified ISSU upgrade, monitoring switches back to the originally
configured mode on both SRPs.
File synchronization and monitoring the file system are separate operations. Depending
on the wake up time of the monitoring task, there is a period of time when corruption can
occur and the file systems are synchronized. We recommend that you run the manual
command to check the file system before you enable HA or perform any unified
ISSU-related operations
Use to detect corruption of running configuration on both primary and standby SRP
due to fatal duplicate key error.
Use to detect corruption of CNF files on the primary SRP only. 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.
When auto mode is enabled, if you check the running configuration for corruption
manually, a warning message appears. If you confirm you want to check the running
configuration in manual mode or ignore the warning message, then manual mode is
enabled.
Use the default version to restore the default setting, manual detection.
Example 1—Check running configuration in auto mode
host1(config)#service check-config auto
Example 2—Check running configuration in manual mode when auto mode is enabled
host1(config)#service check-config running-configuration
WARNING: This command will cause config monitor to switch into manual mode. Proceed
with current command? [confirm]
Chapter 5: Managing the System
259
Need help?
Do you have a question about the JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04 and is the answer not in the manual?
Questions and answers