close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Junos OS Overview
- play_arrow Junos OS Overview
  - Junos OS Overview
play_arrow Install, Upgrade, or Downgrade for Junos OS Software
- play_arrow Junos OS Install and Upgrade Overview
  - Junos OS Installation and Upgrade Overview
  - Storage Media and Routing Engines (Junos OS)
- play_arrow Prepare for Installation and Upgrade
- play_arrow Upgrade to Junos OS with Upgraded FreeBSD
  - Upgrading and Downgrading to Junos with Upgraded FreeBSD
- play_arrow Install Software on Routers
- play_arrow Install Software on Switches
- play_arrow Install Software on Firewalls
- play_arrow Manage YANG Packages During an Upgrade or Downgrade
  - Managing YANG Packages and Configurations During a Software Upgrade or Downgrade
play_arrow System Backup and Recovery
- play_arrow Back Up an Installation
  - Backing Up an Installation Using Snapshots (Junos OS)
- play_arrow Recover Junos OS
play_arrow Installation, Upgrade, and Downgrade VM Host Software, and Back Up and Recovery of VM Host Devices
- play_arrow VM Host Overview and CLI Commands
  - VM Host Overview (Junos OS)
  - VM Host Operations and Management
- play_arrow Boot Process for Routers with VM Host Support
  - Boot Process for Routers with VM Host Support
- play_arrow Installing, Upgrading, Backing Up, and Recovery of VM Host
  - Installing, Upgrading, Backing Up, and Recovery of VM Host
- play_arrow Copying VM Host Installation Package to the PXE Boot Server
  - Copying VM Host Installation Package to the PXE Boot Server
- play_arrow Upgrading NFX Devices
- play_arrow Creating an Emergency Boot Device for Routing Engines with VM Host Support
  - Creating an Emergency Boot Device for Routing Engines with VM Host Support
- play_arrow Upgrading Firmware on Routing Engines with VM Host Support
  - Upgrading the SSD Firmware on Routing Engines with VM Host Support
  - Upgrading the i40e NVM Firmware on Routing Engines with VM Host Support
- play_arrow Disabling Autorecovery on Routing Engines with VM Host Support
  - Disabling Autorecovery on Routing Engines with VM Host Support
play_arrow Installing and Upgrading the BIOS and Firmware
- play_arrow For Routers
  - Installing and Upgrading Firmware
- play_arrow For Switches
- play_arrow For Firewalls
  - Upgrading BIOS and Firmware (SRX only)
  - Upgrading 5.1KW HVAC/HVDC Single and Dual Input PSM Firmware (SRX5800)
play_arrow Zero Touch Provisioning and Secure Zero Touch Provisioning
play_arrow Phone-Home Client
- play_arrow Phone-Home Client
play_arrow Automatic Installation of Configuration Files
- play_arrow Automatic Installation of Configuration Files
play_arrow Configuration Statements and Operational Commands
- play_arrow Configuration Statements and Operational Commands
  - Junos CLI Reference Overview

list Table of Contents

English

Installing Software on QFX Series Devices (Junos OS)

date_range 01-Dec-23

arrow_backward

arrow_forward

QFX Series devices are delivered with the Junos operating system (Junos OS) preinstalled. Before you start this procedure, decide which software package you need and download it. For information on which packages to use for which upgrades, see Junos OS Installation Package Names.

Installing Software Packages on QFX Series Devices (Junos OS)

We recommend that you connect to the console port while installing the installation package so you can respond to any required user input and detect any errors that may occur.

Before you install the new installation package, back up your current configuration files because the upgrade process removes all of the stored files on the switch.

To back up your current configuration files, enter the save command:

content_copy zoom_out_map
user@switch# save filename 

Executing this command saves a copy of your configuration files to a remote location such as an external USB device.

Installation procedures are in the following subsections:

Installing the Software on QFX10002-60C Switches
Installing a Standard Software Package on QFX5000 and EX4600 Switches
Installing a Standard Software Package on QFX10002 Switches
Upgrading Software from Junos OS Release 15.1X53-D3X to Junos OS Release 15.1X53-D60, 15.1X53-D61.7, 15.1X53-D62, and 15.1X53-D63 on QFX10008 and QFX10016 Switches
Installing a Software Package on QFX10008 and QFX10016 Switches

Installing the Software on QFX10002-60C Switches

This section explains how to upgrade the software, which includes both the host OS and the Junos OS. This upgrade requires that you use a VM host package—for example, a junos-vmhost-install-x.tgz .

During a software upgrade, the alternate partition of the SSD is upgraded, which will become primary partition after a reboot. If there is a boot failure on the primary SSD, the switch can boot using the snapshot available on the alternate SSD.

Note:

The QFX10002-60C switch supports only the 64-bit version of Junos OS.

Note:

If you have important files in directories other than /config and /var, copy the files to a secure location before upgrading. The files under /config and /var (except /var/etc) are preserved after the upgrade.

To upgrade the software, you can use the following methods:

If the installation package resides locally on the switch, issue the request vmhost software add <pathname><source> command.
For example:
```
user@switch> request vmhost software add /var/tmp/junos-vmhost-install-qfx-x86-64-18.1R1.9.tgz
```
If the Install Package resides remotely from the switch, issue the request vmhost software add <pathname><source> command.

For example:
```
user@switch> request vmhost software add ftp://ftpserver/directory/junos-vmhost-install-qfx-x86-64-18.1R1.9.tgz
```
After the reboot has finished, verify that the new version of software has been properly installed by issuing the show version command.
```
user@switch> show version
```

Installing a Standard Software Package on QFX5000 and EX4600 Switches

Note:

Before you install the software, back up any critical files in /var/home. For more information regarding how to back up critical files, contact Customer Support at https://www.juniper.net/support.

Note:

On QFX5100 and EX4600 switches, the Host OS is not upgraded automatically, so you must use the force-host option if you want the Junos OS and Host OS versions to be the same.

However, pay attention to these notes regarding Junos OS and Host OS versions:

The Junos OS and Host OS versions do not need to be the same.
During an ISSU, the Host OS cannot be upgraded.
Upgrading the Host OS is not required for every software upgrade, as noted above.

If you are downgrading from Junos OS Release 14.1X53-D40 to any release earlier than 14.1X53-D40, you must use the force-host option or else the switch will issue core dumps.

Note:

