Managing SRP Module Redundancy

You can prevent the redundant SRP module from taking over when:

• The primary SRP module experiences a software failure.
• You push the reset button on the primary SRP module.

  Note: If you do not configure this option, when troubleshooting an SRP module, disconnect the other SRP module from the router. This action prevents the redundant SRP module from taking over if you push the reset button on the primary SRP module.

To configure this option:

1. Issue the disable-switch-on-error command.
2. Synchronize the NVS file system of the redundant SRP module to that of the primary SRP module.

Refer to the commands and guidelines in the previous section and below.

disable-switch-on-error

• Use to prevent the redundant SRP module from taking over if the primary SRP module experiences a software failure or if you push the reset button on the primary SRP module.
• Issue the synchronize command immediately before you issue this command.
• If you issue the disable-switch-on-error command, and later issue the srp switch command, the redundant SRP module waits about 30 seconds before it takes over from the primary SRP module.
• Example

  host1(config)#disable-switch-on-error

• Use the no version to revert to the default situation, in which the redundant SRP module takes over if the primary SRP module experiences a software failure.
• See disable-switch-on-error.

synchronize

• Use to force the NVS 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 Validating and Recovering Redundant SRP File Integrity for details.
• Examples

  host1#synchronize

  host1#synchronize low-level-check all

  host1#synchronize low-level-check configuration

• There is no no version.
• See synchronize.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.