Upgrading Systems That Are Operating with Two SRP Modules E-Series Routers

B-17

If no firewall separates the E-series router from the network host, copy the files to the E-series router (see Installing Software When a Firewall Does Not Exist, earlier in this appendix).

host1#copy hostname:/cdrom/x-y-z/x-y-z.rel x-y-z.rel

If you are transferring the files from one E-series router to another, copy the file to the system space of the second E-series router from the user space of the first E-series router (see Copying Release Files from One E-Series Router to Another, earlier in this appendix).

host1#copy boston:/outgoing/releases/x-y-z.rel x-y-z.rel

3Save the current configuration.

host1#copy running-configuration system2.cnf

4Specify that the E-series router should use the new software release when it reboots.

host1(config)#boot system x-y-z.rel

5Synchronize the NVS file system of the redundant module with that of the primary module.

host1#synchronize

The redundant SRP module will automatically reboot, because the software release that it is configured to run differs from the software release it is running.

6Wait for the redundant SRP module to boot, initialize, and reach the standby state.

When the module is in standby state, the REDUNDANT LED is on and the ONLINE LED is off. If you issue the show version command, the state field for the module should be “standby”.

After any type of reboot, the primary and redundant SRP module NVS file systems will be unsynchronized again.

7Synchronize the NVS file system of the redundant module with that of the primary module.

host1#synchronize

8Switch from the primary SRP module to the redundant SRP module.

host1#srp switch

The redundant SRP module assumes the primary role. The former primary SRP module reboots and assumes the redundant role.

Page 229
Image 229
Juniper Networks E-Series manual Host1#copy running-configuration system2.cnf