Junos OS for EX Series Ethernet Switches,

Release 11.4: Software Installation

Published: 2011-11-23
Revision 2

Copyright 2011, Juniper Networks, Inc.

Juniper Networks, Inc.

1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. Copyright 1986-1997,
Epilogue Technology Corporation. All rights reserved. This program and its documentation were developed at private expense, and no part
of them is in the public domain.
This product includes memory allocation software developed by Mark Moraes, copyright 1988, 1989, 1993, University of Toronto.
This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation
and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents of the University of California. Copyright
1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved.
GateD software copyright 1995, the Regents of the University. All rights reserved. Gate Daemon was originated and developed through
release 3.0 by Cornell University and its collaborators. Gated is based on Kirtons EGP, UC Berkeleys routing daemon (routed), and DCNs
HELLO routing protocol. Development of Gated has been supported in part by the National Science Foundation. Portions of the GateD
software copyright 1988, Regents of the University of California. All rights reserved. Portions of the GateD software copyright 1991, D.
L. S. Associates.
This product includes software developed by Maker Communications, Inc., copyright 1996, 1997, Maker Communications, Inc.
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are
owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,
6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Copyright 2011, Juniper Networks, Inc.
All rights reserved.
Revision History
November 2011Revision 2
November 2011Revision 1
The information in this document is current as of the date listed in the revision history.

END USER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (EULA) posted at

http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions
of that EULA.

ii

Copyright 2011, Juniper Networks, Inc.

Table of Contents
About This Topic Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
List of EX Series Guides for Junos OS Release 11.4 . . . . . . . . . . . . . . . . . . . . . . . . . vii
Downloading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Symbols Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Part 1

Software Installation

Chapter 1

Software Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Junos OSOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Understanding Software Infrastructure and Processes . . . . . . . . . . . . . . . . . . 3
Routing Engine and Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . . . 3
Junos OS Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Understanding Software Installation on EX Series Switches . . . . . . . . . . . . . . 5
Overview of the Software Installation Process . . . . . . . . . . . . . . . . . . . . . 6
Software Package Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Installing Software on a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Installing Software on EX8200 Switches with Redundant Routing
Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Installing Software Using Automatic Software Download . . . . . . . . . . . . . 7
Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Junos OS Package Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Understanding System Snapshot on EX Series Switches . . . . . . . . . . . . . . . . . 8
Understanding Resilient Dual-Root Partitions on Switches . . . . . . . . . . . . . . 10
Resilient Dual-Root Partition Scheme (Junos OS Release 10.4R3 and
Later) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Earlier Partition Scheme (Junos OS Release 10.4R2 and Earlier) . . . . . . . 11
Understanding Upgrading or Downgrading Between Resilient Dual-Root
Partition Releases and Earlier Releases . . . . . . . . . . . . . . . . . . . . . . . 11
Licenses Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Understanding Software Licenses for EX Series Switches . . . . . . . . . . . . . . . . 12
Purchasing a Software Feature License . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Features Requiring a License on EX2200 Switches . . . . . . . . . . . . . . . . . 13
Features Requiring a License on EX3200, EX4200, EX4500, EX6200
and EX8200 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Features Requiring a License on EX3300 Switches . . . . . . . . . . . . . . . . . 14

Copyright 2011, Juniper Networks, Inc.

iii

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

License Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

License Key Components for the EX Series Switch . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2