The QFX5100 and EX4600 standalone SKUs and non-mixed Virtual Chassis, support software images with the package filenames in the yyy-qfx-5-zzz (non-TVP architecture) format, for all Junos OS releases up to Junos OS Release 21.4. They do not support software images with the package filenames in the yyy-qfx-5e-zzz (TVP architecture) format.

If the installation package resides locally on the switch, issue the request system software add <pathname><source> reboot command.
For example:
```
user@switch> request system software add /var/tmp/jinstall-host-qfx-5-17.2R1.n-signed.tgz reboot
```
If the Install Package resides remotely, issue the request system software add <pathname><source> reboot command.

For example:
```
user@switch> request system software add ftp://ftpserver/directory/jinstall-host-qfx-5-17.2R1.n-signed.tgz reboot
```
After the reboot has finished, verify that the new version of software has been properly installed by executing the show version command.
```
user@switch> show version
```

Installing a Standard Software Package on QFX10002 Switches

Note:

Before you install the software, back up any critical files in /var/home. For more information regarding how to back up critical files, contact Customer Support at https://www.juniper.net/support.

Note:

If you want to downgrade from Junos OS Release 15.1X53-D60 to a previous release, pay attention to these caveats:

Table 1: Caveats for Downgrading from Junos OS Release 15.1X53-D60 to Previous Software Releases
Junos OS Software Releases	Using the CLI	Using a USB Stick
15.1X53-D33	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.
15.1X53-D32	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded. Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded. Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D32.
15.1X53-D30	No	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded. Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.
Releases prior to 15.1X53-D30	No	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded. Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.

Install the software in one of two ways:
- If the installation package resides locally on the switch, issue the request system software add <pathname><source> reboot command.
  
  For example:
  user@switch> request system software add /var/tmp/jinstall-host-qfx-10-17.2R1.n-secure-signed.tgz reboot
- If the Install Package resides remotely, issue the request system software add <pathname><source> reboot command.
  
  For example:
  user@switch> request system software add ftp://ftpserver/directory/jinstall-host-qfx-10-17.2R1.n-secure-signed.tgz reboot
After the reboot has finished, verify that the new version of software has been properly installed by issuing the show version command.
```
user@switch> show version
```

Upgrading Software from Junos OS Release 15.1X53-D3X to Junos OS Release 15.1X53-D60, 15.1X53-D61.7, 15.1X53-D62, and 15.1X53-D63 on QFX10008 and QFX10016 Switches

Note:

Before you install the software, back up any critical files in /var/home. For more information regarding how to back up critical files, contact Customer Support at https://www.juniper.net/support.

Note:

If you want to downgrade from Junos OS Release 15.1X53-D60 to a previous release, pay attention to these caveats:

Table 2: Caveats for Downgrading from Junos OS Release 15.1X53-D60 to Previous Software Releases
Junos OS Software Releases	Using the CLI	Using a USB Stick
15.1X53-D33	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded.
15.1X53-D32	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded. Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded. Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D32.
15.1X53-D30	No	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded. Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.
Releases prior to 15.1X53-D30	No	Yes, but the configuration is lost, and there is no workaround. We recommend that you save the configuration to an external location, such as a remote server, and then load the configuration after you have successfully downgraded. Note: You must downgrade to Junos OS Release 15.1X53-D33 before you downgrade to Junos OS Release 15.1X53-D30.

The switch contains two routing engines, so you will need to install the software on each routing engine (re0 and re1).

To install the software on re0:
If the installation package resides locally on the switch, issue the request system software add <pathname><source> command.
```
user@switch> request system software add /var/tmp/jinstall-host-qfx-10-m-15.1X53-D60.4-secure-domestic-signed.tgz re0
```
If the Install Package resides remotely from the switch, issue the request system software add <pathname><source> re0 command.

For example:
```
user@switch> request system software add ftp://ftpserver/directory/jinstall-host-qfx-10-m-15.1X53-D60.4-secure-domestic-signed.tgz re0
```
To install the software on re1:
If the installation package resides locally on the switch, issue the request system software add <pathname><source> command.
```
user@switch> request system software add /var/tmp/jinstall-host-qfx-10-m-15.1X53-D60.4-secure-domestic-signed.tgz re1
```
If the Install Package resides remotely from the switch, issue the request system software add <pathname><source> re1 command.

For example:
```
user@switch> request system software add ftp://ftpserver/directory/jinstall-host-qfx-10-m-15.1X53-D60.4-secure-domestic-signed.tgz re1
```
Reboot both routing engines.
For example:
```
user@switch> request system reboot both-routing-engines
```
After the reboot has finished, verify that the new version of software has been properly installed by executing the show version command.
```
user@switch> show version
```

Installing a Software Package on QFX10008 and QFX10016 Switches

Because the switch has two Routing Engines, perform a Junos OS installation on each Routing Engine separately to avoid disrupting network operation.

Note:

Before you install the software, back up any critical files in /var/home. For more information regarding how to back up critical files, contact Customer Support at https://www.juniper.net/support.

CAUTION:

If graceful Routing Engine switchover (GRES), nonstop bridging (NSB), or nonstop active routing (NSR) is enabled when you initiate a software installation, the software does not install properly. Make sure you issue the CLI delete chassis redundancy command when prompted. If GRES is enabled, it will be removed with the redundancy command. By default, NSR is disabled. If NSR is enabled, remove the nonstop-routing statement from the [edit routing-options] hierarchy level to disable it.

To upgrade the software, perform the following tasks:

Preparing the Switch for Installation (Junos OS)
Installing Software on the Backup Routing Engine (Junos OS)
Installing Software on the Primary Routing Engine (Junos OS)

Preparing the Switch for Installation (Junos OS)

Perform the following steps before installing the software:

Log in to the primary Routing Engine’s console.

For more information about logging in to the Routing Engine through the console port, see the specific hardware guide for your switch.
From the command line, enter configuration mode:
```
user@switch> configure
```
Disable Routing Engine redundancy:
```
user@switch# delete chassis redundancy
```

Disable nonstop-bridging:

content_copy zoom_out_map
user@switch# delete protocols layer2-control nonstop-bridging

Save the configuration change on both Routing Engines:
```
user@switch# commit synchronize
```
Exit the CLI configuration mode:
```
user@switch# exit
```

Installing Software on the Backup Routing Engine (Junos OS)

