Managing Srp Module Redundancy - Juniper SERVICE AVAILABILITY - CONFIGURATION GUIDE V 11.1.X Configuration Manual

JUNOSe 11.1.x Service Availability Configuration Guide
synchronize

Managing SRP Module Redundancy

You can prevent the redundant SRP module from taking over when:
16
Line Module Redundancy Overview
Use the srp keyword to reboot the portion of the SC subsystem that resides
on a specified SRP module.
Use the fabric keyword to reboot the fabric slice that resides on the specified
SRP module.
Example 1 Reboots the module in slot 7
host1#reload slot 7
Example 2 Reboots the SC on the SRP module in slot 7 (applies only to E120
and E320 routers)
host1#reload slot 7 srp
There is no no version.
See reload slot.
Use to force the file system of the redundant SRP module to synchronize with
the NVS file system of the primary SRP module.
If you synchronize the redundant SRP module with the primary SRP module and
the redundant module is armed with a release different from the one it is currently
running, the redundant SRP module is automatically rebooted to load the armed
release.
Optionally, you can use the low-level-check keyword to force the router to
validate all files or only configuration files in NVS, and to synchronize all files
that failed the checksum test during the flash-disk-compare command as well
as any other files that are unsynchronized. See Managing Flash Cards on SRP
Modules in the JUNOSe System Basics Configuration Guide for details.
Examples
host1#synchronize
host1#synchronize low-level-check all
host1#synchronize low-level-check configuration
There is no no version.
See synchronize.
The primary SRP module experiences a software failure.
You push the reset button on the primary SRP module.