[an error occurred while processing this directive][an error occurred while processing this directive]

Upgrading the JUNOS Software on a Routing Matrix with a TX Matrix Plus Router

When you upgrade the JUNOS Software on a routing matrix with a TX Matrix Plus router, the new image is loaded onto the TX Matrix Plus router (sfc0) and distributed to all of the connected T1600 routers (lcc0, lcc1, lcc2, and lcc3).

Note: Throughout this task description, the terms TX Matrix Plus router and T1600 router refer to the routing matrix switch-fabric chassis (SFC) and line-card chassis (LCC), respectively.

Before you begin upgrading the JUNOS Software on a routing matrix, be sure you have:

  • Sufficient free disk space on each Routing Engine in the routing matrix. To determine the amount of disk space currently available on all Routing Engines of the routing matrix, issue the show system storage operational command.
  • Sufficient DRAM on each Routing Engine in the routing matrix. To determine the amount of DRAM currently available on all the Routing Engines in the routing matrix, issue the show chassis routing-engine operational command.
  • Compatible models of Routing Engines (master and backup) in the routing matrix. For this release of JUNOS Software, the TX Matrix Plus router must contain two model RE-DUO-C2600-16G Routing Engines, and each T1600 router in the routing matrix must contain two model RE-DUO-C1800-8G Routing Engines. To determine the Routing Engine models installed in the Routing Engines in a routing matrix, issue the show chassis hardware operational command with the models option. Hardware component model numbers are listed in the FRU model number column.
  • The same version of JUNOS Software running on all Routing Engines in the routing matrix.

    Note: The routing matrix does not operate properly unless all master Routing Engines are running the same version of JUNOS Software.

    Different versions of the JUNOS Software can use different message formats that might be incompatible, particularly when graceful Routing Engine switchover (GRES) is enabled. For more information about GRES, see “Understanding Graceful Routing Engine Switchover in the JUNOS Software” and “Configuring Graceful Routing Engine Switchover” in the JUNOS High Availability Configuration Guide.

    Because the procedure for upgrading the JUNOS Software includes switching of the Routing Engine mastership, we recommend that the same version of JUNOS Software is running on all Routing Engines in the routing matrix. To determine the versions of JUNOS Software running on the Routing Engines in a routing matrix, issue the show version invoke-on operational command.

Best Practice: By default, the Routing Engine in slot 0 (re0) is the master and the one in slot 1 (re1) is the backup. You can modify the default Routing Engine mastership by including the routing-engine slot-number (master | backup | disabled) statement at the [edit chassis redundancy] hierarchy level. However, it is considered best practice to make sure that all master Routing Engines are re0 and all backup Routing Engines are re1 (or vice versa). Throughout this task description, the master Routing Engine is re0 and the backup Routing Engine is re1 in all routers in the routing matrix.

This topic includes the following tasks:

  1. Logging In to the Master Routing Engine on the TX Matrix Plus Router
  2. Disabling Routing Engine Redundancy and GRES on the Routing Matrix
  3. Installing JUNOS Software on the Backup Routing Engines
  4. Loading Software on the Backup Routing Engines
  5. Switching Routing Engine Mastership to the Backup Routing Engines
  6. Installing Software on the New Default Master Routing Engines
  7. Loading Software on the New Default Master Routing Engines
  8. Optional: Switching Routing Engine Mastership Back to the Default Master Routing Engines
  9. Restoring the Original Configuration
  10. Backing Up the Routing Engines

Logging In to the Master Routing Engine on the TX Matrix Plus Router

Log in to the master Routing Engine on the TX Matrix Plus router.

Note: During the upgrade process, in-band management connections to the routing matrix are lost each time you reboot the system (first, to load the new software onto the backup Routing Engines and later, to load the new software onto the master Routing Engines). Therefore, we recommend that you perform the software upgrade procedure out-of-band, over a direct console connection to the TX Matrix Plus router using Secure Shell (SSH) or Telnet. Connect the system console device to the asynchronous serial port (labeled CONSOLE) on the Control Board (CB) associated with the master Routing Engine.

To log in to the master Routing Engine on the TX Matrix Plus router and start the JUNOS CLI:

  1. At a management console attached to the master Routing Engine (re0) on the TX Matrix Plus router, log in to the JUNOS CLI using a root administration account:

    login: root
    Password: •••••••••
    
    --- JUNOS 9.6R1.0 built 2009-07-13 08:52:23 UTC

    Note: From the factory, the root administration user account is not associated with a password.

    Amnesiac (ttyd0)
    
    login: root

    However, you must add a password to the root administration account before you can successfully commit a configuration.

  2. At the shell prompt (%), start the JUNOS CLI:

    % cli
    {master}
    root@mysfc0-re0>

Disabling Routing Engine Redundancy and GRES on the Routing Matrix

By default, graceful Routing Engine switchover (GRES) is disabled. To enable GRES on a router, you can include the graceful-switchover statement at the [edit chassis redundancy] hierarchy level:

[edit]chassis {redundancy { # This enables Routing Engine redundancy on the routergraceful-switchover; # This enables GRES on the router}}

The procedure for upgrading the JUNOS Software on a routing matrix with a TX Matrix Plus router includes tasks that entail disruption of traffic processing by the affected Routing Engines:

  • Upgrading the software on all the backup Routing Engines.
  • Switching the Routing Engine mastership to the backup Routing Engines.
  • Upgrading the software on all the master Routing Engines.
  • Switching the Routing Engine mastership back to the master Routing Engines.

If GRES is enabled on any routers in the routing matrix, disable this feature.

To disable GRES on all routers in the routing matrix:

  1. Enter configuration mode:

    {master}
    root@mysfc0-re0> configure
    Entering configuration mode
    
    

    Note: In the example shown in this step, the form of CLI prompt (beginning with either {master} or {backup} and displaying either -re0 or -re1 in the hostname portion of the prompt) indicates that GRES is enabled on that router.

  2. Display the Routing Engine redundancy stanza:

    {master} 
    [edit] 
    root@mysfc0-re0# show chassis
    ...
        redundancy {
            graceful-switchover;
        }
    ...
    
  3. Disable Routing Engine redundancy in the candidate configuration. If GRES is enabled, it is removed with the redundancy stanza:

    {master}
    [edit]
    root@mysfc0-re0# delete chassis redundancy
    
  4. Verify that the graceful-routing statement has been removed (if it was previously enabled) with the redundancy stanza from the [edit chassis] hierarchy level of the candidate configuration:

    [edit] 
    root@mysfc0# show chassis

    Note: You can also issue the show system switchover all-chassis operational command to display Routing Engine graceful switchover information

  5. Commit the configuration on all Routing Engines in the routing matrix and, if the configuration contains no errors and the commit succeeds, exit CLI configuration mode:

    [edit]
    root@mysfc0# commit synchronize and-quit 
    sfc0-re0: 
    configuration check succeeds
    lcc0-re1: 
    commit complete
    lcc0-re0: 
    commit complete
    lcc2-re1: 
    commit complete
    lcc2-re0: 
    commit complete
    sfc0-re1: 
    commit complete
    sfc0-re0: 
    commit complete
    
    root@mysfc0> 

Installing JUNOS Software on the Backup Routing Engines

Install the new version of JUNOS Software on the backup Routing Engines (re1) of all the routers in the routing matrix while leaving the currently running version of JUNOS Software running on the master Routing Engines (re0). This allows the master Routing Engines to continue operations, minimizing the disruption to the routing matrix and your network.

To install the new version of JUNOS Software on all backup Routing Engines in the routing matrix:

  1. At a management console attached to the backup Routing Engine (re1) on the TX Matrix Plus router, log in to the JUNOS CLI using a root administration account:

    login: root
    Password: •••••••••
    
    --- JUNOS 9.6R1.0 built 2009-07-13 08:52:23 UTC
  2. At the shell prompt (%), start the JUNOS CLI:
    % cli
    root@mysfc0_alt_re> 
    
  3. To install the new JUNOS Software on the backup Routing Engines (re1) in the routing matrix, issue the request system software add operational command at the TX Matrix Plus router, and specify the new JUNOS Software image file.

    The following example shows sample output for the request system software add command:


    root@mysfc0_alt_re> request system software add /var/tmp/jinstall-9.6R1.2-domestic-signed.tgz
    Pushing bundle to lcc0-re1
    Pushing bundle to lcc2-re1
    
    Validating on lcc0-re1
    Checking compatibility with configuration
    Initializing...
    Using jbase-9.6R1.0
    Verified manifest signed by PackageProduction_9_6_0
    Using /var/tmp/jinstall-9.6R1.2-domestic-signed.tgz
    Verified jinstall-9.6R1.2-domestic.tgz signed by PackageProduction_9_6_0
    Using jinstall-9.6R1.2-domestic.tgz
    Using jbundle-9.6R1.2-domestic.tgz
    Checking jbundle requirements on /
    Using jbase-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using /var/validate/chroot/tmp/jbundle/jboot-9.6R1.2.tgz
    Using jkernel-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jcrypto-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jpfe-9.6R1.2.tgz
    Using jdocs-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jroute-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jservices-9.6R1.2.tgz
    Auto-deleting old jservices-voice ...
    Removing /opt/sdk/jservices-voice ...
    Removing jservices-voice-bsg-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-voice ...
    Verified jservices-voice-bsg-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /var/sw/pkg ...
    Creating /opt/sdk/jservices-voice ...
    Storing jservices-voice-bsg-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-voice/jservices-voice-bsg -> /var/sw/pkg/jservices-voice-bsg-9.6R1.2.tgz...
    Auto-deleting old jservices-bgf ...
    Removing /opt/sdk/jservices-bgf ...
    Removing jservices-bgf-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-bgf ...
    Verified jservices-bgf-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-bgf ...
    Storing jservices-bgf-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-bgf/jservices-bgf-pic -> /var/sw/pkg/jservices-bgf-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-aacl ...
    Removing /opt/sdk/jservices-aacl ...
    Removing jservices-aacl-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-aacl ...
    Verified jservices-aacl-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-aacl ...
    Storing jservices-aacl-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-aacl/jservices-aacl-pic -> /var/sw/pkg/jservices-aacl-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-llpdf ...
    Removing /opt/sdk/jservices-llpdf ...
    Removing jservices-llpdf-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-llpdf ...
    Verified jservices-llpdf-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-llpdf ...
    Storing jservices-llpdf-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-llpdf/jservices-llpdf-pic -> /var/sw/pkg/jservices-llpdf-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-sfw ...
    Removing /opt/sdk/jservices-sfw ...
    Removing jservices-sfw-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-sfw ...
    Verified jservices-sfw-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-sfw ...
    Storing jservices-sfw-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-sfw/jservices-sfw-pic -> /var/sw/pkg/jservices-sfw-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-appid ...
    Removing /opt/sdk/jservices-appid ...
    Removing jservices-appid-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-appid ...
    Verified jservices-appid-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-appid ...
    Storing jservices-appid-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-appid/jservices-appid-pic -> /var/sw/pkg/jservices-appid-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-idp ...
    Removing /opt/sdk/jservices-idp ...
    Removing jservices-idp-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-idp ...
    Verified jservices-idp-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-idp ...
    Storing jservices-idp-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-idp/jservices-idp-pic -> /var/sw/pkg/jservices-idp-pic-9.6R1.2.tgz...
    Hardware Database regeneration succeeded
    Validating against /config/juniper.conf.gz
    mgd: commit complete
    Validation succeeded
    
    Validating on lcc2-re1
    Checking compatibility with configuration
    Initializing...
    Using jbase-9.6R1.0
    Verified manifest signed by PackageProduction_9_6_0
    Using /var/tmp/jinstall-9.6R1.2-domestic-signed.tgz
    Verified jinstall-9.6R1.2-domestic.tgz signed by PackageProduction_9_6_0
    Using jinstall-9.6R1.2-domestic.tgz
    Using jbundle-9.6R1.2-domestic.tgz
    Checking jbundle requirements on /
    Using jbase-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using /var/validate/chroot/tmp/jbundle/jboot-9.6R1.2.tgz
    Using jkernel-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jcrypto-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jpfe-9.6R1.2.tgz
    Using jdocs-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jroute-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jservices-9.6R1.2.tgz
    Auto-deleting old jservices-voice ...
    Removing /opt/sdk/jservices-voice ...
    Removing jservices-voice-bsg-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-voice ...
    Verified jservices-voice-bsg-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /var/sw/pkg ...
    Creating /opt/sdk/jservices-voice ...
    Storing jservices-voice-bsg-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-voice/jservices-voice-bsg -> /var/sw/pkg/jservices-voice-bsg-9.6R1.2.tgz...
    Auto-deleting old jservices-bgf ...
    Removing /opt/sdk/jservices-bgf ...
    Removing jservices-bgf-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-bgf ...
    Verified jservices-bgf-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-bgf ...
    Storing jservices-bgf-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-bgf/jservices-bgf-pic -> /var/sw/pkg/jservices-bgf-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-aacl ...
    Removing /opt/sdk/jservices-aacl ...
    Removing jservices-aacl-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-aacl ...
    Verified jservices-aacl-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-aacl ...
    Storing jservices-aacl-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-aacl/jservices-aacl-pic -> /var/sw/pkg/jservices-aacl-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-llpdf ...
    Removing /opt/sdk/jservices-llpdf ...
    Removing jservices-llpdf-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-llpdf ...
    Verified jservices-llpdf-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-llpdf ...
    Storing jservices-llpdf-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-llpdf/jservices-llpdf-pic -> /var/sw/pkg/jservices-llpdf-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-sfw ...
    Removing /opt/sdk/jservices-sfw ...
    Removing jservices-sfw-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-sfw ...
    Verified jservices-sfw-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-sfw ...
    Storing jservices-sfw-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-sfw/jservices-sfw-pic -> /var/sw/pkg/jservices-sfw-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-appid ...
    Removing /opt/sdk/jservices-appid ...
    Removing jservices-appid-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-appid ...
    Verified jservices-appid-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-appid ...
    Storing jservices-appid-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-appid/jservices-appid-pic -> /var/sw/pkg/jservices-appid-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-idp ...
    Removing /opt/sdk/jservices-idp ...
    Removing jservices-idp-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-idp ...
    Verified jservices-idp-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-idp ...
    Storing jservices-idp-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-idp/jservices-idp-pic -> /var/sw/pkg/jservices-idp-pic-9.6R1.2.tgz...
    Hardware Database regeneration succeeded
    Validating against /config/juniper.conf.gz
    mgd: commit complete
    Validation succeeded
    
    Validating on sfc0-re1
    Checking compatibility with configuration
    Initializing...
    Using jbase-9.6R1.0
    Verified manifest signed by PackageProduction_9_6_0
    Using /var/tmp/jinstall-9.6R1.2-domestic-signed.tgz
    Verified jinstall-9.6R1.2-domestic.tgz signed by PackageProduction_9_6_0
    Using jinstall-9.6R1.2-domestic.tgz
    Using jbundle-9.6R1.2-domestic.tgz
    Checking jbundle requirements on /
    Using jbase-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using /var/validate/chroot/tmp/jbundle/jboot-9.6R1.2.tgz
    Using jkernel-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jcrypto-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jpfe-9.6R1.2.tgz
    Using jdocs-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jroute-9.6R1.2.tgz
    Verified manifest signed by PackageProduction_9_6_0
    Using jservices-9.6R1.2.tgz
    Auto-deleting old jservices-voice ...
    Removing /opt/sdk/jservices-voice ...
    Removing jservices-voice-bsg-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-voice ...
    Verified jservices-voice-bsg-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /var/sw/pkg ...
    Creating /opt/sdk/jservices-voice ...
    Storing jservices-voice-bsg-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-voice/jservices-voice-bsg -> /var/sw/pkg/jservices-voice-bsg-9.6R1.2.tgz...
    Auto-deleting old jservices-bgf ...
    Removing /opt/sdk/jservices-bgf ...
    Removing jservices-bgf-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-bgf ...
    Verified jservices-bgf-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-bgf ...
    Storing jservices-bgf-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-bgf/jservices-bgf-pic -> /var/sw/pkg/jservices-bgf-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-aacl ...
    Removing /opt/sdk/jservices-aacl ...
    Removing jservices-aacl-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-aacl ...
    Verified jservices-aacl-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-aacl ...
    Storing jservices-aacl-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-aacl/jservices-aacl-pic -> /var/sw/pkg/jservices-aacl-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-llpdf ...
    Removing /opt/sdk/jservices-llpdf ...
    Removing jservices-llpdf-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-llpdf ...
    Verified jservices-llpdf-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-llpdf ...
    Storing jservices-llpdf-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-llpdf/jservices-llpdf-pic -> /var/sw/pkg/jservices-llpdf-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-sfw ...
    Removing /opt/sdk/jservices-sfw ...
    Removing jservices-sfw-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-sfw ...
    Verified jservices-sfw-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-sfw ...
    Storing jservices-sfw-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-sfw/jservices-sfw-pic -> /var/sw/pkg/jservices-sfw-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-appid ...
    Removing /opt/sdk/jservices-appid ...
    Removing jservices-appid-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-appid ...
    Verified jservices-appid-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-appid ...
    Storing jservices-appid-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-appid/jservices-appid-pic -> /var/sw/pkg/jservices-appid-pic-9.6R1.2.tgz...
    Auto-deleting old jservices-idp ...
    Removing /opt/sdk/jservices-idp ...
    Removing jservices-idp-pic-9.6R1.0.tgz from /var/sw/pkg ...
    Notifying mspd ...
    Installing new jservices-idp ...
    Verified jservices-idp-pic-9.6R1.2.tgz signed by PackageProduction_9_6_0
    Creating /opt/sdk/jservices-idp ...
    Storing jservices-idp-pic-9.6R1.2.tgz in /var/sw/pkg ...
    Link: /opt/sdk/jservices-idp/jservices-idp-pic -> /var/sw/pkg/jservices-idp-pic-9.6R1.2.tgz...
    Hardware Database regeneration succeeded
    Validating against /config/juniper.conf.gz
    mgd: commit complete
    Validation succeeded
    Done with validate on all chassis
    
    lcc0-re1:
    Installing package '/var/tmp/jinstall-9.6R1.2-domestic-signed.tgz' ...
    Verified jinstall-9.6R1.2-domestic.tgz signed by PackageProduction_9_6_0
    Adding jinstall...
    Verified manifest signed by PackageProduction_9_6_0
    
    WARNING:     This package will load JUNOS 9.6R1.2 software.
    WARNING:     It will save JUNOS configuration files, and SSH keys
    WARNING:     (if configured), but erase all other files and information
    WARNING:     stored on this machine.  It will attempt to preserve dumps
    WARNING:     and log files, but this can not be guaranteed.  This is the
    WARNING:     pre-installation stage and all the software is loaded when
    WARNING:     you reboot the system.
    
    Saving the config files ...
    NOTICE: uncommitted changes have been saved in /var/db/config/juniper.conf.pre-install
    Installing the bootstrap installer ...
    
    WARNING:     A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use the
    WARNING:     'request system reboot' command when software installation is
    WARNING:     complete. To abort the installation, do not reboot your system,
    WARNING:     instead use the 'request system software delete jinstall'
    WARNING:     command as soon as this operation completes.
    
    Saving package file in /var/sw/pkg/jinstall-9.6R1.2-domestic-signed.tgz ...
    Saving state for rollback ...
    
    lcc2-re1:
    Installing package '/var/tmp/jinstall-9.6R1.2-domestic-signed.tgz' ...
    Verified jinstall-9.6R1.2-domestic.tgz signed by PackageProduction_9_6_0
    Adding jinstall...
    Verified manifest signed by PackageProduction_9_6_0
    
    WARNING:     This package will load JUNOS 9.6R1.2 software.
    WARNING:     It will save JUNOS configuration files, and SSH keys
    WARNING:     (if configured), but erase all other files and information
    WARNING:     stored on this machine.  It will attempt to preserve dumps
    WARNING:     and log files, but this can not be guaranteed.  This is the
    WARNING:     pre-installation stage and all the software is loaded when
    WARNING:     you reboot the system.
    
    Saving the config files ...
    NOTICE: uncommitted changes have been saved in /var/db/config/juniper.conf.pre-install
    Installing the bootstrap installer ...
    
    WARNING:     A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use the
    WARNING:     'request system reboot' command when software installation is
    WARNING:     complete. To abort the installation, do not reboot your system,
    WARNING:     instead use the 'request system software delete jinstall'
    WARNING:     command as soon as this operation completes.
    
    Saving package file in /var/sw/pkg/jinstall-9.6R1.2-domestic-signed.tgz ...
    Saving state for rollback ...
    
    sfc0-re1:
    Installing package '/var/tmp/jinstall-9.6R1.2-domestic-signed.tgz' ...
    Verified jinstall-9.6R1.2-domestic.tgz signed by PackageProduction_9_6_0
    Adding jinstall...
    Verified manifest signed by PackageProduction_9_6_0
    
    WARNING:     This package will load JUNOS 9.6R1.2 software.
    WARNING:     It will save JUNOS configuration files, and SSH keys
    WARNING:     (if configured), but erase all other files and information
    WARNING:     stored on this machine.  It will attempt to preserve dumps
    WARNING:     and log files, but this can not be guaranteed.  This is the
    WARNING:     pre-installation stage and all the software is loaded when
    WARNING:     you reboot the system.
    
    Saving the config files ...
    NOTICE: uncommitted changes have been saved in /var/db/config/juniper.conf.pre-install
    Installing the bootstrap installer ...
    
    WARNING:     A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use the
    WARNING:     'request system reboot' command when software installation is
    WARNING:     complete. To abort the installation, do not reboot your system,
    WARNING:     instead use the 'request system software delete jinstall'
    WARNING:     command as soon as this operation completes.
    
    Saving package file in /var/sw/pkg/jinstall-9.6R1.2-domestic-signed.tgz ...
    Saving state for rollback ...
    
    root@host> 

    For more information on the request system software add command, see the JUNOS System Basics and Services Command Reference.

Loading Software on the Backup Routing Engines

To start running the newly installed JUNOS Software on all the backup Routing Engines in the routing matrix, you must reboot those Routing Engines. The Routing Engines reboot from the boot device on which the software was just installed. Each reboot operation can take between 5 and 10 minutes to complete.

Note: This is your last chance to abort the upgrade of the JUNOS Software on the backup Routing Engines. If you want to abort the software upgrade, do not reboot the backup Routing Engines.

If you choose to abort the software upgrade, you can remove the new JUNOS Software package or bundle from the router by issuing the request system software delete operational command and specifying the jinstall command.

To start running the new JUNOS Software on the backup Routing Engines:

  1. To reboot all the backup Routing Engines (re1), issue the request system reboot operational command at the backup Routing Engine one theTX Matrix Plus router. At the warning message and prompt, type yes to allow the command to proceed:

    root@mysfc0_alt_ret> request system reboot
    Reboot the system ? [yes,no] (no) yes 
    
    rebooting lcc0-re1
    Rebooting lcc2-re1
    Shutdown NOW!
    Reboot consistency check bypassed - jinstall 9.6R1.2 will complete installation upon reboot
    [pid 23517]

    root@mysfc0_alt_re>
    *** FINAL System shutdown message from root@host-sfc0-re1> *** 
    
    System going down IMMEDIATELY 
    
    rlogin: connection closed

    root@host>

    All of the backup Routing Engines (re1) in the routing matrix reboot from the boot devices on which the software was just installed, which loads the new JUNOS Software. Each reboot operation can take between 5 and 10 minutes to complete.

    When the backup Routing Engine on the TX Matrix Plus router (sfc0-re1) finishes rebooting, the management console attached to the backup Routing Engine on the TX Matrix Plus router displays the login prompt.

  2. Log in to the TX Matrix Plus backup Routing Engine (sfc0-re1) and issue the show version command to verify the version of the software installed:

    root@mysfc0_alt_re> show version
    sfc0-re1:
    --------------------------------------------------------------------------
    Hostname: mysfc0_alt_re
    Model: txp
    JUNOS Base OS boot [9.6R1.2]
    JUNOS Base OS Software Suite [9.6R1.2]
    JUNOS Kernel Software Suite [9.6R1.2]
    JUNOS Crypto Software Suite [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (M/T Common) [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (T-Series) [9.6R1.2]
    JUNOS Online Documentation [9.6R1.2]
    JUNOS Voice Services Container package [9.6R1.2]
    JUNOS Border Gateway Function package [9.6R1.2]
    JUNOS Services AACL Container package [9.6R1.2]
    JUNOS Services LL-PDF Container package [9.6R1.2]
    JUNOS Services Stateful Firewall [9.6R1.2]
    JUNOS AppId Services [9.6R1.2]
    JUNOS IDP Services [9.6R1.2]
    JUNOS Routing Software Suite [9.6R1.2]
    
    lcc0-re1:
    --------------------------------------------------------------------------
    Hostname: mylcc0_alt_re
    Model: t1600
    JUNOS Base OS boot [9.6R1.2]
    JUNOS Base OS Software Suite [9.6R1.2]
    JUNOS Kernel Software Suite [9.6R1.2]
    JUNOS Crypto Software Suite [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (M/T Common) [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (T-Series) [9.6R1.2]
    JUNOS Online Documentation [9.6R1.2]
    JUNOS Voice Services Container package [9.6R1.2]
    JUNOS Border Gateway Function package [9.6R1.2]
    JUNOS Services AACL Container package [9.6R1.2]
    JUNOS Services LL-PDF Container package [9.6R1.2]
    JUNOS Services Stateful Firewall [9.6R1.2]
    JUNOS AppId Services [9.6R1.2]
    JUNOS IDP Services [9.6R1.2]
    JUNOS Routing Software Suite [9.6R1.2]
    
    lcc2-re1:
    --------------------------------------------------------------------------
    Hostname: mylcc2_alt_re
    Model: t1600
    JUNOS Base OS boot [9.6R1.2]
    JUNOS Base OS Software Suite [9.6R1.2]
    JUNOS Kernel Software Suite [9.6R1.2]
    JUNOS Crypto Software Suite [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (M/T Common) [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (T-Series) [9.6R1.2]
    JUNOS Online Documentation [9.6R1.2]
    JUNOS Voice Services Container package [9.6R1.2]
    JUNOS Border Gateway Function package [9.6R1.2]
    JUNOS Services AACL Container package [9.6R1.2]
    JUNOS Services LL-PDF Container package [9.6R1.2]
    JUNOS Services Stateful Firewall [9.6R1.2]
    JUNOS AppId Services [9.6R1.2]
    JUNOS IDP Services [9.6R1.2]
    JUNOS Routing Software Suite [9.6R1.2]
    

Switching Routing Engine Mastership to the Backup Routing Engines

The new JUNOS Software is now running on all the backup Routing Engines (re1) in the routing matrix. Next, you must install and load the same new software on the master Routing Engines (re0) of the routing matrix.

While the JUNOS Software is being upgraded (installed and then loaded), the Routing Engine on which you are performing the software upgrade does not route traffic. Therefore, to minimize disruption to network operation, you need to temporarily switch Routing Engine mastership over to the backup Routing Engines (re1), which are now running the new version of JUNOS Software.

To switch Routing Engine mastership over to the backup Routing Engines:

  1. At a management console attached to the master Routing Engine (re0) on the TX Matrix Plus router, log in to the JUNOS CLI using a root administration account:

    login: root
    Password: •••••••••
    
    --- JUNOS 9.6R1.0 built 2009-07-13 08:52:23 UTC
  2. At the shell prompt (%), start the JUNOS CLI:
    % cli
    root@mysfc0> 
    
  3. To transfer Routing Engine mastership to the backup Routing Engine (re1) for all routers in the routing matrix, issue the request chassis routing-engine master command with the switch and all-chassis options.

    Caution: Switching Routing Engine mastership causes traffic to be disrupted.

    At the warning message and prompt, type yes to allow the command to proceed:


    root@mysfc0> request chassis routing-engine master switch all-chassis
    warning: Traffic will be interrupted while the PFE is re-initialized
    Toggle mastership between routing engines ? [yes,no] (no) yes 
    
    lcc0-re0:
    --------------------------------------------------------------------------
    warning: Traffic will be interrupted while the PFE is re-initialized
    Resolving mastership...
    Complete. The other routing engine becomes the master.
    
    lcc2-re0:
    --------------------------------------------------------------------------
    warning: Traffic will be interrupted while the PFE is re-initialized
    Resolving mastership...
    Complete. The other routing engine becomes the master.
    
    sfc0-re0:
    --------------------------------------------------------------------------
    warning: Traffic will be interrupted while the PFE is re-initialized
    Resolving mastership...
    Complete. The other routing engine becomes the master.
  4. To verify that the default backup Routing Engines (installed in slot 1) are now operating the elected master Routing Engines, issue the show chassis routing-engine command at the TX Matrix Plus router:
    root@mysfc0> show chassis routing-engine
    sfc0-re0:
    --------------------------------------------------------------------------
    Routing Engine status:
      Slot 0:
        Current state                  Backup
        Election priority              Master (default)
        ...output_truncated...
    
    Routing Engine status:
      Slot 1:
        Current state                  Master
        Election priority              Backup (default)
        ...output_truncated...
    
    lcc0-re0:
    --------------------------------------------------------------------------
    Routing Engine status:
      Slot 0:
        Current state                  Backup
        Election priority              Master (default)
        ...output_truncated...
    
                                           0.02       0.07       0.11
    Routing Engine status:
      Slot 1:
        Current state                  Master
        Election priority              Backup (default)
        ...output_truncated...
    
    lcc2-re0:
    --------------------------------------------------------------------------
    Routing Engine status:
      Slot 0:
        Current state                  Backup
        Election priority              Master (default)
        ...output_truncated...
    
    Routing Engine status:
      Slot 1:
        Current state                  Master
        Election priority              Backup (default)
        ...output_truncated...
    

The default backup Routing Engines (re1), which are now running the new version of JUNOS Software, are temporarily operating as the elected master Routing Engines. This enables you to avoid disruption to network operation while you install and load the new version of JUNOS Software on the default master Routing Engines (re0) .

Installing Software on the New Default Master Routing Engines

To install the new version of JUNOS Software on the new default master Routing Engines (re0) in the routing matrix, issue the request system software add operational command at the default master Routing Engine (re0 in this procedure) of the TX Matrix Plus router, and specify the new JUNOS Software image file.

Note: The default backup Routing Engines (re1), which are now running the new version of JUNOS Software, are operating as the elected master Routing Engines. This enables you to avoid disruption to network operation while you install and load the new version of JUNOS Software on the default master Routing Engines (re0).

The following example of the request system software add command is truncated, but the command output is similar to the output displayed when you installed the new software on the default backup Routing Engines:


root@mysfc0> request system software add /var/tmp/jinstall-9.6R1.1-domestic-signed.tgz
Pushing bundle to lcc0-re0
Pushing bundle to lcc2-re0
...output_truncated...

Loading Software on the New Default Master Routing Engines

To start running the newly installed JUNOS Software on all the default master Routing Engines in the routing matrix, you must reboot those Routing Engines. The Routing Engines reboot from the boot device on which the software was just installed. Each reboot operation can take between 5 and 10 minutes to complete.

Note: This is your last chance to abort the upgrade of the JUNOS Software on the default master Routing Engines. If you want to abort the software upgrade, do not reboot the default master Routing Engines. However, aborting the software upgrade procedure at this point this is not recommend, because the default backup routing Engines are already running the new JUNOS Software.

If you choose to abort the software upgrade, you can remove the new JUNOS Software package or bundle from the router by issuing the request system software delete operational command and specifying the jinstall command.

To start running the new JUNOS Software on the default master Routing Engines:

  1. To reboot all the default master Routing Engines (re0), issue the request system reboot operational command at the TX Matrix Plus router.

    At the warning message and prompt, type yes to allow the command to proceed:

    root@mysfc0> request system reboot
    Reboot the system ? [yes,no] (no) yes 
    
    Rebooting lcc0-re1
    Rebooting lcc2-re1
    Shutdown NOW!
    Reboot consistency check bypassed - jinstall 9.6R1.2 will complete installation upon reboot
    [pid 23517]
    
    *** FINAL System shutdown message from root@mysfc0> ***
    System going down IMMEDIATELY 
    
    root@mysfc0> Jul 23 14:00:52 Waiting (max 60 seconds) for system process `vnlru' to stop...done
    Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
    Waiting (max 60 seconds) for system process `syncer' to stop...
    Syncing disks, vnodes remaining...1 1 1 0 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 done
    
    syncing disks... All buffers synced.
    Uptime: 26m26s
    recorded reboot as normal shutdown
    Rebooting...
    

    All of the default master Routing Engines (re0) in the routing matrix reboot from the boot devices on which the software was just installed, which loads the new JUNOS Software. Each reboot operation can take between 5 and 10 minutes to complete.

    ...router_boot_sequence... 
    

    When the default master Routing Engine on the TX Matrix Plus router (sfc0-re0) finishes rebooting, the management console attached to the default master Routing Engine on the TX Matrix Plus router displays the login prompt.

    var/pdb/profile_db initialized
    
    Profile database initialized
    Local package initialization:.
    kern.securelevel: -1 -> 1
    starting local daemons:.
    Thu Jul 23 14:11:00 PDT 2009
    
    login:

    The new version of JUNOS software is loaded and running on the new default master Routing Engines

  2. At a management console attached to the new default master Routing Engine (re1) on the TX Matrix Plus router, log in to the JUNOS CLI using a root administration account:
    Thu Jul 23 14:11:00 PDT 2009
    
    login: root
    Password: •••••••••
    
    --- JUNOS 9.6R1.2 built 2009-07-13 08:52:23 UTC
  3. Issue the show version command to verify the version of the software installed:
    root@mysfc0> show version
    sfc0-re0:
    --------------------------------------------------------------------------
    Hostname: mysfc0
    Model: txp
    JUNOS Base OS boot [9.6R1.2]
    JUNOS Base OS Software Suite [9.6R1.2]
    JUNOS Kernel Software Suite [9.6R1.2]
    JUNOS Crypto Software Suite [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (M/T Common) [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (T-Series) [9.6R1.2]
    JUNOS Online Documentation [9.6R1.2]
    JUNOS Voice Services Container package [9.6R1.2]
    JUNOS Border Gateway Function package [9.6R1.2]
    JUNOS Services AACL Container package [9.6R1.2]
    JUNOS Services LL-PDF Container package [9.6R1.2]
    JUNOS Services Stateful Firewall [9.6R1.2]
    JUNOS AppId Services [9.6R1.2]
    JUNOS IDP Services [9.6R1.2]
    JUNOS Routing Software Suite [9.6R1.2]
    
    lcc0-re0:
    --------------------------------------------------------------------------
    Hostname: mylcc0
    Model: t1600
    JUNOS Base OS boot [9.6R1.2]
    JUNOS Base OS Software Suite [9.6R1.2]
    JUNOS Kernel Software Suite [9.6R1.2]
    JUNOS Crypto Software Suite [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (M/T Common) [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (T-Series) [9.6R1.2]
    JUNOS Online Documentation [9.6R1.2]
    JUNOS Voice Services Container package [9.6R1.2]
    JUNOS Border Gateway Function package [9.6R1.2]
    JUNOS Services AACL Container package [9.6R1.2]
    JUNOS Services LL-PDF Container package [9.6R1.2]
    JUNOS Services Stateful Firewall [9.6R1.2]
    JUNOS AppId Services [9.6R1.2]
    JUNOS IDP Services [9.6R1.2]
    JUNOS Routing Software Suite [9.6R1.2]
    
    lcc2-re0:
    --------------------------------------------------------------------------
    Hostname: mylcc2
    Model: t1600
    JUNOS Base OS boot [9.6R1.2]
    JUNOS Base OS Software Suite [9.6R1.2]
    JUNOS Kernel Software Suite [9.6R1.2]
    JUNOS Crypto Software Suite [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (M/T Common) [9.6R1.2]
    JUNOS Packet Forwarding Engine Support (T-Series) [9.6R1.2]
    JUNOS Online Documentation [9.6R1.2]
    JUNOS Voice Services Container package [9.6R1.2]
    JUNOS Border Gateway Function package [9.6R1.2]
    JUNOS Services AACL Container package [9.6R1.2]
    JUNOS Services LL-PDF Container package [9.6R1.2]
    JUNOS Services Stateful Firewall [9.6R1.2]
    JUNOS AppId Services [9.6R1.2]
    JUNOS IDP Services [9.6R1.2]
    JUNOS Routing Software Suite [9.6R1.2]
    

Optional: Switching Routing Engine Mastership Back to the Default Master Routing Engines

The default backup Routing Engines (re1) are still operating as the elected master Routing Engines while the default master Routing Engines (re0) are operating as the elected backup Routing Engines.

To avoid confusion about which Routing Engine in any router is the master and which is the backup, you should switch the Routing Engine mastership assignment back to the original designations (with the re0 Routing Engines operating as the master Routing Engines and the re1 Routing Engines operating as the backup Routing Engines).

Note: Switching Routing Engine mastership causes traffic to be disrupted.

However, if you need to avoid another disruption to traffic while the Routing Engine mastership is switched on all the routers, you can skip this task.

To switch Routing Engine mastership back to the default master Routing Engine (re0) on all routers in the routing matrix:

  1. Transfer Routing Engine mastership to the backup Routing Engine (re1) for all routers in the routing matrix. To do this, issue the request chassis routing-engine master command and specify the switch and all-chassis options.

    At the warning message and prompt, type yes to allow the command to proceed:

    root@mysfc0> request chassis routing-engine master switch all-chassis
    warning: Traffic will be interrupted while the PFE is re-initialized
    Toggle mastership between routing engines ? [yes,no] (no) yes
    
    lcc0-re0:
    --------------------------------------------------------------------------
    warning: Traffic will be interrupted while the PFE is re-initialized
    Resolving mastership...
    Complete. The local routing engine becomes the master.
    
    lcc2-re0:
    --------------------------------------------------------------------------
    warning: Traffic will be interrupted while the PFE is re-initialized
    Resolving mastership...
    Complete. The local routing engine becomes the master.
    
    sfc0-re0:
    --------------------------------------------------------------------------
    warning: Traffic will be interrupted while the PFE is re-initialized
    Resolving mastership...
    Complete. The local routing engine becomes the master.
  2. Verify that Routing Engine mastership has indeed switched back to the default master Routing Engines (re0) in the routing matrix. To display Routing Engine mastership information, issue the show chassis routing-engine command at the TX Matrix Plus router:
    root@mysfc0> show chassis routing-engine
    sfc0-re0:
    --------------------------------------------------------------------------
    Routing Engine status:
      Slot 0:
        Current state                  Master
        Election priority              Master (default)
        ...output_truncated...
    
    Routing Engine status:
      Slot 1:
        Current state                  Backup
        Election priority              Backup (default)
        ...output_truncated...
    
    lcc0-re0:
    --------------------------------------------------------------------------
    Routing Engine status:
      Slot 0:
        Current state                  Master
        Election priority              Master (default)
        ...output_truncated...
    
    Routing Engine status:
      Slot 1:
        Current state                  Backup
        Election priority              Backup (default)
        ...output_truncated...
    
    lcc2-re0:
    --------------------------------------------------------------------------
    Routing Engine status:
      Slot 0:
        Current state                  Master
        Election priority              Master (default)
        ...output_truncated...
    
    Routing Engine status:
      Slot 1:
        Current state                  Backup
        Election priority              Backup (default)
        ...output_truncated...

Restoring the Original Configuration

After you have installed the new JUNOS Software and are satisfied that it is running properly on all Routing Engines, restore the routing matrix to the original configuration (that existed before you deleted it at the beginning of this procedure) and then back up the configuration change.

To restore the previous configuration and then create a configuration backup, perform the following steps at the master Routing Engine of the TX Matrix Plus router:

  1. Restore the routing matrix configuration that existed before you deleted it at the start of this procedure:
    {master}
    root@mysfc0-re0> configure
    Entering configuration mode
    
    {master}
    root@mysfc0# rollback 1
    load complete
    
  2. Commit the configuration changes on all Routing Engines, which activates the original configuration, and then return to operational mode:
    {master}
    root@mysfc0-re0# commit synchronize and-quit
    sfc0-re0: 
    configuration check succeeds
    lcc0-re1: 
    commit complete
    lcc0-re0: 
    commit complete
    lcc2-re1: 
    commit complete
    lcc2-re0: 
    commit complete
    sfc0-re1: 
    commit complete
    sfc0-re0: 
    commit complete
    
    {master}
    root@mysfc0-re0> 

Backing Up the Routing Engines

Back up the currently running and active file system partitions on each Routing Engine to standby partitions that are not running. Specifically, the root file system (/) is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on each Routing Engine's flash drive, and the /altroot and /altconfig file systems are on Routing Engine's hard drive.

Caution: After you run the request system snapshot command, you cannot return to the previous version of the software, because the running and backup copies of the software are identical.

To back up the Routing Engines of the routing matrix:

  1. To back up the master Routing Engines (re0) in the routing matrix, issue the request system snapshot command.

    The following example shows sample output for backing up the master Routing Engines:

    {master} 
    root@mysfc0-re0> request system snapshot 
    sfc0-re0:
    --------------------------------------------------------------------------
    Verifying compatibility of destination media partitions...
    Running newfs (220MB) on hard-disk media / partition (ad1s1a)...
    Running newfs (24MB) on hard-disk media /config partition (ad1s1e)...
    Copying '/dev/ad0s1a' to '/dev/ad1s1a' .. (this may take a few minutes)
    Copying '/dev/ad0s1e' to '/dev/ad1s1e' .. (this may take a few minutes)
    The following filesystems were archived: / /config
    
    lcc0-re0:
    --------------------------------------------------------------------------
    Verifying compatibility of destination media partitions...
    Running newfs (220MB) on hard-disk media / partition (ad1s1a)...
    Running newfs (24MB) on hard-disk media /config partition (ad1s1e)...
    Copying '/dev/ad0s1a' to '/dev/ad1s1a' .. (this may take a few minutes)
    Copying '/dev/ad0s1e' to '/dev/ad1s1e' .. (this may take a few minutes)
    The following filesystems were archived: / /config
    
    lcc2-re0:
    --------------------------------------------------------------------------
    Verifying compatibility of destination media partitions...
    Running newfs (220MB) on hard-disk media / partition (ad1s1a)...
    Running newfs (24MB) on hard-disk media /config partition (ad1s1e)...
    Copying '/dev/ad0s1a' to '/dev/ad1s1a' .. (this may take a few minutes)
    Copying '/dev/ad0s1e' to '/dev/ad1s1e' .. (this may take a few minutes)
    The following filesystems were archived: / /config
  2. To transfer Routing Engine mastership back to the default backup Routing Engines, issue the request chassis routing-engine command with the switch and all-chassis options.

    Caution: Switching Routing Engine mastership causes traffic to be disrupted.

    At the warning message and prompt, type yes to allow the operation to proceed

    {master} 
    root@mysfc0-re0> request chassis routing-engine master switch all-chassis 
    Toggle mastership between routing engines ? [yes,no] (no) yes 
    
    lcc0-re0:
    --------------------------------------------------------------------------
    Resolving mastership...
    Complete. The other routing engine becomes the master.
    
    lcc2-re0:
    --------------------------------------------------------------------------
    Resolving mastership...
    Complete. The other routing engine becomes the master.
    
    sfc0-re0:
    --------------------------------------------------------------------------
    Resolving mastership...
    Complete. The other routing engine becomes the master.
  3. To back up the backup Routing Engines (re1), issue the request system snapshot operational command at the backup Routing Engine on the TX Matrix Plus router.

    The following examples shows sample command output for backing up the backup Routing Engines:

    {master}
    root@mysfc0-re1> request system snapshot
    sfc0-re1:
    --------------------------------------------------------------------------
    Verifying compatibility of destination media partitions...
    Running newfs (220MB) on hard-disk media / partition (ad1s1a)...
    Running newfs (24MB) on hard-disk media /config partition (ad1s1e)...
    Copying '/dev/ad0s1a' to '/dev/ad1s1a' .. (this may take a few minutes)
    Copying '/dev/ad0s1e' to '/dev/ad1s1e' .. (this may take a few minutes)
    The following filesystems were archived: / /config
    
    lcc0-re1:
    --------------------------------------------------------------------------
    Verifying compatibility of destination media partitions...
    Running newfs (223MB) on hard-disk media / partition (ad2s1a)...
    Running newfs (24MB) on hard-disk media /config partition (ad2s1e)...
    Copying '/dev/ad0s1a' to '/dev/ad2s1a' .. (this may take a few minutes)
    Copying '/dev/ad0s1e' to '/dev/ad2s1e' .. (this may take a few minutes)
    The following filesystems were archived: / /config
    
    lcc2-re1:
    --------------------------------------------------------------------------
    Verifying compatibility of destination media partitions...
    Running newfs (220MB) on hard-disk media / partition (ad1s1a)...
    Running newfs (24MB) on hard-disk media /config partition (ad1s1e)...
    Copying '/dev/ad0s1a' to '/dev/ad1s1a' .. (this may take a few minutes)
    Copying '/dev/ad0s1e' to '/dev/ad1s1e' .. (this may take a few minutes)
    The following filesystems were archived: / /config

Published: 2010-04-15

[an error occurred while processing this directive]