After the switch has been prepared, you first install the new Junos OS release on the backup Routing Engine, while keeping the currently running software version on the primary Routing Engine. This enables the primary Routing Engine to continue operations, minimizing disruption to your network.

After making sure that the new software version is running correctly on the backup Routing Engine, you are ready to switch routing control to the backup Routing Engine, and then upgrade or downgrade the software version on the other Routing Engine.

Log in to the console port on the other Routing Engine (currently the backup).

For more information about logging in to the Routing Engine through the console port, see the specific hardware guide for your switch.
Install the new software package using the request system software add command:
```
user@switch> request system software add validate /var/tmp/jinstall-host-qfx-10-17.2R1.n-secure-signed.tgz
```
For more information about the request system software add command, see the CLI Explorer.
Reboot the switch to start the new software using the request system reboot command:
```
user@switch> request system reboot
```
Note:
You must reboot the switch to load the new installation of Junos OS on the switch.

To terminate the installation, do not reboot your switch. Instead, finish the installation and then issue the request system software delete <package-name> command. This is your last chance to stop the installation.
All the software is loaded when you reboot the switch. Installation can take between 5 and 10 minutes. The switch then reboots from the boot device on which the software was just installed. When the reboot is complete, the switch displays the login prompt.

While the software is being upgraded, the Routing Engine on which you are performing the installation is not sending traffic.
Log in and issue the show version command to verify the version of the software installed.
```
user@switch> show version
```

Installing Software on the Primary Routing Engine (Junos OS)

Once the software is installed on the backup Routing Engine, you are ready to switch routing control to the backup Routing Engine, and then upgrade or downgrade the primary Routing Engine software:

Log in to the primary Routing Engine console port.

For more information about logging in to the Routing Engine through the console port, see the specific hardware guide for your switch.
Transfer routing control to the backup Routing Engine:
```
user@switch> request chassis routing-engine master switch
```
For more information about the request chassis routing-engine master command, see the CLI Explorer.

Verify that the backup Routing Engine (slot 1) is the primary Routing Engine:

content_copy zoom_out_map
user@switch> show chassis routing-engine
Routing Engine status:
  Slot 0:
    Current state                  Backup
    Election priority              Master (default)

Routing Engine status:
  Slot 1:
    Current state                  Master
    Election priority              Backup (default)

Install the new software package using the request system software add command:
```
user@switch> request system software add validate /var/tmp/jinstall-host-qfx-10-17.2R1.n-secure-signed.tgz
```
For more information about the request system software add command, see the CLI Explorer.
Reboot the Routing Engine using the request system reboot command:
```
user@switch> request system reboot
```
Note:
You must reboot to load the new installation of Junos OS on the switch.

To terminate the installation, do not reboot your system. Instead, finish the installation and then issue the request system software delete jinstall <package-name> command. This is your last chance to stop the installation.
The software is loaded when you reboot the system. Installation can take between 5 and 10 minutes. The switch then reboots from the boot device on which the software was just installed. When the reboot is complete, the switch displays the login prompt.

While the software is being upgraded, the Routing Engine on which you are performing the installation does not send traffic.
Log in and issue the show version command to verify the version of the software installed.
Transfer routing control back to the primary Routing Engine:
```
user@switch> request chassis routing-engine master switch
```
For more information about the request chassis routing-engine master command, see the CLI Explorer.

Verify that the primary Routing Engine (slot 0) is indeed the primary Routing Engine:

content_copy zoom_out_map
user@switch> show chassis routing-engine
Routing Engine status:
  Slot 0:
    Current state                  Master
    Election priority              Master (default)

outing Engine status:
  Slot 1:
    Current state                  Backup
    Election priority              Backup (default)

Upgrading Software by Using Automatic Software Download for Switches (Junos OS)

The automatic software download feature uses the Dynamic Host Configuration Protocol (DHCP) message exchange process to download and install software packages. You configure the automatic software download feature on switches that act as DHCP clients. You must enable automatic software download on a switch before the software upgrade can occur.

You configure a path to a software package file on the DHCP server. The server communicates the path to the software package file through DHCP server messages.

If you enable automatic software download, the DHCP client switch compares the software package name in the DHCP server message with the name of the software package that booted the switch. If the software packages are different, the DHCP client switch downloads and installs the software package specified in the DHCP server message.

Complete the following tasks in order:

Configuring DHCP Services for the Switch (Junos OS)
Enabling Automatic Software Download on a Switch (Junos OS)
Verifying That Automatic Software Download Is Working Correctly (Junos OS)

Configuring DHCP Services for the Switch (Junos OS)

Before you upgrade software by using automatic software download, ensure that you have configured DHCP services for the switch, including configuring a path to a boot server and a boot file.

To configure a path to a boot server and a boot file:

Configure the name of the boot server advertised to DHCP clients. The client uses a boot file located on the boot server to complete DHCP setup. This configuration is equivalent to DHCP option 66:
```
[edit system services dhcp]
user@switch# set boot-server (address | hostname) 
```
Set the boot file advertised to DHCP clients. After the client receives an IP address and the boot file location from the DHCP server, the client uses the boot image stored in the boot file to complete the DHCP setup. This configuration is equivalent to DHCP option 67:
```
[edit system services dhcp]
user@switch# set boot-file filename
```

Enabling Automatic Software Download on a Switch (Junos OS)

To enable automatic software download on a switch that acts as a DHCP client:

content_copy zoom_out_map
[edit chassis]
user@switch# set auto-image-upgrade

After automatic software download is enabled on your DHCP client switch and after DHCP services are enabled on your network, an automatic software download can occur at any time as part of the DHCP message exchange process.

If an automatic software download occurs, you see the following message on the switch:

content_copy zoom_out_map
Auto-image upgrade started 
On successful installation system will reboot automatically

The switch reboots automatically to complete the upgrade.

Verifying That Automatic Software Download Is Working Correctly (Junos OS)

Purpose
Action
Meaning

Purpose

Verify that the automatic software download feature is working correctly.

Action

Use the show system services dhcp client interface-name command to verify that the automatic software download feature has been used to install a software package.