Installing Junos OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Downloading Software Packages from Juniper Networks . . . . . . . . . . . . . . . . . . . . 17
Installing Software on an EX Series Switch with a Single Routing Engine (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing Software on an EX Series Switch with Redundant Routing Engines
(CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Preparing the Switch for the Software Installation . . . . . . . . . . . . . . . . . . . . . 20
Installing Software on the Backup Routing Engine . . . . . . . . . . . . . . . . . . . . . 21
Installing Software on the Default Master Routing Engine . . . . . . . . . . . . . . . 22
Returning Routing Control to the Default Master Routing Engine
(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing Software on EX Series Switches (J-Web Procedure) . . . . . . . . . . . . . . . 24
Installing Software Upgrades from a Server . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Installing Software Upgrades by Uploading Files . . . . . . . . . . . . . . . . . . . . . . 25
Rebooting or Halting the EX Series Switch (J-Web Procedure) . . . . . . . . . . . . . . . 25

Chapter 3

Registering the Switch, Booting the Switch, Upgrading Software, and

Managing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Registering the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Registering the EX Series Switch with the J-Web Interface . . . . . . . . . . . . . . . 27
Booting the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Booting an EX Series Switch Using a Software Package Stored on a USB
Flash Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Creating a Snapshot and Using It to Boot an EX Series Switch . . . . . . . . . . . 29
Creating a Snapshot on a USB Flash Drive and Using It to Boot the
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Creating a Snapshot on an Internal Flash Drive and Using it to Boot the
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Upgrading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Upgrading Software Using Automatic Software Download on EX Series
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Managing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Managing Licenses for the EX Series Switch (CLI Procedure) . . . . . . . . . . . . . 31
Adding New Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Deleting Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Saving License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Managing Licenses for the EX Series Switch (J-Web Procedure) . . . . . . . . . . 33
Adding New Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Deleting Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Displaying License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Downloading Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

iv

Copyright 2011, Juniper Networks, Inc.

Table of Contents

Chapter 4

Verifying Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Routine Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Verifying That Automatic Software Download Is Working Correctly . . . . . . . 35
Verifying That a System Snapshot Was Created on an EX Series Switch . . . 36
Verifying Junos OS and Boot Loader Software Versions on an EX Series
Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Verifying the Number of Partitions and File System Mountings . . . . . . . . 37
Verifying the Loader Software Version . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Verifying Which Root Partition Is Active . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Verifying the Junos OS Version in Each Root Partition . . . . . . . . . . . . . . . 39
Monitoring Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Monitoring Licenses for the EX Series Switch . . . . . . . . . . . . . . . . . . . . . . . . . 40
Displaying Installed Licenses and License Usage Details . . . . . . . . . . . . 40
Displaying Installed License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 5

Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Recovering from a Failed Software Upgrade on an EX Series Switch . . . . . . 43
Rebooting from the Inactive Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Freeing Disk Space for Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Installation from the Boot Loader Generates cannot open package
Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Troubleshooting a Switch That Has Booted from the Backup Junos OS
Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Resilient Dual-Root Partitions Frequently Asked Questions . . . . . . . . . . . . . . . . . 47
How Does Upgrading to Junos OS Release 10.4R3 and Later Differ from
Normal Upgrades? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
What Happens If I Do Not Upgrade Both the Loader Software and Junos OS
at the Same Time? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Can I Downgrade Junos OS Without Downgrading the Loader
Software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Can I Upgrade to a Resilient Dual-Root Partition Release by Using the
CLI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Will I Lose My Configuration During an Upgrade? . . . . . . . . . . . . . . . . . . . . . . 49
How Long Will the Upgrade Process Take? . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
What Happens to My Files If the System Detects a File System
Corruption? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
How Will I Be Informed If My Switch Boots from the Alternate Slice Due to
Corruption in the Root File System? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Can I Use Automatic Software Update and Download to Upgrade to a
Resilient Dual-Root Partition Release? . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Why Is the Message "At least one package installed on this device has
limited support" Displayed When Users Log In to a Switch? . . . . . . . . . . 51
Where Can I Find Instructions for Upgrading? . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 6

Configuration Statements for Software Installation . . . . . . . . . . . . . . . . . . . 53

[edit chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 53
auto-image-upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Copyright 2011, Juniper Networks, Inc.

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Chapter 7

Operational Commands for Software Installation . . . . . . . . . . . . . . . . . . . . . 55

request system license add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
request system license delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
request system license save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
request system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
request system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
request system snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
request system software add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
request system software delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
request system software rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
request system software validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
request system software validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
request system zeroize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
show system autoinstallation status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
show system boot-messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
show system license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
show system snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
show system storage partitions (EX Series Switches Only) . . . . . . . . . . . . . . . . . 109

vi

Copyright 2011, Juniper Networks, Inc.

About This Topic Collection

How to Use This Guide on page vii

List of EX Series Guides for Junos OS Release 11.4 on page vii

Downloading Software on page ix

Documentation Symbols Key on page x

Documentation Feedback on page xi

Requesting Technical Support on page xii

How to Use This Guide

Complete documentation for the EX Series product family is provided on webpages at
http://www.juniper.net/techpubs/en_US/release-independent/information-products/
pathway-pages/ex-series/product/index.html. We have selected content from these

webpages and created a number of EX Series guides that collect related topics into a
book-like format so that the information is easy to print and easy to download to your
local computer.
Software features for EX Series switches are listed by platform and by Junos OS release
in a standalone document. See EX Series Switch Software Features Overview.
The release notes are at http://www.juniper.net/techpubs/en_US/junos11.4/
information-products/topic-collections/release-notes/11.4/junos-release-notes-11.4.pdf.

List of EX Series Guides for Junos OS Release 11.4

Title

Description

Complete Hardware Guide for EX2200 Ethernet Switches

Component descriptions, site preparation, installation,

replacement, and safety and compliance information
for EX2200 Ethernet switches

Complete Hardware Guide for EX3200 Ethernet Switches

Component descriptions, site preparation, installation,

replacement, and safety and compliance information
for EX3200 Ethernet switches

Complete Hardware Guide for EX3300 Ethernet Switches

Component descriptions, site preparation, installation,

replacement, and safety and compliance information
for EX3300 Ethernet switches

Copyright 2011, Juniper Networks, Inc.

vii

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Title

Description

Complete Hardware Guide for EX4200 Ethernet Switches

Component descriptions, site preparation, installation,

replacement, and safety and compliance information
for EX4200 Ethernet switches

Complete Hardware Guide for EX4500 Ethernet Switches

Component descriptions, site preparation, installation,

replacement, and safety and compliance information
for EX4500 Ethernet switches

Complete Hardware Guide for EX6210 Ethernet Switches

Component descriptions, site preparation, installation,

replacement, and safety and compliance information
for EX6210 Ethernet switches

Complete Hardware Guide for EX8208 Ethernet Switches

Component descriptions, site preparation, installation,

replacement, and safety and compliance information
for EX8208 Ethernet switches

Complete Hardware Guide for EX8216 Ethernet Switches

Component descriptions, site preparation, installation,

replacement, and safety and compliance information
for EX8216 Ethernet switches

Complete Hardware Guide for the XRE200 External Routing Engine

Component descriptions, site preparation, installation,

replacement, and safety and compliance information
for the XRE200 External Routing Engine

Complete Software Guide for Junos OS for EX Series Ethernet

Switches, Release 11.4

Software feature descriptions, configuration examples,

and tasks for Junos OS for EX Series switches

Software Topic Collections

Software feature descriptions, configuration examples

and tasks, and reference pages for configuration
statements and operational commands (This
information also appears in the Complete Software Guide

for Junos OS for EX Series Ethernet Switches, Release

11.4.)

Junos OS for EX Series Ethernet Switches, Release 11.4: Access and

User Management

Junos OS for EX Series Ethernet Switches, Release 11.4: Access Control

Junos OS for EX Series Ethernet Switches, Release 11.4: Configuration

Management

Junos OS for EX Series Ethernet Switches, Release 11.4: Class of

Service

Junos OS for EX Series Ethernet Switches, Release 11.4: Device Security

Junos OS for EX Series Ethernet Switches, Release 11.4: Ethernet

Switching

Junos OS for EX Series Ethernet Switches, Release 11.4: EX3300,

EX4200, and EX4500 Virtual Chassis

viii

Copyright 2011, Juniper Networks, Inc.

About This Topic Collection

Title

Description

Junos OS for EX Series Ethernet Switches, Release 11.4: EX8200 Virtual

Chassis

Junos OS for EX Series Ethernet Switches, Release 11.4: Fibre Channel

over Ethernet

Junos OS for EX Series Ethernet Switches, Release 11.4: High

Availability

Junos OS for EX Series Ethernet Switches, Release 11.4: Interfaces

Junos OS for EX Series Ethernet Switches, Release 11.4: Layer 3

Protocols

Junos OS for EX Series Ethernet Switches, Release 11.4: MPLS

Junos OS for EX Series Ethernet Switches, Release 11.4: Multicast

Junos OS for EX Series Switches, Release 11.4: Network Management

and Monitoring

Junos OS for EX Series Switches, Release 11.4: Port Security

Junos OS for EX Series Switches, Release 11.4: Power over Ethernet

Junos OS for EX Series Ethernet Switches, Release 11.4: Routing Policy

and Packet Filtering

Junos OS for EX Series Ethernet Switches, Release 11.4: Software

Installation

Junos OS for EX Series Ethernet Switches, Release 11.4: Spanning-Tree

Protocols

Junos OS for EX Series Ethernet Switches, Release 11.4: System

Monitoring

Junos OS for EX Series Ethernet Switches, Release 11.4: System

Services

Junos OS for EX Series Ethernet Switches, Release 11.4: System Setup

Junos OS for EX Series Ethernet Switches, Release 11.4: User Interfaces

Downloading Software
You can download Junos OS for EX Series switches from the Download Software area
at http://www.juniper.net/customers/support/ . To download the software, you must

Copyright 2011, Juniper Networks, Inc.

ix

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

have a Juniper Networks user account. For information about obtaining an account, see
http://www.juniper.net/entitlement/setupAccountInfo.do.

Documentation Symbols Key

Notice Icons
Icon

Meaning

Description

Informational note

Indicates important features or instructions.

Caution

Indicates a situation that might result in loss of data or hardware

damage.

Warning

Alerts you to the risk of personal injury or death.

Laser warning

Alerts you to the risk of personal injury from a laser.

Text and Syntax Conventions

Convention

Description

Examples

Bold text like this

Represents text that you type.

To enter configuration mode, type the

configure command:
user@host> configure

Fixed-width text like this

Italic text like this

Italic text like this

Plain text like this

Represents output that appears on the

terminal screen.

user@host> show chassis alarms

Introduces important new terms.

Identifies book names.

A policy term is a named structure that

defines match conditions and actions.

Identifies RFC and Internet draft titles.

Junos OS System Basics Configuration

Guide

RFC 1997, BGP Communities Attribute

No alarms currently active

Represents variables (options for which

you substitute a value) in commands or
configuration statements.

Configure the machines domain name:

Represents names of configuration

statements, commands, files, and
directories; IP addresses; configuration
hierarchy levels; or labels on routing
platform components.

To configure a stub area, include the

stub statement at the [edit protocols
ospf area area-id] hierarchy level.

The console port is labeled CONSOLE.

[edit]
root@# set system domain-name
domain-name

Copyright 2011, Juniper Networks, Inc.

About This Topic Collection

Text and Syntax Conventions

Convention

Description

Examples

< > (angle brackets)

Enclose optional keywords or variables.

stub <default-metric metric>;

| (pipe symbol)

Indicates a choice between the mutually

exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.

broadcast | multicast

# (pound sign)

Indicates a comment specified on the

same line as the configuration statement
to which it applies.

rsvp { # Required for dynamic MPLS only

[ ] (square brackets)

Enclose a variable for which you can

substitute one or more values.

community name members [

community-ids ]

Indention and braces ( { } )

Identify a level in the configuration

hierarchy.

; (semicolon)

Identifies a leaf statement at a

configuration hierarchy level.

(string1 | string2 | string3)

[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}

J-Web GUI Conventions

Bold text like this

Represents J-Web graphical user

interface (GUI) items you click or select.

> (bold right angle bracket)

Separates levels in a hierarchy of J-Web

selections.

In the Logical Interfaces box, select All

Interfaces.

To cancel the configuration, click

Cancel.

In the configuration editor hierarchy,

select Protocols>Ospf.

Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. Send e-mail to [email protected] with the
following:

Document URL or title

Page number if applicable

Software version

Your name and company

Copyright 2011, Juniper Networks, Inc.

xi

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Requesting Technical Support

Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,
or are covered under warranty, and need post-sales technical support, you can access
our tools and resources online or open a case with JTAC.

JTAC policiesFor a complete understanding of our JTAC procedures and policies,

review the JTAC User Guide located at
http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf .

Product warrantiesFor product warranty information, visit

http://www.juniper.net/support/warranty/ .

JTAC hours of operationThe JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with the
following features:

Find CSC offerings: http://www.juniper.net/customers/support/

Search for known bugs: http://www2.juniper.net/kb/

Find product documentation: http://www.juniper.net/techpubs/

Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

Search technical bulletins for relevant hardware and software notifications:

https://www.juniper.net/alerts/

Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/

To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

Use the Case Management tool in the CSC at http://www.juniper.net/cm/ .

Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, see

http://www.juniper.net/support/requesting-support.html .

xii

Copyright 2011, Juniper Networks, Inc.

PART 1

Software Installation

Software Installation Overview on page 3

Installing Junos OS on page 17

Registering the Switch, Booting the Switch, Upgrading Software, and Managing
Licenses on page 27

Verifying Software Installation on page 35

Troubleshooting Software Installation on page 43

Configuration Statements for Software Installation on page 53

Operational Commands for Software Installation on page 55

Copyright 2011, Juniper Networks, Inc.

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Copyright 2011, Juniper Networks, Inc.

CHAPTER 1

Software Installation Overview

Junos OSOverview on page 3

Installation Overview on page 5

Licenses Overview on page 12

Junos OSOverview

Understanding Software Infrastructure and Processes on page 3

Understanding Software Infrastructure and Processes

Each switch runs the Juniper Networks Junos operating system (Junos OS) for Juniper
Networks EX Series Ethernet Switches on its general-purpose processors. Junos OS
includes processes for Internet Protocol (IP) routing and for managing interfaces,
networks, and the chassis.
The Junos OS runs on the Routing Engine. The Routing Engine kernel coordinates
communication among the Junos OS processes and provides a link to the Packet
Forwarding Engine.
With the J-Web interface and the command-line interface (CLI) to the Junos OS, you
configure switching features and routing protocols and set the properties of network
interfaces on your switch. After activating a software configuration, use either the J-Web
or CLI user interface to monitor the switch, manage operations, and diagnose protocol
and network connectivity problems.

Routing Engine and Packet Forwarding Engine on page 3

Junos OS Processes on page 4

Routing Engine and Packet Forwarding Engine

A switch has two primary software processing components:

Packet Forwarding EngineProcesses packets; applies filters, routing policies, and

other features; and forwards packets to the next hop along the route to their final
destination.

Routing EngineProvides three main functions:

Copyright 2011, Juniper Networks, Inc.

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Creates the packet forwarding switch fabric for the switch, providing route lookup,
filtering, and switching on incoming data packets, then directing outbound packets
to the appropriate interface for transmission to the network

Maintains the routing tables used by the switch and controls the routing protocols
that run on the switch.

Provides control and monitoring functions for the switch, including controlling power
and monitoring system status.

Junos OS Processes
The Junos OS running on the Routing Engine and Packet Forwarding Engine consists of
multiple processes that are responsible for individual functions.
The separation of functions provides operational stability, because each process accesses
its own protected memory space. In addition, because each process is a separate software
package, you can selectively upgrade all or part of the Junos OS, for added flexibility.
Table 1 on page 4 describes the primary Junos OS processes.

Table 1: Junos OS Processes

Process

Name

Description

Chassis process

chassisd

Detects hardware on the system that is used to configure network interfaces.

Monitors the physical status of hardware components and field-replaceable units
(FRUs), detecting when environment sensors such as temperature sensors are triggered.
Relays signals and interruptsfor example, when devices are taken offline, so that the
system can close sessions and shut down gracefully.

Ethernet
switching
process

eswd

Handles Layer 2 switching functionality such as MAC address learning, Spanning Tree
protocol and access port security. The process is also responsible for managing Ethernet
switching interfaces, VLANs, and VLAN interfaces.
Manages Ethernet switching interfaces, VLANs, and VLAN interfaces.

Forwarding
process

pfem

Defines how routing protocols operate on the switch. The overall performance of the
switch is largely determined by the effectiveness of the forwarding process.

Interface
process

dcd

Configures and monitors network interfaces by defining physical characteristics such

as link encapsulation, hold times, and keepalive timers.

Copyright 2011, Juniper Networks, Inc.

Chapter 1: Software Installation Overview

Table 1: Junos OS Processes (continued)

Process

Name

Description

Management
process

mgd

Provides communication between the other processes and an interface to the

configuration database.
Populates the configuration database with configuration information and retrieves the
information when queried by other processes to ensure that the system operates as
configured.
Interacts with the other processes when commands are issued through one of the user
interfaces on the switch.
If a process terminates or fails to start when called, the management process attempts
to restart it a limited number of times to prevent thrashing and logs any failure
information for further investigation.

Routing protocol
process

rpd

Related
Documentation

Defines how routing protocols such as RIP, OSPF, and BGP operate on the device,
including selecting routes and maintaining forwarding tables.

For more information about processes, see Junos OS Network Operations Guide

For more information about basic system parameters, supported protocols, and software
processes, see Junos OS System Basics Configuration Guide

Installation Overview

Understanding Software Installation on EX Series Switches on page 5

Junos OS Package Names on page 8

Understanding System Snapshot on EX Series Switches on page 8

Understanding Resilient Dual-Root Partitions on Switches on page 10

Understanding Software Installation on EX Series Switches

A Juniper Networks EX Series Ethernet Switch is delivered with Juniper Networks Junos
operating system (Junos OS) preinstalled. As new features and software fixes become
available, you must upgrade your software to use them. You can also downgrade Junos
OS to a previous release.
This topic covers:

Overview of the Software Installation Process on page 6

Software Package Security on page 6

Installing Software on a Virtual Chassis on page 6

Installing Software on EX8200 Switches with Redundant Routing Engines on page 7

Installing Software Using Automatic Software Download on page 7

Troubleshooting Software Installation on page 7

Copyright 2011, Juniper Networks, Inc.

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Overview of the Software Installation Process

An EX Series switch is delivered with Junos OS preinstalled. When you connect power to
the switch, it starts (boots) up from the installed software.
You upgrade Junos OS on an EX Series switch by copying a software package to your
switch or another system on your local network, then use either the J-Web interface or
the CLI to install the new software package on the switch. Finally, you reboot the switch;
it boots from the upgraded software. After a successful upgrade, you should back up the
new current configuration to a secondary device.
During a successful upgrade, the upgrade package removes all files from /var/tmp and
completely reinstalls the existing software. It retains configuration files, and similar
information, such as secure shell and host keys, from the previous version. The previous
software package is preserved in a separate disk partition, and you can manually revert
back to it if necessary. If the software installation fails for any reason, such as loss of
power during the installation process, the system returns to the originally active installation
when you reboot.

Software Package Security

All Junos OS releases are delivered in signed packages that contain digital signatures to
ensure official Juniper Networks software. For more information about signed software
packages, see the Junos OS Installation and Upgrade Guide.

Installing Software on a Virtual Chassis

You can connect individual EX Series switches together to form one unit and manage
the unit as a single device, called a Virtual Chassis. The Virtual Chassis operates as a
single network entity composed of members. Each member of a Virtual Chassis runs a
Junos OS package. Supported Virtual Chassis include EX4200 Virtual Chassis, EX4500
Virtual Chassis, mixed EX4200 and EX4500 Virtual Chassis, or EX8200 Virtual Chassis.
For ease of management, a Virtual Chassis provides flexible methods to upgrade software
releases. You can deploy a new software release to all members of a Virtual Chassis or
to only a particular member.
You can also upgrade the software on an EX8200 Virtual Chassis using nonstop software
upgrade (NSSU). Unlike a standard software upgrade, NSSU does not require a reboot
of the Virtual Chassis. Instead, it takes advantage of graceful Routing Engine switchover
and nonstop active routing (NSR) to ensure no disruption to the control plane during the
upgrade. You can minimize disruption to network traffic by defining link aggregation
groups (LAGs) such that the member links of each LAG reside on different line cards.
The line cards are upgraded one at a time, so that traffic continues to flow through the
other line cards while a line card is being upgraded.

Copyright 2011, Juniper Networks, Inc.

Chapter 1: Software Installation Overview

Installing Software on EX8200 Switches with Redundant Routing Engines

You can install software on an EX8200 switch with redundant Routing Engines in one
of two ways:

Perform a nonstop software upgrade (NSSU)An NSSU upgrades both Routing

Engines with a single command and with a minimum of network disruption. An NSSU
takes advantage of graceful Routing Engine switchover (GRES) and nonstop active
routing (NSR) to ensure no disruption to the control plane. You can minimize disruption
to network traffic by defining link aggregation groups (LAGs) such that the member
links of each LAG reside on different line cards. The line cards are upgraded one at a
time, so that traffic continues to flow through the other line cards while a line card is
being upgraded.
You cannot use NSSU to downgrade the software running on a switch.
For more information about NSSU, see Understanding Nonstop Software Upgrade on
EX Series Switches.

Upgrade each Routing Engine manuallyYou can perform a Junos OS installation on

each Routing Engine separately, starting with the backup Routing Engine. You can use
this procedure to downgrade the software running on a switch. See Installing Software
on an EX Series Switch with Redundant Routing Engines (CLI Procedure) on page 19.

Installing Software Using Automatic Software Download

The automatic software download feature uses the DHCP message exchange process
to download and install software packages. Users can define a path to a software package
on the DHCP server and then the DHCP server communicates this path to EX Series
switches acting as DHCP clients as part of the DHCP message exchange process. The
DHCP clients that have been configured for automatic software download receive these
messages and, when the software package name in the DHCP server message is different
from that of the software package that booted the DHCP client switch, download and
install the software package. See Upgrading Software Using Automatic Software
Download on EX Series Switches on page 30.

Troubleshooting Software Installation

If the Junos OS loads but the CLI is not working for any reason, or if the switch has no
software installed, you can use the recovery installation procedure to install the software
on the switch. See Troubleshooting Software Installation on page 43.

NOTE: You can also use this procedure to load two versions of Junos OS in
separate partitions on the switch.

Related
Documentation

Downloading Software Packages from Juniper Networks on page 17

Installing Software on EX Series Switches (J-Web Procedure) on page 24

Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure)
on page 18

Copyright 2011, Juniper Networks, Inc.

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Installing Software on an EX Series Switch with Redundant Routing Engines (CLI

Procedure) on page 19

Understanding Nonstop Software Upgrade on EX Series Switches

Junos OS Package Names

You upgrade the Juniper Networks Junos operating system (Junos OS) on a Juniper
Networks EX Series Ethernet Switch by copying a software package to your switch or
another system on your local network, then install the new software package on the
switch.
A software package name is in the following format:
package-name-m.nZx.y-domestic-signed.tgz

where:

package-name is the name of the packagefor example, jinstall-ex-4200.

m.n is the software release, with m representing the major release number and n

representing the minor release numberfor example, 9.5.

Z indicates the type of software release, where R indicates released software and B

indicates beta-level software.

x.y represents the version of the major software release (x) and an internal tracking

number (y)for example, 1.6.

domestic-signed is appended to all EX Series package names. For most Junos packages,
domestic is used for the United States and Canada and export for worldwide distribution.

However, for EX Series software, domestic is used for worldwide distribution as well.
A sample EX Series software package name is:
jinstall-ex-4200-9.5R1.6-domestic-signed.tgz

Related
Documentation

Installing Software on EX Series Switches (J-Web Procedure) on page 24

Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure)
on page 18

Installing Software on an EX Series Switch with Redundant Routing Engines (CLI

Procedure) on page 19

Downloading Software Packages from Juniper Networks on page 17

Understanding Software Installation on EX Series Switches on page 5

Understanding System Snapshot on EX Series Switches

You can create copies of the software running a Juniper Networks EX Series Ethernet
Switch using the system snapshot feature. The system snapshot feature takes a
snapshot of the files currently used to run the switchthe complete contents of the
/config and /var directories, which include the running Juniper Networks Juniper operating

Copyright 2011, Juniper Networks, Inc.

Chapter 1: Software Installation Overview

system (Junos OS), the active configuration, and the rescue configurationand copies
all of these files into an alternate (internal, meaning internal flash, or an external, meaning
USB flash) memory source. You can then use this snapshot to boot the switch at the
next bootup or as a backup boot option.
You can only use snapshots to move files to external memory if the switch was booted
from internal memory, or to move files to internal memory if the switch was booted from
external memory. You cannot create a snapshot in the memory source that booted the
switch even if the snapshot is being created on a different partition in the same memory
source.
Snapshots are particularly useful for moving files onto USB flash drives. You cannot use
the copy command or any other file-moving technique to move files from an internal
memory source to USB memory on the switch.
System snapshots on EX Series switches have the following limitations:

Related
Documentation

You cannot use snapshots to move files to any destination outside of the switch other
than an installed external USB flash drive or to move files between switches that are
members of the same virtual chassis.

Snapshot commands, like other virtual chassis commands, are always executed on a
local switch. In cases where a different member switches of the same virtual chassis
requests the snapshot, the snapshot command is pushed to the VC member creating
the snapshot, executed, and the output is then returned to the switch that initiated the
process. For instance, if the command to create an external snapshot on virtual chassis
member 3 is entered from virtual chassis member 1, the snapshot of internal memory
on virtual chassis member 3 is taken on external memory on virtual chassis member
3. The output of the process is seen from virtual chassis member 1. No files move
between the switches.

Understanding Software Installation on EX Series Switches on page 5

Creating a Snapshot and Using It to Boot an EX Series Switch on page 29

Copyright 2011, Juniper Networks, Inc.

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Understanding Resilient Dual-Root Partitions on Switches

Resilient dual-root partitioning, introduced on Juniper Networks EX Series Ethernet
Switches in Junos operating system (Junos OS) Release 10.4R3, provides additional
resiliency to switches in the following ways:

Allows the switch to boot transparently from the second root partition if the system
fails to boot from the primary root partition.

Provides separation of the root Junos OS file system from the /var file system. If
corruption occurs in the /var file system (a higher probability than in the root file system
due to the greater frequency in /var of reads and writes), the root file system is insulated
from the corruption.

NOTE: For instructions on upgrading to release that supports resilient

dual-root partitions from a release that does not, see the Release Notes. The
procedure for upgrading to a resilient dual-root partition release is different
from the normal upgrade procedure.

This topic covers:

Resilient Dual-Root Partition Scheme (Junos OS Release 10.4R3 and Later) on page 10

Earlier Partition Scheme (Junos OS Release 10.4R2 and Earlier) on page 11

Understanding Upgrading or Downgrading Between Resilient Dual-Root Partition

Releases and Earlier Releases on page 11

Resilient Dual-Root Partition Scheme (Junos OS Release 10.4R3 and Later)

EX Series switches that ship with Junos OS Release 10.4R3 or later are configured with
a root partition scheme that is optimized for resiliency, as shown in Table 2 on page 10.

Table 2: Resilient Dual-Root Partition Scheme

Slice 1

Slice 2

Slice 3

s1a

s2a

s3e

s3d

s4d

/var

/var/tmp

/config

(root Junos OS )

(root Junos OS )

Slice 4

In the resilient dual-root partition scheme, the /var file system is contained in a separate
slice from the root file systems, the /config directory is contained in its own slice, and
switches ship from the factory with identical Junos OS images in slice 1 and slice 2. The
/var file system, which has a greater frequency of reads and writes than the root file
systems and is therefore more likely to have corruption issues, is isolated from the root
directories and the /config directory. If the switch fails to boot, the system automatically
boots from the alternate root partition. (If the switch fails to boot from the active root
partition and instead boots from the alternate root partition, an alarm is triggered.)

10

Copyright 2011, Juniper Networks, Inc.

Chapter 1: Software Installation Overview

Earlier Partition Scheme (Junos OS Release 10.4R2 and Earlier)

The earlier partition scheme is shown in Table 3 on page 11.

Table 3: Earlier Partition Scheme

Slice 2

Slice 1

Slice 3

s1a

s1f

s2a

s2f

s3d

s3e

/var

(empty until
initial
software
upgrade)

(empty until
initial
software
upgrade)

/var/tmp

/config

(root Junos
OS)

This is the partitioning scheme for a switch shipped with Release 10.4R2 or earlier (or
after you reformat the disk during a downgrade from Release 10.4R3 or later to Release
10.4R2 or earlier). In this partitioning scheme, the switch comes from the factory with
only one Junos OS image installed in the root Junos OS partition of slice 1. The first time
that you perform a software upgrade, the new Junos OS image is installed in slice 2. If
the switch fails to boot, you must manually trigger it to boot from the alternate partition
(rebooting from the alternate partition does not occur automatically).

Understanding Upgrading or Downgrading Between Resilient Dual-Root Partition

Releases and Earlier Releases
Upgrading from Release 10.4R2 or earlier to Release 10.4R3 or later differs from other
upgrades in two important ways:

You must install a new loader software package in addition to installing the new Junos
OS image.

Rebooting after the upgrade reformats the disk from three partitions to four partitions.

You can perform all operations for this special software upgrade from the CLI.

CAUTION: Back up any important log files because the /var/log files are not
saved or restored during an upgrade from a nonresilient dual-root partition
release to a release that supports resilient dual-root partitions.
We recommend that you also save your /config files and any important log
files to an external medium because if there is a power interruption during
the upgrade process, they could be lost.

Related
Documentation

Resilient Dual-Root Partitions Frequently Asked Questions on page 47

Copyright 2011, Juniper Networks, Inc.

11

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Licenses Overview

Understanding Software Licenses for EX Series Switches on page 12

License Key Components for the EX Series Switch on page 16

Understanding Software Licenses for EX Series Switches

To enable and use some of the Juniper Networks operating system (Junos OS) features,
you must purchase, install, and manage separate software licenses. If the switch has the
appropriate software license, you can configure and use these features.
The Junos OS feature license (that is, the purchased authorization code) is universal.
However, to conform to Junos OS feature licensing requirements, you must install a
unique license key (a combination of the authorization code and the switchs serial
number) on each switch.
For a Virtual Chassis deployment, two license keys are recommended for redundancyone
for the device in the master role and the other for the device in the backup role:

In an EX8200 Virtual Chassis, the devices in the master and backup roles are always
XRE200 External Routing Engines.

In all other Virtual Chassis, the devices in the master and backup roles are switches.

You do not need additional license keys for Virtual Chassis member switches that are in
the linecard role or for the redundant Routing Engine (RE) modules or the redundant
Switch Fabric and Routing Engine (SRE) modules in an EX8200 member switch.
This topic describes:

Purchasing a Software Feature License on page 12

Features Requiring a License on EX2200 Switches on page 13

Features Requiring a License on EX3200, EX4200, EX4500, EX6200 and EX8200

Switches on page 14

Features Requiring a License on EX3300 Switches on page 14

License Warning Messages on page 15

Purchasing a Software Feature License

The following sections list features that require separate licenses on EX Series switches.
To purchase a software license, contact your Juniper Networks sales representative
(http://www.juniper.net/us/en/contact-us/sales-offices). You will be asked to supply the
chassis serial number of your switch; you can obtain the serial number by running the
show chassis hardware command.

12

Copyright 2011, Juniper Networks, Inc.

Chapter 1: Software Installation Overview

NOTE: You are required to provide a 12-digit serial number when purchasing
a license for an XRE200 External Routing Engine in an EX8200 Virtual Chassis.
The serial number listed on the XRE200 External Routing Engine serial ID
label is 16 digits long. Use the last 12 digits of the 16-digit serial number to
purchase the license.
You can use the show chassis hardware command output to display the 12-digit
serial number of the XRE200 External Routing Engine to use when you
purchase the license.

Features Requiring a License on EX2200 Switches

For Juniper Networks EX2200 Ethernet Switches, the following features can be added
to basic Junos OS by installing an enhanced feature license (EFL):

Bidirectional forwarding detection (BFD)

Connectivity fault management (IEEE 802.1ag)

IGMP (Internet Group Management Protocol) version 1 (IGMPv1), IGMPv2, and IGMPv3

OSPFv1/v2 (with 4 active interfaces)

Protocol Independent Multicast (PIM) dense mode, PIM source-specific mode, PIM
sparse mode

Q-in-Q tunneling (IEEE 802.1ad)

Real-time performance monitoring (RPM)

Table 4 on page 13 lists the EFLs that you can purchase for EX2200 switch models. If
you have the license, you can run all the enhanced software features on your switch.

Table 4: Junos OS EFL Part Number on EX2200 Switches

Switch Model

EFL Part Number

EX2200-C-12P-2G
EX2200-C-12T-2G

EX-12-EFL

EX2200-24T-4G
EX2200-24P-4G

EX-24-EFL

EX2200-48T-4G
EX2200-48P-4G

EX-48-EFL

Copyright 2011, Juniper Networks, Inc.

13

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Features Requiring a License on EX3200, EX4200, EX4500, EX6200 and EX8200

Switches
Juniper Networks EX3200, EX4200, EX4500, and EX8200 Ethernet Switches require an
advanced feature license (AFL) for the following Junos OS features:

Border Gateway Protocol (BGP) and multiprotocol BGP (MBGP)

Intermediate System-to-Intermediate System (IS-IS)

IPv6 protocols: OSPFv3, RIPng, IS-IS for IPv6, IPv6 BGP

MPLS with RSVP-based label-switched paths (LSPs) and MPLS-based circuit

cross-connects (CCCs)

Table 5 on page 14 lists the AFLs you can purchase for EX Series switch models. If you
have the license, you can run all the advanced software features on your switch.

Table 5: Junos OS AFL Part Number on EX3200, EX4200, EX4500,

EX6200 and EX8200 Switches
Switch Model

AFL Part Number

EX3200-24P
EX3200-24T
EX4200-24F
EX4200-24P
EX4200-24T

EX-24-AFL

EX3200-48P
EX3200-48T
EX4200-48F
EX4200-48P
EX4200-48T

EX-48-AFL

EX4500-40F-BF
EX4500-40F-BF-C
EX4500-40F-FB
EX4500-40F-FB-C

EX-48-AFL

EX6200

EX6200-AFL

EX8208

EX8208-AFL

EX8216

EX8216-AFL

Features Requiring a License on EX3300 Switches

Juniper Networks EX3300 Ethernet Switches require a feature license for the following
Junos OS features:

14

OSPFv1/v2 (with 4 active interfaces)

Q-in-Q tunneling (IEEE 802.1ad)

Copyright 2011, Juniper Networks, Inc.

Chapter 1: Software Installation Overview

Table 6 on page 15 lists the EFLs that you can purchase for EX3300 switch models. If
you have the license, you can run all the above-mentioned enhanced software features
on your switch.

Table 6: Junos OS EFL Part Number on EX3300 Switches

Switch Model

EFL Part Number

EX3300-24T
EX3300-24P
EX3300-24T-DC

EX-24-EFL

EX3300-48T/P
EX3300-48P
EX3300-48T-DC

EX-48-EFL

License Warning Messages

For using features that require a license, you must install and configure a license key. To
obtain a license key, use the contact information provided in your certificate.
If you have not purchased the AFL or EFL and installed the license key, you receive
warnings when you try to commit the configuration:
[edit protocols]
'bgp'
warning: requires 'bgp' license
error: commit failed: (statements constraint check failed)

The system generates system log (syslog) alarm messages notifying you that the feature
requires a licensefor example:
Sep 3 05:59:11
craftd[806]: Minor alarm set, BGP Routing Protocol usage
requires a license
Sep 3 05:59:11
alarmd[805]: Alarm set: License color=YELLOW, class=CHASSIS,
reason=BGP Routing Protocol usage requires a license
Sep 3 05:59:11
alarmd[805]: LICENSE_EXPIRED: License for feature bgp(47) expired

Output of the show system alarms command displays the active alarms:
user@switch> show system alarms
1 alarm currently active
Alarm time
Class
2009-09-03 06:00:11 UTC Minor

Related
Documentation

Description
BGP Routing Protocol usage requires a license

Managing Licenses for the EX Series Switch (CLI Procedure) on page 31

Managing Licenses for the EX Series Switch (J-Web Procedure) on page 33

Monitoring Licenses for the EX Series Switch on page 40

License Key Components for the EX Series Switch on page 16

EX Series Switch Software Features Overview

Copyright 2011, Juniper Networks, Inc.

15

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

License Key Components for the EX Series Switch

When you purchase a license for a Junos OS feature that requires a separate license, you
receive a license key.
A license key consists of two parts:

License IDAlphanumeric string that uniquely identifies the license key. When a license
is generated, it is given a license ID.

License dataBlock of binary data that defines and stores all license key objects.

For example, in the following typical license key, the string Junos204558 is the license
ID, and the trailing block of data is the license data:
Junos204558 aeaqea qmijhd amrqha ztfmbu gqzama uqceds
ra32zr lsevik ftvjed o4jy5u fynzzj mgviyl
kgioyf ardb5g sj7wnt rsfked wbjf5a sg

The license data defines the device ID for which the license is valid and the version of the
license.
Related
Documentation

16

Managing Licenses for the EX Series Switch (CLI Procedure) on page 31

Managing Licenses for the EX Series Switch (J-Web Procedure) on page 33

Understanding Software Licenses for EX Series Switches on page 12

Copyright 2011, Juniper Networks, Inc.

CHAPTER 2

Installing Junos OS

Downloading Software Packages from Juniper Networks on page 17

Installing Software on an EX Series Switch with a Single Routing Engine (CLI

Procedure) on page 18

Installing Software on an EX Series Switch with Redundant Routing Engines (CLI

Procedure) on page 19

Installing Software on EX Series Switches (J-Web Procedure) on page 24

Rebooting or Halting the EX Series Switch (J-Web Procedure) on page 25

Downloading Software Packages from Juniper Networks

You can download Junos OS packages from the Juniper Networks website to upgrade
software on your EX Series switch.
Before you begin to download software upgrades, ensure that you have a Juniper Networks
Web account and a valid support contract. To obtain an account, complete the registration
form at the Juniper Networks website: https://www.juniper.net/registration/Register.jsp.
To download software upgrades from Juniper Networks:
1.

Using a Web browser, follow the links to the download URL on the Juniper Networks
webpage. For EX Series, there are not separate software packages for Canada the
U.S. and other locations. Therefore, select Canada and U.S. Version regardless of
your location:

https://www.juniper.net/support/csc/swdist-domestic/

2. Log in to the Juniper Networks authentication system using the username (generally

your e-mail address) and password supplied by Juniper Networks representatives.

3. Using the J-Web interface or the CLI, select the appropriate software package for your

application. See Junos OS Package Names on page 8.

4. Download the software to a local host or to an internal software distribution site.

Related
Documentation

Installing Software on EX Series Switches (J-Web Procedure) on page 24

Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure)
on page 18

Copyright 2011, Juniper Networks, Inc.

17

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Understanding Software Installation on EX Series Switches on page 5

Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure)
You can use this procedure to upgrade Junos OS on an EX Series switch with a single
Routing Engine, including an individual member of an EX4200 Virtual Chassis or all
members of an EX4200 Virtual Chassis, or an EX8200 switch using a single Routing
Engine. To upgrade software on an EX8200 switch running two Routing Engines, see
Installing Software on an EX Series Switch with Redundant Routing Engines (CLI
Procedure) on page 19 or Upgrading Software on an EX8200 Standalone Switch Using
Nonstop Software Upgrade (CLI Procedure).
To install software upgrades on a switch with a single Routing Engine:
1.

Download the software package as described in Downloading Software Packages

from Juniper Networks on page 17.

2. (Optional) Back up the current software configuration to a second storage option.

See the Junos OS Installation and Upgrade Guide for instructions on performing this task.
3. (Optional) Copy the software package to the switch. We recommend that you use

FTP to copy the file to the /var/tmp directory.

This step is optional because Junos OS can also be upgraded when the software
image is stored at a remote location. These instructions describe the software upgrade
process for both scenarios.
4. Install the new package on the switch:

user@switch> request system software add package

Replace package with one of the following paths:

For a software package in a local directory on the switch/var/tmp/package.tgz.

For a software package on a remote server:

ftp://hostname/pathname/package.tgz

http://hostname/pathname/package.tgz

where package.tgz is, for example, jinstall-ex-4200-9.4R1.8-domestic-signed.tgz.

Include the optional member option to install the software package on only one
member of an EX4200 Virtual Chassis:
user@switch> request system software add source member member-id reboot

Other members of the Virtual Chassis are not affected. To install the software on all
members of the Virtual Chassis, do not include the member option.

18

Copyright 2011, Juniper Networks, Inc.

Chapter 2: Installing Junos OS

NOTE: To abort the installation, do not reboot your device; instead, finish
the installation and then issue the request system software delete
package.tgz command, where package.tgz is, for example,
jinstall-ex-8200-10.2R1.8-domestic-signed.tgz. This is your last chance to
stop the installation.

5. Reboot to start the new software:

user@switch> request system reboot

6. After the reboot has completed, log in and verify that the new version of the software

is properly installed:
user@switch> show version

Related
Documentation

Installing Software on EX Series Switches (J-Web Procedure) on page 24

Troubleshooting Software Installation on page 43

Junos OS Package Names on page 8

Understanding Software Installation on EX Series Switches on page 5

Installing Software on an EX Series Switch with Redundant Routing Engines (CLI

Procedure)
For an EX6200 switch or an EX8200 switch with redundant Routing Engines, you can
minimize disruption to network operation during a Junos OS upgrade by upgrading the
Routing Engines separately, starting with the backup Routing Engine.

NOTE: If your EX8200 switch is running Junos OS Release 10.4 or later, you
can upgrade the software packages on both Routing Engines with a single
command and with minimal network disruption by using nonstop software
upgrade (NSSU) instead of this procedure. See Upgrading Software on an
EX8200 Standalone Switch Using Nonstop Software Upgrade (CLI
Procedure).

WARNING: If graceful routing engine switchover (GRES) or nonstop active

routing (NSR) is enabled when you initiate a software installation, the
software does not install properly. Make sure you disable GRES before you
begin the software installation by using the deactivate chassis redundancy
graceful-switchover command in configuration mode. 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.

Copyright 2011, Juniper Networks, Inc.

19

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

To upgrade the software package on an EX6200 switch or an EX8200 switch with one
installed Routing Engine, see Installing Software on an EX Series Switch with a Single
Routing Engine (CLI Procedure) on page 18.
To upgrade redundant Routing Engines, you first install the new Junos OS release on the
backup Routing Engine while keeping the currently running software version on the master
Routing Engine. After making sure that the new software version is running correctly on
the backup Routing Engine, you switch device control to the backup Routing Engine.
Finally, you install the new software on the new backup Routing Engine.
To upgrade Junos OS on the switch, perform the following tasks:
1.

Preparing the Switch for the Software Installation on page 20

2. Installing Software on the Backup Routing Engine on page 21

3. Installing Software on the Default Master Routing Engine on page 22
4. Returning Routing Control to the Default Master Routing Engine (Optional) on page 23

Preparing the Switch for the Software Installation

Perform the following steps before installing the software:
1.

Log in to the master Routing Engines console.

For information on logging in to the Routing Engine through the console port, see
Connecting and Configuring an EX Series Switch (CLI Procedure).

2. Enter the Junos OS CLI configuration mode:

a. Start the CLI from the shell prompt:

user@switch:RE% cli

You will see:

{master}
user@switch>
b. Enter configuration mode:

user@switch> configure

You will see:

{master}[edit]
user@switch#
3. Disable nonstop active routing (NSR) (supported on switches running Junos OS

Release 10.4 or later):

{master}[edit]
user@switch# delete routing-options nonstop-routing
4. Disable graceful Routing Engine switchover (GRES):

{master}[edit]
user@switch# deactivate chassis redundancy graceful-switchover

20

Copyright 2011, Juniper Networks, Inc.

Chapter 2: Installing Junos OS

5. Save the configuration change on both Routing Engines:

{master}[edit]
user@switch# commit synchronize

NOTE: To ensure the most recent configuration changes are committed

before the software upgrade, perform this step even if nonstop active
routing and graceful Routing Engine switchover were previously disabled.

6. Exit the CLI configuration mode:

[edit]
user@switch# exit
7. (Optional) Back up the current software configuration to a second storage option.

See the Junos OS Installation and Upgrade Guide for instructions on performing this task.

Installing Software on the Backup Routing Engine

After you have prepared the switch for software installation, install the software on the
backup Routing Engine. During the installation, the master Routing Engine continues
operations, minimizing the disruption to network traffic.
1.

Download the software by following the procedures in Downloading Software

Packages from Juniper Networks on page 17.

2. Copy the software package to the switch. We recommend that you use FTP to copy

the file to the /var/tmp directory.

3. Log in to the console of the backup Routing Engine.
4. Install the new software package:

user@switch> request system software add /var/tmp/package.tgz

where package.tgz is, for example, jinstall-ex-8200-10.2R1.8-domestic-signed.tgz.

NOTE: To abort the installation, do not reboot your device; instead, finish
the installation and then issue the request system software delete
package.tgz command, where package.tgz is, for example,
jinstall-ex-8200-10.2R1.8-domestic-signed.tgz. This is your last chance to
stop the installation.

5. Reboot to start the new software:

user@switch> request system reboot

Reboot the system? [yes, no] (no) yes

NOTE: You must reboot the switch to load the new installation of the
Junos OS.

Copyright 2011, Juniper Networks, Inc.

21

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

6. After the reboot has completed, log in and verify the new version of the software is

properly installed:
user@switch> show version

Installing Software on the Default Master Routing Engine

To transfer control to the backup Routing Engine and then upgrade or downgrade the
master Routing Engine software:
1.

Log in to the master Routing Engine console port.

2. Transfer control to the backup Routing Engine:

CAUTION: Because graceful Routing Engine switchover is disabled, this

switchover causes all line cards in the switch to reload. All network traffic
passing through these line cards is lost during the line card reloads.

user@switch> request chassis routing-engine master switch

3. Verify that the default backup Routing Engine (shown as slot 1 in the command output)

is now the master Routing Engine:

user@switch> show chassis routing-engine

You will see:

Routing Engine status:
Slot 0:
Current state
Election priority
Routing Engine status:
Slot 1:
Current state
Election priority

Backup
Master (default)

Master
Backup (default)

4. Install the new software package:

user@switch> request system software add package.tgz

5. Reboot the Routing Engine:

user@switch> request system reboot

Reboot the system? [yes, no] (no) yes

When the reboot completes, the prompt will reappear. Wait for this prompt to reappear
before proceeding to the next step.
6. Log in to the default backup Routing Engine (slot 1) through the console port.
7. Re-enable graceful Routing Engine switchover:

[edit]
user@switch# activate chassis redundancy graceful-switchover

Re-enabling graceful Routing Engine switchover allows any future Routing Engine
switchovers to occur without loss of any network traffic.

22

Copyright 2011, Juniper Networks, Inc.

Chapter 2: Installing Junos OS

8. Re-enable nonstop active routing:

[edit]
user@switch# set routing-options nonstop-routing

NOTE: Automatic commit synchronization is a requirement for nonstop

active routing. If you have not yet enabled it, do so with the set system
commit synchronize command.

9. Save the configuration change:

[edit]
user@switch# commit synchronize
10. Log in and verify the version of the software installed.

If you want to return routing control to the Routing Engine that was the master Routing
Engine at the beginning of the procedure (the default master Routing Engine), perform
the next task.

Returning Routing Control to the Default Master Routing Engine (Optional)

The switch can maintain normal operations with the Routing Engine in slot 1 acting as
the master Routing Engine after the software upgrade, so only perform this task if you
want to return routing control to the default master Routing Engine in slot 0.
1.

Transfer routing control back to the default master Routing Engine:

user@switch> request chassis routing-engine master switch

2. Verify that the default master Routing Engine (slot 0) is indeed the master Routing

Engine:
user@switch> show chassis routing-engine

You will see:

Routing Engine status:
Slot 0:
Current state
Election priority
Routing Engine status:
Slot 1:
Current state
Election priority

Related
Documentation

Master
Master (default)

Backup
Backup (default)

Installing Software on EX Series Switches (J-Web Procedure) on page 24

Upgrading Software on an EX8200 Standalone Switch Using Nonstop Software

Upgrade (CLI Procedure)

Troubleshooting Software Installation on page 43

Junos OS Package Names on page 8

Understanding Software Installation on EX Series Switches on page 5

Copyright 2011, Juniper Networks, Inc.

23

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Installing Software on EX Series Switches (J-Web Procedure)

You can upgrade software packages on a single fixed-configuration switch, on an
individual member of a Virtual Chassis, or for all members of a Virtual Chassis.
You can use the J-Web interface to install software upgrades from a server using FTP or
HTTP, or by copying the file to the EX Series switch.
This topic describes:
1.

Installing Software Upgrades from a Server on page 24

2. Installing Software Upgrades by Uploading Files on page 25

Installing Software Upgrades from a Server

To install software upgrades from a remote server by using FTP or HTTP:
1.

Download the software package as described in Downloading Software Packages

from Juniper Networks on page 17.

2. Log in to the Juniper Networks authentication system using the username (generally

your e-mail address) and password supplied by Juniper Networks representatives.

3. In the J-Web interface, select Maintain > Software > Install Package.
4. On the Install Remote page, enter information into the fields described in Table 7 on

page 24.
5. Click Fetch and Install Package. The software is activated after the switch has

rebooted.

Table 7: Install Remote Summary

Field

Function

Your Action

Package Location
(required)

Specifies the FTP or HTTP server, file path, and

software package name.

Type the full address of the software package

location on the FTP or HTTP serverone of the
following:
ftp://hostname/pathname/package-name
http://hostname/pathname/package-name

User

Specifies the username, if the server requires

one.

Type the username.

Password

Specifies the password, if the server requires

one.

Type the password.

Reboot If Required

If this box is checked, the switching platform is

automatically rebooted when the upgrade is
complete.

Check the box if you want the switching platform to

reboot automatically when the upgrade is complete.

24

Copyright 2011, Juniper Networks, Inc.

Chapter 2: Installing Junos OS

Installing Software Upgrades by Uploading Files

To install software upgrades by uploading files:
1.

Download the software package.

2. In the J-Web interface, select Maintain>Software>Upload Package.

3. On the Upload Package page, enter information into the fields described in Table 8

on page 25.
4. Click Upload and Install Package. The software is activated after the switching

platform has rebooted.

Table 8: Upload Package Summary

Field

Function

Your Action

File to Upload
(required)

Specifies the location of the software

package.

Type the location of the software package, or click

Browse to navigate to the location.

Reboot If Required

Specifies that the switching platform is

automatically rebooted when the upgrade
is complete.

Select the check box if you want the switching

platform to reboot automatically when the upgrade
is complete.

Related
Documentation

Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure)
on page 18

Understanding Software Installation on EX Series Switches on page 5

Troubleshooting Software Installation on page 43

Rebooting or Halting the EX Series Switch (J-Web Procedure)

You can use the J-Web interface to schedule a reboot or to halt the switching platform.
To reboot or halt the switching platform by using the J-Web interface:
1.

In the J-Web interface, select Maintain > Reboot.

2. Select one:

Reboot ImmediatelyReboots the switching platform immediately.

Reboot in number of minutesReboots the switch in the number of minutes from

now that you specify.

Reboot when the system time is hour:minute Reboots the switch at the absolute
time that you specify, on the current day. You must select a 2-digit hour in 24-hour
format and a 2-digit minute.

Halt Immediately Stops the switching platform software immediately. After the
switching platform software has stopped, you can access the switching platform
through the console port only.

Copyright 2011, Juniper Networks, Inc.

25

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

3. (Optional) In the Message box, type a message to be displayed to any users on the

switching platform before the reboot occurs.

4. Click Schedule. The J-Web interface requests confirmation to perform the reboot or

halt.
5. Click OK to confirm the operation.

Related
Documentation

26

If the reboot is scheduled to occur immediately, the switch reboots. You cannot
access the J-Web interface until the switch has restarted and the boot sequence
is complete. After the reboot is complete, refresh the browser window to display
the J-Web interface login page.

If the reboot is scheduled to occur in the future, the Reboot page displays the time
until reboot. You have the option to cancel the request by clicking Cancel Reboot
on the J-Web interface Reboot page.

If the switch is halted, all software processes stop and you can access the switching
platform through the console port only. Reboot the switch by pressing any key on
the keyboard.

Starting the J-Web Interface

Copyright 2011, Juniper Networks, Inc.

CHAPTER 3

Registering the Switch, Booting the

Switch, Upgrading Software, and
Managing Licenses

Registering the Switch on page 27

Booting the Switch on page 27

Upgrading Software on page 30

Managing Licenses on page 31

Registering the Switch

Registering the EX Series Switch with the J-Web Interface on page 27

Registering the EX Series Switch with the J-Web Interface

You can register your EX Series switch with the J-Web interface so that you can request
technical assistance as and when required. To register an EX Series switch:
1.

In the J-Web interface, select Maintain > Customer Support > Product Registration.
Note the serial number that is displayed.

2. Click Register. Enter the serial number in the page that is displayed.

Related
Documentation

EX Series Switch Software Features Overview

Booting an EX Series Switch Using a Software Package Stored on a USB Flash

Drive on page 28

Creating a Snapshot and Using It to Boot an EX Series Switch on page 29

Booting the Switch

Copyright 2011, Juniper Networks, Inc.

27

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Booting an EX Series Switch Using a Software Package Stored on a USB Flash Drive
There are two methods of getting Junos OS onto a USB flash drive before using the
software to boot the switch. You can pre-install the software onto the USB flash drive
before inserting the USB flash drive into the USB port, or you can use the system snapshot
feature to copy files from internal switch memory to the USB flash drive.
To move files into USB flash memory using a system snapshot and use those files to
boot the switch, see Creating a Snapshot and Using It to Boot an EX Series Switch on
page 29. We recommend that you use this method to boot the switch from a USB flash
drive if your switch is running properly.
If you need to pre-install the software onto the USB flash drive, you can use the method
described in this topic. Pre-installing the Junos OS onto a USB flash drive to boot the
switch can be done at any time and is particularly useful when the switch boots to the
loader prompt because the switch cannot locate the Junos OS in internal flash memory.
Ensure that you have the following tools and parts available to boot the switch from a
USB flash drive:

A USB flash drive that meets the EX Series switch USB port specifications. See USB
Port Specifications for an EX Series Switch.

A computer or other device that you can use to download the software package from
the Internet and copy it to the USB flash drive.

To download a Junos OS package onto a USB flash drive before inserting the USB flash
drive:
1.

Download the Junos OS package that you would like to place onto the EX Series
switch from the Internet onto the USB flash drive using your computer or other device.
See Downloading Software Packages from Juniper Networks on page 17.

2. Remove the USB flash drive from the computer or other device.
3. Insert the USB flash drive into the USB port on the switch.
4. This step can only be performed when the prompt for the loader script (loader>) is

displayed. The loader script starts when the Junos OS loads but the CLI is not working
for any reason or if the switch has no software installed.
Install the software package onto the switch:
loader> install source

where source represents the name and location of the Junos OS package on the USB
flash drive. The Junos OS package on a flash drive is commonly stored in the root drive
as the only filefor example, file:///jinstall-ex-4200-9.4R1.5-domestic-signed.tgz.

Related
Documentation

28

Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure)
on page 18

