Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All
     

    Related Documentation

     

    Automatically Recovering Corrupt Configuration Files

    You can automatically recover corrupted CFG files detected in the running configuration. When you turn on auto-recovery, the behavior of the file synchronization, stateful SRP switchover (high availability), and unified ISSU tasks changes to prevent synchronization of corrupt configuration. On detecting configuration file corruption, JunosE Software determines whether a corrupt file is recoverable by the application. If the file is recoverable:

    1. The configuration monitor on the SRP tries to recover it from a good configuration as determined by the application.
    2. The file synchronization, high availability, and unified ISSU operations are re-enabled.

    You can manually or automatically recover the recoverable corrupt configuration files in the running configuration as determined by the application.

    You can use the service check-config auto-recover command to enable auto-recovery of corrupt CFG files in the running configuration.

    You can use the service check-config running-configuration command to view a list of corrupt files in the running configuration and the files that are recoverable.

    You can use the service check-config running-configuration recover command to recover the corrupted CFG files in the running configuration. You can recover only the files that the service check-config running-configuration command output lists as recoverable.

    Auto-recovery of a corrupted running configuration in the active and standby SRPs works as follows:

    • If the file system on the primary SRP is corrupt when HA is disabled and the mode of the service check-config command has been set to auto-recover, the following changes occur:
      • File Synchronization–Configuration files are not synchronized to the standby SRP until successful recovery of the corrupted files is complete.
      • HA–Enabling of HA is prevented during recovery and the state is restored on successful recovery.
      • Unified ISSU–If unified ISSU is in the idle state, the operation is disabled until recovery is complete. The unified ISSU process continues if it has started.
      • Auto-Recovery—A message indicates whether the configuration files are recoverable. If the files are recoverable, the auto-recovery process starts. If the recovery is unsuccessful, configuration monitoring is turned off. You can revert the SRP to the last-known good configuration on the standby SRP using the srp switch force command. The standby SRP boots up using the last indicated configuration using the boot conf command.
    • If the file system on the primary SRP is corrupt when HA is enabled and the mode of the service check-config command has been set to auto-recover, the following changes occur:
      • File Synchronization–Configuration files are not synchronized to the standby SRP when the HA state changes to disabled and the status is restored when the recovery window is complete.
      • HA–Enabling of HA is prevented (HA remains in disabled state) during the recovery window and the state is restored after the recovery window is complete.
      • Unified ISSU–If unified ISSU is in the idle state, the operation is disabled until successful recovery or the recovery window is complete. The unified ISSU process continues if it has started.
      • Auto-Recovery—A message indicates whether the configuration files are recoverable. If the files are recoverable, the auto-recovery process starts. If the recovery is unsuccessful, configuration monitoring is turned off. You can revert the SRP to the last-known good configuration on the standby SRP using the srp switch force command. The standby SRP boots up using the last indicated configuration using the boot conf command.
    • If the file system on the standby SRP is corrupt when HA is disabled and the mode of the service check-config command has been set to auto-recover, auto, or manual, the following changes occur:
      • File Synchronization–Configuration files do not synchronize and the synchronization state does not restore until successful recovery of the corrupted files or the recovery window is complete.
      • HA–Enabling of HA is prevented during recovery and the state is restored on successful recovery.
      • Unified ISSU–If unified ISSU is in the idle state, the operation is disabled until successful recovery or the recovery window is complete. The unified ISSU process continues if it has started.
      • Auto-Recovery—Monitoring of corrupt configuration stops and a message indicating whether the files are recoverable appears. If the SRP is successfully recovered, monitoring of corrupt configuration resumes. If recovery fails, reload the standby SRP module using the reload standby-srp command and re-initiate the flash system on the standby SRP.
    • If the file system on the standby SRP is corrupt when HA is enabled and the mode of the service check-config command has been set to auto-recover, auto, or manual, the following changes occur:
      • File Synchronization–Configuration files are not synchronized when the HA state changes to disabled and the synchronization state is not restored until the successful recovery of the corrupted files or the recovery window is complete.
      • HA–HA is disabled during recovery and the state is restored on successful recovery.
      • Unified ISSU–If unified ISSU is in the idle state, the operation is disabled until successful recovery or the recovery window is complete. The unified ISSU process continues if it has started.
      • Auto-Recovery—Monitoring of corrupt configuration stops and a message indicating whether the files are recoverable appears. If the SRP is successfully recovered, monitoring of corrupt configuration resumes. If recovery fails, reload the standby SRP module using the reload standby-srp command and re-initiate the flash system on the standby SRP.
    • If the file systems on both the primary and standby SRPs are corrupt when HA is disabled, the following changes occur:
      • File Synchronization–Configuration files are not synchronized and the synchronization state is not restored until the successful recovery of the corrupted files or the recovery window is complete.
      • HA–Enabling of HA is prevented during recovery and the state is restored on successful recovery.
      • Unified ISSU–If unified ISSU is in the idle state, the operation is disabled until successful recovery or the recovery window is complete. The unified ISSU process continues if it has started.
      • Auto-Recovery—Monitoring of corrupt configuration stops on both the primary and standby SRP modules and a message appears indicating whether the files are recoverable. If the SRPs are successfully recovered, monitoring of corrupt configuration resumes. If recovery fails, load another release on the primary SRP and run the reload force command. The primary and standby SRP modules re-initiate during a reboot.
    • If the file systems on both the primary and standby SRPs are corrupt when HA is enabled, the following changes occur:
      • File Synchronization–Configuration files are not synchronized when the HA state changes to disabled and the synchronization state is not restored until the successful recovery of the corrupted files or the recovery window is complete.
      • HA–HA is disabled during recovery and the state is restored on successful recovery.
      • Unified ISSU–If unified ISSU is in the idle state, the operation is disabled until successful recovery or the recovery window is complete. The unified ISSU process continues if it has started.
      • Auto-Recovery—Monitoring of corrupt configuration stops on both the primary and standby SRP modules and a message appears indicating whether the files are recoverable. If the SRPs are successfully recovered, monitoring of corrupt configuration resumes. If recovery fails, load another release on the primary SRP and run the reload force command. The primary and standby SRP modules re-initiate during a reboot.

    To recover corrupted CFG files:

    • Enable auto-recovery of files in the running configuration that are corrupted due to a fatal duplicate key error or the existence of values such as 0XFF and 0x00 in sectors of a Flash.
      host1(config)#service check-config auto-recover

      Note: You cannot auto-recover CNF files on the primary and standby SRPs.

      Use the no version without the auto-recover option to restore the default action, manual detection.

    • View a list of corrupt files in the running configuration and the files that are recoverable on the primary SRP and the standby SRP.
      host1(config)#service check-config running-configuration

      Use the no version without the running-configuration option to restore the default action, manual detection.

    • Recover the corrupted CFG files in the running configuration.
      host1(config)#service check-config running-configuration recover

      Note: You can recover only the files that the service check-config running-configuration command output lists as recoverable.

      Use the no version without the running-configuration recover option to restore the default action, manual detection.

     

    Related Documentation

     

    Published: 2014-08-12