content_copy zoom_out_map
user@switch> show system services dhcp client ge-0/0/1.0              
 Logical Interface Name       ge-0/0/1.0      
  Hardware address        00:0a:12:00:12:12      
  Client Status           bound      
  Vendor Identifier       ether      
  Server Address          10.1.1.1      
  Address obtained        10.1.1.89       
  Lease Obtained at       2009-08-20 18:13:04 PST
  Lease Expires at        2009-08-22 18:13:04 PST 

DHCP Options :                      
  Name: name-server, Value: [ 10.209.194.131, 203.0.113.2, 203.0.113.3 ]           
  Name: server-identifier, Value: 10.1.1.1           
  Name: router, Value: [ 10.1.1.80 ]            
  Name: boot-image, 
  Value: jinstall-ex-4200-9.6R1.5-domestic-signed.tgz
  Name: boot-image-location,
  Value: 10.1.1.25:/bootfiles/

Meaning

The output from this command shows the name and location of the software package under DHCP options when automatic software download was last used to install a software package. The sample output in DHCP options shows that the last DHCP server message to arrive on the DHCP client had a boot server address of 10.1.1.1 and a boot file named jinstall-ex-4200-9.6R1.5-domestic-signed.tgz. If automatic software download was enabled on this client switch during the last DHCP message exchange, these values were used by the switch to upgrade the software.

Upgrading Jloader Software on QFX Series Devices

Jloader software contains a boot loader (Uboot), which is used to bring up QFX Series devices and load the Junos OS from the flash memory of these devices. You can upgrade Jloader software on QFX3500 switches, QFX3500 and QFX3600 Node devices, and QFX3600-I and QFX3008-I Interconnect devices.

Note:

Before you upgrade the Jloader software, see Table 3, Table 4, and Table 5 to make sure that you are upgrading to the right version of Jloader software for the Junos OS software release running on your QFX3500 switches, or Node devices and Interconnect devices in your QFabric system.

See Table 6 to see which Uboot software versions are available and the filenames of the Jloader software packages.

Table 3: Junos OS and Jloader Software Compatibility Matrix for the QFX3500 Switch and QFX3500 Node Device
Junos OS Software Version
Junos OS Software Version	1.1.2	1.1.4	1.1.5	1.1.8
11.3R1 and later (QFX3500 switch)	Supported	Supported	Not supported	Supported and recommended
11.3X30.6 and later (QFX3500 Node device)	Supported	Supported	Not supported	Supported and recommended
12.1X49-D1 and later (QFX3500 switch)	Supported	Supported	Not supported	Supported and recommended
12.2X50-D1 and later (QFX3500 switch and QFX3500 Node device)	Supported	Supported	Not supported	Supported and recommended

Note:

An en dash means that the item is not applicable.

Table 4: Junos OS and Jloader Software Compatibility Matrix for the QFX3008-I Interconnect Device
Junos OS Software Version
Junos OS Software Version	1.1.2	1.1.4	1.1.5	1.1.8
11.3X30.9 and later (QFX3008-I Interconnect device)	Supported	Supported	Not supported	Supported and recommended
11.3X30.6 and later (QFX3008-I Interconnect device)	Supported	Supported	Not supported	Supported and recommended
12.2X50-D10.3 and later (QFX3008-I Interconnect device)	Supported	Supported	Not supported	Supported and recommended

Note:

An en dash means that the item is not applicable.

Table 5: Junos OS and Jloader Software Compatibility Matrix for the QFX3600-I Interconnect Device and QFX3600 Node Device
Junos OS Software Version
Junos OS Software Version	1.1.2	1.1.4	1.1.5	1.1.8
12.2X50-D10.3 and later (QFX3600-I Interconnect Device and QFX3600 Node Device)	-	-	Supported	Supported and recommended
12.2X50-D20 and later (QFX3600 switch)	-	-	Supported	Supported and recommended

Table 6: Uboot Software Release and Jloader Software Compatibility Matrix
Uboot Software Release Number	Jloader Software Package Name
1.1.2	jloader-qfx-11.3X30.9-signed.tgz
1.1.4 (11.3R3 and 11.3R2 releases only. Not supported on 11.3R1)	jloader-qfx-11.3I20120127_0733_dc-builder-signed.tgz
1.1.4 (12.1R1 release and later)	jloader-qfx-12.1-20120125_pr.0-signed.tgz
1.1.5 (12.2X50-D10.3 and later)	jloader-qfx-12.2X50.D10.3-signed.tgz
1.1.8 (13.1X50-D15.1 and later)	jloader-qfx-13.3-20130831_pr_branch_qfd.0.tgz

Jloader Software Version 1.1.4 Guidelines
Upgrading Jloader Software on a QFX3500 Switch
Upgrading Jloader Software on a QFabric System

Jloader Software Version 1.1.4 Guidelines

Jloader Release 1.1.4 is compatible with Junos OS Release 11.3R3 and 11.3R2, and Junos OS Release 12.1R1 and later. Jloader Release 1.1.4 is not compatible with Junos OS Release 11.3R1. The Jloader software package names are different for versions 1.1.4 (Junos OS 11.3R3 and 11.3R2) and 1.1.4 (Junos OS 12.2R1 release and later), but the binaries are the same. Because the binaries are the same, you can upgrade or downgrade to any Junos OS release.

If you have Junos OS Release 11.3 installed and want to upgrade the Jloader software from version 1.1.2 to version 1.1.4, you need to upgrade using the jloader-qfx-11.3I20120127_0733_dc-builder-signed.tgz software package.
If you have Junos OS Release 11.3R2 installed and want to upgrade to Junos OS Release 12.1, you do not need to upgrade the Jloader Release and can continue to use Jloader Release 1.1.2.
If you have Junos OS Release 12.1 installed and want to upgrade the Jloader software from version 1.1.2 to version 1.1.4, you need to upgrade using the jloader-qfx-12.1-20120125_pr.0-signed.tgz software package.
If you upgrade to Junos OS Release 12.1, you can upgrade to Jloader Release 1.1.4 using the jloader-qfx-12.1-20120125_pr.0-signed.tgz software package.

Upgrading Jloader Software on a QFX3500 Switch

The Jloader software for a QFX3500 switch resides in two flash memory banks. At any time, one bank acts as the primary bank, and the QFX3500 switch boots from it. The other bank is the backup bank—if the QFX3500 switch cannot boot from the primary bank, it boots from the backup bank. When you upgrade the Jloader software, the upgraded software is installed in the backup bank, which then becomes the new primary bank. Thus the primary and backup banks alternate each time you upgrade the Jloader software, with the primary bank containing the most recently installed version of the software, and the backup bank containing the previous version. To upgrade the Jloader software on a QFX3500 switch, you must perform the upgrade twice: once for each bank. Each upgrade requires that you to reboot the QFX3500 switch.