Installing Software on EX Series Switches (J-Web Procedure) on page 24

Copyright 2011, Juniper Networks, Inc.

Chapter 3: Registering the Switch, Booting the Switch, Upgrading Software, and Managing Licenses

See Rear Panel of an EX3200 Switch for USB port location.

See Rear Panel of an EX4200 Switch for USB port location.

See Switch Fabric and Routing Engine (SRE) Module in an EX8208 Switch for USB
port location.

See Routing Engine (RE) Module in an EX8216 Switch for USB port location.

Understanding Software Installation on EX Series Switches on page 5

Creating a Snapshot and Using It to Boot an EX Series Switch

The system snapshot feature takes a snapshot of the files currently used to run the EX
Series switchthe complete contents of the /config and /var directories, which include
the running Juniper Networks Junos OS, the active configuration, and the rescue
configurationand copies all of these files into an alternate (internal, meaning internal
flash, or an external, meaning USB flash) memory source. You can then use these
snapshots to boot the switch at the next bootup or as a backup boot option.
This topic includes the following tasks:

Creating a Snapshot on a USB Flash Drive and Using It to Boot the Switch on page 29

Creating a Snapshot on an Internal Flash Drive and Using it to Boot the

Switch on page 30

Creating a Snapshot on a USB Flash Drive and Using It to Boot the Switch
A snapshot can be created on USB flash memory after a switch is booted using files
stored in internal memory.
Ensure that you have the following tools and parts available before creating a snapshot
on a USB Flash drive:

A USB flash drive that meets the EX Series switch USB port specifications. See USB
Port Specifications for an EX Series Switch.

To create a snapshot on USB flash memory and use it to boot the switch:
1.

Place the snapshot into USB flash memory:

user@switch> request system snapshot partition media external slice 1

NOTE: This example uses the partition option. If you have already created
a partition for the snapshot, you dont need to use the partition option.

2. (Optional) Perform this step if you want to boot the switch now using the snapshot

stored on the USB flash drive. If you created the snapshot as a backup, do not perform
this step.

To reboot the switch using the most recently created snapshot:

user@switch> request system reboot media external

Copyright 2011, Juniper Networks, Inc.

29

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

To reboot the switch using a snapshot in a specific partition on the USB flash drive:
user@switch> request system reboot media external slice 1

Creating a Snapshot on an Internal Flash Drive and Using it to Boot the Switch
A snapshot can be created on internal memory after a switch is booted using files stored
in external memory.
To create a snapshot in internal memory and use it to boot the switch:
1.

Place the snapshot files in internal memory:

user@switch> request system snapshot parition media internal slice 1

NOTE: This example uses the partition option. If you have already created
a partition for the snapshot, you dont need to use the partition option.

2. (Optional) Perform this step if you want to boot the switch now using the newly

created snapshot. If you created the snapshot as a backup, do not perform this step.

To reboot the switch using the most recently created snapshot:

user@switch> request system reboot media internal

To reboot the switch using a snapshot in a specific partition in internal memory:

user@switch> request system reboot media internal slice 1

Related
Documentation

Verifying That a System Snapshot Was Created on an EX Series Switch on page 36

Understanding System Snapshot on EX Series Switches on page 8

Upgrading Software

Upgrading Software Using Automatic Software Download on EX Series

Switches on page 30

Upgrading Software Using Automatic Software Download on EX Series Switches

The automatic software download feature uses the DHCP message exchange process
to download and install software packages. You configure the automatic software
download feature on EX Series switches acting as DHCP clients. You must enable
automatic software download on the EX Series 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 EX Series switch compares
the software package name in the DHCP server message to the name of the software
package that booted the switch. If the software packages are different, the DHCP client

30

Copyright 2011, Juniper Networks, Inc.

Chapter 3: Registering the Switch, Booting the Switch, Upgrading Software, and Managing Licenses

EX Series switch downloads and installs the software package specified in the DHCP
server message.
Before you upgrade software 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. See the Junos OS System Basics Configuration Guide for information about
using the CLI to configure DHCP services and settings. See Configuring DHCP Services
(J-Web Procedure) for information about using the J-Web interface to configure DHCP
services and settings.
To enable automatic software download on an EX Series switch acting as a DHCP client:
[edit chassis]
user@switch# set auto-image-upgrade

Once automatic software download is enabled on your DHCP client EX Series switch
and once 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:
Auto-image upgrade started
On successful installation system will reboot automatically

The switch reboots automatically to complete the upgrade.

Related
Documentation

Verifying That Automatic Software Download Is Working Correctly on page 35

Understanding Software Installation on EX Series Switches on page 5

DHCP Services for EX Series Switches Overview

Managing Licenses for the EX Series Switch (CLI Procedure) on page 31

Managing Licenses for the EX Series Switch (J-Web Procedure) on page 33

Managing Licenses

Managing Licenses for the EX Series Switch (CLI Procedure)

To enable and use some Junos OS features on an EX Series switch, you must purchase,
install, and manage separate software licenses. Each switch requires one license. For a
Virtual Chassis deployment, two licenses are recommended for redundancy. After you
have configured the features, you see a warning message if the switch does not have a
license for the feature.
Before you begin managing licenses, be sure that you have:

Obtained the needed licenses. For information about how to purchase software licenses,
contact your Juniper Networks sales representative.

Copyright 2011, Juniper Networks, Inc.

31

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Understand what makes up a license key. For more information, see License Key
Components for the EX Series Switch on page 16.

This topic includes the following tasks:

Adding New Licenses on page 32

Deleting Licenses on page 32

Saving License Keys on page 32

Adding New Licenses

To add one or more new license keys on the switch, with the CLI:
1.

Add the license key or keys:

To add one or more license keys from a file or URL, specify the filename of the file
or the URL where the key is located:
user@switch> request system license add filename | url

To add a license key from the terminal:

user@switch> request system license add terminal

2. When prompted, enter the license key, separating multiple license keys with a blank

line.
If the license key you enter is invalid, an error appears in the CLI output when you press
Ctrl+d to exit the license entry mode.

Deleting Licenses
To delete one or more license keys from the switch with the CLI, specify the license ID:
user@switch> request system license delete license-id

You can delete only one license at a time.

Saving License Keys

To save the installed license keys to a file (which can be a URL) or to the terminal:
user@switch> request system license save filename | url

For example, the following command saves the installed license keys to a file named
license.conf:
user@switch> request system license save ftp://user@switch/license.conf

Related
Documentation

32

Managing Licenses for the EX Series Switch (J-Web Procedure) on page 33

Monitoring Licenses for the EX Series Switch on page 40

Understanding Software Licenses for EX Series Switches on page 12

Copyright 2011, Juniper Networks, Inc.

Chapter 3: Registering the Switch, Booting the Switch, Upgrading Software, and Managing Licenses

Managing Licenses for the EX Series Switch (J-Web Procedure)

To enable and use some Junos OS features on an EX Series switch, you must purchase,
install, and manage separate software licenses. Each switch requires one license. For a
Virtual Chassis deployment, two licenses are recommended for redundancy. After you
have configured the features, you see a warning message if the switch does not have a
license for the feature.
Before you begin managing licenses, be sure that you have:

Obtained the needed licenses. For information about how to purchase software licenses,
contact your Juniper Networks sales representative.

Understand what makes up a license key. For more information, see License Key
Components for the EX Series Switch on page 16.

This topic includes the following tasks:

Adding New Licenses on page 33

Deleting Licenses on page 33

Displaying License Keys on page 34

Downloading Licenses on page 34

Adding New Licenses

To add one or more new license keys on the switch, with the J-Web license manager:
1.

In the J-Web interface, select Maintain > Licenses.

2. Under Installed Licenses, click Add to add a new license key or keys.
3. Do one of the following, using a blank line to separate multiple license keys:

In the License File URL box, type the full URL to the destination file containing the
license key or keys to be added.

In the License Key Text box, paste the license key text, in plain-text format, for the
license to be added.

4. Click OK to add the license key or keys.

A list of features that use the license key is displayed. The table also lists the ID, state,
and version of the license key.

Deleting Licenses
To delete one or more license keys from a switch with the J-Web license manager:
1.

In the J-Web interface, select Maintain > Licenses.

2. Select the check box of the license or licenses you want to delete.
3. Click Delete.

Copyright 2011, Juniper Networks, Inc.

33

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Displaying License Keys

To display the license keys installed on a switch with the J-Web license manager:
1.

In the J-Web interface, select Maintain > Licenses.

2. Under Installed Licenses, click Display Keys to display all the license keys installed

on the switch.
A screen displaying the license keys in text format appears. Multiple licenses are separated
by a blank line.

Downloading Licenses
To download the license keys installed on the switch with the J-Web license manager:
1.

In the J-Web interface, select Maintain > Licenses.

2. Under Installed Licenses, click Download Keys to download all the license keys

installed on the switch to a single file.

3. Select Save it to disk and specify the file to which the license keys are to be written.

You can also download the license file to your system.

Related
Documentation

34

Managing Licenses for the EX Series Switch (CLI Procedure) on page 31

Monitoring Licenses for the EX Series Switch on page 40

Understanding Software Licenses for EX Series Switches on page 12

Copyright 2011, Juniper Networks, Inc.

CHAPTER 4

