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.
service check-config auto-recover
•
Use to 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. You cannot auto-recover CNF files on the primary and standby SRPs.
•
Example
host1(config)#
service check-config auto-recover
•
Use the
no
version without the
auto-recover
option to restore the default action,
manual detection.
•
See service check-config.
service check-config running-configuration
•
Use to view a list of corrupt files in the running configuration and the files that are
recoverable on the primary SRP and the standby SRP.
•
Example
host1(config)#
service check-config running-configuration
•
Use the
no
version without the
running-configuration
option to restore the default
action, manual detection.
•
See service check-config.
service check-config running-configuration recover
263
Copyright © 2010, Juniper Networks, Inc.
Chapter 5: Managing the System
Summary of Contents for JUNOSE 11.3
Page 6: ...Copyright 2010 Juniper Networks Inc vi...
Page 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 3 x System Basics Configuration Guide...
Page 24: ...Copyright 2010 Juniper Networks Inc xxiv JunosE 11 3 x System Basics Configuration Guide...
Page 32: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 3 x System Basics Configuration Guide...
Page 146: ...Copyright 2010 Juniper Networks Inc 116 JunosE 11 3 x System Basics Configuration Guide...
Page 166: ...Copyright 2010 Juniper Networks Inc 136 JunosE 11 3 x System Basics Configuration Guide...
Page 432: ...Copyright 2010 Juniper Networks Inc 402 JunosE 11 3 x System Basics Configuration Guide...
Page 488: ...Copyright 2010 Juniper Networks Inc 458 JunosE 11 3 x System Basics Configuration Guide...
Page 524: ...Copyright 2010 Juniper Networks Inc 494 JunosE 11 3 x System Basics Configuration Guide...
Page 554: ...Copyright 2010 Juniper Networks Inc 524 JunosE 11 3 x System Basics Configuration Guide...
Page 566: ...Copyright 2010 Juniper Networks Inc 536 JunosE 11 3 x System Basics Configuration Guide...
Page 588: ...Copyright 2010 Juniper Networks Inc 558 JunosE 11 3 x System Basics Configuration Guide...
Page 613: ...PART 3 Index Index on page 585 583 Copyright 2010 Juniper Networks Inc...
Page 614: ...Copyright 2010 Juniper Networks Inc 584 JunosE 11 3 x System Basics Configuration Guide...
Page 632: ...Copyright 2010 Juniper Networks Inc 602 JunosE 11 3 x System Basics Configuration Guide...