Note:

If you are running Junos OS Release 11.3R1 or Junos OS Release 11.3R2, you must use the no-validate option when you issue the request system software add command to upgrade the Jloader software. Otherwise, the installation will fail and you receive a configuration error. The no-validate option is not required for Junos OS Release 11.3R3 and later.

Note:

After you upgrade the Jloader software on the first bank, the software package is deleted after you reboot. Make sure that you have either downloaded the Jloader software package to either a remote site or in a local directory on the switch, such as the /var/tmp directory on the QFX3500 device.

In a browser, go to https://support.juniper.net.
The Junos Platforms Download Software page appears.
In the QFX Series section of the Junos Platforms Download Software download page, select the QFX Series platform software you want to download.
Select the number of the software version that you want to download.
Read the End User License Agreement, click the I agree radio button, and then click Proceed.
Open or save the jloader-qfx-version-signed.tgz file either to a local system or to a remote location. If you are saving the installation package to a remote system, make sure that you can access it using HTTP, TFTP, FTP, or scp.
Log in to the QFX3500 switch and enter the shell. We recommend using a console connection.
Determine the version of the Jloader software package installed on the switch.
For example:
```
root@switch% ls
gres-tp krt_gencfg_filter.txt
jloader-qfx-11.3-20110510.0-signed.tgz
```
Determine the version of the Uboot software that is running in the bank:
For example:
```
root@switch% kenv | grep boot.version

boot.version="1.0.7"
```

Enter the CLI and install the Jloader software package.

To install a Jloader software package that is located in the /var/tmp directory, issue the request system software add /var/tmp/jloader-qfx-version.tgz no-validate command:

For example:

content_copy zoom_out_map
user@switch> request system software add /var/tmp/jloader-qfx-11.3-20110510.0-signed.tgz no-validate

You see the following messages during the installation:

content_copy zoom_out_map
Verified jloader-qfx-11.3-20110510.0.tgz signed by PackageProduction_11_3_0
Adding jloader-qfx...
Installation in progress, please wait...
Mounted jloader-qfx package on /dev/md8...
Verified manifest signed by PackageProduction_11_3_0
Verified jloader-qfx-11.3-20110510.0 signed by PackageProduction_11_3_0
Registering jloader-qfx as unsupported

Installation finished successfully.
Please reboot to activate the package
Saving package file in /var/sw/pkg/jloader-qfx-11.3-20110510.0-signed.tgz ...
Saving state for rollback ...

juniper@qfx3500> 

To install a Jloader software package located on a remote server using FTP, issue the request system software add /ftp://hostname/pathname/jloader-qfx-version-signed.tgz no-validate command.

For example:
```
user@switch> request system software add /ftp://hostname/pathname/jloader-qfx-11.3-20110510.0-signed.tgz no-validate
```
To install a Jloader software package located on a remote server using HTTP, issue the request system software add /http://hostname/pathname/jloader-qfx- version-signed.tgz no-validate command.

For example:
```
user@switch> request system software add /http://hostname/pathname/jloader-qfx-11.3-20110510.0-signed.tgz no-validate
```

When prompted, reboot the Control Board by issuing the request system reboot command.
For example:
```
user@switch> request system reboot
Reboot the system ? [yes,no] (no) yes
```
Enter the shell and verify that the version of the Uboot software in the primary bank is the version you just installed.
For example:
```
root@switch% kenv | grep boot.version

boot.version="1.1.1"
```
To install the Jloader software package on the current backup bank, repeat Step 10 through Step 14.

Upgrading Jloader Software on a QFabric System

This procedure explains how to upgrade the Jloader software on your Node devices and Interconnect devices. The example shows how to upgrade the Jloader Release 1.1.1 to 1.1.2 on a Node device with the serial number BBAK1186.

Note:

Before you upgrade the Jloader software, make sure you have the serial numbers of the Node devices, Interconnect devices, and Control Boards in the Interconnect devices you want to upgrade.

Issue the show chassis hardware node-device ? command to view the serial numbers of the Node devices.

For example:

content_copy zoom_out_map
user@qfabric> show chassis hardware node-device ?

  <node-device>        Node device identifier
  BBAK1186             Node device
  BBAK3149             Node device
  BBAK3177             Node device
  BBAK8063             Node device
  BBAK8799             Node device
  P2443-C              Node device
  P2515-C              Node device
  P3708-C              Node device
  P3885-C              Node device
  P3916-C              Node device
  node0                Node device
  node1                Node device
  node2                Node device
  node3                Node device
  node4                Node device
  node5                Node device
  node6                Node device
  node7                Node device
  node8                Node device

An example of a Node device serial number is BBAK1186.

Issue the show chassis hardware interconnect-device ? command to view the serial numbers of the Interconnect devices.

For example:

content_copy zoom_out_map
user@qfabric> show chassis hardware interconnect-device ?

Possible completions:
  interconnect-device  Interconnect device identifier
  IC-F1052             Interconnect device
  IC-F3947             Interconnect device

The Interconnect device serial numbers are IC-F1052 and IC-F3947.

Issue the show chassis hardware interconnect-device name command to view the serial numbers of the Control Boards in the Interconnect device.

For example:

content_copy zoom_out_map
user@qfabric> show chassis hardware interconnect-device IC-F3947

Hardware inventory:
Item             Version  Part number  Serial number     Description
Chassis          REV 10                F3947             QFXC08-3008
Midplane         REV 10   750-035835   F3947-C           QFX Midplane
CB 0             REV 14   750-035855   ZJ9432            QFX Chassis Control Board
  Routing Engine 0        BUILTIN      BUILTIN           QFX Routing Engine
CB 1             REV 14   750-035855   ZJ9404            QFX Chassis Control Board

The Control Board serial numbers are ZJ9432 and ZJ9404.

Issue the show chassis firmware node-device name command to see which version of Uboot software you have installed on your Node device.
For example:
```
user@qfabric> show chassis firmware node-device BBAK1186

Part                     Type       Version
node4                    U-Boot     1.1.6 (May 10 2011 - 04:52:59) 1.1.1       
                         loader     FreeBSD/MIPS U-Boot bootstrap loader 0.1   
```
The Uboot software version is 1.1.1. The loader software version appears after the timestamp for U-Boot 1.1.6.