Verifying Software Installation

Routine Monitoring on page 35

Monitoring Licenses on page 40

Verifying That Automatic Software Download Is Working Correctly on page 35

Verifying That a System Snapshot Was Created on an EX Series Switch on page 36

Verifying Junos OS and Boot Loader Software Versions on an EX Series

Switch on page 36

Routine Monitoring

Verifying That Automatic Software Download Is Working Correctly

Purpose
Action

Verify that the automatic software download feature is working correctly.

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.
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, 2.2.2.2, 3.3.3.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

Copyright 2011, Juniper Networks, Inc.

35

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

message to arrive on the DHCP client had a boot server address of 192.168.1.165 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.

Related
Documentation

Upgrading Software Using Automatic Software Download on EX Series Switches on

page 30

DHCP Services for EX Series Switches Overview

Verifying That a System Snapshot Was Created on an EX Series Switch

Purpose
Action

Verify that a system snapshot was created with the proper files on an EX Series switch.
View the snapshot:
user@switch> show system snapshot media external
Information for snapshot on external (da1s1)
Creation date: Oct 1320:23:23 2009
Junos version on snapshot:
jbase : 10.0I20090726_0011_user
jcrypto-ex: 10.0I20090726_0011_user
jdocs-ex: 10.0I20090726_0011_user
jkernel-ex: 10.0I20090726_0011_user
jroute-ex: 10.0I20090726_0011_user
jswitch-ex: 10.0I20090726_0011_user
jweb-ex: 10.0I20090726_0011_user
jpfe-ex42x: 10.0I20090726_0011_user

Meaning

The output shows the date and time when the snapshot was created and the packages
that are part of the snapshot. The date and time match the time when you created the
snapshot.
You can compare the output of this command to the output of the show system software
command to ensure that the snapshot contains the same packages as the software
currently running the switch.

Related
Documentation

Creating a Snapshot and Using It to Boot an EX Series Switch on page 29

Verifying Junos OS and Boot Loader Software Versions on an EX Series Switch

Before or after upgrading or downgrading Junos OS, you might need to verify the Junos
OS version. You might also need to verify the boot loader software version if you are
upgrading to or downgrading from a release that supports resilient dual-root partitions
(Junos OS Release 10.4R3 and later).
This topic includes:

36

Verifying the Number of Partitions and File System Mountings on page 37

Verifying the Loader Software Version on page 38

Copyright 2011, Juniper Networks, Inc.

Chapter 4: Verifying Software Installation

Verifying Which Root Partition Is Active on page 38

Verifying the Junos OS Version in Each Root Partition on page 39

Verifying the Number of Partitions and File System Mountings

Purpose

Action

Between Junos OS Release 10.4R2 and Release 10.4R3, upgrades were made to further
increase resiliency of root partitions, which required reformatting the disk from three
partitions to four partitions. If your switch is running Release 10.4R2 or earlier, it has three
partitions, and if it is running Release 10.4R3 or later, it has four partitions.
Verify how many partitions the disk has, as well as where each file system is mounted,
by using the following command:
user@switch> show system storage
fpc0:
----------------------------------------------------------------------Filesystem Size Used Avail Capacity Mounted on
/dev/da0s1a 184M 124M
45M
73%
/
devfs
1.0K 1.0K
0B
100% /dev
/dev/md0
37M
37M
0B
100% /packages/mnt/jbase
/dev/md1
18M
18M
0B
100%
/packages/mnt/jcrypto-ex-10.4I20110121_0509_hbRPSRLI15184421081
/dev/md2
6.1M 6.1M
0B
100%
/packages/mnt/jdocs-ex-10.4I20110121_0509_hbRPSRLI15184421081
/dev/md3
154M 154M
0B
100%
/packages/mnt/jkernel-ex-10.4I20110121_0509_hbRPSRLI15184421081
/dev/md4
23M
23M
0B
100%
/packages/mnt/jpfe-ex42x-10.4I20110121_0509_hbRPSRLI15184421081
/dev/md5
46M
46M
0B
100%
/packages/mnt/jroute-ex-10.4I20110121_0509_hbRPSRLI15184421081
/dev/md6
28M
28M
0B
100%
/packages/mnt/jswitch-ex-10.4I20110121_0509_hbRPSRLI15184421081
/dev/md7
22M
22M
0B
100%
/packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081
/dev/md8
126M 10.0K 116M
0% /tmp
/dev/da0s3e 123M
632K 112M
1% /var
/dev/da0s3d 369M
20K 339M
0% /var/tmp
/dev/da0s4d
62M
62K
57M
0% /config
/dev/md9
118M
12M
96M
11% /var/rundb
procfs
4.0K 4.0K
0B
100% /proc
/var/jail/etc 123M 632K 112M
1%
/packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081/jail/var/etc
/var/jail/run 123M
632K 112M
1%
/packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081/jail/var/run
/var/jail/tmp 123M
632K 112M
1%
/packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081/jail/var/tmp
/var/tmp
369M
20K 339M
0%
/packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081/jail/var/tmp/uploads
devfs
1.0K
1.0K
0B 100%
/packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081/jail/dev

Meaning

The presence of the partition name containing s4d indicates the fourth slice. If this were
a three-slice partition scheme, in place of s1a, s3e, s3d, and s4d, you would see s1a, s1f,
s2a, s2f, s3d, and s3e and you would not see s4d.

Copyright 2011, Juniper Networks, Inc.

37

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Verifying the Loader Software Version

Purpose

Action

For the special case of upgrading from Junos OS Release 10.4R2 or earlier to Release
10.4R3 or later, you must upgrade the loader software.
For EX Series switches, except EX8200 switches:
user@switch> show chassis firmware
Part
Type
FPC 0
uboot
loader

Version
U-Boot 1.1.6 (Jan

3 2011 - 16:14:58) 1.0.0

FreeBSD/PowerPC U-Boot bootstrap loader 2.4

For EX8200 switches:

user@switch> show chassis firmware
Part
Type
FPC 0
uboot
loader

Meaning

Version
U-Boot 1.1.6 (Jan

3 2011 - 16:14:58) 3.5.0

FreeBSD/PowerPC U-Boot bootstrap loader 2.4

For EX Series switches, other than EX8200 switches, with Junos OS Release 10.4R3 or
later installed:

If there is version information following the timestamp for U-Boot (1.0.0 in the preceding
example), then the loader software does not require upgrading.

If there is no version number following the timestamp for U-boot, then the loader
software requires upgrading.

NOTE: If the software version is Release 10.4R2 or earlier, no version number

is displayed following the timestamp for U-boot, regardless of the loader
software version installed. If you do not know whether you have installed the
new loader software, you should upgrade the loader software when you
upgrade the software version.

For EX8200 switches, if the version number following the timestamp for U-Boot is earlier
than 3.5.0, you must upgrade the loader software when you upgrade the software version.

Verifying Which Root Partition Is Active

Purpose

Switches running Release 10.4R3 or later have resilient dual-root partition functionality,
which includes the ability to boot transparently from the inactive partition if the system
fails to boot from the primary root partition.
You can verify which root partition is active using the following command:

Action

38

user@switch> show system storage partitions

fpc0:
-------------------------------------------------------------------------Boot Media: internal (da0)

Copyright 2011, Juniper Networks, Inc.

Chapter 4: Verifying Software Installation

Active Partition: da0s1a

Backup Partition: da0s2a

Currently booted from: active (da0s1a)

Partitions information:
Partition Size
Mountpoint
s1a
184M
/
s2a
184M
altroot
s3d
369M
/var/tmp
s3e
123M
/var
s4d
62M
/config
s4e
unused (backup config)

Verifying the Junos OS Version in Each Root Partition

Purpose

Action

Each switch contains two root partitions. We recommend that you copy the same Junos
OS version in each partition when you upgrade. In Junos OS Release 10.4R2 and earlier,
you might choose to have different Junos OS release versions in each partition. You might
have different versions during a software upgrade and before you have finished verifying
the new software installation. To enable a smooth reboot if corruption is found in the
primary root file system, ensure that the identical Junos OS images are in each root
partition. For Release 10.4R2 and earlier, you must manually reboot the switch from the
backup root partition. However, for Release 10.4R3 and later, the switch reboots
automatically from the backup root partition if it fails to reboot from the active partition.
Verify whether both root partitions contain the same image by using the following
commands:
user@switch> show system snapshot media internal slice 1
Information for snapshot on internal (da0s1)
Creation date: Jan 21 05:48:34 2011
JUNOS version on snapshot:
jbase : 10.4I20110121_0509_hbRPSRLI15184421081
jcrypto-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jdocs-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jkernel-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jroute-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jswitch-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jweb-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jpfe-ex42x: 10.4I20110121_0509_hbRPSRLI15184421081
user@switch# run show system snapshot media internal slice 2
Information for snapshot on internal (da0s2)
Creation date: Jan 21 05:47:54 2011
JUNOS version on snapshot:
jbase : 10.4I20110121_0509_hbRPSRLI15184421081
jcrypto-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jdocs-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jkernel-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jroute-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jswitch-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jweb-ex: 10.4I20110121_0509_hbRPSRLI15184421081
jpfe-ex42x: 10.4I20110121_0509_hbRPSRLI15184421081

Related
Documentation

Upgrading EX Series Switches to Support Resilient Dual-Root Partitions

Copyright 2011, Juniper Networks, Inc.

39

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Verifying Junos OS and Boot Loader Software Versions on an EX Series Switch on

page 36

Troubleshooting Software Installation on page 43

Troubleshooting a Switch That Has Booted from the Backup Junos OS Image on
page 46

Understanding Resilient Dual-Root Partitions on Switches on page 10

Resilient Dual-Root Partitions Frequently Asked Questions on page 47

Monitoring Licenses

Monitoring Licenses for the EX Series Switch on page 40

Monitoring Licenses for the EX Series Switch

To enable and use some Junos OS features on the EX Series switch, you must purchase,
install, and manage the appropriate software licenses. Each switch requires one license.
For a Virtual Chassis deployment, two licenses are recommended for redundancy.
To monitor your installed licenses, perform the following tasks:

Displaying Installed Licenses and License Usage Details on page 40

Displaying Installed License Keys on page 41

Displaying Installed Licenses and License Usage Details

Purpose

Verify that the expected license is installed and active on the switch and fully covers the
switch configuration.

Action

From the CLI, enter the show system license command. (To display only the License usage
list, enter the show system license usage command. To display only the Licenses installed
output, enter show system license installed.)
user@switch> show system license
License usage:
Licenses

Licenses

Licenses

used

installed

needed

bgp

permanent

isis

permanent

ospf3

permanent

ripng

permanent

mpls

permanent

Feature name

40

Expiry

Copyright 2011, Juniper Networks, Inc.

Chapter 4: Verifying Software Installation

Licenses installed:
License identifier: JUNOS204558
License version: 2
Valid for device: BN0208380000
Features:
exseries - Licensed routing protocols in ex-series
permanent

Meaning

The output shows the license or licenses (for Virtual Chassis deployments) installed on
the switch and license usage. Verify the following information:

If a feature that requires a license is configured (used), a license is installed on the

switch. The Licenses needed column must show that no licenses are required.

The appropriate number of licenses is installed. Each switch requires one license. For
a Virtual Chassis deployment, two licenses are recommended for redundancy.

The expected license is installed.

Displaying Installed License Keys

Purpose
Action

Verify that the expected license keys are installed on the switch.
From the CLI, enter the show system license keys command.
user@switch> show system license keys
JUNOS204558 aeaqea qmijhd amrqha ztfmbu gqzama uqceds
ra32zr lsevik ftvjed o4jy5u fynzzj mgviyl
kgioyf ardb5g sj7wnf rsdked wbjf5a sg

Meaning

Related
Documentation

The output shows the license key or keys (for Virtual Chassis deployments) installed on
the switch. Verify that each expected license key is present.

Managing Licenses for the EX Series Switch (CLI Procedure) on page 31

Managing Licenses for the EX Series Switch (J-Web Procedure) on page 33

Understanding Software Licenses for EX Series Switches on page 12

Copyright 2011, Juniper Networks, Inc.

41

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

42

Copyright 2011, Juniper Networks, Inc.

CHAPTER 5

Troubleshooting Software Installation

Troubleshooting Software Installation on page 43

Troubleshooting a Switch That Has Booted from the Backup Junos OS Image on page 46

Resilient Dual-Root Partitions Frequently Asked Questions on page 47

Troubleshooting Software Installation

This topic describes troubleshooting issues with software installations on EX Series
switches.

Recovering from a Failed Software Upgrade on an EX Series Switch on page 43

Rebooting from the Inactive Partition on page 44

Freeing Disk Space for Software Installation on page 45

Installation from the Boot Loader Generates cannot open package Error on page 45

Recovering from a Failed Software Upgrade on an EX Series Switch

Problem

If Junos OS loads but the CLI is not working, or if the switch has no software installed,
use this recovery installation procedure to install Junos OS.

Solution

If there is already a Junos OS image on the system, you can either install the new Junos
OS package in a separate partition and have both Junos OS images remain on the system,
or you can wipe the disk clean before the new installation proceeds.
If there is no Junos OS image on the system, follow the instructions in Booting an EX
Series Switch Using a Software Package Stored on a USB Flash Drive on page 28 to get
an image on the system and boot the switch.
To perform a recovery installation:
1.

Power on the switch. The loader script starts.

After the message Loading /boot/defaults/loader.conf displays, you are prompted
with:
Hit [Enter] to boot immediately, or space bar for command prompt.

2. Press the space bar to enter the manual loader. The loader> prompt displays.
3. Enter the following command:

Copyright 2011, Juniper Networks, Inc.

43

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

loader> install [ format] [ external] source

where:

formatUse this option to wipe the installation media before installing the software

package. If you do not include this option, the system installs the new Junos OS
package in a different partition from the partition used by the most recently installed
Junos OS package.

externalUse this option to install the software package on an external medium.

sourceRepresents the name and location of the Junos OS package either on a

server on the network or as a file on the USB flash drive:

Network address of the server and the path on the server; for example,
tftp://192.17.1.28/junos/jinstall-ex-4200-9.4R1.5-domestic-signed.tgz

The Junos OS package on a USB device is commonly stored in the root drive as
the only file; for example, file:///jinstall-ex-4200-9.4R1.5-domestic-signed.tgz

The boot process proceeds as normal and ends with a login prompt.

Rebooting from the Inactive Partition

Problem

EX Series switches shipped with Junos OS Release 10.4R2 or earlier have Junos OS loaded
on the system disk in partition 1. The first time you upgrade, the new software package
is installed in partition 2. When you finish the installation and reboot, partition 2 becomes
the active partition. Similarly, subsequent software packages are installed in the inactive
partition, which becomes the active partition when you reboot at the end of the installation
process.
On switches shipped with Release 10.4R3 and later, the same Junos OS image is loaded
in each of the two root partitions, and you should copy the new software image to the
alternate partition each time you upgrade.
If you performed an upgrade and rebooted, the system resets the active partition. You
can use this procedure to manually boot from the inactive partition.

NOTE: If you have completed the installation of the software image but have
not yet rebooted, issue the request system software rollback command to
return to the original software installation package.

Solution

Reboot from the inactive partition:

user@switch> request system reboot slice alternate

44

Copyright 2011, Juniper Networks, Inc.

Chapter 5: Troubleshooting Software Installation

NOTE: If you cannot access the CLI, you can reboot from the inactive partition
using the following procedure from the loader script prompt:
1.

Unload and clear the interrupted boot from the active partition:
loader> unload
loader> unset vfs.root.mountfrom

2. Select the new (inactive) partition to boot from:

loader> set currdev=diskxsy:

where x is either 0 (internal) or 1 (external) and the y indicates the number

of the inactive partition, either 1 or 2.
You must include the colon (:) at the end of this command.
3. Boot Junos OS from the inactive partition:

loader> boot

Freeing Disk Space for Software Installation

Problem

The software installation process requires a certain amount of unused disk space. If there
is not enough space, you might receive an error message such as:
fetch: /var/tmp/incoming-package.tgz: No space left on device

Solution

Identify and delete unnecessary files by using the request system storage cleanup
command.

Installation from the Boot Loader Generates cannot open package Error
Problem

When installing a Junos OS software image from the loader prompt, a cannot open
package error is generated:
loader> install - -format
tftp://10.204.33.248/images/Flash_corr/official/jinstall-ex-4200-10.4I2011012-domestic-signed.tgz
Speed: 1000, full duplex
bootp: no reply
No response for RARP request
net_open: RARP failed
cannot open package (error 5)

Solution

This might be due to the IP address, gateway IP address, netmask address, or server IP
address not being properly set. You can set these values either from the shell or from the
u-boot prompt.
To set these values from the shell:
%
%
%
%

nvram setenv ipaddr 10.204.35.235

nvram setenv netmask 255.255.240.0
nvram setenv gatewayip 10.204.47.254
nvram setenv serverip 10.204.33.248

Copyright 2011, Juniper Networks, Inc.

45

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

To set these values from the u-boot prompt, log in to a console connection, reboot, and
stop at the u-boot prompt (Cntrl+c):
=> setenv ipaddr 10.204.35.235
=> setenv gatewayip 10.204.47.254
=> setenv serverip 10.204.33.248
=> setenv netmask 255.255.240.0
=> saveenv
=> printenv Verify whether variables are set properly or not
=> boot

Related
Documentation

Upgrading EX Series Switches to Support Resilient Dual-Root Partitions

Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure)
on page 18

Upgrading Software on an EX8200 Standalone Switch Using Nonstop Software

Upgrade (CLI Procedure)

Installing Software on EX Series Switches (J-Web Procedure) on page 24

Understanding Software Installation on EX Series Switches on page 5

show system storage partitions (EX Series Switches Only) on page 109

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

The switch boots from the backup root file partition. This event is flagged in two ways:

Upon login through the console or management port, the following warning message
is displayed:
WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE
It is possible that the primary copy of JUNOS failed to boot up
properly, and so this device has booted from the backup copy.
Please re-install JUNOS to recover the primary copy in case
it has been corrupted.

The following alarm message is generated:

user@switch> show chassis alarms
1 alarms currently active
Alarm time
Class
2011-02-17 05:48:49 PST Minor

Solution

Description
Host 0 Boot from backup root

Install a new Junos OS image on the partition that had the corruption, or take a snapshot
(request system snapshot ) of the currently active partition and use it to replace the
image in the backup partition:
user@switch> request system snapshot media internal slice alternate
Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes)
The following filesystems were archived: /

46

Copyright 2011, Juniper Networks, Inc.

Chapter 5: Troubleshooting Software Installation

Related
Documentation

Verifying Junos OS and Boot Loader Software Versions on an EX Series Switch on

page 36

Troubleshooting Software Installation on page 43

show system storage partitions (EX Series Switches Only) on page 109

Resilient Dual-Root Partitions Frequently Asked Questions

This FAQ addresses questions regarding resilient dual-root partitions on EX Series switches
and upgrading to resilient dual-root partition releases. This feature was introduced on
EX Series switches at Junos OS Release 10.4R3. It provides additional resiliency for EX
Series switches.
This FAQ covers the following questions:

How Does Upgrading to Junos OS Release 10.4R3 and Later Differ from Normal
Upgrades? on page 47

What Happens If I Do Not Upgrade Both the Loader Software and Junos OS at the
Same Time? on page 48

Can I Downgrade Junos OS Without Downgrading the Loader Software? on page 48

Can I Upgrade to a Resilient Dual-Root Partition Release by Using the CLI? on page 49

Will I Lose My Configuration During an Upgrade? on page 49

How Long Will the Upgrade Process Take? on page 49

What Happens to My Files If the System Detects a File System Corruption? on page 49

How Will I Be Informed If My Switch Boots from the Alternate Slice Due to Corruption
in the Root File System? on page 50

Can I Use Automatic Software Update and Download to Upgrade to a Resilient

Dual-Root Partition Release? on page 50

Why Is the Message "At least one package installed on this device has limited support"
Displayed When Users Log In to a Switch? on page 51

Where Can I Find Instructions for Upgrading? on page 51

How Does Upgrading to Junos OS Release 10.4R3 and Later Differ from Normal Upgrades?
Upgrading from Junos OS Release 10.4R2 or earlier to Release 10.4R3 or later differs from
other upgrades in these ways:

You must upgrade the loader software in addition to installing the new Junos OS image.

Rebooting after the upgrade reformats the disk from three partitions to four partitions.

The upgrade process and the reboot take longer due to the additional time required
to upgrade the loader software and additional time for the first reboot after the Junos
OS installation (longer than normal because it reformats the disk from three partitions
to four). Also, EX8200 switches require an additional reboot per Routing Engine as
part of the loader software upgrade.

Copyright 2011, Juniper Networks, Inc.

47

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

What Happens If I Do Not Upgrade Both the Loader Software and Junos OS at the Same Time?
You must install a new loader software package if you are upgrading to a release that
supports resilient dual-root partitions (Release 10.4R3 and later) from an earlier release
(Release 10.4R2 and earlier).
If you upgrade to Release 10.4R3 or later from Release 10.4R2 or earlier and do not upgrade
the loader software, the switch will come up and function normally. However, if the switch
encounters a problem and cannot boot from the active root partition, it cannot
transparently boot up from the alternate root partition and you will need to perform a
manual reboot.

Table 9: Combinations of Junos OS Versions and Loader Software Versions

Junos OS Release

Loader Software

Notes

Release 10.4R3 and

later

New loader software

Recommended

For all EX Series switches except EX8200 switches:

U-Boot 1.1.6 (Mar 11 2011 - 04:39:06) 1.0.0

(Contains version 1.0.0 after the timestamp.)

For EX8200 switches:
U-Boot 1.1.6 (Jan 11 2008 - 05:24:35) 3.5.0

(Contains version 3.5.0.)

Release 10.4R2 and
earlier

Old loader software

If you downgrade to Release 10.4R2 or

earlier after having upgraded to the new
loader software version, you do not need
to downgrade the loader software. The
switch will function normally.

Release 10.4R3 and

later

Old loader software

The switch will come up and function

normally. However, in the event that the
switch cannot boot from the active root
partition, it will not transparently boot up
from the alternate root partition.

For all EX Series switches except EX8200 switches:

U-Boot 1.1.6 (Jan 11 2008 - 05:24:35)

(Does not contain a version number after the

timestamp)
For EX8200 switches:
U-Boot 1.1.6 (Jan 11 2008 - 05:24:35) 2.3.0

(Contains a version earlier than 3.5.0.)

Release 10.4R2 and
earlier

New loader software

The switch will come up and function

normally.

NOTE: For EX Series switches except EX8200

switches, in Release 10.4R2 and earlier the version
number after the timestamp (shown in the previous
row) is not displayed, and you cannot verify whether
the old or the new loader software version is installed.

