book software ex series software installation

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 AvenueSunnyvale, California 94089USA408-745-2000www.juniper.net

This product includes the Envoy SNMPEngine, developed by Epilogue Technology, an IntegratedSystemsCompany. Copyright 1986-1997,Epilogue Technology Corporation. All rights reserved. This program and its documentation were developed at private expense, and no partof 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 documentationand 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 throughrelease 3.0 by Cornell University and its collaborators. Gated is based on Kirtons EGP, UC Berkeleys routing daemon (routed), and DCNsHELLO routing protocol. Development of Gated has been supported in part by the National Science Foundation. Portions of the GateDsoftware 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 UnitedStates and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All othertrademarks, 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 areowned 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.

JunosOS for EX Series Ethernet Switches, Release 11.4: Software InstallationCopyright 2011, Juniper Networks, Inc.All rights reserved.

Revision HistoryNovember 2011Revision 2November 2011Revision 1

The information in this document is current as of the date listed in the revision history.

ENDUSER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networkssoftware. Use of such software is subject to the terms and conditions of the End User License Agreement (EULA) posted athttp://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditionsof that EULA.

Copyright 2011, Juniper Networks, Inc.ii

Table of ContentsAbout This Topic Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiList of EX Series Guides for Junos OS Release 11.4 . . . . . . . . . . . . . . . . . . . . . . . . . viiDownloading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixDocumentation Symbols Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xDocumentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiRequesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiOpening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Part 1 Software InstallationChapter 1 Software Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Junos OSOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Understanding Software Infrastructure and Processes . . . . . . . . . . . . . . . . . . 3

Routing Engine and Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . . . 3Junos OS Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Understanding Software Installation on EX Series Switches . . . . . . . . . . . . . . 5

Overview of the Software Installation Process . . . . . . . . . . . . . . . . . . . . . 6Software Package Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Installing Software on a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Installing Software on EX8200 Switches with Redundant Routing

Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Installing Software Using Automatic Software Download . . . . . . . . . . . . . 7Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Junos OS Package Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Understanding System Snapshot on EX Series Switches . . . . . . . . . . . . . . . . . 8Understanding Resilient Dual-Root Partitions on Switches . . . . . . . . . . . . . . 10

Resilient Dual-Root Partition Scheme (Junos OS Release 10.4R3 andLater) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Earlier Partition Scheme (Junos OS Release 10.4R2 and Earlier) . . . . . . . 11UnderstandingUpgradingorDowngradingBetweenResilientDual-Root

Partition Releases and Earlier Releases . . . . . . . . . . . . . . . . . . . . . . . 11Licenses Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Understanding Software Licenses for EX Series Switches . . . . . . . . . . . . . . . . 12Purchasing a Software Feature License . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Features Requiring a License on EX2200 Switches . . . . . . . . . . . . . . . . . 13Features Requiring a License on EX3200, EX4200, EX4500, EX6200

and EX8200 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Features Requiring a License on EX3300 Switches . . . . . . . . . . . . . . . . . 14

iiiCopyright 2011, Juniper Networks, Inc.

License Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15License Key Components for the EX Series Switch . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2 Installing Junos OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Downloading Software Packages from Juniper Networks . . . . . . . . . . . . . . . . . . . . 17Installing Software on an EX Series Switch with a Single Routing Engine (CLI

Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Installing Software on an EX Series Switch with Redundant Routing Engines

(CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Preparing the Switch for the Software Installation . . . . . . . . . . . . . . . . . . . . . 20Installing Software on the Backup Routing Engine . . . . . . . . . . . . . . . . . . . . . 21Installing Software on the Default Master Routing Engine . . . . . . . . . . . . . . . 22Returning Routing Control to the Default Master Routing Engine

(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Installing Software on EX Series Switches (J-Web Procedure) . . . . . . . . . . . . . . . 24

Installing Software Upgrades from a Server . . . . . . . . . . . . . . . . . . . . . . . . . . 24Installing 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, andManaging Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Registering the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Registering the EX Series Switch with the J-Web Interface . . . . . . . . . . . . . . . 27

Booting the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Booting an EX Series Switch Using a Software Package Stored on a USB

Flash Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Creating 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 theSwitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Creating a Snapshot on an Internal Flash Drive and Using it to Boot theSwitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Upgrading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Upgrading Software Using Automatic Software Download on EX Series

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Managing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Managing Licenses for the EX Series Switch (CLI Procedure) . . . . . . . . . . . . . 31Adding New Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Deleting Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Saving License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Managing Licenses for the EX Series Switch (J-Web Procedure) . . . . . . . . . . 33Adding New Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Deleting Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Displaying License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Downloading Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Copyright 2011, Juniper Networks, Inc.iv

JunosOS for EX Series Ethernet Switches, Release 11.4: Software Installation

Chapter 4 Verifying Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Routine Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Verifying That Automatic Software Download Is Working Correctly . . . . . . . 35Verifying That a System Snapshot Was Created on an EX Series Switch . . . 36Verifying Junos OS and Boot Loader Software Versions on an EX Series

Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Verifying the Number of Partitions and File SystemMountings . . . . . . . . 37Verifying the Loader Software Version . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Verifying Which Root Partition Is Active . . . . . . . . . . . . . . . . . . . . . . . . . . 38Verifying the Junos OS Version in Each Root Partition . . . . . . . . . . . . . . . 39

Monitoring Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Monitoring Licenses for the EX Series Switch . . . . . . . . . . . . . . . . . . . . . . . . . 40

Displaying Installed Licenses and License Usage Details . . . . . . . . . . . . 40Displaying Installed License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 5 Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Recovering from a Failed Software Upgrade on an EX Series Switch . . . . . . 43Rebooting from the Inactive Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Freeing Disk Space for Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 45Installation from the Boot Loader Generates cannot open package

Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Troubleshooting a Switch That Has Booted from the Backup Junos OS

Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Resilient Dual-Root Partitions Frequently Asked Questions . . . . . . . . . . . . . . . . . 47

How Does Upgrading to Junos OS Release 10.4R3 and Later Differ fromNormal Upgrades? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

WhatHappens If I DoNotUpgradeBoth the Loader Software and JunosOSat the Same Time? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Can I Downgrade Junos OSWithout Downgrading the LoaderSoftware? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Can I Upgrade to a Resilient Dual-Root Partition Release by Using theCLI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Will I Lose My Configuration During an Upgrade? . . . . . . . . . . . . . . . . . . . . . . 49How LongWill the Upgrade Process Take? . . . . . . . . . . . . . . . . . . . . . . . . . . . 49What Happens to My Files If the System Detects a File System

Corruption? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49HowWill I Be Informed If My Switch Boots from the Alternate Slice Due to

Corruption in the Root File System? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Can I Use Automatic Software Update and Download to Upgrade to a

Resilient Dual-Root Partition Release? . . . . . . . . . . . . . . . . . . . . . . . . . . 50Why Is the Message "At least one package installed on this device has

limited support" Displayed When Users Log In to a Switch? . . . . . . . . . . 51Where Can I Find Instructions for Upgrading? . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 6 Configuration Statements for Software Installation . . . . . . . . . . . . . . . . . . . 53

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

vCopyright 2011, Juniper Networks, Inc.

Table of Contents

Chapter 7 Operational Commands for Software Installation . . . . . . . . . . . . . . . . . . . . . 55

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

Copyright 2011, Juniper Networks, Inc.vi


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 athttp://www.juniper.net/techpubs/en_US/release-independent/information-products/pathway-pages/ex-series/product/index.html. We have selected content from thesewebpages and created a number of EX Series guides that collect related topics into abook-like format so that the information is easy to print and easy to download to yourlocal computer.

Software features for EX Series switches are listed by platform and by Junos OS releasein 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

DescriptionTitle

Component descriptions, site preparation, installation,replacement, and safety and compliance informationfor EX2200 Ethernet switches

Complete Hardware Guide for EX2200 Ethernet Switches





viiCopyright 2011, Juniper Networks, Inc.

DescriptionTitle











Component descriptions, site preparation, installation,replacement, and safety and compliance informationfor the XRE200 External Routing Engine

Complete Hardware Guide for the XRE200 External Routing Engine

Software feature descriptions, configuration examples,and tasks for Junos OS for EX Series switches

Complete Software Guide for JunosOS for EX Series EthernetSwitches, Release 11.4

Software feature descriptions, configuration examplesand tasks, and reference pages for configurationstatements and operational commands (Thisinformationalsoappears in theCompleteSoftwareGuidefor JunosOS for EX Series Ethernet Switches, Release11.4.)

Software Topic Collections

JunosOS for EX Series Ethernet Switches, Release 11.4: Access andUser Management

JunosOS for EXSeries EthernetSwitches, Release 11.4: AccessControl

JunosOS for EX Series Ethernet Switches, Release 11.4: ConfigurationManagement

JunosOS for EX Series Ethernet Switches, Release 11.4: Class ofService

JunosOSfor EXSeriesEthernetSwitches, Release 11.4:DeviceSecurity

JunosOS for EX Series Ethernet Switches, Release 11.4: EthernetSwitching

JunosOS for EX Series Ethernet Switches, Release 11.4: EX3300,EX4200, and EX4500 Virtual Chassis

Copyright 2011, Juniper Networks, Inc.viii


DescriptionTitle

JunosOSforEXSeriesEthernetSwitches,Release 11.4: EX8200VirtualChassis

JunosOS for EX Series Ethernet Switches, Release 11.4: Fibre Channelover Ethernet

JunosOS for EX Series Ethernet Switches, Release 11.4: HighAvailability

JunosOS for EX Series Ethernet Switches, Release 11.4: Interfaces

JunosOS for EX Series Ethernet Switches, Release 11.4: Layer 3Protocols

JunosOS for EX Series Ethernet Switches, Release 11.4: MPLS

JunosOS for EX Series Ethernet Switches, Release 11.4: Multicast

JunosOS for EX Series Switches, Release 11.4: Network Managementand Monitoring

JunosOS for EX Series Switches, Release 11.4: Port Security

JunosOS for EX Series Switches, Release 11.4: Power over Ethernet

JunosOS for EXSeries Ethernet Switches, Release 11.4: RoutingPolicyand Packet Filtering

JunosOS for EX Series Ethernet Switches, Release 11.4: SoftwareInstallation

JunosOSfor EXSeries EthernetSwitches, Release 11.4: Spanning-TreeProtocols

JunosOS for EX Series Ethernet Switches, Release 11.4: SystemMonitoring

JunosOS for EX Series Ethernet Switches, Release 11.4: SystemServices

JunosOS for EXSeries Ethernet Switches, Release 11.4: SystemSetup

JunosOSfor EXSeries EthernetSwitches, Release 11.4:User Interfaces

Downloading Software

You can download Junos OS for EX Series switches from the Download Software areaat http://www.juniper.net/customers/support/ . To download the software, youmust

ixCopyright 2011, Juniper Networks, Inc.


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

Documentation Symbols Key

Notice Icons

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardwaredamage.

Caution

Alerts you to the risk of personal injury or death.Warning

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

Text and Syntax Conventions

ExamplesDescriptionConvention

To enter configuration mode, type theconfigure command:

user@host> configure

Represents text that you type.Bold text like this

user@host> show chassis alarms

No alarms currently active

Represents output that appears on theterminal screen.

Fixed-width text like this

Apolicy term is anamedstructure thatdefinesmatchconditionsandactions.

Junos OS System Basics ConfigurationGuide

RFC 1997, BGP Communities Attribute

Introduces important new terms.

Identifies book names.

Identifies RFCand Internet draft titles.

Italic text like this

Configure the machines domain name:

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

Represents variables (options for whichyou substitute a value) in commands orconfiguration statements.

Italic text like this

To configure a stub area, include thestub statement at the [edit protocolsospf area area-id] hierarchy level.

The console port is labeledCONSOLE.

Represents names of configurationstatements, commands, files, anddirectories; IP addresses; configurationhierarchy levels; or labels on routingplatform components.

Plain text like this

Copyright 2011, Juniper Networks, Inc.x


Text and Syntax Conventions

ExamplesDescriptionConvention

stub ;Enclose optional keywords or variables.< > (angle brackets)

broadcast | multicast

(string1 | string2 | string3)

Indicates a choice between themutuallyexclusive keywords or variables on eitherside of the symbol. The set of choices isoften enclosed in parentheses for clarity.

| (pipe symbol)

rsvp { # Required for dynamicMPLS onlyIndicates a comment specified on thesame lineas theconfiguration statementto which it applies.

# (pound sign)

community namemembers [community-ids ]

Enclose a variable for which you cansubstitute one or more values.

[ ] (square brackets)

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

}}

}

Identify a level in the configurationhierarchy.

Indention and braces ( { } )

Identifies a leaf statement at aconfiguration hierarchy level.

; (semicolon)

J-Web GUI Conventions

In the Logical Interfacesbox, selectAllInterfaces.

To cancel the configuration, clickCancel.

Represents J-Web graphical userinterface (GUI) items you click or select.

Bold text like this

In the configuration editor hierarchy,select Protocols>Ospf.

Separates levels in a hierarchy of J-Webselections.

> (bold right angle bracket)

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we canimprove the documentation. Send e-mail to [email protected] thefollowing:

Document URL or title

Page number if applicable

Software version

Your name and company

xiCopyright 2011, Juniper Networks, Inc.


Requesting Technical Support

Technical product support is available through the JuniperNetworksTechnicalAssistanceCenter (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 accessour 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 athttp://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf .

Product warrantiesFor product warranty information, visithttp://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 onlineself-service portal called the Customer Support Center (CSC) that provides youwith thefollowing 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/

Toverify serviceentitlementbyproduct serial number, useourSerialNumberEntitlement(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Casewith JTAC

You can open a case with JTAC on theWeb 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, seehttp://www.juniper.net/support/requesting-support.html .

Copyright 2011, Juniper Networks, Inc.xii


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 ManagingLicenses 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

1Copyright 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 JuniperNetworks EX Series Ethernet Switches on its general-purpose processors. Junos OSincludes 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 coordinatescommunication among the Junos OS processes and provides a link to the PacketForwarding Engine.

With the J-Web interface and the command-line interface (CLI) to the Junos OS, youconfigure switching features and routing protocols and set the properties of networkinterfaces on your switch. After activating a software configuration, use either the J-Webor CLI user interface to monitor the switch, manage operations, and diagnose protocoland 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, andother features; and forwards packets to the next hop along the route to their finaldestination.

Routing EngineProvides three main functions:


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

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

Provides control andmonitoring functions for the switch, including controllingpowerandmonitoring system status.

Junos OS Processes

The Junos OS running on the Routing Engine and Packet Forwarding Engine consists ofmultiple processes that are responsible for individual functions.

Theseparationof functionsprovidesoperational stability, becauseeachprocessaccessesitsownprotectedmemory space. Inaddition, becauseeachprocess isa separate softwarepackage, 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

DescriptionNameProcess

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

Monitors the physical status of hardware components and field-replaceable units(FRUs),detectingwhenenvironmentsensors suchas temperaturesensorsare triggered.

Relays signals and interruptsfor example, when devices are taken offline, so that thesystem can close sessions and shut down gracefully.

chassisdChassis process

Handles Layer 2 switching functionality such as MAC address learning, Spanning Treeprotocol andaccessport security. Theprocess is also responsible formanagingEthernetswitching interfaces, VLANs, and VLAN interfaces.

Manages Ethernet switching interfaces, VLANs, and VLAN interfaces.

eswdEthernetswitchingprocess

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

pfemForwardingprocess

Configures andmonitors network interfaces by defining physical characteristics suchas link encapsulation, hold times, and keepalive timers.

dcdInterfaceprocess



Table 1: Junos OS Processes (continued)

DescriptionNameProcess

Provides communication between the other processes and an interface to theconfiguration database.

Populates the configuration databasewith configuration information and retrieves theinformation when queried by other processes to ensure that the system operates asconfigured.

Interactswith the other processeswhen commands are issued through one of the userinterfaces on the switch.

If a process terminates or fails to startwhen called, themanagement process attemptsto restart it a limited number of times to prevent thrashing and logs any failureinformation for further investigation.

mgdManagementprocess

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

rpdRoutingprotocolprocess

RelatedDocumentation

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

Formore information about basic system parameters, supported protocols, and softwareprocesses, 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 Junosoperating system (Junos OS) preinstalled. As new features and software fixes becomeavailable, youmust upgrade your software to use them. You can also downgrade JunosOS 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



Chapter 1: Software Installation Overview

Overview of the Software Installation Process

An EX Series switch is delivered with Junos OS preinstalled. When you connect power tothe switch, it starts (boots) up from the installed software.

You upgrade Junos OS on an EX Series switch by copying a software package to yourswitch or another system on your local network, then use either the J-Web interface orthe 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 thenew current configuration to a secondary device.

During a successful upgrade, the upgrade package removes all files from /var/tmp andcompletely reinstalls the existing software. It retains configuration files, and similarinformation, such as secure shell and host keys, from the previous version. The previoussoftware package is preserved in a separate disk partition, and you canmanually revertback to it if necessary. If the software installation fails for any reason, such as loss ofpowerduring the installationprocess, thesystemreturns to theoriginallyactive installationwhen you reboot.

Software Package Security

All Junos OS releases are delivered in signed packages that contain digital signatures toensure official Juniper Networks software. For more information about signed softwarepackages, 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 andmanagethe unit as a single device, called a Virtual Chassis. The Virtual Chassis operates as asingle network entity composed of members. Eachmember of a Virtual Chassis runs aJunos OS package. Supported Virtual Chassis include EX4200 Virtual Chassis, EX4500Virtual Chassis, mixed EX4200 and EX4500 Virtual Chassis, or EX8200 Virtual Chassis.

For easeofmanagement, aVirtualChassisprovides flexiblemethods toupgradesoftwarereleases. You can deploy a new software release to all members of a Virtual Chassis orto only a particular member.

Youcanalsoupgrade thesoftwareonanEX8200VirtualChassis usingnonstopsoftwareupgrade (NSSU). Unlike a standard software upgrade, NSSU does not require a rebootof the Virtual Chassis. Instead, it takes advantage of graceful Routing Engine switchoverand nonstop active routing (NSR) to ensure no disruption to the control plane during theupgrade. You canminimize disruption to network traffic by defining link aggregationgroups (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 theother line cards while a line card is being upgraded.



Installing Software on EX8200 Switches with Redundant Routing Engines

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

Perform a nonstop software upgrade (NSSU)An NSSU upgrades both RoutingEngines with a single command and with aminimum of network disruption. An NSSUtakes advantage of graceful Routing Engine switchover (GRES) and nonstop activerouting (NSR) toensurenodisruption to thecontrol plane. Youcanminimizedisruptionto network traffic by defining link aggregation groups (LAGs) such that the memberlinks of each LAG reside on different line cards. The line cards are upgraded one at atime, so that traffic continues to flow through the other line cards while a line card isbeing upgraded.

You cannot use NSSU to downgrade the software running on a switch.

For more information about NSSU, see Understanding Nonstop Software Upgrade onEX Series Switches.

Upgrade each Routing Engine manuallyYou can perform a Junos OS installation oneach Routing Engine separately, starting with the backup Routing Engine. You can usethis procedure todowngrade the software runningonaswitch. See InstallingSoftwareon 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 DHCPmessage exchange processtodownloadand install softwarepackages.Userscandefineapath toasoftwarepackageon the DHCP server and then the DHCP server communicates this path to EX Seriesswitches acting as DHCP clients as part of the DHCPmessage exchange process. TheDHCP clients that have been configured for automatic software download receive thesemessagesand,when thesoftwarepackagename in theDHCPservermessage isdifferentfrom that of the software package that booted the DHCP client switch, download andinstall the software package. See Upgrading Software Using Automatic SoftwareDownload 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 nosoftware installed, you can use the recovery installation procedure to install the softwareon the switch. See Troubleshooting Software Installation on page 43.

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


Downloading Software Packages from Juniper Networks on page 17

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

InstallingSoftwareonanEXSeriesSwitchwithaSingleRoutingEngine (CLIProcedure)on page 18



Installing Software on an EX Series Switch with Redundant Routing Engines (CLIProcedure) 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 JuniperNetworks EX Series Ethernet Switch by copying a software package to your switch oranother system on your local network, then install the new software package on theswitch.

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, withm representing the major release number and nrepresenting the minor release numberfor example, 9.5.

Z indicates the type of software release, where R indicates released software and Bindicates beta-level software.

x.y represents the version of the major software release (x) and an internal trackingnumber (y)for example, 1.6.

domestic-signed is appended toall EXSeriespackagenames. Formost Junospackages,domestic is used for theUnitedStatesandCanadaandexport forworldwidedistribution.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







Understanding SystemSnapshot on EX Series Switches

You can create copies of the software running a Juniper Networks EX Series EthernetSwitch using the system snapshot feature. The system snapshot feature takes asnapshot of the files currently used to run the switchthe complete contents of the/configand /vardirectories,which include the running JuniperNetworks Juniper operating



system (Junos OS), the active configuration, and the rescue configurationand copiesall of these files intoanalternate (internal,meaning internal flash, or anexternal,meaningUSB flash) memory source. You can then use this snapshot to boot the switch at thenext bootup or as a backup boot option.

You can only use snapshots to move files to external memory if the switch was bootedfrom internalmemory, or tomove files to internalmemory if the switchwas booted fromexternal memory. You cannot create a snapshot in the memory source that booted theswitch even if the snapshot is being created on a different partition in the samememorysource.

Snapshots are particularly useful for moving files onto USB flash drives. You cannot usethe copy command or any other file-moving technique to move files from an internalmemory source to USBmemory on the switch.

System snapshots on EX Series switches have the following limitations:

You cannot use snapshots tomove files to any destination outside of the switch otherthan an installed external USB flash drive or to move files between switches that aremembers of the same virtual chassis.

Snapshot commands, like other virtual chassis commands, are always executed on alocal switch. In cases where a different member switches of the same virtual chassisrequests the snapshot, the snapshot command is pushed to the VCmember creatingthe snapshot, executed, and the output is then returned to the switch that initiated theprocess. For instance, if the command to createanexternal snapshot on virtual chassismember 3 is entered from virtual chassis member 1, the snapshot of internal memoryon virtual chassis member 3 is taken on external memory on virtual chassis member3. The output of the process is seen from virtual chassis member 1. No files movebetween the switches.



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



Understanding Resilient Dual-Root Partitions on Switches

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

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

Provides separation of the root Junos OS file system from the /var file system. Ifcorruptionoccurs in the /var file system(ahigher probability than in the root file systemdue to thegreater frequency in /varof readsandwrites), the root file system is insulatedfrom the corruption.

NOTE: For instructions on upgrading to release that supports resilientdual-root partitions froma release that does not, see theReleaseNotes. Theprocedure for upgrading to a resilient dual-root partition release is differentfrom the normal upgrade procedure.

This topic covers:

Resilient Dual-Root Partition Scheme (JunosOSRelease 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 PartitionReleases 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 witha root partition scheme that is optimized for resiliency, as shown in Table 2 on page 10.

Table 2: Resilient Dual-Root Partition Scheme

Slice 4Slice 3Slice 2Slice 1

s4ds3ds3es2as1a

/config/var/tmp/var/

(root Junos OS )

/

(root Junos OS )

In the resilient dual-root partition scheme, the /var file system is contained in a separateslice from the root file systems, the /config directory is contained in its own slice, andswitches 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 filesystems and is therefore more likely to have corruption issues, is isolated from the rootdirectories and the /config directory. If the switch fails to boot, the system automaticallyboots from the alternate root partition. (If the switch fails to boot from the active rootpartition and instead boots from the alternate root partition, an alarm is triggered.)



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 3Slice 2Slice 1

s3es3ds2fs2as1fs1a

/config/var/tmp(empty untilinitialsoftwareupgrade)

(empty untilinitialsoftwareupgrade)

/var/

(root JunosOS)

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

UnderstandingUpgradingorDowngradingBetweenResilientDual-RootPartitionReleases and Earlier Releases

Upgrading from Release 10.4R2 or earlier to Release 10.4R3 or later differs from otherupgrades in two important ways:

Youmust install a new loader software package in addition to installing the new JunosOS 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 notsaved or restored during an upgrade from a nonresilient dual-root partitionrelease to a release that supports resilient dual-root partitions.

We recommend that you also save your /config files and any important logfiles to an external medium because if there is a power interruption duringthe upgrade process, they could be lost.


Resilient Dual-Root Partitions Frequently Asked Questions on page 47



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,youmust purchase, install, andmanage separate software licenses. If the switch has theappropriate 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, youmust install aunique license key (a combination of the authorization code and the switchs serialnumber) on each switch.

ForaVirtualChassisdeployment, two licensekeysare recommendedfor redundancyonefor 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 alwaysXRE200 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 inthe linecard role or for the redundant Routing Engine (RE) modules or the redundantSwitch Fabric and Routing Engine (SRE) modules in an EX8200member 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 EX8200Switches on page 14

Features Requiring a License on EX3300 Switches on page 14

LicenseWarning 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 thechassis serial number of your switch; you can obtain the serial number by running theshow chassis hardware command.



NOTE: You are required to provide a 12-digit serial number when purchasinga license foranXRE200ExternalRoutingEngine inanEX8200VirtualChassis.

The serial number listed on the XRE200 External Routing Engine serial IDlabel is 16 digits long. Use the last 12 digits of the 16-digit serial number topurchase the license.

Youcanusetheshowchassishardwarecommandoutput todisplay the 12-digitserial number of the XRE200 External Routing Engine to use when youpurchase the license.

Features Requiring a License on EX2200 Switches

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

Bidirectional forwarding detection (BFD)

Connectivity fault management (IEEE 802.1ag)

IGMP (InternetGroupManagementProtocol) version 1 (IGMPv1), IGMPv2, and IGMPv3

OSPFv1/v2 (with 4 active interfaces)

Protocol Independent Multicast (PIM) densemode, PIM source-specific mode, PIMsparse mode

Q-in-Q tunneling (IEEE 802.1ad)

Real-time performancemonitoring (RPM)

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

Table 4: Junos OS EFL Part Number on EX2200 Switches

EFL Part NumberSwitch Model

EX-12-EFLEX2200-C-12P-2GEX2200-C-12T-2G

EX-24-EFLEX2200-24T-4GEX2200-24P-4G

EX-48-EFLEX2200-48T-4GEX2200-48P-4G



FeaturesRequiringaLicenseonEX3200,EX4200,EX4500,EX6200andEX8200Switches

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

Border Gateway Protocol (BGP) andmultiprotocol BGP (MBGP)

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

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

MPLSwith RSVP-based label-switched paths (LSPs) and MPLS-based circuitcross-connects (CCCs)

Table 5 on page 14 lists the AFLs you can purchase for EX Series switch models. If youhave 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

AFL Part NumberSwitch Model

EX-24-AFLEX3200-24PEX3200-24TEX4200-24FEX4200-24PEX4200-24T

EX-48-AFLEX3200-48PEX3200-48TEX4200-48FEX4200-48PEX4200-48T

EX-48-AFLEX4500-40F-BFEX4500-40F-BF-CEX4500-40F-FBEX4500-40F-FB-C

EX6200-AFLEX6200

EX8208-AFLEX8208

EX8216-AFLEX8216

Features Requiring a License on EX3300 Switches

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

OSPFv1/v2 (with 4 active interfaces)

Q-in-Q tunneling (IEEE 802.1ad)



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

Table 6: Junos OS EFL Part Number on EX3300 Switches

EFL Part NumberSwitch Model

EX-24-EFLEX3300-24TEX3300-24PEX3300-24T-DC

EX-48-EFLEX3300-48T/PEX3300-48PEX3300-48T-DC

LicenseWarningMessages

For using features that require a license, youmust install and configure a license key. Toobtain 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 receivewarnings when you try to commit the configuration:

[edit protocols] 'bgp' warning: requires 'bgp' licenseerror: commit failed: (statements constraint check failed)

The systemgenerates system log (syslog) alarmmessages notifying you that the featurerequires a licensefor example:

Sep 3 05:59:11 craftd[806]: Minor alarm set, BGP Routing Protocol usage requires a licenseSep 3 05:59:11 alarmd[805]: Alarm set: License color=YELLOW, class=CHASSIS, reason=BGP Routing Protocol usage requires a licenseSep 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 alarms1 alarm currently activeAlarm time Class Description2009-09-03 06:00:11 UTC Minor 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



License Key Components for the EX Series Switch

When you purchase a license for a Junos OS feature that requires a separate license, youreceive a license key.

A license key consists of two parts:

License IDAlphanumeric string thatuniquely identifies the licensekey.Whena licenseis 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 licenseID, and the trailing block of data is the license data:

Junos204558 aeaqea qmijhd amrqha ztfmbu gqzama uqcedsra32zr lsevik ftvjed o4jy5u fynzzj mgviylkgioyf ardb5g sj7wnt rsfked wbjf5a sg

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


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



CHAPTER 2

Installing Junos OS


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



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 upgradesoftware on your EX Series switch.

Beforeyoubegin todownloadsoftwareupgrades, ensure that youhavea JuniperNetworksWebaccountandavalid support contract. Toobtainanaccount, complete the registrationform at the Juniper Networks website: https://www.juniper.net/registration/Register.jsp.

To download software upgrades from Juniper Networks:

1. Using aWeb browser, follow the links to the download URL on the Juniper Networkswebpage. For EX Series, there are not separate software packages for Canada theU.S. and other locations. Therefore, select Canada and U.S. Version regardless ofyour location:

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

2. Log in to the Juniper Networks authentication system using the username (generallyyour e-mail address) and password supplied by Juniper Networks representatives.

3. Using the J-Web interface or theCLI, select the appropriate software package for yourapplication. See Junos OS Package Names on page 8.

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






InstallingSoftwareonanEXSeriesSwitchwithaSingleRoutingEngine(CLIProcedure)

You can use this procedure to upgrade Junos OS on an EX Series switch with a singleRouting Engine, including an individual member of an EX4200 Virtual Chassis or allmembers of an EX4200 Virtual Chassis, or an EX8200 switch using a single RoutingEngine. To upgrade software on an EX8200 switch running two Routing Engines, seeInstalling Software on an EX Series Switch with Redundant Routing Engines (CLIProcedure) on page 19 or Upgrading Software on an EX8200 Standalone Switch UsingNonstop 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 Packagesfrom Juniper Networks on page 17.

2. (Optional) Back up the current software configuration to a second storage option.See the JunosOS InstallationandUpgradeGuide for instructionsonperforming this task.

3. (Optional) Copy the software package to the switch. We recommend that you useFTP to copy the file to the /var/tmp directory.

This step is optional because Junos OS can also be upgraded when the softwareimage is storedata remote location. These instructionsdescribe the softwareupgradeprocess for both scenarios.

4. Install the new package on the switch:

user@switch> request system software add packageReplace packagewith 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 optionalmember option to install the software package on only onemember of an EX4200 Virtual Chassis:

user@switch> request system software add sourcemembermember-id reboot

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



NOTE: To abort the installation, do not reboot your device; instead, finishthe installation and then issue the request system software deletepackage.tgz command, where package.tgz is, for example,jinstall-ex-8200-10.2R1.8-domestic-signed.tgz. This is your last chance tostop 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 softwareis properly installed:

user@switch> show version






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

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

NOTE: If your EX8200 switch is running Junos OS Release 10.4 or later, youcan upgrade the software packages on both Routing Engines with a singlecommand andwithminimal network disruption by using nonstop softwareupgrade (NSSU) instead of this procedure. See Upgrading Software on anEX8200 Standalone Switch Using Nonstop Software Upgrade (CLIProcedure).

WARNING: If graceful routing engine switchover (GRES) or nonstop activerouting (NSR) is enabled when you initiate a software installation, thesoftware does not install properly. Make sure you disable GRES before youbegin the software installation by using the deactivate chassis redundancygraceful-switchover command in configurationmode. If GRES is enabled, itwill be removedwith the redundancy command. By default, NSR is disabled.If NSR is enabled, remove the nonstop-routing statement from the [editrouting-options] hierarchy level to disable it.


Chapter 2: Installing Junos OS

To upgrade the software package on an EX6200 switch or an EX8200 switch with oneinstalled Routing Engine, see Installing Software on an EX Series Switch with a SingleRouting Engine (CLI Procedure) on page 18.

To upgrade redundant Routing Engines, you first install the new Junos OS release on thebackupRoutingEnginewhile keeping thecurrently running softwareversionon themasterRouting Engine. After making sure that the new software version is running correctly onthe 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. ReturningRoutingControl to theDefaultMasterRoutingEngine (Optional)onpage23

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, seeConnecting 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 OSRelease 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



5. Save the configuration change on both Routing Engines:

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

NOTE: To ensure themost recent configuration changes are committedbefore the software upgrade, perform this step even if nonstop activerouting 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 JunosOS InstallationandUpgradeGuide for instructionsonperforming this task.

Installing Software on the Backup Routing Engine

After you have prepared the switch for software installation, install the software on thebackup Routing Engine. During the installation, the master Routing Engine continuesoperations, minimizing the disruption to network traffic.

1. Download the software by following the procedures in Downloading SoftwarePackages from Juniper Networks on page 17.

2. Copy the software package to the switch. We recommend that you use FTP to copythe 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, finishthe installation and then issue the request system software deletepackage.tgz command, where package.tgz is, for example,jinstall-ex-8200-10.2R1.8-domestic-signed.tgz. This is your last chance tostop the installation.

5. Reboot to start the new software:

user@switch> request system rebootReboot the system? [yes, no] (no) yes

NOTE: Youmust reboot the switch to load the new installation of theJunos OS.



6. After the reboot has completed, log in and verify the new version of the software isproperly 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 themaster 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, thisswitchover causes all line cards in the switch to reload. All network trafficpassing through these line cards is lost during the line card reloads.

user@switch> request chassis routing-enginemaster switch

3. Verify that thedefault backupRoutingEngine (shownasslot 1 in thecommandoutput)is now themaster Routing Engine:

user@switch> show chassis routing-engine

You will see:

Routing Engine status:Slot 0:Current state BackupElection priority Master (default)

Routing Engine status:Slot 1:Current state MasterElection priority 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 rebootReboot the system? [yes, no] (no) yes

Whenthe rebootcompletes, thepromptwill reappear.Wait for thisprompt to reappearbefore 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 Engineswitchovers to occur without loss of any network traffic.



8. Re-enable nonstop active routing:

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

NOTE: Automatic commit synchronization is a requirement for nonstopactive routing. If you have not yet enabled it, do so with the set systemcommit 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 themaster RoutingEngine at the beginning of the procedure (the default master Routing Engine), performthe next task.

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

The switch canmaintain normal operations with the Routing Engine in slot 1 acting asthe master Routing Engine after the software upgrade, so only perform this task if youwant 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-enginemaster switch

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

user@switch> show chassis routing-engine

You will see:

Routing Engine status:Slot 0:Current state MasterElection priority Master (default)

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



Upgrading Software on an EX8200 Standalone Switch Using Nonstop SoftwareUpgrade (CLI Procedure)






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

You can upgrade software packages on a single fixed-configuration switch, on anindividual 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 orHTTP, 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 Packagesfrom Juniper Networks on page 17.

2. Log in to the Juniper Networks authentication system using the username (generallyyour e-mail address) and password supplied by Juniper Networks representatives.

3. In the J-Web interface, selectMaintain > Software > Install Package.

4. On the Install Remote page, enter information into the fields described in Table 7 onpage 24.

5. Click Fetch and Install Package. The software is activated after the switch hasrebooted.

Table 7: Install Remote Summary

Your ActionFunctionField

Type the full address of the software packagelocation on the FTP or HTTP serverone of thefollowing:

ftp://hostname/pathname/package-namehttp://hostname/pathname/package-name

Specifies the FTP or HTTP server, file path, andsoftware package name.

Package Location(required)

Type the username.Specifies the username, if the server requiresone.

User

Type the password.Specifies the password, if the server requiresone.

Password

Check the box if you want the switching platform toreboot automatically when the upgrade is complete.

If this box is checked, the switching platform isautomatically rebooted when the upgrade iscomplete.

Reboot If Required



Installing Software Upgrades by Uploading Files

To install software upgrades by uploading files:

1. Download the software package.

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

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

4. ClickUpload and Install Package. The software is activated after the switchingplatform has rebooted.

Table 8: Upload Package Summary

Your ActionFunctionField

Type the location of the software package, or clickBrowse to navigate to the location.

Specifies the location of the softwarepackage.

File to Upload(required)

Select the check box if you want the switchingplatform to reboot automatically when the upgradeis complete.

Specifies that the switching platform isautomatically rebooted when the upgradeis complete.

Reboot If Required





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, selectMaintain > Reboot.

2. Select one:

Reboot ImmediatelyReboots the switching platform immediately.

Reboot in number ofminutesReboots the switch in the number of minutes fromnow that you specify.

Rebootwhen the systemtime ishour:minuteReboots the switch at the absolutetime that you specify, on the current day. Youmust select a 2-digit hour in 24-hourformat and a 2-digit minute.

Halt ImmediatelyStops the switching platform software immediately. After theswitching platform software has stopped, you can access the switching platformthrough the console port only.



3. (Optional) In the Message box, type amessage to be displayed to any users on theswitching platform before the reboot occurs.

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

5. ClickOK to confirm the operation.

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

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

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


Starting the J-Web Interface



CHAPTER 3

Registering the Switch, Booting theSwitch, Upgrading Software, andManaging 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 requesttechnical assistance as and when required. To register an EX Series switch:

1. In the J-Web interface, selectMaintain > Customer Support > Product Registration.

Note the serial number that is displayed.

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


EX Series Switch Software Features Overview

Booting the Switch

Booting an EX Series Switch Using a Software Package Stored on a USB FlashDrive on page 28

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


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

There are twomethods of getting Junos OS onto a USB flash drive before using thesoftware to boot the switch. You can pre-install the software onto the USB flash drivebefore inserting theUSBflashdrive into theUSBport, or youcanuse thesystemsnapshotfeature to copy files from internal switch memory to the USB flash drive.

Tomove files into USB flash memory using a system snapshot and use those files toboot the switch, see Creating a Snapshot and Using It to Boot an EX Series Switch onpage 29. We recommend that you use this method to boot the switch from a USB flashdrive if your switch is running properly.

If you need to pre-install the software onto the USB flash drive, you can use themethoddescribed in this topic. Pre-installing the Junos OS onto a USB flash drive to boot theswitch can be done at any time and is particularly useful when the switch boots to theloader prompt because the switch cannot locate the Junos OS in internal flashmemory.

Ensure that you have the following tools and parts available to boot the switch from aUSB flash drive:

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

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

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

1. Download the Junos OS package that you would like to place onto the EX Seriesswitch from the Internet onto theUSB 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>) isdisplayed. The loader script startswhen the JunosOS loads but the CLI is notworkingfor 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 USBflash drive. The JunosOSpackage on a flash drive is commonly stored in the root driveas the only filefor example, file:///jinstall-ex-4200-9.4R1.5-domestic-signed.tgz.






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 USBport location.

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


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 EXSeries switchthe complete contents of the /config and /var directories, which includethe running Juniper Networks Junos OS, the active configuration, and the rescueconfigurationand copies all of these files into an alternate (internal, meaning internalflash, or an external, meaning USB flash) memory source. You can then use thesesnapshots 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 theSwitch 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 filesstored in internal memory.

Ensure that you have the following tools and parts available before creating a snapshoton a USB Flash drive:

A USB flash drive that meets the EX Series switch USB port specifications. See USBPort 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 partitionmedia external slice 1

NOTE: This example uses the partition option. If you have already createda 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 snapshotstored on theUSB flash drive. If you created the snapshot as a backup, do not performthis step.

To reboot the switch using the most recently created snapshot:

user@switch> request system rebootmedia external


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

To reboot the switch using a snapshot in a specific partition on the USB flash drive:

user@switch> request system rebootmedia external slice 1

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

A snapshot can be created on internalmemory after a switch is booted using files storedin 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 paritionmedia internal slice 1

NOTE: This example uses the partition option. If you have already createda 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 newlycreated 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 rebootmedia internal

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

user@switch> request system rebootmedia internal slice 1


Verifying That a System SnapshotWas 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 SeriesSwitches on page 30

Upgrading Software Using Automatic Software Download on EX Series Switches

The automatic software download feature uses the DHCPmessage exchange processto download and install software packages. You configure the automatic softwaredownload feature on EX Series switches acting as DHCP clients. Youmust enableautomatic software download on the EX Series switch before the software upgrade canoccur.

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

If you enable automatic software download, the DHCP client EX Series switch comparesthe software package name in the DHCP server message to the name of the softwarepackage 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 DHCPserver message.

Before you upgrade software using automatic software download, ensure that you haveconfigured DHCP services for the switch, including configuring a path to a boot serverand a boot file. See the Junos OS System Basics Configuration Guide

book software ex series software installation

Documents