Issue the show chassis firmware interconnect-device name command to see which version of Uboot software you have installed on the Routing Engines located on the Control Boards of the Interconnect device.

For example:

content_copy zoom_out_map
user@qfabric> show chassis firmware interconnect-device IC-F3947

Part                     Type       Version
Routing Engine 0         U-Boot     U-Boot 1.1.6 (Jan 27 2012 - 03:24:34) 1.1.4
                         loader     FreeBSD/MIPS U-Boot bootstrap loader 0.1   
Routing Engine 1         U-Boot     U-Boot 1.1.6 (Jan 27 2012 - 03:24:34) 1.1.4
                         loader     FreeBSD/MIPS U-Boot bootstrap loader 0.1   

The Uboot software version is 1.1.4. The loader software version appears after the timestamp for U-Boot 1.1.6.

In a browser, go to https://support.juniper.net.
The Downloads page appears.
Select the product you want software for.
Find and click the file you want to download.
A login screen appears.
Enter your username and password, and press Enter.
Read the End User License Agreement, click the I agree radio button, and then click Proceed.
Open or save the jloader-qfx-version-signed.tgz file either to a local system or to a remote location. If you are saving the installation package to a remote system, make sure that you can access it using HTTP, TFTP, FTP, or scp.
Retrieve the software from the location in which you downloaded it. To do this, issue the request system software download /path/package-name command.
For example:
```
user@qfabric> request system software download ftp://server/files/jloader-qfx-11.3X30.9-signed.tgz
```
Log in to the Director device as root and enter the shell to verify that you have downloaded the Jloader software package. We recommend using a console connection. The software package is copied from where you downloaded it and is placed locally on the QFabric system in the /pbdata/packages directory.
For example:
```
[root@dg0] # pwd
/pbdata/packages
[root@dg0] # ls
jloader-qfx-11.3X30.9-signed.tgz
```
Before you copy over the Jloader software package to the Node device or Interconnect device, determine the directory that matches the serial number of the Node device or Interconnect device that you want to upgrade. View the remote logs and the Node device and Interconnect device serial numbers by issuing the ls /pdbata/export/rlogs command at the command line of the Director device before you copy the software package over to the device.
Note:
The /pbdata/export/rlogs/node-device-serial-ID and /pbdata/export/rlogs/interconnect-device-serial-ID directories on the Director device are NFS mounted as the /tftpboot/logfiles directories on the Node device and Interconnect device. These directories are created for all Node devices and Interconnect devices in a QFabric system. The Jloader files are stored in the /tftpboot/logfiles directories for each Node device and Interconnect device.
For example:
```
[root@dg0 tmp] # ls /pdbata/export/rlogs
02de4930-828b-11e1-a319-00e081c57938  c9898afe-828b-11e1-956c-00e081c57938
04103b2a-29d5-e011-bf8a-0e6bdf3aa1e6  eeba4aac-828b-11e1-85e2-00e081c57938
1e2739e0-828b-11e1-bf74-00e081c57938  F1052
8d8a978c-828b-11e1-a833-00e081c57938  F3947
ad55b89e-828b-11e1-b70e-00e081c57938  P2443-C
BBAK1186                              P2515-C
BBAK3149                              P3708-C
BBAK3177                              P3885-C
BBAK8063                              P3916-C
BBAK8799
```
BBAK1186 is the serial number of the Node device that needs to be upgraded.
Copy the Jloader software package from the /var/tmp directory to the /pbdata/export/rlogs/BBAK1186 directory.
For example:
```
[root@dg0 tmp] # cp jloader-qfx-11.3X30.9-signed.tgz /pbdata/export/rlogs/BBAK1186
```
Confirm that the Jloader software package you copied over is in the /pbdata/export/rlogs/BBAK1186 directory.
For example:
```
[root@dg0 tmp] # ls /pbdata/export/rlogs/BBAK1186
jloader-qfx-11.3X30.9-signed.tgz
```

Issue the /root/dns.dump command to find out the internal IP addresses of the Node device or Interconnect device.

content_copy zoom_out_map
[root@dg0 tmp] # /root/dns.dump
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5 <<>> -t axfr pkg.test.device.net @169.254.0.1
;; global options:  printcmd
pkg.test.device.net.   600     IN      SOA     ns.pkg.test.device.net. mail.pkg.test.device.net. 152 3600 600 7200 3600
pkg.test.device.net.   600     IN      NS      ns.pkg.test.device.net.
pkg.test.device.net.   600     IN      A       169.254.0.1
pkg.test.device.net.   600     IN      MX      1 mail.pkg.test.device.net.
dcfnode---DCF-ROOT.pkg.test.device.net. 45 IN A 169.254.192.17
dcfnode---DRE-0.pkg.test.device.net. 45 IN A   169.254.3.3
dcfnode-8d8a978c-828b-11e1-a833-00e081c57938.pkg.test.device.net. 45 IN A 169.254.128.19
dcfnode-ad55b89e-828b-11e1-b70e-00e081c57938.pkg.test.device.net. 45 IN A 169.254.128.20
dcfnode-BBAK1186.pkg.test.device.net. 45 IN A  169.254.128.14

The internal IP address for BBAK1186 is 169.254.128.14.

Upgrade the Jloader software on the Node device or Interconnect device.

Before you can upgrade the Jloader software, you need to use SSH to log in to the Node device or Interconnect device and verify that the software is in the /tftpboot/logfiles directory.

Use SSH to log in to the Node device or Interconnect device.

For example:

content_copy zoom_out_map
[root@dg0 tmp] # ssh 160.254.128.14
root@169.254.128.14's password: 
--- JUNOS 11.3X30.10 built 2012-03-11 22:55:43 UTC
At least one package installed on this device has limited support.
Run 'file show /etc/notices/unsupported.txt' for details.
root@sng3% 

Verify that the Jloader software package is in the tftpboot/logfiles directory of the Node device or Interconnect device.
For example:
```
root@sng3% ls /tftpboot/logfiles
.index                                  jloader-qfx-11.3X30.9-signed.tgz
```
Copy the Jloader software package from the /tftpboot/logfiles directory to the /var/tmp directory of the Node device or Interconnect device.
For example:
```
root@sng3% cp /tftpboot/logfiles/jloader-qfx-11.3X30.9-signed.tgz /var/tmp
```