Can I Downgrade Junos OS Without Downgrading the Loader Software?

Yes, when you downgrade from most releases, the new loader software runs seamlessly
with the earlier Junos OS version.

48

Copyright 2011, Juniper Networks, Inc.

Chapter 5: Troubleshooting Software Installation

NOTE: If you downgrade specifically from Release 10.4R3 or Release 11.1R1

to nonresilient dual-root partition release (10.4R2 or earlier), you must disable
the boot-sequencing function. If you do not take this action, the switch will
boot on each subsequent reboot from the alternate root partition rather than
from the active partition.
Disable the boot-sequencing function in one of two ways:

From the shell as the root user:

% nvram setenv boot.btsq.disable 1

From a console connection, reboot and stop at the u-boot prompt (Ctrl+c):
=> setenv boot.btsq.disable 1
=> savenv

If you are downgrading from Release 10.4R4 or from Release 11.1R2 or later
to Release 10.4R2 or earlier, you do not need to disable the boot-sequencing
functionthe software does it automatically.

Can I Upgrade to a Resilient Dual-Root Partition Release by Using the CLI?

Yes, you can perform the entire upgrade to resilient dual-root partitions from the CLI.
You download both the new loader software and Junos OS packages and install them
from the CLI. During the final reboot, the disk is automatically reformatted from three
partitions to four partitions.

Will I Lose My Configuration During an Upgrade?

Configuration files are preserved and restored during the reformatting of the disk. We
recommend that you save your configuration before upgrading because if there is a power
interruption during the installation process, files might be lost.

How Long Will the Upgrade Process Take?

The process of upgrading to a resilient dual-root partition release takes longer than other
upgrades due to the additional step of upgrading the loader software and a longer reboot
time while the disk is reformatted to four partitions during the reboot of the switch that
completes the Junos OS upgrade. The reformat increases the reboot time for EX2200,
EX3200, EX4200, and EX4500 switches by 5 to 10 minutes. For EX8200 switches, the
reboot time increases by 10 to 25 minutes per Routing Engine, and additional reboots are
required.

What Happens to My Files If the System Detects a File System Corruption?

During a reboot, the system checks each file system partition for corruption. Table 10 on
page 50 shows the action the system takes if corruption is detected and the corrective
action that you can take.

Copyright 2011, Juniper Networks, Inc.

49

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Table 10: Actions If Corrupt Files Are Found

Slice 1

Slice 2

Slice 3

s1a

s2a

s3e

s3d

s4d

/var

/var/tmp

/config

(root Junos OS)

(root Junos OS)

Slice 4

If a root directory (/) is corrupted, the

corrupted file system is not mounted
and the switch boots from the
alternate slice.

During early boot, the integrity of /var, /var/tmp, and

/config files is verified. If they are corrupted, the corrupted
slice is reformatted and the file directory in that slice is
lost.

Corrective action: Issue a request

system snapshot command from the
good root directory to the corrupted
slice.

Corrective action: Restore the /var or /config files from

the external backup.

How Will I Be Informed If My Switch Boots from the Alternate Slice Due to Corruption in the
Root File System?
If the switch detects corruption in the primary root file system, it boots from the alternate
root partition. When this occurs, you are notified in two ways:

If you are logged in through the console port or the management port:
WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE
It is possible that the primary copy of JUNOS failed to boot up
properly, and so this device has booted from the backup copy.
Please re-install JUNOS to recover the primary copy in case
it has been corrupted.

The following alarm message is displayed when you issue show chassis alarms:
user@switch> show chassis alarms
1 alarms currently active
Alarm time
Class
2011-02-17 05:48:49 PST Minor

Description
Host 0 Boot from backup root

Can I Use Automatic Software Update and Download to Upgrade to a Resilient Dual-Root
Partition Release?
Automatic software update and automatic software download are both supported with
upgrading to resilient dual-root partition releases. However, after an automatic installation,
you must take the extra step of upgrading the loader software.
Automatic software update is for new members added to a Virtual Chassis that do not
have the same software as the master. Once this feature is configured on the Virtual
Chassis, any new member added with a different software version will be upgraded
automatically.

50

Copyright 2011, Juniper Networks, Inc.

Chapter 5: Troubleshooting Software Installation

Automatic software download uses the DHCP message exchange process to download
and install software packages.

Why Is the Message "At least one package installed on this device has limited support" Displayed
When Users Log In to a Switch?
The following message might be displayed when a user logs in:
Logging to master
..Password:
--- JUNOS 10.4R3.4 built 2011-03-19 22:06:32 UTC
At least one package installed on this device has limited support.
Run 'file show /etc/notices/unsupported.txt' for details.

This message can be safely ignored or you can permanently remove it. It appears because
the jloader package file has been detected, and it only appears when Junos OS is installed
before the loader software is upgraded (required only for EX8200 switches).
You can permanently remove this message by removing the jloader package and rebooting
the system:
user@switch> request system software delete jloader-ex-zzzz
user@switch> request system reboot

Where jloader-ex-zzzz represents the name of the jloader software package for your
platformjloader-ex2200 for an EX2200 switch, jloader-ex3242 for an EX3200 or EX4200
switch, or jloader-ex8200 for an EX8200 switch.

Where Can I Find Instructions for Upgrading?

The procedure for upgrading to a release that supports resilient dual-root partitions (from
a release that does not) is different from the normal upgrade procedure. For instructions
on upgrading to a resilient dual-root partition release, see the Release Notes.
Related
Documentation

Verifying Junos OS and Boot Loader Software Versions on an EX Series Switch on

page 36

Troubleshooting Software Installation on page 43

Troubleshooting a Switch That Has Booted from the Backup Junos OS Image on
page 46

Verifying Junos OS and Boot Loader Software Versions on an EX Series Switch on

page 36

Copyright 2011, Juniper Networks, Inc.

51

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

52

Copyright 2011, Juniper Networks, Inc.

CHAPTER 6

Configuration Statements for Software

Installation

[edit chassis] Configuration Statement Hierarchy on page 53

[edit chassis] Configuration Statement Hierarchy

chassis {
aggregated-devices {
ethernet {
device-count number;
}
}
auto-image-upgrade;
fpc slot {
pic pic-number {
sfpplus {
pic-mode mode;
}
}
power-budget-priority priority;
}
lcd-menu {
fpc slot-number {
menu-item (menu-name | menu-option) {
disable;
}
}
}
nssu {
upgrade-group group-name {
fpcs (slot-number | [list-of-slot-numbers]);
member member-id {
fpcs (slot-number | [list-of-slot-numbers]);
}
}
}
psu {
redundancy {
n-plus-n;
}
}

Copyright 2011, Juniper Networks, Inc.

53

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

redundancy {
graceful-switchover;
}
}

Related
Documentation

Configuring Aggregated Ethernet Interfaces (CLI Procedure)

Upgrading Software Using Automatic Software Download on EX Series Switches on

page 30

Configuring the LCD Panel on EX Series Switches (CLI Procedure)

Configuring Graceful Routing Engine Switchover in an EX3300, EX4200, or EX4500

Virtual Chassis (CLI Procedure)

Configuring Power Supply Redundancy (CLI Procedure)

Configuring the Power Priority of Line Cards (CLI Procedure)

Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade (CLI Procedure)

auto-image-upgrade
Syntax
Hierarchy Level
Release Information
Description

auto-image-upgrade;
[edit chassis]

Statement introduced in Junos OS Release 9.6 for EX Series switches.

Enable automatic software download on an EX Series switch acting as a DHCP client.
The DHCP client EX Series switch compares the software package name in the DHCP
server message to the name of the software package that booted the switch. If the
software packages are different, the DHCP client EX Series switch downloads and installs
the software package specified in the DHCP server message.
Before you upgrade software 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. See the Junos OS System Basics Configuration Guide for information about
using the CLI to configure DHCP services and settings. See Configuring DHCP Services
(J-Web Procedure) for information about using the J-Web interface to configure DHCP
services and settings.

Default
Required Privilege
Level
Related
Documentation

54

Automatic software download is disabled.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Upgrading Software Using Automatic Software Download on EX Series Switches on

page 30

Understanding Software Installation on EX Series Switches on page 5

DHCP Services for EX Series Switches Overview

Copyright 2011, Juniper Networks, Inc.

CHAPTER 7

Operational Commands for Software

Installation

Copyright 2011, Juniper Networks, Inc.

55

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

request system license add

Syntax
Release Information

Description
Options

request system license add (filename | terminal)

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Add a license key.
filenameLicense key from a file or URL. Specify the filename or the URL where the key

is located.
terminalLicense key from the terminal.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

maintenance

Adding New Licenses

request system license add on page 56

When you enter this command, you are provided feedback on the status of your request.

Sample Output
request system license
add

56

user@host> request system license add terminal

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

request system license delete

Syntax

request system license delete license-id

Syntax (QFX Series)

request system license delete license-identifier

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.1 for the QFX Series.

Description
Options

Delete a license key. You can delete only one license at a time.
license-idLicense ID that uniquely identifies a license key.
license-identification(QFX Series) License ID that uniquely identifies a license key.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

maintenance

Deleting a License

request system license delete on page 57

When you enter this command, you are provided feedback on the status of your request.

Sample Output
request system license
delete

user@host> request system license delete G03000002223

Copyright 2011, Juniper Networks, Inc.

57

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

request system license save

Syntax
Release Information

Description
Options

request system license save (filename | terminal)

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Save installed license keys to a file or URL.
filenameLicense key from a file or URL. Specify the filename or the URL where the key

is located.
terminalLicense key from the terminal.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

maintenance

Saving License Keys

request system license save on page 58

When you enter this command, you are provided feedback on the status of your request.

Sample Output
request system license
save

58

user@host> request system license save ftp://user@host/license.conf

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

request system reboot

Syntax

request system reboot

<other-routing-engine>
<at time>
<in minutes>
<media (compact-flash | disk | removable-compact-flash | usb)>
<message "text">

Syntax (EX Series

Switch)

request system reboot

<all-members>
<at time>
<in minutes>
<local>
<media (external | internal)>
<member member-id>
<message "text">
<other-routing-engine>
<slice slice>

Syntax (TX Matrix

Router)

request system reboot

<all-chassis | all-lcc | lcc number | scc>
<other-routing-engine>
<at time>
<in minutes>
<media (compact-flash | disk)>
<message "text">

Syntax (TX Matrix Plus

Router)

Syntax (MX Series

Router)

Release Information

Description

request system reboot

<all-chassis | all-lcc | lcc number | sfc number>
<other-routing-engine>
<partition (1 | 2 | alternate)>
<at time>
<in minutes>
<media (compact-flash | disk)>
<message "text">
request system reboot
<all-members>
<at time>
<in minutes>
<local>
<media (external | internal)>
<member member-id>
<message "text">
<other-routing-engine>

Command introduced before Junos OS Release 7.4.

other-routing-engine option added in Junos OS Release 8.0.
Command introduced in Junos OS Release 9.0 for EX Series switches.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Reboot the software.

Copyright 2011, Juniper Networks, Inc.

59

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Options

noneReboot the software immediately.

all-chassis(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,

reboot all T640 routers (or line-card chassis) connected to the TX Matrix router. On
a TX Matrix Plus router, reboot all T1600 routers (or line-card chassis) connected
to the TX Matrix Plus router.
all-lcc(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,

reboot all T640 routers (or line-card chassis) connected to the TX Matrix router. On
a TX Matrix Plus router, reboot all T1600 routers (or line-card chassis) connected
to the TX Matrix Plus router.
all-members(EX4200 switches and MX Series routers only) (Optional) Reboot the

software on all members of the Virtual Chassis configuration.

at time(Optional) Time at which to reboot the software, specified in one of the following

ways:

nowStop or reboot the software immediately. This is the default.

+minutesNumber of minutes from now to reboot the software.

yymmddhhmmAbsolute time at which to reboot the software, specified as year,

month, day, hour, and minute.

hh:mmAbsolute time on the current day at which to stop the software, specified

in 24-hour time.
in minutes(Optional) Number of minutes from now to reboot the software. This option

is an alias for the at +minutes option.

lcc number(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,

the number of a T640 router that is connected to the TX Matrix router. On a TX Matrix
Plus router, the number of a T1600 router that is connected to the TX Matrix Plus
router. Replace number with a value from 0 through 3.
local(EX4200 switches and MX Series routers only) (Optional) Reboot the software

on the local Virtual Chassis member.

media (compact-flash | disk | removable-compact-flash | usb)(Optional) Boot medium

for next boot. (The options removable-compact-flash and usb pertain to the J Series
routers only.)
media (external | internal)(EX Series switches and MX Series routers only) (Optional)

Reboot the boot media:

externalReboot the external mass storage device.

internalReboot the internal flash device.

member member-id(EX4200 switches and MX Series routers only) (Optional) Reboot

the software on the specified member of the Virtual Chassis configuration. For
EX4200 switches, replace member-id with a value from 0 through 9. For an MX Series
Virtual Chassis, replace member-id with a value of 0 or 1.

60

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

message "text"(Optional) Message to display to all system users before stopping or

rebooting the software.

other-routing-engine(Optional) Reboot the other Routing Engine from which the

command is issued. For example, if you issue the command from the master Routing
Engine, the backup Routing Engine is rebooted. Similarly, if you issue the command
from the backup Routing Engine, the master Routing Engine is rebooted.
partition(TX Matrix Plus routers only) (Optional) Reboot using the specified partition

on the boot media. This option has the following suboptions:

1Reboot from partition 1.

2Reboot from partition 2.

alternateReboot from the alternate partition.

scc(TX Matrix routers only) (Optional) Reboot the Routing Engine on the TX Matrix

router (or switch-card chassis). If you issue the command from re0, re0 is rebooted.
If you issue the command from re1, re1 is rebooted.
sfc number(TX Matrix Plus routers only) (Optional) Reboot the Routing Engine on the

TX Matrix Plus router (or switch-fabric chassis). If you issue the command from re0,
re0 is rebooted. If you issue the command from re1, re1 is rebooted. Replace number
with 0.
slice slice(EX Series switches only) (Optional) Reboot a partition on the boot media.

This option has the following suboptions:

Additional Information

1Power off partition 1.

2Power off partition 2.

alternateReboot from the alternate partition.

Reboot requests are recorded in the system log files, which you can view with the show
log command (see show log). Also, the names of any running processes that are scheduled
to be shut down are changed. You can view the process names with the show system
processes command (see show system processes).
On a TX Matrix or TX Matrix Plus router, if you issue the request system reboot command
on the master Routing Engine, all the master Routing Engines connected to the routing
matrix are rebooted. If you issue this command on the backup Routing Engine, all the
backup Routing Engines connected to the routing matrix are rebooted.

NOTE: To reboot a router that has two Routing Engines, reboot the backup
Routing Engine (if you have upgraded it) first, and then reboot the master
Routing Engine.

Copyright 2011, Juniper Networks, Inc.

61

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

maintenance

clear system reboot

request system halt

request system reboot

Rebooting and Halting a QFX Series Product

request system reboot on page 62

request system reboot (at 2300) on page 62
request system reboot (in 2 Hours) on page 62
request system reboot (Immediately) on page 62
request system reboot (at 1:20 AM) on page 62
When you enter this command, you are provided feedback on the status of your request.

Sample Output
request system reboot

user@host> request system reboot

Reboot the system ? [yes,no] (no)

request system reboot

(at 2300)

user@host> request system reboot at 2300 message ?Maintenance time!?

Reboot the system ? [yes,no] (no) yes
shutdown: [pid 186]
*** System shutdown message from [email protected] ***
System going down at 23:00

request system reboot

(in 2 Hours)

The following example, which assumes that the time is 5 PM (17:00), illustrates
three different ways to request the system to reboot in two hours:
user@host> request system reboot at +120
user@host> request system reboot in 120
user@host> request system reboot at 19:00

request system reboot

(Immediately)

user@host> request system reboot at now

request system reboot

(at 1:20 AM)

To reboot the system at 1:20 AM, enter the following command. Because 1:20 AM is
the next day, you must specify the absolute time.
user@host> request system reboot at 06060120
request system reboot at 120
Reboot the system at 120? [yes,no] (no) yes

62

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

request system reboot

Syntax

Release Information

Description

request system reboot

<all-members | local | member member-id>
<at time>
<in minutes>
<media (external | internal)>
<message text>
<slice (1 | 2 | alternate)>

Command introduced in Junos OS Release 9.0 for EX Series switches.

Option partition changed to slice in Junos OS Release 10.0 for EX Series switches.
Reboot the Junos OS.
Reboot requests are recorded in the system log files, which you can view with the show
log command. You can view the process names with the show system processes
command.

Options

noneReboots the software immediately.

all-members | local | member member-id(EX4200 switch only) (Optional) Specify which

member of the Virtual Chassis to reboot:

all-membersReboots each switch that is a member of the Virtual Chassis.

localReboots the local switch, meaning the switch you are logged into, only.

member member-idReboots the specified member switch of the Virtual Chassis.

at time(Optional) Time at which to reboot the software, specified in one of the following

ways:

+minutesNumber of minutes from now to reboot the software.

hh:mmAbsolute time on the current day at which to reboot the software, specified

in 24-hour time.

nowStop or reboot the software immediately. This is the default.

yymmddhhmmAbsolute time at which to reboot the software, specified as year,

month, day, hour, and minute.

in minutes(Optional) Number of minutes from now to reboot the software. This option

is an alias for the at +minutes option.

media (external | internal)(Optional) Boot medium for the next boot. The external option

reboots the switch using a software package stored on an external boot source, such
as a USB flash drive. The internal option reboots the switch using a software package
stored in an internal memory source.
message text(Optional) Message to display to all system users before rebooting the

software.

Copyright 2011, Juniper Networks, Inc.

63

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

slice (1 | 2 | alternate)(Optional) Reboot using the specified partition on the boot media.

This option has the following suboptions:

1Reboot from partition 1.

2Reboot from partition 2.

alternateReboot from the alternate partition, which is the partition that did not

boot the switch at the last bootup.

Required Privilege
Level
Related
Documentation
Output Fields

maintenance

clear system reboot

When you enter this command, you are provided feedback on the status of your request.

Sample Output
request system reboot

user@host> request system reboot

Reboot the system ? [yes,no] (no)

request system reboot

(at 2300)

user@host> request system reboot at 2300 message ?Maintenance time!?

Reboot the system ? [yes,no] (no) yes
shutdown: [pid 186]
*** System shutdown message from [email protected] ***
System going down at 23:00

request system reboot

(in 2 Hours)

The following example, which assumes that the time is 5 PM (17:00), illustrates three
different ways to request the system to reboot in two hours:
user@host> request system reboot at +120
user@host> request system reboot in 120
user@host> request system reboot at 19:00

request system reboot

(Immediately)

user@host> request system reboot at now

request system reboot

(at 1:20 AM)

To reboot the system at 1:20 AM, enter the following command. Because 1:20 AM is the
next day, you must specify the absolute time.
user@host> request system reboot at 06060120
request system reboot at 120
Reboot the system at 120? [yes,no] (no) yes

64

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

request system snapshot

Syntax

Syntax (EX Series

Switch)

request system snapshot

<partition>
request system snapshot
<all-members | local | member member-id>
<media type>
<partition>
<re0 | re1 | routing-engine routing-engine-id>
<slice (1 | 2 | alternate)>

Syntax (J Series
Routers)

request system snapshot

<as-primary>
<config-size size>
<data-size size>
<factory>
<media type>
<partition>
<root-size size>
<swap-size size>

Syntax (MX Series

Router)

request system snapshot

<all-members>
<local>
<member member-id>
<partition>

Syntax (TX Matrix

Router)

request system snapshot

<all-chassis | all-lcc | lcc number | scc>
<partition>

Syntax (TX Matrix Plus

Router)

Release Information

Description

request system snapshot

<all-chassis | all-lcc | lcc number | sfc number>
<partition>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 10.0 for EX Series switches.

On the router, back up the currently running and active file system partitions 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 the router's flash drive, and the /altroot and /altconfig file systems are on the router's
hard drive.

On the switch, take a snapshot of the files currently used to run the switchthe
complete contents of the root (/) , /config, and /var directories, which include the
running Junos OS, the active configuration, and log files.

Copyright 2011, Juniper Networks, Inc.

65

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

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.

Options

The specific options available depend upon the router or switch:

noneBack up the currently running software as follows:

On the router, back up the currently running and active file system partitions 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 the router's flash drive, and the /altroot and /altconfig file
systems are on the router's hard drive.

On the switch, take a snapshot of the files currently used to run the switchthe
complete contents of the root file system /, /config directory, and /var directory,
which include the running Junos OS, the active configuration, and log filesand
copy all these files onto an external drive. (If a USB flash drive is not connected,
an error message is displayed.)

all-chassis | all-lcc | lcc number (TX Matrix and TX Matrix Plus router only) (Optional)

all-chassisOn a TX Matrix router, archive data and executable areas for all Routing

Engines in the chassis. On a TX Matrix Plus router, archive data and executable
areas for all Routing Engines in the chassis.

all-lccOn a TX Matrix router, archive data and executable areas for all T640

routers (or line-card chassis) connected to a TX Matrix router. On a TX Matrix Plus

router, archive data and executable areas for all T1600 routers (or line-card chassis)
connected to a TX Matrix Plus router.

lcc numberOn a TX Matrix router, archive data and executable areas for a specific

T640 router (or line-card chassis) that is connected to a TX Matrix router. On a

TX Matrix Plus router, archive data and executable areas for a specific T1600
router (or line-card chassis) that is connected to a TX Matrix Plus router. Replace
number with a value from 0 through 3.
all-members | local | member member-id(EX4200, EX4500, and EX8200 Virtual Chassis

and MX Series routers only) (Optional) Specify where to place the snapshot (archive
data and executable areas) in a Virtual Chassis:

all-membersCreate a snapshot (archive data and executable areas) for all

members of the Virtual Chassis.

localCreate a snapshot (archive data and executable areas) on the member of

the Virtual Chassis that you are currently logged into.

member member-idCreate a snapshot (archive data and executable areas) for

the specified member of the Virtual Chassis.

66

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

as-primary(J Series routers only) (Optional) Create a snapshot that can be used to

replace the medium in the primary compact flash drive. This option can be used on
the removable compact flash only. The option copies the default files that were
loaded on the primary compact flash drive when it was shipped from the factory,
plus the rescue configuration if one has been set. This option is useful if you have
multiple routers and want to use the same software and configuration on each router.
After a boot device is created as a primary compact flash drive, it can operate in only
a primary compact flash drive slot. This option causes the boot medium to be
partitioned.
config-size size(J Series routers only) (Optional) Specify the size of the config partition,

in megabytes. The default value is 10 percent of physical memory on the boot

partition. The config partition is mounted on /config, and the configuration files are
stored in this partition. This option causes the boot medium to be partitioned.
data-size size(J Series routers only) (Optional) Specify the size of the data partition, in

megabytes. The default value is 0 MB. The data partition is mounted on /data. This
space is not used by the router, and can be used for extra storage. This option causes
the boot medium to be partitioned.
factory(J Series routers only) (Optional) Copy only default files that were loaded on

the primary compact flash drive when it was shipped from the factory, plus the rescue
configuration if one has been set. After the boot medium is created with the factory
option, it can operate in only the primary compact flash drive.
media type(J Series routers and EX Series switches only)(Optional) Specify the boot

device the software is copied to:

compact-flashCopy software to the primary compact flash drive.

external(Switches only) Copy software to an external mass storage device, such

as a USB flash drive. If the media option is not specified, this is the default. If a USB
drive is not connected, the switch displays an error message.

internal(Switches only) Copy software to an internal flash drive.

removable-compact-flashCopy software to the removable compact flash drive.

usb(M320, T640, MX960, and J Series routers only) Copy software to the device

connected to the USB port.

partition(Optional) Repartition the flash drive before a snapshot occurs. If the partition

table on the flash drive is corrupted, the request system snapshot command fails
and reports errors. The partition option is only supported for restoring the software
image from the hard drive to the flash drive.
(Routers only) You cannot issue the request system snapshot command when you
enable flash disk mirroring. We recommend that you disable flash disk mirroring
when you upgrade or downgrade the software. For more information, see the Junos
OS System Basics Configuration Guide.
re0 | re1 | routing-engine routing-engine-id(EX8200 switch only) Specify where to place

the snapshot in a redundant Routing Engine configuration.

Copyright 2011, Juniper Networks, Inc.

67

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

re0Create a snapshot on Routing Engine 0.

re1Create a snapshot on Routing Engine 1.

routing-engine routing-engine-idCreate a snapshot on the specified Routing

Engine.
root-size size(J Series routers only) (Optional) Specify the size of the root partition, in

megabytes. The default value is one-third of the physical memory minus the config,
data, and swap partitions. The root partition is mounted on / and does not include
configuration files. This option causes the boot medium to be partitioned.
slice (1 | 2 |alternate)(EX Series switches only) (Optional) Take a snapshot of the active

root partition and copy it to the selected slice on the boot media.
scc(TX Matrix router only) (Optional) Archive data and executable areas for a TX Matrix

router (or switch-card chassis).

sfc number(TX Matrix Plus router only) (Optional) Archive data and executable areas

for a TX Matrix Plus router (or switch-fabric chassis). Replace number with 0.
swap-size size(J Series router only) (Optional) Specify the size of the swap partition,

in megabytes. The default value is one-third of the physical memory on a boot

medium larger than 128 MB, or 0 MB on a smaller boot device. The swap partition is
used for swap files and software failure memory snapshots. Software failure memory
snapshots are saved to the boot medium only if it is specified as the dump device in
the system dump-device configuration hierarchy. This option causes the boot medium
to be partitioned.
Additional Information

(Routers only) Before upgrading the software on the router, when you have a known
stable system, issue the request system snapshot command to back up the software,
including the configuration, to the /altroot and /altconfig file systems. After you have
upgraded the software on the router and are satisfied that the new packages are
successfully installed and running, issue the request system snapshot command again
to back up the new software to the /altroot and /altconfig file systems.

(Routers only) You cannot issue the request system snapshot command when you
enable flash disk mirroring. We recommend that you disable flash disk mirroring when
you upgrade or downgrade the software. For more information, see the Junos OS System
Basics Configuration Guide

Required Privilege
Level

68

(TX Matrix and TX Matric Plus router only) On a routing matrix, if you issue the request
system snapshot command on the master Routing Engine, all the master Routing
Engines connected to the routing matrix are backed up. If you issue this command on
the backup Routing Engine, all the backup Routing Engines connected to the routing
matrix are backed up.

maintenance

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

Related
Documentation
List of Sample Output

Output Fields

show system snapshot on page 106

request system snapshot (Routers) on page 69

request system snapshot (EX Series Switches) on page 69
request system snapshot (When Partition Flag Is On) on page 69
request system snapshot (When Mirroring Is Enabled) on page 69
request system snapshot all-lcc (Routing Matrix) on page 69
request system snapshot all-members (Virtual Chassis) on page 70
When you enter this command, you are provided feedback on the status of your request.

Sample Output
request system
snapshot (Routers)

user@host> request system snapshot

umount: /altroot: not currently mounted
Copying / to /altroot.. (this may take a few minutes)
umount: /altconfig: not currently mounted
Copying /config to /altconfig.. (this may take a few minutes)
The following filesystems were archived: / /config

request system
snapshot (EX Series
Switches)

user@switch> request system snapshot

fpc0:
-------------------------------------------------------------------------Verifying compatibility of destination media partitions...
Running newfs (345MB) on external media / partition ...
Running newfs (235MB) on external media /config partition ...
The following filesystems were archived: / /config /var

request system
snapshot (When
Partition Flag Is On)

user@host> request system snapshot partition

Performing preliminary partition checks ...
Partitioning ad0 ...
umount: /altroot: not currently mounted
Copying / to /altroot.. (this may take a few minutes)
The following filesystems were archived: / /config

request system
snapshot (When
Mirroring Is Enabled)
request system
snapshot all-lcc
(Routing Matrix)

user@host> request system snapshot

Snapshot is not possible since mirror-flash-on-disk is configured.

user@host> request system snapshot all-lcc

lcc0-re0:
-------------------------------------------------------------------------Copying '/' to '/altroot' .. (this may take a few minutes)
Copying '/config' to '/altconfig' .. (this may take a few minutes)
The following filesystems were archived: / /config
lcc2-re0:
-------------------------------------------------------------------------Copying '/' to '/altroot' .. (this may take a few minutes)
Copying '/config' to '/altconfig' .. (this may take a few minutes)
The following filesystems were archived: / /config

Copyright 2011, Juniper Networks, Inc.

69

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

request system
snapshot all-members
(Virtual Chassis)

user@switch> request system snapshot all-members media internal

fpc0:
-------------------------------------------------------------------------Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes)
The following filesystems were archived: /
fpc1:
-------------------------------------------------------------------------Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes)
The following filesystems were archived: /
fpc2:
-------------------------------------------------------------------------Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes)
The following filesystems were archived: /
fpc3:
-------------------------------------------------------------------------Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes)
The following filesystems were archived: /
fpc4:
-------------------------------------------------------------------------Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes)
The following filesystems were archived: /
fpc5:
-------------------------------------------------------------------------Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes)
The following filesystems were archived: /

