Day One Tips
Highlighted
Day One Tips

Technique: Installing the JUNOS Software on Routers with Redundant Routing Engines

‎11-24-2010 04:23 AM

If the router has two Routing Engines, perform a JUNOS software installation on each Routing Engine separately to avoid disrupting network operation. Install the new JUNOS software release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine. After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the newly installed Routing Engine to activate the new software. Finally, install the new software on the new backup Routing Engine. To install a new version of JUNOS software on a router with redundant Routing Engines, follow these steps:


1. Log in to the master Routing Engine.
2. Enter the JUNOS software configuration mode:
{master}
user@host-re0> configure

3. Disable Routing Engine redundancy.
{master} [edit]
user@host-re0# delete chassis redundancy
4. Save the configuration change on both Routing Engines.
{master} [edit]
user@host-re0# commit synchronize and-quit
5. Log in to the backup Routing Engine:
{backup}
user@host-re0> request routing-engine login other routing-engine Notice that the host name changes, because you are now connected to the backup Routing Engine.
6. Install the JUNOS software on the backup Routing Engine. See “Upgrading All Software Packages” on page 29. {backup}
user@host-re1> request system software add validate
/var/tmp/jinstall-8.x-domestic-signed.tgz reboot
7. The installation process reboots the router, activates the installation environment, and performs the installation without intervention. When the installation is complete, the backup Routing Engine reboots. During this time, you are logged out of the backup Routing Engine and returned to the master. You will not be able to log back in to the backup Routing Engine until the installation is complete. Use the request routing-engine login other-routing-engine command to periodically (every minute) determine whether the installation is complete.
8. Log out of the backup Routing Engine (re1), then switch over to the master Routing Engine (re0):
{backup}
user@host-re1> quit
{master}
user@host-re0> request chassis routing-engine master switch
{backup}
user@host-re0>
This command causes the backup Routing Engine (re1), on which you just installed the software, to switch to become the master Routing Engine. The master Routing Engine (re0) becomes the backup.
9. Install the new software version on the new backup Routing Engine (re1):
{backup}
user @host-re0> request system software add validate
/var/tmp/jinstall-8.x-domestic-signed.tgz reboot

10. When the Routing Engine reboots, you are logged out of the router. Log back in after a few minutes and restore the immediately preceding redundancy configuration that existed before you deleted it in Step 3.
{backup}
user@host-re0> configure
[edit]
user@host-re0# rollback 1
11. Save the configuration change on both Routing Engines
[edit]
user@host-re0> commit synchronize and-quit
12. After you have installed the new software and are satisfied that the new software is successfully running, issue the request system snapshot command to back up the new software on both master and backup Routing Engines.
{master}
user@host-re0> request system snapshot
{master}
user@host-re0> request routing-engine login other routing-engine
{backup}
user@host-re1> request system snapshot
{backup}
user@host-re1> quit
The root file system is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on the router’s flash disk, and the /altroot and /altconfig file systems are on the router’s hard disk.