Verify that the Jloader software package is in the /var/tmp directory of the Node device or Interconnect device.

For example:

content_copy zoom_out_map
root@sng3% ls /var/tmp
.snap                                   jloader-qfx-11.3X30.9-signed.tgz        tmp
gres-tp                                 krt_gencfg_filter.txt                   vc-autoupgrade
if-rtsdb                                rtsdb

Enter CLI mode and issue the request system software add /var/tmp/jloader-qfx-version-signed.tgz command.

For example:

content_copy zoom_out_map
root@sng3% cli
root@sng3> request system software add /var/tmp/jloader-qfx-11.3X30.9-signed.tgz
Validating on fpc0
Checking compatibility with configuration
Initializing...
Using jbase-11.3X30.10
Verified manifest signed by PackageProduction_11_3_0
Verified jbase-11.3X30.10 signed by PackageProduction_11_3_0
Using /var/tmp/jloader-qfx-11.3X30.9-signed.tgz
Verified jloader-qfx-11.3X30.9.tgz signed by PackageProduction_11_3_0
Using jloader-qfx-11.3X30.9.tgz
Checking jloader-qfx requirements on /
Verified manifest signed by PackageProduction_11_3_0
Verified jloader-qfx-11.3X30.9 signed by PackageProduction_11_3_0
Using jkernel-qfx-11.3X30.10
Verified manifest signed by PackageProduction_11_3_0
Verified jkernel-qfx-11.3X30.10 signed by PackageProduction_11_3_0
Using jroute-qfx-11.3X30.10
Verified manifest signed by PackageProduction_11_3_0
Verified jroute-qfx-11.3X30.10 signed by PackageProduction_11_3_0
Using jcrypto-qfx-11.3X30.10
Verified manifest signed by PackageProduction_11_3_0
Verified jcrypto-qfx-11.3X30.10 signed by PackageProduction_11_3_0
Using jweb-qfx-11.3X30.10
Verified manifest signed by PackageProduction_11_3_0
Verified jweb-qfx-11.3X30.10 signed by PackageProduction_11_3_0
Using jswitch-qfx-11.3X30.10
Verified manifest signed by PackageProduction_11_3_0
Verified jswitch-qfx-11.3X30.10 signed by PackageProduction_11_3_0
Hardware Database regeneration succeeded
Validating against /config/juniper.conf.gz
mgd: commit complete
Validation succeeded
Done with validate on all chassis

fpc0:
Verified jloader-qfx-11.3X30.9.tgz signed by PackageProduction_11_3_0
Adding jloader-qfx...
Installation in progress, please wait...
Mounted jloader-qfx package on /dev/md10...
Verified manifest signed by PackageProduction_11_3_0
Verified jloader-qfx-11.3X30.9 signed by PackageProduction_11_3_0
#######################################
################################################################################################################################################################################################
Installation finished successfully.
Please reboot to activate the package
Saving package file in /var/sw/pkg/jloader-qfx-11.3X30.9-signed.tgz ...
Saving state for rollback ...


Upgrade has completed successfully.  
Reboot is now required.  

Reboot both the Node device and Interconnect device twice, because they each contain two partitions.

For example:

content_copy zoom_out_map
root@sng3> request system reboot
Reboot the system ? [yes,no] (no) yes
Shutdown NOW!
[pid 37663]

root@sng3>                                                                                
*** FINAL System shutdown message from root@sng3 ***                         
System going down IMMEDIATELY 

Verify that the Uboot software on the Node device or Interconnect device has been upgraded to the new Uboot software by logging in to the QFabric CLI and issuing either the show chassis firmware node-device name command or the show chassis firmware interconnect-device name command.
For example:
```
user@qfabric> show chassis firmware node-device BBAK1186
Part                     Type       Version
node4                    U-Boot     1.1.6 (Nov 19 2011 - 11:42:07) 1.1.2       
                         loader     FreeBSD/MIPS U-Boot bootstrap loader 0.1   
```
The Uboot software version is now 1.1.2. The loader software version appears after the timestamp for U-Boot 1.1.6.

Installing Junos OS Software with Junos Automation Enhancements

Before you install software, download the Junos OS jinstall-qfx-5-flex-x.tgz software bundle. For information on downloading and accessing the files, see Installing Software Packages on QFX Series Devices (Junos OS).

Junos operating system (Junos OS) with Junos Automation Enhancements is a full-featured version of Junos OS with Veriexec disabled, which can only be installed on supported devices.

Note:

You must install the jinstall-qfx-5-flex-x.tgz software bundle in order to use the automation enhancements.

Best Practice:

Before you install the software, back up any critical files in /var/home. For more information regarding how to back up critical files, contact Customer Support at https://www.juniper.net/support.

Install the software:

Issue the request system software add command with the validate option:
- If the installation package resides locally on the switch, issue the request system software add validate pathname source reboot command, using the following format:
  user@switch> request system software add validate /var/tmp/jinstall-qfx-5-flex-x.tgz reboot
- If the installation package resides remotely, issue the request system software add validate pathname source reboot command, using the following format:
  user@switch> request system software add validate ftp://ftpserver/directory/jinstall-qfx-5-flex-x.tgz reboot

After the reboot has finished, verify that the new version of software has been properly installed by executing the

show
version

command.

content_copy zoom_out_map
user@switch> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx5100-24q-et013
Model: qfx5100-24q-2p
JUNOS Base OS Software Suite [13.2X51-D20]
JUNOS Base OS boot [13.2X51-D20]
JUNOS Crypto Software Suite [13.2X51-D20]
JUNOS Online Documentation [13.2X51-D20]
JUNOS Kernel Software Suite [13.2X51-D20]
JUNOS Packet Forwarding Engine Support (qfx-x86-32) [13.2X51-D20]
JUNOS Routing Software Suite [13.2X51-D20]
JUNOS Enterprise Software Suite [13.2X51-D20]
JUNOS py-base-i386 [13.2X51-D20]
Puppet on Junos [2.7.19_1.junos.i386]
Ruby Interpreter [11.10.4_1.junos.i386]
Chef [11.10.4_1.junos.i386]
junos-ez-stdlib [11.10.4_1.junos.i386]
JUNOS Host Software [13.2X51-D20] 
JUNOS for Automation Enhancement