70

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

request system software add

Syntax

request system software add package-name

<best-effort-load>
<delay-restart>
<force>
<no-copy>
<no-validate>
<re0 | re1>
<reboot>
<unlink>
<validate>

Syntax (EX Series

Switches)

request system software add package-name

<best-effort-load>
<delay-restart>
<force>
<no-copy>
<no-validate>
<re0 | re1>
<reboot>
<set [package-name package-name]>
<unlink>
<validate>

Syntax (TX Matrix

Router)

request system software add package-name

<best-effort-load>
<delay-restart>
<force>
<lcc number | scc>
<no-copy>
<no-validate>
<re0 | re1>
<reboot>
<unlink>
<validate>

Syntax (TX Matrix Plus

Router)

request system software add package-name

<best-effort-load>
<delay-restart>
<force>
<lcc number | sfc number>
<no-copy>
<no-validate>
<re0 | re1>
<reboot>
<unlink>
<validate>

Syntax (MX Series

Router)

request system software add package-name

<best-effort-load>
<delay-restart>
<force>
<member member-id>

Copyright 2011, Juniper Networks, Inc.

71

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

<no-copy>
<no-validate>
<re0 | re1>
<reboot>
<unlink>
<validate>

Syntax (QFX Series)

request system software add package-name

<best-effort-load>
<component (all | director-group | fabric | node-group-name)
<delay-restart>
<force>
<no-copy>
<no-validate>
<partition>
<reboot>
<unlink>
<validate>

Release Information

Command introduced before Junos OS Release 7.4.

best-effort-load and unlink options added in Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Command introduced in Junos OS Release 11.1 for the QFX Series.
The set [package-name package-name] option added in Junos OS Release 11.1 for EX Series
switches.

Description
Options

Install a software package or bundle on the router or switch.

package-nameLocation from which the software package or bundle is to be installed.

For example:

/var/tmp/package-nameFor a software package or bundle that is being installed

from a local directory on the router or switch.

protocol://hostname/pathname/package-nameFor a software package or bundle

that is to be downloaded and installed from a remote location. Replace protocol

with one of the following:

ftpFile Transfer Protocol.

Use ftp://hostname/pathname/package-name. To specify authentication

credentials, use
ftp://<username>:<password>@hostname/pathname/package-name. To have
the system prompt you for the password, specify prompt in place of the
password. If a password is required, and you do not specify the password or
prompt, an error message is displayed.

httpHypertext Transfer Protocol.

Use http://hostname/pathname/package-name. To specify authentication

credentials, use
http://<username>:<password>@hostname/pathname/package-name. If a
password is required and you omit it, you are prompted for it.

72

scpSecure copy (available only for Canada and U.S. version).

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

Use scp://hostname/pathname/package-name. To specify authentication

credentials, use
scp://<username>:<password>@hostname/pathname/package-name.

NOTE:

The pathname in the protocol is the relative path to the users home
directory on the remote system and not the root directory.

Do not use the scp protocol in the request system software add
command to download and install a software package or bundle from
a remote location. The previous statement does not apply to the
QFabric switch. The software upgrade is handled by the MGD process
which does not support scp.
Use the file copy command to copy the software package or bundle
from the remote location to the /var/tmp directory on the hard disk:
file copy scp://source/package-name /var/tmp

Then install the software package or bundle using the request system
software add command:
request system software add /var/tmp/package-name

On a J Series Services Router, when you install the software from a

remote location, the package is removed at the earliest opportunity in
order to make room for the installation to be completed. If you copy
the software to a local directory on the router and then install the new
package, use the unlink option to achieve the same effect and allow
the installation to be completed.

all (QFabric switches only) (Optional) Install the software package on all of the QFabric

components.
best-effort-load(Optional) Activate a partial load and treat parsing errors as warnings

instead of errors.
component (all | director-group | fabric | node-group-name)(QFabric switches only)

(Optional) Install software package on one or all of the QFabric components.

delay-restart(Optional) Install software package or bundle, but do not restart software

processes.
director-group (QFabric switches only) (Optional) Install software package on the

Director group and Fabric managers.

fabric (QFabric switches only) (Optional) Install software package on the Interconnect

devices and Fabric controls.

force(Optional) Force the addition of the software package or bundle (ignore warnings).

Copyright 2011, Juniper Networks, Inc.

73

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

lcc number (TX Matrix and TX Matrix Plus routers only) (Optional) In a routing matrix

based on the TX Matrix router, install a software package or bundle on a T640 router
(or line-card chassis) that is connected to the TX Matrix router. In a routing matrix
based on the TX Matrix Plus router, install a software package or bundle on a T1600
router (or line-card chassis) that is connected to the TX Matrix Plus router. Replace
number with a value from 0 through 3.
member member-id(MX Series routers only) (Optional) Install a software package on

the specified Virtual Chassis member. Replace member-id with a value of 0 or 1.

partition (QFX3500 switches only) (Optional) Format and repartition the media before

installation.
scc(TX Matrix routers only) (Optional) Install a software package or bundle on a Routing

Engine on a TX Matrix router (or switch-card chassis).

sfc number(TX Matrix Plus routers only) (Optional) Install a software package or bundle

on a Routing Engine on a TX Matrix Plus router (or switch-fabric chassis). Replace

number with 0.
no-copy(Optional) Install a software package or bundle, but do not save copies of

package or bundle files.

no-validate(Optional) When loading a software package or bundle with a different

release, suppress the default behavior of the validate option.

re0 | re1(Optional) On routers that support dual or redundant Routing Engines, load a

software package or bundle on the Routing Engine in slot 0 (re0) or Routing Engine
in slot 1 (re1).
reboot(Optional) After adding the software package or bundle, reboot the system. On

a QFabric switch, the software installation is not complete until you reboot the
component for which you have installed the software.
set [package-name package-name](Mixed EX4200 and EX4500 Virtual Chassis only)

(Optional) Install two software packages-a package for an EX4200 switch and the
same release of the package for an EX4500 switch-to upgrade all member switches
in a mixed EX4200 and EX4500 Virtual Chassis.
unlink(Optional) On J Series Services Routers, this option ensures that the software

package is removed at the earliest opportunity in order to make room for the
installation to be completed. On M Series, T Series, and MX Series routers, use the
unlink option to remove the software package from this directory after a successful
upgrade is completed.
validate(Optional) Validate the software package or bundle against the current

configuration as a prerequisite to adding the software package or bundle. This is the

default behavior when the software package or bundle being added is a different
release.

74

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

Additional Information

NOTE: The request system snapshot command is currently not supported on

the QFX Series. Also, you cannot add or install multiple packages on a QFabric
switch.

Before upgrading the software on the router or switch, when you have a known stable
system, issue the request system snapshot command to back up the software, including
the configuration, to the /altroot and /altconfig file systems. After you have upgraded
the software on the router or switch and are satisfied that the new package or bundle is
successfully installed and running, issue the request system snapshot command again
to back up the new software to the /altroot and /altconfig file systems.
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.
If you are upgrading more than one package at the same time, delete the operating
system package, jkernel, last. Add the operating system package, jkernel, first and the
routing software package, jroute, last. If you are upgrading all packages at once, delete
and add them in the following order:
user@host> request system software add /var/tmp/jbase
user@host> request system software add /var/tmp/jkernel
user@host> request system software add /var/tmp/jpfe
user@host> request system software add /var/tmp/jdocs
user@host> request system software add /var/tmp/jroute
user@host> request system software add /var/tmp/jcrypto

By default, when you issue the request system software add package-name command on
a TX Matrix master Routing Engine, all the T640 master Routing Engines that are
connected to it are upgraded to the same version of software. If you issue the same
command on the TX Matrix backup Routing Engine, all the T640 backup Routing Engines
that are connected to it are upgraded to the same version of software.
Likewise, when you issue the request system software add package-name command on
a TX Matrix Plus master Routing Engine, all the T1600 master Routing Engines that are
connected to it are upgraded to the same version of software. If you issue the same
command on the TX Matrix Plus backup Routing Engine, all the T1600 backup Routing
Engines that are connected to it are upgraded to the same version of software.
Required Privilege
Level
Related
Documentation

maintenance

request system software delete on page 78

request system software rollback on page 81

request system storage cleanup

Upgrading Software on a QFX3500 Switch

Copyright 2011, Juniper Networks, Inc.

75

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

List of Sample Output

request system software add validate on page 76

request system software add (Mixed EX4200 and EX4500 Virtual Chassis) on page 76
request system software add (QFabric Switch) on page 77

Output Fields

When you enter this command, you are provided feedback on the status of your request.

Sample Output
request system
software add validate

user@host> request system software add validate /var/tmp/ jinstall-7.2R1.7-domestic-signed.tgz

Checking compatibility with configuration
Initializing...
Using jbase-7.1R2.2
Using /var/tmp/jinstall-7.2R1.7-domestic-signed.tgz
Verified jinstall-7.2R1.7-domestic.tgz signed by PackageProduction_7_2_0
Using /var/validate/tmp/jinstall-signed/jinstall-7.2R1.7-domestic.tgz
Using /var/validate/tmp/jinstall/jbundle-7.2R1.7-domestic.tgz
Checking jbundle requirements on /
Using /var/validate/tmp/jbundle/jbase-7.2R1.7.tgz
Using /var/validate/tmp/jbundle/jkernel-7.2R1.7.tgz
Using /var/validate/tmp/jbundle/jcrypto-7.2R1.7.tgz
Using /var/validate/tmp/jbundle/jpfe-7.2R1.7.tgz
Using /var/validate/tmp/jbundle/jdocs-7.2R1.7.tgz
Using /var/validate/tmp/jbundle/jroute-7.2R1.7.tgz
Validating against /config/juniper.conf.gz
mgd: commit complete
Validation succeeded
Validating against /config/rescue.conf.gz
mgd: commit complete
Validation succeeded
Installing package '/var/tmp/jinstall-7.2R1.7-domestic-signed.tgz' ...
Verified jinstall-7.2R1.7-domestic.tgz signed by PackageProduction_7_2_0
Adding jinstall...
WARNING:
WARNING:
WARNING:
WARNING:
WARNING:
WARNING:
WARNING:

This package will load JUNOS 7.2R1.7 software.

It will save JUNOS configuration files, and SSH keys
(if configured), but erase all other files and information
stored on this machine. It will attempt to preserve dumps
and log files, but this can not be guaranteed. This is the
pre-installation stage and all the software is loaded when
you reboot the system.

Saving the config files ...

Installing the bootstrap installer ...
WARNING:
WARNING:
WARNING:
WARNING:
WARNING:

A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use the

'request system reboot' command when software installation is
complete. To abort the installation, do not reboot your system,
instead use the 'request system software delete jinstall'
command as soon as this operation completes.

Saving package file in /var/sw/pkg/jinstall-7.2R1.7-domestic-signed.tgz ...

Saving state for rollback ...

Sample Output
request system
software add (Mixed

76

user@switch> request system software add set

[/var/tmp/jinstall-ex-4200-11.1R1.1-domestic-signed.tgz
/var/tmp/jinstall-ex-4500-11.1R1.1-domestic-signed.tgz]

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

EX4200 and EX4500

Virtual Chassis)
request system
software add (QFabric
Switch)

...

user@switch> request system software add /pbdata/packages/jinstall-qfabric-11.3X30.6.rpm

component all reboot
...

Copyright 2011, Juniper Networks, Inc.

77

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

request system software delete

Syntax

request system software delete software-package

<force>

Syntax (TX Matrix

Router)

request system software delete software-package

<force>
<lcc number | scc>

Syntax (TX Matrix Plus

Router)

request system software delete software-package

<force>
<lcc number | sfc number>

Release Information

Description

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Remove a software package or bundle from the router or switch.

CAUTION: Before removing a software package or bundle, make sure that

you have already placed the new software package or bundle that you intend
to load onto the router or switch.

Options

software-packageSoftware package or bundle name. You can delete any or all of the

following software bundles or packages:

jbase(Optional) Junos base software suite

jcrypto(Optional, in domestic version only) Junos security software

jdocs(Optional) Junos online documentation file

jkernel(Optional) Junos kernel software suite

jpfe(Optional) Junos Packet Forwarding Engine support

jroute(Optional) Junos routing software suite

junos(Optional) Junos base software

force(Optional) Ignore warnings and force removal of the software.