Note:

If you are upgrading a device from standard Junos OS to use Junos Automation Enhancements and you are not loading the new factory default configuration, you need to use the following procedure.

Edit your existing Junos OS configuration to include the following configuration statements:

content_copy zoom_out_map
[edit]
user@switch# set system extensions providers juniper license-type juniper deployment-scope commercial
user@switch#  set system extensions providers chef license-type juniper deployment-scope commercial

Note:

The factory default configuration of the QFX5100 switch jinstall-qfx-5-flex-x.tgz software bundle is a Layer 3 configuration, whereas the factory default configuration for QFX5100 switch software bundles is a Layer 2 configuration. Therefore, if you are running the jinstall-qfx-5-flex-x.tgz software bundle on a QFX5100 switch and you use the load factory-default command, the resulting factory default configuration is set up for Layer 3 interfaces.

This is the factory default configuration for QFX5100 switch jinstall-qfx-5-flex-x.tgz software bundle:

content_copy zoom_out_map
user@switch> show configuration

content_copy zoom_out_map
system syslog user * any emergency
system syslog file messages any notice
system syslog file messages authorization info
system syslog file interactive-commands interactive-commands any
system extensions providers juniper license-type juniper deployment-scope commercial
system extensions providers chef license-type juniper deployment-scope commercial
system commit factory-settings reset-virtual-chassis-configuration
system commit factory-settings reset-chassis-lcd-menu
system processes app-engine-virtual-machine-management-service traceoptions level notice
system processes app-engine-virtual-machine-management-service traceoptions flag all
interfaces et-0/0/0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/0:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/0:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/0:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/0:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/1:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/1:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/1:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/1:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/2:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/2:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/2:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/2:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/3:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/3:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/3:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/3:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/4 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/4:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/4:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/4:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/4:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/5 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/5:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/5:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/5:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/5:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/6 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/6:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/6:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/6:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/6:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/7 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/7:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/7:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/7:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/7:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/8 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/8:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/8:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/8:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/8:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/9 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/9:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/9:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/9:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/9:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/10 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/10:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/10:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/10:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/10:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/11 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/11:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/11:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/11:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/11:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/12 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/12:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/12:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/12:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/12:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/13 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/13:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/13:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/13:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/13:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/14 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/14:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/14:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/14:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/14:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/15 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/15:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/15:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/15:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/15:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/16 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/16:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/16:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/16:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/16:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/17 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/17:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/17:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/17:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/17:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/18 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/18:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/18:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/18:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/18:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/19 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/19:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/19:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/19:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/19:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/20 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/20:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/20:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/20:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/20:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/21 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/21:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/21:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/21:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/21:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/22 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/22:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/22:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/22:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/22:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/0/23 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/23:0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/23:1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/23:2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces xe-0/0/23:3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/1/0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/1/1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/1/2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/1/3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/2/0 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/2/1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/2/2 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
interfaces et-0/2/3 unit 0 family inet dhcp vendor-id Juniper-qfx5100-24q-2p
forwarding-options storm-control-profiles default all
protocols lldp interface all
protocols lldp-med interface all
protocols igmp-snooping vlan default
vlans default vlan-id 1

arrow_backward PREVIOUS Troubleshooting a Switch That Has Booted from the Backup Junos OS Image

NEXT arrow_forward Installing and Recovering Software Using the Open Network Install Environment (ONIE)

Junos® OS Software Installation and Upgrade Guide

ON THIS PAGE

Installing Software on QFX Series Devices (Junos OS)

Installing Software Packages on QFX Series Devices (Junos OS)

Installing the Software on QFX10002-60C Switches

Installing a Standard Software Package on QFX5000 and EX4600 Switches

Installing a Standard Software Package on QFX10002 Switches

Upgrading Software from Junos OS Release 15.1X53-D3X to Junos OS Release 15.1X53-D60, 15.1X53-D61.7, 15.1X53-D62, and 15.1X53-D63 on QFX10008 and QFX10016 Switches

Installing a Software Package on QFX10008 and QFX10016 Switches

Preparing the Switch for Installation (Junos OS)

Installing Software on the Backup Routing Engine (Junos OS)

Installing Software on the Primary Routing Engine (Junos OS)

Upgrading Software by Using Automatic Software Download for Switches (Junos OS)

Configuring DHCP Services for the Switch (Junos OS)

Enabling Automatic Software Download on a Switch (Junos OS)

Verifying That Automatic Software Download Is Working Correctly (Junos OS)

Purpose

Action

Meaning

Upgrading Jloader Software on QFX Series Devices

Jloader Software Version 1.1.4 Guidelines

Upgrading Jloader Software on a QFX3500 Switch

Upgrading Jloader Software on a QFabric System

Installing Junos OS Software with Junos Automation Enhancements

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Junos® OS Software Installation and Upgrade Guide

ON THIS PAGE

Installing Software on QFX Series Devices (Junos OS)

Installing Software Packages on QFX Series Devices (Junos OS)

Installing the Software on QFX10002-60C Switches

Installing a Standard Software Package on QFX5000 and EX4600 Switches

Installing a Standard Software Package on QFX10002 Switches

Upgrading Software from Junos OS Release 15.1X53-D3X to Junos OS Release 15.1X53-D60, 15.1X53-D61.7, 15.1X53-D62, and 15.1X53-D63 on QFX10008 and QFX10016 Switches

Installing a Software Package on QFX10008 and QFX10016 Switches

Preparing the Switch for Installation (Junos OS)

Installing Software on the Backup Routing Engine (Junos OS)

Installing Software on the Primary Routing Engine (Junos OS)

Upgrading Software by Using Automatic Software Download for Switches (Junos OS)

Configuring DHCP Services for the Switch (Junos OS)

Enabling Automatic Software Download on a Switch (Junos OS)

Verifying That Automatic Software Download Is Working Correctly (Junos OS)

Purpose

Action

Meaning

See Also

Upgrading Jloader Software on QFX Series Devices

Jloader Software Version 1.1.4 Guidelines

Upgrading Jloader Software on a QFX3500 Switch

Upgrading Jloader Software on a QFabric System

See Also

Installing Junos OS Software with Junos Automation Enhancements

See Also

Stay in touch