lcc number(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,

remove an extension or upgrade package from a specific T640 router (or line-card
chassis) that is connected to the TX Matrix router. On a TX Matrix Plus router, remove
an extension or upgrade package from a specific T1600 router (or line-card chassis)
that is connected to the TX Matrix Plus router. Replace number with a value from 0
through 3.

78

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

scc(TX Matrix routers only) (Optional) Remove an extension or upgrade package from

the TX Matrix router (or switch-card chassis).

sfc number(TX Matrix Plus routers only) (Optional) Remove an extension or upgrade

package from the TX Matrix Plus router (or switch-fabric chassis). Replace number
with 0.
Additional Information

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

Before upgrading the software on the router or switch, when you have a known stable
system, issue the request system snapshot command to back up the software, including
the configuration, to the /altroot and /altconfig file systems. After you have upgraded
the software on the router or switch and are satisfied that the new packages are
successfully installed and running, issue the request system snapshot command again
to back up the new software to the /altroot and /altconfig file systems. 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.
maintenance

request system software add on page 71

request system software rollback on page 81

request system software validate on page 84

request system software delete jdocs on page 79

When you enter this command, you are provided feedback on the status of your request.

Sample Output
request system
software delete jdocs

The following example displays the system software packages before and after the jdocs
package is deleted through the request system software delete command:
user@host> show system software
Information for jbase:
Comment:
JUNOS Base OS Software Suite [7.2R1.7]

Information for jcrypto:

Comment:
JUNOS Crypto Software Suite [7.2R1.7]

Information for jdocs:

Comment:
JUNOS Online Documentation [7.2R1.7]

Information for jkernel:

Copyright 2011, Juniper Networks, Inc.

79

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Comment:
JUNOS Kernel Software Suite [7.2R1.7]
...

user@host> request system software delete jdocs

Removing package 'jdocs' ...

user@host> show system software

Information for jbase:
Comment:
JUNOS Base OS Software Suite [7.2R1.7]

Information for jcrypto:

Comment:
JUNOS Crypto Software Suite [7.2R1.7]

Information for jkernel:

Comment:
JUNOS Kernel Software Suite [7.2R1.7]
...

80

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

request system software rollback

Syntax

request system software rollback

Syntax (EX Series

Switch)

request system software rollback

<all-members>
<local>
<member member-id>

Syntax (TX Matrix

Router)

request system software rollback

<lcc number | scc>

Syntax (TX Matrix Plus

Router)

request system software rollback

<lcc number | sfc number>

Syntax (MX Series

Router)

request system software rollback

<all-members>
<local>
<member member-id>

Release Information

Description

Options

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Revert to the software that was loaded at the last successful request system software
add command.
noneRevert to the set of software as of the last successful request system software
add.

all-members(EX4200 switches and MX Series routers only) (Optional) Attempt to roll

back to the previous set of packages on all members of the Virtual Chassis
configuration.
lcc number(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,

attempt to roll back to the previous set of packages on a T640 router (or line-card
chassis) connected to the TX Matrix router. On a TX Matrix Plus router, attempt to
roll back to the previous set of packages on a T1600 router (or line-card chassis)
connected to the TX Matrix Plus router. Replace number with a value from 0 through
3.
local(EX4200 switches and MX Series routers only) (Optional) Attempt to roll back

to the previous set of packages on the local Virtual Chassis member.

member member-id(EX4200 switches and MX Series routers only) (Optional) Attempt

to roll back to the previous set of packages on the specified member of the Virtual
Chassis configuration. For EX4200 switches, replace member-id with a value from
0 through 9. For an MX Series Virtual Chassis, replace member-id with a value of 0
or 1.

Copyright 2011, Juniper Networks, Inc.

81

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

scc(TX Matrix routers only) (Optional) Attempt to roll back to the previous set of

packages on the TX Matrix router (or switch-card chassis).

sfc number(TX Matrix Plus routers only) (Optional) Attempt to roll back to the previous

set of packages on the TX Matrix Plus router (or switch-fabric chassis). Replace
number with 0.
Additional Information

On the J Series router, you can use this command to roll back to a previous software
package when the current upgrade has been successful or has failed. On M Series and
T Series routers, use this command only to recover from a failed software upgradeyou
cannot issue this command to return to the previously installed software after using a
jinstall package. To return to the previously installed software, use the corresponding
jinstall package.
A software rollback fails if any required package (or a jbundle package containing the
required package) cannot be found in /var/sw/pkg.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

82

maintenance

request system software abort

request system software add on page 71

request system software delete on page 78

request system software validate on page 84

request system configuration rescue delete

request system configuration rescue save

request system software rollback on page 83

When you enter this command, you are provided feedback on the status of your request.

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

Sample Output
request system
software rollback

user@host> request system software rollback

Verified SHA1 checksum of ./jbase-7.2R1.7.tgz
Verified SHA1 checksum of ./jdocs-7.2R1.7.tgz
Verified SHA1 checksum of ./jroute-7.2R1.7.tgz
Installing package './jbase-7.2R1.7.tgz' ...
Available space: 35495 require: 7335
Installing package './jdocs-7.2R1.7.tgz' ...
Available space: 35339 require: 3497
Installing package './jroute-7.2R1.7.tgz' ...
Available space: 35238 require: 6976
NOTICE: uncommitted changes have been saved in
/var/db/config/juniper.conf.pre-install
Reloading /config/juniper.conf.gz ...
Activating /config/juniper.conf.gz ...
mgd: commit complete
Restarting mgd ...
Restarting aprobed ...
Restarting apsd ...
Restarting cosd ...
Restarting fsad ...
Restarting fud ...
Restarting gcdrd ...
Restarting ilmid ...
Restarting irsd ...
Restarting l2tpd ...
Restarting mib2d ...
Restarting nasd ...
Restarting pppoed ...
Restarting rdd ...
Restarting rmopd ...
Restarting rtspd ...
Restarting sampled ...
Restarting serviced ...
Restarting snmpd ...
Restarting spd ...
Restarting vrrpd ...
WARNING: cli has been replaced by an updated version:
CLI release 7.2R1.7 built by builder on 2005-04-22 02:03:44 UTC
Restart cli using the new version ? [yes,no] (yes) yes
Restarting cli ...
user@host

Copyright 2011, Juniper Networks, Inc.

83

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

request system software validate

Syntax

request system software validate package-name

Syntax (EX Series

Switch)

request system software validate

<member member-id>

Syntax (TX Matrix

Router)

request system software validate package-name

<lcc number | scc>

Syntax (TX Matrix Plus

Router)

request system software validate package-name

<lcc number | sfc number>

Syntax (MX Series

Router)

request system software validate package-name

<member member-id>

Release Information

Description
Options

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Validate candidate software against the current configuration of the router or switch.
lcc number(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,

validate the software bundle or package on a specific T640 router (or line-card
chassis) that is connected to the TX Matrix router. On a TX Matrix Plus router, validate
the software bundle or package on a specific T1600 router (or line-card chassis)
that is connected to the TX Matrix Plus router. Replace number with a value from 0
through 3.
member member-id(EX4200 switches and MX Series routers only) (Optional) Validate

the software bundle or package on the specified member of the Virtual Chassis
configuration. For EX4200 switches, replace member-id with a value from 0 through
9. For an MX Series Virtual Chassis, replace member-id with a value of 0 or 1.
package-nameName of the software bundle or package to test.
scc(TX Matrix routers only) (Optional) Validate the software bundle or package for

the TX Matrix router (or switch-card chassis).

sfc number(TX Matrix Plus routers only) (Optional) Validate the software bundle or

package for the TX Matrix Plus router (or switch-fabric chassis).

Additional Information

84

By default, when you issue the request system software validate command on a TX Matrix
master Routing Engine, all the T640 master Routing Engines that are connected to it are
validated. If you issue the same command on the TX Matrix backup Routing Engine, all
the T640 backup Routing Engines that are connected to it are upgraded to the same
version of software.

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

Likewise, if you issue the request system software validate command on a TX Matrix Plus
master Routing Engine, all the T1600 master Routing Engines that are connected to it
are validated. If you issue the same command on a TX Matrix Plus backup Routing Engine,
all the T1600 backup Routing Engines that are connected to it are upgraded to the same
version of software.
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

maintenance

request system software abort

request system software add on page 71

request system software delete on page 78

request system software rollback on page 81

request system software validate (Successful Case) on page 86

request system software validate (Failure Case) on page 86
When you enter this command, you are provided feedback on the status of your request.

Copyright 2011, Juniper Networks, Inc.

85

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Sample Output
request system
software validate
(Successful Case)

user@host> request system software validate /var/sw/pkg/jbundle-5.3I20020124_0520_sjg.tgz

Checking compatibility with configuration
Initializing...
Using /packages/jbase-5.3I20020122_1901_sjg
Using /var/sw/pkg/jbundle-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jbase-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jkernel-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jcrypto-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jpfe-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jdocs-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jroute-5.3I20020124_0520_sjg.tgz
Validating against /config/juniper.conf.gz
mgd: commit complete
WARNING: cli has been replaced by an updated version:
CLI release 5.3I0 built by sjg on 2002-01-24 05:23:53 UTC
Restart cli using the new version ? [yes,no] (yes)

request system
software validate
(Failure Case)

user@host> request system software validate 6.3/

Pushing bundle to lcc0-re0
error: Failed to transfer package to lcc0-re0

user@host> request system software validate test

Pushing bundle to lcc0-re0
Pushing bundle to lcc2-re0
lcc0-re0:
gzip: stdin: not in gzip format
tar: child returned status 1
ERROR: Not a valid package: /var/tmp/test

86

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

request system software validate

Syntax

request system software validate package-name

Syntax (EX Series

Switch)

request system software validate

<member member-id>

Syntax (TX Matrix

Router)

request system software validate package-name

<lcc number | scc>

Syntax (TX Matrix Plus

Router)

request system software validate package-name

<lcc number | sfc number>

Syntax (MX Series

Router)

request system software validate package-name

<member member-id>

Release Information

Description
Options

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Validate candidate software against the current configuration of the router or switch.
lcc number(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,

validate the software bundle or package on a specific T640 router (or line-card
chassis) that is connected to the TX Matrix router. On a TX Matrix Plus router, validate
the software bundle or package on a specific T1600 router (or line-card chassis)
that is connected to the TX Matrix Plus router. Replace number with a value from 0
through 3.
member member-id(EX4200 switches and MX Series routers only) (Optional) Validate

the software bundle or package on the specified member of the Virtual Chassis
configuration. For EX4200 switches, replace member-id with a value from 0 through
9. For an MX Series Virtual Chassis, replace member-id with a value of 0 or 1.
package-nameName of the software bundle or package to test.
scc(TX Matrix routers only) (Optional) Validate the software bundle or package for

the TX Matrix router (or switch-card chassis).

sfc number(TX Matrix Plus routers only) (Optional) Validate the software bundle or

package for the TX Matrix Plus router (or switch-fabric chassis).

Additional Information

By default, when you issue the request system software validate command on a TX Matrix
master Routing Engine, all the T640 master Routing Engines that are connected to it are
validated. If you issue the same command on the TX Matrix backup Routing Engine, all
the T640 backup Routing Engines that are connected to it are upgraded to the same
version of software.

Copyright 2011, Juniper Networks, Inc.

87

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Likewise, if you issue the request system software validate command on a TX Matrix Plus
master Routing Engine, all the T1600 master Routing Engines that are connected to it
are validated. If you issue the same command on a TX Matrix Plus backup Routing Engine,
all the T1600 backup Routing Engines that are connected to it are upgraded to the same
version of software.
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

88

maintenance

request system software abort

request system software add on page 71

request system software delete on page 78

request system software rollback on page 81

request system software validate (Successful Case) on page 89

request system software validate (Failure Case) on page 89
When you enter this command, you are provided feedback on the status of your request.

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

Sample Output
request system
software validate
(Successful Case)

user@host> request system software validate /var/sw/pkg/jbundle-5.3I20020124_0520_sjg.tgz

Checking compatibility with configuration
Initializing...
Using /packages/jbase-5.3I20020122_1901_sjg
Using /var/sw/pkg/jbundle-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jbase-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jkernel-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jcrypto-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jpfe-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jdocs-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jroute-5.3I20020124_0520_sjg.tgz
Validating against /config/juniper.conf.gz
mgd: commit complete
WARNING: cli has been replaced by an updated version:
CLI release 5.3I0 built by sjg on 2002-01-24 05:23:53 UTC
Restart cli using the new version ? [yes,no] (yes)

request system
software validate
(Failure Case)

user@host> request system software validate 6.3/

Pushing bundle to lcc0-re0
error: Failed to transfer package to lcc0-re0

user@host> request system software validate test

Pushing bundle to lcc0-re0
Pushing bundle to lcc2-re0
lcc0-re0:
gzip: stdin: not in gzip format
tar: child returned status 1
ERROR: Not a valid package: /var/tmp/test

Copyright 2011, Juniper Networks, Inc.

89

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

request system zeroize

Syntax

Release Information

Description

request system zeroize

<media>

Command introduced in Junos OS Release 11.2 for EX Series switches.

Option media added in Junos OS Release 11.4 for EX Series switches.
Remove all configuration information on the Routing Engines and reset all key values.
The command removes all data files, including customized configuration and log files,
by unlinking the files from their directories.
To completely erase user-created data so that it is unrecoverable, use the media option.

CAUTION: Before issuing this command, use the request system snapshot
command to back up the files currently used to run the switch to a secondary
device.

This command reboots the switch and sets it to the factory default configuration. After
the reboot, you cannot access the switch through the management Ethernet interface.
Log in through the console as root and start the Junos OS command-line interface (CLI)
by typing cli at the prompt.
Options

media(Optional) Erase all user-created files from the system including all plain-text

passwords, secrets, and private keys for SSH, local encryption, local authentication,
IPsec, RADIUS, TACACS+, and Simple Network Management Protocol (SNMP).
Instead of simply removing the user-created files, the media option erases the files
completely from the system and replaces all user-created data with zeros. Because
it scrubs the system more thoroughly and reboots the switch twice instead of once,
the request system zeroize media operation is more time-consuming than request
system zeroize and might require 10 minutes, for example.
Required Privilege
Level
Related
Documentation

List of Sample Output

maintenance

Reverting to the Default Factory Configuration for the EX Series Switch

Reverting to the Rescue Configuration for the EX Series Switch

request system zeroize on page 90

request system zeroize media on page 91

Sample Output
request system zeroize

90

user@switch> request system zeroize

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

warning: System will be rebooted and may not boot without configuration
Erase all data, including configuration and log files? [yes,no] (no) yes
0 1 1 0 0 0 done
syncing disks... All buffers synced.
Uptime: 5d19h20m26s
recorded reboot as normal shutdown
Rebooting...
U-Boot 1.1.6 (Mar 11 2011 - 04:39:06)
Board:
EPLD:
DRAM:
FLASH:

EX4200-24T 2.11
Version 6.0 (0x85)
Initializing (1024 MB)
8 MB

Firmware Version: --- 01.00.00 --USB:

scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
ELF file is 32 bit
Consoles: U-Boot console
FreeBSD/PowerPC U-Boot bootstrap loader, Revision 2.4
([email protected], Fri Mar 11 03:03:36 UTC 2011)
Memory: 1024MB
bootsequencing is enabled
bootsuccess is set
new boot device = disk0s1:
Loading /boot/defaults/loader.conf
/kernel data=0x915c84+0xa1260 syms=[0x4+0x7cbd0+0x4+0xb1c19]

Hit [Enter] to boot immediately, or space bar for command prompt.

Booting [/kernel]...
Kernel entry at 0x800000e0 ...
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1996-2011, Juniper Networks, Inc.
All rights reserved.
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
JUNOS 11.1R1.8 #0: 2011-03-09 20:14:25 UTC
[email protected]:/volume/build/junos/11.1/release/11.1R1.8/obj-powerpc/bsd/kernels/
JUNIPER-EX/kernel
Timecounter "decrementer" frequency 50000000 Hz quality 0
cpu0: Freescale e500v2 core revision 2.2
cpu0: HID0 80004080
...

request system zeroize

media

user@switch> request system zeroize media

warning: System will be rebooted and may not boot without configuration
Erase all data, including configuration and log files? [yes,no] (no) yes
warning: ipsec-key-management subsystem not running - not needed by configuration.
warning: zeroizing fpc0

Copyright 2011, Juniper Networks, Inc.

91

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

{master:0}
root> Waiting (max 60 seconds) for system process `vnlru' to stop...done
. . .
Syncing disks, vnodes remaining...2 4 2 4 3 2 1 1 0 0 0 done
syncing disks... All buffers synced.
Uptime: 14m50s
recorded reboot as normal shutdown
Rebooting...
U-Boot 1.1.6 (Apr 21 2011 - 13:58:42)
Board:
EPLD:
DRAM:
FLASH:
NAND:
0 MiB

EX4200-48PX 1.1
Version 8.0 (0x82)
Initializing (512 MB)
8 MB
No NAND device found!!!

Firmware Version: --- 01.00.00 --USB:

scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
ELF file is 32 bit
Consoles: U-Boot console
FreeBSD/PowerPC U-Boot bootstrap loader, Revision 2.2
([email protected], Fri Feb 26 17:48:51 PST 2010)
Memory: 512MB
Loading /boot/defaults/loader.conf
/kernel data=0x9abfdc+0xb06e4 syms=[0x4+0x83b30+0x4+0xbd7c6]
Hit [Enter] to boot immediately, or space bar for command prompt.
Booting [/kernel] in 1 second... Booting [/kernel]...
Kernel entry at 0x800000e0 ...
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1996-2011, Juniper Networks, Inc.
All rights reserved.
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
JUNOS 11.4R1.2 #0: 2011-10-27 18:05:39 UTC
[email protected]:/volume/build/junos/11.4/release/11.4R1.2/obj-powerpc/
bsd/kernels/JUNIPER-EX/kernel
can't re-use a leaf (all_slot_serialid)!
Timecounter "decrementer" frequency 50000000 Hz quality 0
cpu0: Freescale e500v2 core revision 2.2
cpu0: HID0 80004080<EMCP,TBEN,EN_MAS7_UPDATE>
real memory = 511705088 (488 MB)
avail memory = 500260864 (477 MB)
ETHERNET SOCKET BRIDGE initialising
Initializing EXSERIES platform properties ...
. . .
Automatic reboot in progress...
Media check on da0 on ex platforms
** /dev/da0s2a
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 20055 free (31 frags, 2503 blocks, 0.0% fragmentation)
zeroizing /dev/da0s1a ...

92

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

. . .
zeroizing
. . .
zeroizing
. . .
zeroizing
. . .
zeroizing
. . .

/dev/da0s3d ...
/dev/da0s3e ...
/dev/da0s4d ...
/dev/da0s4e ...

syncing disks... All buffers synced.

Uptime: 3m40s
Rebooting...
U-Boot 1.1.6 (Apr 21 2011 - 13:58:42)
Board:
EPLD:
DRAM:
FLASH:
NAND:
0 MiB

EX4200-48PX 1.1
Version 8.0 (0x82)
Initializing (512 MB)
8 MB
No NAND device found!!!

Firmware Version: --- 01.00.00 --USB:

scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
ELF file is 32 bit
Consoles: U-Boot console
FreeBSD/PowerPC U-Boot bootstrap loader, Revision 2.2
([email protected], Fri Feb 26 17:48:51 PST 2010)
Memory: 512MB
Loading /boot/defaults/loader.conf
/kernel data=0x9abfdc+0xb06e4 syms=[0x4+0x83b30+0x4+0xbd7c6]
Hit [Enter] to boot immediately, or space bar for command prompt.
Booting [/kernel] in 1 second... Booting [/kernel]...
Kernel entry at 0x800000e0 ...
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1996-2011, Juniper Networks, Inc.
All rights reserved.
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
JUNOS 11.4R1.2 #0: 2011-10-27 18:05:39 UTC
[email protected]:/volume/build/junos/11.4/release/11.4R1.2/obj-powerpc/
bsd/kernels/JUNIPER-EX/kernel
can't re-use a leaf (all_slot_serialid)!
Timecounter "decrementer" frequency 50000000 Hz quality 0
cpu0: Freescale e500v2 core revision 2.2
cpu0: HID0 80004080 <EMCP,TBEN,EN_MAS7_UPDATE>
real memory = 511705088 (488 MB)
avail memory = 500260864 (477 MB)
ETHERNET SOCKET BRIDGE initialising
Initializing EXSERIES platform properties ...
. . .
Automatic reboot in progress...
Media check on da0 on ex platforms

Copyright 2011, Juniper Networks, Inc.

93

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

** /dev/da0s1a
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 20064 free (48 frags, 2502 blocks, 0.1% fragmentation)
zeroizing /dev/da0s2a ...
. . .
Creating initial configuration...mgd: error: Cannot open configuration file:
/config/juniper.conf
mgd: warning: activating factory configuration
mgd: commit complete
mgd: ---------------------------------------------------------mgd: Please login as 'root'. No password is required.
mgd: To start Initial Setup, type 'ezsetup' at the JUNOS prompt.
mgd: To start JUNOS CLI, type 'cli' at the JUNOS prompt.
mgd: ---------------------------------------------------------Setting initial options: debugger_on_panic=NO debugger_on_break=NO.
Starting optional daemons: .
Doing initial network setup:
. . .
Amnesiac (ttyu0)

94

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

show system autoinstallation status

Syntax

show system autoinstallation status

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description

(J Series routers and EX Series switches only) Display autoinstallation status information.

Options

This command has no options.

Required Privilege
Level

view

List of Sample Output

show system autoinstallation status on page 95

Output Fields

Table 11 on page 95 describes the output fields for the show system autoinstallation status
command. Output fields are listed in the approximate order in which they appear.

Table 11: show system autoinstallation status Output Fields

Field Name

Field Description

Autoinstallation status

Display autoinstallation status information:

Last committed fileFile last committed for autoinstallation configuration.

Configuration server of last committed fileIP address or URL of server configured to retrieve

configuration information for the last committed configuration file.

InterfaceInterface configured for autoinstallation.

NameName of interface.

StateInterface state.

Address acquisitionDisplay IP address acquired and protocol used for acquisition upon bootup.

ProtocolProtocol used for acquisition: BOOTP/DHCP or RARP.

Acquired addressIP address acquired from the DHCPserver.

Sample Output
show system
autoinstallation status

user@host> show system autoinstallation status

Autoinstallation status:
Master state: Active
Last committed file: None
Configuration server of last committed file: 0.0.0.0
Interface:
Name: fe-0/0/1
State: None
Address acquisition:
Protocol: DHCP Client
Acquired address: None
Protocol: RARP Client
Acquired address: None

Copyright 2011, Juniper Networks, Inc.

95

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

show system boot-messages

Syntax

show system boot-messages

Syntax (EX Series

Switch)

show system boot-messages

<all-members>
<local>
<member member-id>

Syntax (TX Matrix

Router)

show system boot-messages

<all-chassis | all-lcc | lcc number | scc>

Syntax (TX Matrix Plus

Router)
Syntax (MX Series
Router)

show system boot-messages

<all-chassis | all-lcc | lcc number | sfc number>
show system boot-messages
<all-members>
<local>
<member member-id>

Syntax (QFX Series)

show system boot-messages

infrastructure name | interconnect-device name | node-group name

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Command introduced in Junos OS Release 11.1 for the QFX Series.

Description

Options

Display initial messages generated by the system kernel upon startup. These messages
are the contents of /var/run/dmesg.boot.
noneDisplay all boot time messages.
all-chassis(TX Matrix and TX Matrix Plus routers only) (Optional) Display boot time

messages for all of the chassis.

all-lcc(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,

display boot time messages for all T640 routers (or line-card chassis) connected
to a TX Matrix router. On a TX Matrix Plus router, display boot time messages for all
T1600 routers (or line-card chassis) connected to a TX Matrix Plus router.
all-members(EX4200 switches and MX Series routers only) (Optional) Display boot

time messages on all members of the Virtual Chassis configuration.

infrastructure name(QFabric switches only) (Optional) Display boot time messages on

the fabric control Routing Engine or fabric manager Routing engines.

interconnect-device name(QFabric switches only) (Optional) Display boot time messages

on the Interconnect device.

lcc number(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,

display boot time messages for a specific T640 router connected to a TX Matrix

96

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

router. On a TX Matrix Plus router, display boot time messages for a specific T1600
router connected to a TX Matrix Plus router. Replace number with a value from 0
through 3.
local(EX4200 switches and MX Series routers only) (Optional) Display boot time

messages on the local Virtual Chassis member.

member member-id(EX4200 switches and MX Series routers only) (Optional) Display

boot time messages on the specified member of the Virtual Chassis configuration.
For EX4200 switches, replace member-id with a value from 0 through 9. For an MX
Series Virtual Chassis, replace member-id with a value of 0 or 1.
node-group name(QFabric switches only) (Optional) Display boot time messages on

the Node group.

scc(TX Matrix routers only) (Optional) Display boot time messages for the TX Matrix

router (or switch-card chassis).

sfc number(TX Matrix Plus routers only) (Optional) Display boot time messages for the

TX Matrix Plus router (or switch-fabric chassis). Replace number with 0.

Additional Information

Required Privilege
Level
List of Sample Output

By default, when you issue the show system boot-messages command on a TX Matrix
or TX Matrix Plus master Routing Engine, the command is broadcast to all the T640 (in
a routing matrix based on a TX Matrix router) master Routing Engines or T1600 (in a
routing matrix based on a TX Matrix Plus router) master Routing Engines connected to
it. Likewise, if you issue the same command on the TX Matrix or TX Matrix Plus backup
Routing Engine, the command is broadcast to all the T640 (in a routing matrix based on
a TX Matrix router) backup Routing Engines or T1600 (routing matrix based on a TX
Matrix Plus router) backup Routing Engines that are connected to it.
view

show system boot-messages (TX Matrix Router) on page 97

show system boot-messages lcc (TX Matrix Router) on page 99
show system boot-messages (TX Matrix Plus Router) on page 99
show system boot-messages (QFX3500 Switch) on page 100

Sample Output
show system
boot-messages (TX
Matrix Router)

user@host> show system boot-messages

Copyright (c) 1992-1998 FreeBSD Inc.
Copyright (c) 1996-2000 Juniper Networks, Inc.
All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.

All rights reserved.

JUNOS 4.1-20000216-Zf8469 #0: 2000-02-16 12:57:28 UTC

[email protected]:/p/build/20000216-0905/4.1/release_kernel/sys/compil
e/GENERIC
CPU: Pentium Pro (332.55-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x66a Stepping=10
Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,<b
16>,<b17>,MMX,<b24>>

Copyright 2011, Juniper Networks, Inc.

97

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Teknor CPU Card Recognized

real memory = 805306368 (786432K bytes)
avail memory = 786280448 (767852K bytes)
Probing for devices on PCI bus 0:
chip0 <generic PCI bridge (vendor=8086 device=7192 subclass=0)> rev 3 class 6000
0 on pci0:0:0
chip1 <Intel 82371AB PCI-ISA bridge> rev 1 class 60100 on pci0:7:0
chip2 <Intel 82371AB IDE interface> rev 1 class 10180 on pci0:7:1
chip3 <Intel 82371AB USB interface> rev 1 class c0300 int d irq 11 on pci0:7:2
smb0 <Intel 82371AB SMB controller> rev 1 class 68000 on pci0:7:3
pcic0 <TI PCI-1131 PCI-CardBus Bridge> rev 1 class 60700 int a irq 15 on pci0:13
:0
TI1131 PCI Config Reg: [pci only][FUNC0 pci int]
pcic1 <TI PCI-1131 PCI-CardBus Bridge> rev 1 class 60700 int b irq 12 on pci0:13
:1
TI1131 PCI Config Reg: [pci only][FUNC1 pci int]
fxp0 <Intel EtherExpress Pro 10/100B Ethernet> rev 8 class 20000 int a irq 12 on
pci0:16:0
chip4 <generic PCI bridge (vendor=1011 device=0022 subclass=4)> rev 4 class 6040
0 on pci0:17:0
fxp1 <Intel EtherExpress Pro 10/100B Ethernet> rev 8 class 20000 int a irq 10 on
pci0:19:0
Probing for devices on PCI bus 1:
mcs0 <Miscellaneous Control Subsystem> rev 12 class ff0000 int a irq 12 on pci1:
13:0
fxp2 <Intel EtherExpress Pro 10/100B Ethernet> rev 8 class 20000 int a irq 10 on
pci1:14:0
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: EGA color <16 virtual consoles, flags=0x0>
ed0 not found at 0x300
ed1 not found at 0x280
ed2 not found at 0x340
psm0 not found at 0x60
sio0 at 0x3f8-0x3ff irq 4 flags 0x20010 on isa
sio0: type 16550A, console
sio1 at 0x3e8-0x3ef irq 5 flags 0x20000 on isa
sio1: type 16550A
sio2 at 0x2f8-0x2ff irq 3 flags 0x20000 on isa
sio2: type 16550A
pcic0 at 0x3e0-0x3e1 on isa
PC-Card ctlr(0) TI PCI-1131 [CardBus bridge mode] (5 mem & 2 I/O windows)
pcic0: slot 0 controller I/O address 0x3e0
npx0 flags 0x1 on motherboard
npx0: INT 16 interface
fdc0: direction bit not set
fdc0: cmd 3 failed at out byte 1 of 3
fdc0 not found at 0x3f0
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <SunDisk SQFXB-80>, single-sector-i/o
wd0: 76MB (156672 sectors), 612 cyls, 8 heads, 32 S/T, 512 B/S
wdc0: unit 1 (wd1): <IBM-DCXA-210000>
wd1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 not found at 0x170
wdc2 not found at 0x180
ep0 not found at 0x300
fxp0: Ethernet address 00:a0:a5:12:05:5a
fxp1: Ethernet address 00:a0:a5:12:05:59

98

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

fxp2: Ethernet address 02:00:00:00:00:01

swapon: adding /dev/wd1s1b as swap device
Automatic reboot in progress...
/dev/rwd0s1a: clean, 16599 free (95 frags, 2063 blocks, 0.1% fragmentation)
/dev/rwd0s1e: clean, 9233 free (9 frags, 1153 blocks, 0.1% fragmentation)
/dev/rwd0s1a: clean, 16599 free (95 frags, 2063 blocks, 0.1% fragmentation)
/dev/rwd1s1f: clean, 4301055 free (335 frags, 537590 blocks, 0.0% fragmentation)

show system
boot-messages lcc (TX
Matrix Router)

user@host> show system boot-messages lcc 2

lcc2-re0:
-------------------------------------------------------------------------Copyright (c) 1996-2001, Juniper Networks, Inc.
All rights reserved.
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
JUNOS 7.0-20040912.0 #0: 2004-09-12 09:16:32 UTC
[email protected]:/build/benten-b/7.0/20040912.0/obj-i386/sys/compile/JUNIPER
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 601368936 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (601.37-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x68a Stepping = 10
Features=0x387f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE>
real memory = 2147467264 (2097136K bytes)
sio0: gdb debugging port
avail memory = 2084040704 (2035196K bytes)
Preloaded elf kernel "kernel" at 0xc06d9000.
DEVFS: ready for devices
Pentium Pro MTRR support enabled
md0: Malloc disk
DRAM Data Integrity Mode: ECC Mode with h/w scrubbing
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <ServerWorks NB6635 3.0LE host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcic-pci0: <TI PCI-1410 PCI-CardBus Bridge> irq 15 at device 1.0 on pci0
pcic-pci0: TI12XX PCI Config Reg: [pwr save][pci only]
fxp0: <Intel Embedded 10/100 Ethernet> port 0x1000-0x103f mem
0xfb800000-0xfb81ffff,0xfb820000-0xfb820fff irq 9 at device 3.0 on pci0
fxp1: <Intel Embedded 10/100 Ethernet> port 0x1040-0x107f mem
0xfb840000-0xfb85ffff,0xfb821000-0xfb821fff irq 11 at device 4.0 on pci0
...

show system
boot-messages (TX
Matrix Plus Router)

user@host> show system boot-messages

sfc0-re0:
-------------------------------------------------------------------------Copyright (c) 1996-2009, Juniper Networks, Inc.
All rights reserved.
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
JUNOS 9.6B3.3 #0: 2009-06-17 19:52:08 UTC
[email protected]:/volume/build/junos/9.6/release/9.6B3.3/obj-i386/bsd/sys/compile/JUNIPER
MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R)
CPU
L5238 @ 2.66GHz (2660.01-MHz 686-class CPU)
Origin =
"GenuineIntel" Id = 0x1067a Stepping = 10
Features=0xbfebfbff
...
lcc1-re0:

Copyright 2011, Juniper Networks, Inc.

99

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

-------------------------------------------------------------------------Copyright (c) 1996-2009, Juniper Networks, Inc.

All rights reserved.
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
JUNOS 9.6-20090617.0 #0: 2009-06-17 04:15:14 UTC
[email protected]:/volume/build/junos/9.6/production/20090617.0/obj-i386/bsd/sys/compile/JUNIPER
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU
@ 1.86GHz (1862.01-MHz 686-class CPU)
Origin = "GenuineIntel"
Features=0xbfebfbff
...

show system
boot-messages
(QFX3500 Switch)

Id = 0x1067a

Stepping = 10

user@switch> show sytem boot-messages

getmemsize: msgbufp[size=32768] = 0x81d07fe4
System physical memory distribution:
------------------------------------------------------------------------------Total physical memory: 4160749568 (3968 MB)
Physical memory used: 3472883712 (3312 MB)
Physical memory allocated to kernel: 2130706432 (2032 MB)
Physical memory allocated to user BTLB: 1342177280 (1280 MB)
------------------------------------------------------------------------------Copyright (c) 1996-2010, Juniper Networks, Inc.
All rights reserved.
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
JUNOS 11.1I #0: 2010-09-17 19:18:07 UTC
[email protected]:/c/ssiano/DEV_QFX_SI_BRANCH/03/20100917.399988/
obj-xlr/bsd/sys/compile/JUNIPER-DCTOR
WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
JUNOS 11.1I #0: 2010-09-17 19:18:07 UTC
[email protected]:/c/ssiano/DEV_QFX_SI_BRANCH/03/20100917.399988/
obj-xlr/bsd/sys/compile/JUNIPER-DCTOR
real memory = 3472883712 (3312MB)
avail memory = 1708171264 (1629MB)
cpuid: 0, btlb_cpumap:0xfffffff8
FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs
ETHERNET SOCKET BRIDGE initialising
Initializing QFX platform properties ..
cpu0 on motherboard
: RMI's XLR CPU Rev. 0.3 with no FPU implemented
L1 Cache: I size 32kb(32 line), D size 32kb(32 line), eight way.
L2 Cache: Size 1024kb, eight way
pic_lbus0: <XLR Local Bus>
pic_lbus0: <XLR Local Bus> on motherboard
Enter qfx control ethernet probe addr:0xc5eeec00
gmac4: <XLR GMAC GE Ethernet> on pic_lbus0
me0: Ethernet address 00:1d:b5:f7:68:40
Enter qfx control ethernet probe addr:0xc5eeeb40
gmac5: <XLR GMAC GE Ethernet> on pic_lbus0
me1: Ethernet address 00:1d:b5:f7:68:41
Enter qfx control ethernet probe addr:0xc5eeea80
gmac6: <XLR GMAC GE Ethernet> on pic_lbus0

100

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

me1: Ethernet address 00:1d:b5:f7:68:42

sio0 on pic_lbus0
Entering sioattach
sio0: type 16550A, console
xls_setup_intr: skip irq 3, xlr regs are set up somewhere else.
gblmem0 on pic_lbus0
ehci0: <RMI XLS USB 2.0 controller> on pic_lbus0
ehci_bus_attach: allocated resource. tag=1, base=bef24000
xls_ehci_init: endian hardware swapping NOT enabled.
usb0: EHCI version 1.0
usb0 on ehci0
usb0: USB revision 2.0
uhub0: vendor 0x0000 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
umass0: USB USBFlashDrive, rev 2.00/11.00, addr 2
pcib0: PCIe link 0 up
pcib0: PCIe link 2 up
pcib0: PCIe link 3 up
pcib0: <XLS PCI Host Controller> on pic_lbus0
pci0: <PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 0.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <network, ethernet> at device 0.0 (no driver attached)
pcib2: <PCI-PCI bridge> at device 1.0 on pci0
pcib3: <PCI-PCI bridge> at device 2.0 on pci0
pci2: <PCI bus> on pcib3
pci2: <network, ethernet> at device 0.0 (no driver attached)
pcib4: <PCI-PCI bridge> at device 3.0 on pci0
pci3: <PCI bus> on pcib4
pci3: <network, ethernet> at device 0.0 (no driver attached)
cfi device address space at 0xbc000000
cfi0: <AMD/Fujitsu - 8MB> on pic_lbus0
cfi device address space at 0xbc000000
i2c0: <I2C bus controller> on pic_lbus0
i2c1: <I2C bus controller> on pic_lbus0
qfx_fmn0 on pic_lbus0
pool offset 1503776768
xlr_lbus0: <XLR Local Bus Controller> on motherboard
qfx_bcpld_probe[124]
qfx_bcpld_probe[138]: dev_type=0x0
qfx_bcpld_probe[124]
qfx_bcpld0: QFX BCPLD probe success
qfx_bcpld0qfx_bcpld_attach[174]
qfx_bcpld_attach[207] : bus_space_tag=0x0, bus_space_handle=0xbd900000
qfx_bcpld_probe[124]
qfx_bcpld1: QFX BCPLD probe success
qfx_bcpld1qfx_bcpld_attach[174]
tor_bcpld_slave_attach[1245] : bus_space_tag=0x0, bus_space_handle=0xbda00000
Initializing product: 96 ..
bmeb: bmeb_lib_init done 0xc60a5000, addr 0x809c99a0
bme0:Virtual BME driver initializing
Timecounter "mips" frequency 1200000000 Hz quality 0
Timecounter "xlr_pic_timer" frequency 66666666 Hz quality 1
Timecounters tick every 1.000 msec
Loading the NETPFE fc module
IPsec: Initialized Security Association Processing.
SMP: AP CPU #3 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #4 Launched!
SMP: AP CPU #5 Launched!

Copyright 2011, Juniper Networks, Inc.

101

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

SMP: AP CPU #7 Launched!

SMP: AP CPU #6 Launched!
SMP: AP CPU #11 Launched!
SMP: AP CPU #10 Launched!
SMP: AP CPU #9 Launched!
SMP: AP CPU #8 Launched!
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <USB USBFlashDrive 1100> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 3920MB (8028160 512 byte sectors: 255H 63S/T 499C)
Trying to mount root from ufs:/dev/da0s1a

102

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

show system license

Syntax

Release Information

Description
Options

show system license

<installed | keys | usage>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Display licenses and information about how they are used.
noneDisplay all license information.
installed(Optional) Display installed licenses only.
keys(Optional) Display a list of license keys. Use this information to verify that each

expected license key is present.

usage(Optional) Display the state of licensed features.

Required Privilege
Level
List of Sample Output

Output Fields

maintenance

show system license on page 104

show system license installed on page 104
show system license keys on page 105
show system license usage on page 105
Table 12 on page 103 lists the output fields for the show system license command. Output
fields are listed in the approximate order in which they appear.

Table 12: show system license Output Fields

Field Name

Field Description

Feature name

Name assigned to the configured feature. You use this information to verify that all the features for
which you installed licenses are present.

Licenses used

Number of licenses used by a router or switch. You use this information to verify that the number of
licenses used matches the number configured. If a licensed feature is configured, the feature is
considered used.
NOTE: In Junos OS Release 10.1 and later, the Licenses used column displays the actual usage count
based on the number of active sessions or connections as reported by the corresponding feature
daemons. This is applicable for scalable license-based features such as Subscriber Access
(scale-subscriber), L2TP (scale-l2tp), Mobile IP (scale-mobile-ip), and so on.

Copyright 2011, Juniper Networks, Inc.

103

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Table 12: show system license Output Fields (continued)

Field Name

Field Description

Licenses installed

Information about the installed license key:

License identifierIdentifier associated with a license key.

StateState of the license key:valid or invalid. An invalid state indicates that the key was entered

incorrectly or is not valid for the specific device.

License versionVersion of a license. The version indicates how the license is validated, the type

of signature, and the signer of the license key.

Valid for deviceDevice that can use a license key.

Group definedGroup membership of a device.

FeaturesFeature associated with a license, such as data link switching (DLSw).

Licenses needed

Number of licenses required for features being used but not yet properly licensed.

Expiry

Amount of time left within the grace period before a license is required for a feature being used.

Sample Output
show system license

user@host> show system license

License usage:
Feature name
subscriber-accounting
subscriber-authentication
subscriber-address-assignment
subscriber-vlan
subscriber-ip
scale-subscriber
scale-l2tp
scale-mobile-ip

Licenses
used
2
1
2
2
0
2
4
1

Licenses
installed
2
2
2
2
2
3
5
2

Licenses
needed
0
0
0
0
0
0
0
0

Expiry
permanent
permanent
permanent
permanent
permanent
permanent
permanent
permanent

Licenses installed:
License identifier: XXXXXXXXXX
License version: 2
Features:
subscriber-accounting - Per Subscriber Radius Accounting
permanent
subscriber-authentication - Per Subscriber Radius Authentication
permanent
subscriber-address-assignment - Radius/SRC Address Pool Assignment
permanent
subscriber-vlan - Dynamic Auto-sensed Vlan
permanent
subscriber-ip
- Dynamic and Static IP
permanent

show system license

installed

104

user@host> show system license installed

License identifier: XXXXXXXXXX
License version: 2
Features:
subscriber-accounting - Per Subscriber Radius Accounting
permanent
subscriber-authentication - Per Subscriber Radius Authentication

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

permanent
subscriber-address-assignment - Radius/SRC Address Pool Assignment
permanent
subscriber-vlan - Dynamic Auto-sensed Vlan
permanent
subscriber-ip
- Dynamic and Static IP
permanent

show system license

keys

user@host> show system license keys

XXXXXXXXXX xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx
xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx
xxxxxx xxxxxx xxx

show system license

usage

user@host> show system license usage

License usage:
Licenses
Feature name
used
subscriber-accounting
2
subscriber-authentication
1
subscriber-address-assignment
2
subscriber-vlan
2
subscriber-ip
0
scale-subscriber
2
scale-l2tp
4
scale-mobile-ip
1

Copyright 2011, Juniper Networks, Inc.

Licenses
installed
2
2
2
2
2
3
5
2

Licenses
needed
0
0
0
0
0
0
0
0

Expiry
permanent
permanent
permanent
permanent
permanent
permanent
permanent
permanent

105

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

show system snapshot

Syntax
Syntax (EX Series
Switch)

Release Information

Description

show system snapshot

show system snapshot
<all-members|local|member member-id>
<media (external | internal)>
<slice (1 | 2 | alternate)>

Command introduced in Junos OS Release 7.6.

Command introduced in Junos OS Release 10.0 for EX Series switches.
Display information about the backup software:

On the routers, display information about the backup software, which is located in the
/altroot, and /altconfig file systems or on the alternate media.

On the switches, display information about the backup of the root fie system /, /config
directory, and /var directory, which are located either on an external USB flash drive
or in internal flash memory.

NOTE: To back up software, use the request system snapshot command.

Options

noneDisplay information about the backup software.

all-members | local | member member-id(EX4200 switch and EX4200, EX4500, and

EX8200 Virtual Chassis only) (Optional) Display the snapshot in a Virtual Chassis:

all-membersDisplay the snapshot for all members of the Virtual Chassis.

localDisplay the snapshot on the member of the Virtual Chassis that you are

currently logged into.

member member-idDisplay the snapshot for the specified member of the Virtual

Chassis.
media (external | internal)(EX Series switch only) (Optional) Display the destination

media location for the snapshot. The external option specifies the snapshot on an
external mass storage device, such as a USB flash drive. The internal option specifies
the snapshot on an internal memory source, such as internal flash memory. If no
additional options are specified, the command displays the snapshot stored in both
slices.
slice (1 | 2 | alternate)(EX Series switch only) Display the snapshot in a specific partition:

1Display the snapshot in partition 1.

2Display the snapshot in partition 2.

alternateDisplay the snapshot in the alternate partition, which is the partition

that did not boot the switch at the last bootup.

106

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

request system snapshot on page 65

show system snapshot (Router) on page 107

show system snapshot media external (Switch) on page 107
show system snapshot media internal (Switch) on page 107
show system snapshot media internal slice 2 (Switch) on page 108
Table 13 on page 107 lists the output fields for the show system snapshot command.
Output fields are listed in the approximate order in which they appear.

Table 13: show system snapshot Output Fields

Field Name

Field Description

Creation date

Date and time of the last snapshot.

JUNOS version on snapshot

Junos OS release number of individual software

packages.

Sample Output
show system snapshot
(Router)

user@host> show system snapshot

Information for snapshot on hard-disk
Creation date: Oct 5 13:53:29 2005
JUNOS version on snapshot:
jbase : 7.3R2.5
jcrypto: 7.3R2.5
jdocs : 7.3R2.5
jkernel: 7.3R2.5
jpfe
: M40-7.3R2.5
jroute : 7.3R2.5

show system snapshot

media external
(Switch)

user@switch> show system snapshot media external

Information for snapshot on external (da1s1)
Creation date: Oct 13 20:23:23 2009
JUNOS version on snapshot:
jbase : 10.0I20090726_0011_user
jcrypto-ex: 10.0I20090726_0011_user
jdocs-ex: 10.0I20090726_0011_user
jkernel-ex: 10.0I20090726_0011_user
jroute-ex: 10.0I20090726_0011_user
jswitch-ex: 10.0I20090726_0011_user
jweb-ex: 10.0I20090726_0011_user
jpfe-ex42x: 10.0I20090726_0011_user

show system snapshot

media internal
(Switch)

user@switch> show system snapshot media internal

Information for snapshot on internal (/dev/da0s1a) (backup)
Creation date: Mar 14 05:01:02 2011
JUNOS version on snapshot:
jbase : 11.1R1.9
jcrypto-ex: 11.1R1.9
jdocs-ex: 11.1R1.9

Copyright 2011, Juniper Networks, Inc.

107

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

jkernel-ex: 11.1R1.9
jroute-ex: 11.1R1.9
jswitch-ex: 11.1R1.9
jweb-ex: 11.1R1.9
jpfe-ex42x: 11.1R1.9
Information for snapshot on internal (/dev/da0s2a) (primary)
Creation date: Mar 30 08:46:27 2011
JUNOS version on snapshot:
jbase : 11.2-20110330.0
jcrypto-ex: 11.2-20110330.0
jdocs-ex: 11.2-20110330.0
jkernel-ex: 11.2-20110330.0
jroute-ex: 11.2-20110330.0
jswitch-ex: 11.2-20110330.0
jweb-ex: 11.2-20110330.0
jpfe-ex42x: 11.2-20110330.0

show system snapshot

media internal slice 2
(Switch)

108

user@switch> show system snapshot media internal slice 2

Information for snapshot on internal (/dev/da0s2a) (primary)
Creation date: Mar 30 08:46:27 2011
JUNOS version on snapshot:
jbase : 11.2-20110330.0
jcrypto-ex: 11.2-20110330.0
jdocs-ex: 11.2-20110330.0
jkernel-ex: 11.2-20110330.0
jroute-ex: 11.2-20110330.0
jswitch-ex: 11.2-20110330.0
jweb-ex: 11.2-20110330.0
jpfe-ex42x: 11.2-20110330.0

Copyright 2011, Juniper Networks, Inc.

Chapter 7: Operational Commands for Software Installation

show system storage partitions (EX Series Switches Only)

Syntax

Release Information
Description
Options

show system storage partitions

<all-members>
<local>
<member member-id>

Command introduced in Junos OS Release 11.1 for EX Series switches.

Display information about the disk partitions on EX Series switches.
noneDisplay partition information.
all-members(Virtual Chassis systems only) (Optional) Display partition information

for all members of the Virtual Chassis.

local(Virtual Chassis systems only) (Optional) Display partition information for the

local Virtual Chassis member.

member member-id(Virtual Chassis systems only) (Optional) Display partition

information for the specified member of the Virtual Chassis configuration.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

Verifying Junos OS and Boot Loader Software Versions on an EX Series Switch on

page 36

show system storage partitions on page 110

Table 14 on page 109 describes the output fields for the show system storage partitions
command. Output fields are listed in the approximate order in which they appear.

Table 14: show system storage partitions Output Fields

Field Name

Field Description

Boot Media

Media (internal or external) from which the switch was booted.

Active Partition

Name of the active root partition.

Backup Partition

Name of the backup (alternate) root partition.

Currently booted from

Partition from which the switch was last booted.

Partitions information

Information about partitions on the boot media:

Copyright 2011, Juniper Networks, Inc.

PartitionPartition identifier.

SizeSize of partition.

MountpointDirectory on which the partition is mounted.

109

Junos OS for EX Series Ethernet Switches, Release 11.4: Software Installation

Sample Output
show system storage
partitions

user@switch> show system storage partitions

fpc0:
-------------------------------------------------------------------------Boot Media: internal (da0)
Active Partition: da0s1a
Backup Partition: da0s2a
Currently booted from: active (da0s1a)
Partitions information:
Partition Size
Mountpoint
s1a
184M
/
s2a
184M
altroot
s3d
369M
/var/tmp
s3e
123M
/var
s4d
62M
/config
s4e
unused (backup config)

110

Copyright 2011, Juniper Networks, Inc.