Juniper EX9200 Series Specification sheet

High Availability Feature Guide for EX9200
Switches
Modified: 2017-02-23
Copyright © 2017, Juniper Networks, Inc.

Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
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.
High Availability Feature Guide for EX9200 Switches
Copyright © 2017, Juniper Networks, Inc.
All rights reserved.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the
year 2038. However, the NTP application is known to have some difficulty in the year 2036.
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.
Copyright © 2017, Juniper Networks, Inc.ii

Table of Contents
AbouttheDocumentation............................................xv
DocumentationandReleaseNotes.................................xv
SupportedPlatforms.............................................xv
UsingtheExamplesinThisManual.................................xv
MergingaFullExample.......................................xvi
MergingaSnippet...........................................xvi
Documentation Conventions .....................................xvii
DocumentationFeedback........................................xix
RequestingTechnicalSupport.....................................xix
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
OpeningaCasewithJTAC.....................................xx
Part 1 Configuring Graceful Routing Engine Switchover (GRES)
Chapter 1 Understanding How GRES Enables Uninterrupted Packet Forwarding
DuringaRoutingEngineSwitchover..................................3
Understanding Graceful Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . . . 3
Graceful Routing Engine Switchover Concepts . . . . . . . . . . . . . . . . . . . . . . . . . 3
Effects of a Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter2 GRESSystem Requirements........................................11
Graceful Routing Engine Switchover System Requirements . . . . . . . . . . . . . . . . . . 11
Graceful Routing Engine Switchover Platform Support . . . . . . . . . . . . . . . . . . 11
Graceful Routing Engine Switchover Feature Support . . . . . . . . . . . . . . . . . . . 12
Graceful Routing Engine Switchover DPC Support . . . . . . . . . . . . . . . . . . . . . 13
Graceful Routing Engine Switchover and Subscriber Access . . . . . . . . . . . . . . 13
Graceful Routing Engine Switchover PIC Support . . . . . . . . . . . . . . . . . . . . . . 14
Requirements for Routers with a Backup Router Configuration . . . . . . . . . . . . . . . 15
Chapter3 ConfiguringGRES..................................................17
Configuring Graceful Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Enabling Graceful Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring Graceful Routing Engine Switchover with Graceful Restart . . . . . 17
Synchronizing the Routing Engine Configuration . . . . . . . . . . . . . . . . . . . . . . . 18
Verifying Graceful Routing Engine Switchover Operation . . . . . . . . . . . . . . . . 19
ResettingLocalStatistics............................................20
Example: Configuring IS-IS for GRES with Graceful Restart . . . . . . . . . . . . . . . . . 20
iiiCopyright © 2017, Juniper Networks, Inc.

Part 2 Configuring Nonstop Bridging
Chapter 4 Understanding How Nonstop Bridging Preserves Layer 2 Protocol
Information During a Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . 25
NonstopBridgingConcepts...........................................25
Chapter 5 Nonstop Bridging System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Nonstop Bridging System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
PlatformSupport...............................................29
Protocol Support ...............................................29
Chapter6 ConfiguringNonstopBridging.......................................31
ConfiguringNonstopBridging..........................................31
EnablingNonstopBridging........................................31
Synchronizing the Routing Engine Configuration . . . . . . . . . . . . . . . . . . . . . . . 31
Verifying Nonstop Bridging Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
ResettingLocalStatistics.............................................32
Part 3 Configuring Nonstop Active Routing (NSR)
Chapter 7 Understanding How Nonstop Active Routing Preserves Routing Protocol
Information During a Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . 35
NonstopActiveRoutingConcepts......................................35
Chapter 8 Nonstop Active Routing System Requirements . . . . . . . . . . . . . . . . . . . . . . . 39
Nonstop Active Routing System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Nonstop Active Routing Platform and Switching Platform Support . . . . . . . 39
Nonstop Active Routing Protocol and Feature Support . . . . . . . . . . . . . . . . . . 41
Nonstop Active Routing BFD Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Nonstop Active Routing BGP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Nonstop Active Routing Layer 2 Circuit and VPLS Support . . . . . . . . . . . . . . 46
Nonstop Active Routing PIM Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Nonstop Active Routing MSDP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Nonstop Active Routing Support for RSVP-TE LSPs . . . . . . . . . . . . . . . . . . . 49
Chapter 9 Configuring Nonstop Active Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
ConfiguringNonstopActiveRouting....................................53
EnablingNonstopActiveRouting...................................53
Synchronizing the Routing Engine Configuration . . . . . . . . . . . . . . . . . . . . . . . 54
Verifying Nonstop Active Routing Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Tracing Nonstop Active Routing Synchronization Events . . . . . . . . . . . . . . . . . . . . 55
traceoptions.......................................................58
Example: Configuring Nonstop Active Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Part 4 Configuring Graceful Restart
Chapter 10 Understanding How Graceful Restart Enables Uninterrupted Packet
Forwarding When a Router Is Restarted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
GracefulRestartConcepts...........................................65
Graceful Restart for Aggregate and Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . 66
Copyright © 2017, Juniper Networks, Inc.iv
High Availability Feature Guide for EX9200 Switches

Graceful Restart and Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
BGP ..........................................................67
IS-IS..........................................................67
OSPFandOSPFv3..............................................67
PIMSparseMode...............................................68
RIPandRIPng..................................................69
Graceful Restart and MPLS-Related Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
LDP ..........................................................69
RSVP .........................................................70
CCCandTCC...................................................70
Graceful Restart and Layer 2 and Layer 3 VPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
GracefulRestartonLogicalSystems....................................71
Chapter 11 Graceful Restart System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Graceful Restart System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Chapter12 ConfiguringGracefulRestart........................................75
EnablingGracefulRestart............................................75
Configuring Routing Protocols Graceful Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
EnablingGracefulRestart.........................................76
Configuring Graceful Restart Options for BGP . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configuring Graceful Restart Options for ES-IS . . . . . . . . . . . . . . . . . . . . . . . . 78
Configuring Graceful Restart Options for IS-IS . . . . . . . . . . . . . . . . . . . . . . . . 78
Configuring Graceful Restart Options for OSPF and OSPFv3 . . . . . . . . . . . . . 79
Configuring Graceful Restart Options for RIP and RIPng . . . . . . . . . . . . . . . . . 81
Configuring Graceful Restart Options for PIM Sparse Mode . . . . . . . . . . . . . . 81
TrackingGracefulRestartEvents...................................82
Configuring Graceful Restart for MPLS-Related Protocols . . . . . . . . . . . . . . . . . . 83
Configuring Graceful Restart Globally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Configuring Graceful Restart Options for RSVP, CCC, and TCC . . . . . . . . . . . 83
Configuring Graceful Restart Options for LDP . . . . . . . . . . . . . . . . . . . . . . . . . 84
ConfiguringVPNGracefulRestart......................................85
Configuring Graceful Restart Globally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Configuring Graceful Restart for the Routing Instance . . . . . . . . . . . . . . . . . . 85
Configuring Logical System Graceful Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Enabling Graceful Restart Globally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Configuring Graceful Restart for a Routing Instance . . . . . . . . . . . . . . . . . . . . 87
ConfiguringGracefulRestart..........................................87
Example: Managing Helper Modes for OSPF Graceful Restart . . . . . . . . . . . . . . . 112
Part 5 Configuring Virtual Router Redundancy Protocol (VRRP)
Chapter 13 Understanding How the VRRP Router Failover Mechanism Prevents
NetworkFailures..................................................119
Understanding VRRP ...............................................119
JunosOSSupportforVRRPv3........................................121
JunosOSVRRPSupport.........................................121
IPv6 VRRP Checksum Behavioral Differences . . . . . . . . . . . . . . . . . . . . . . . . 122
VRRP Interoperability ...........................................122
UpgradingfromVRRPv2toVRRPv3................................123
vCopyright © 2017, Juniper Networks, Inc.
Table of Contents

FunctionalityofVRRPv3Features.................................125
VRRPv3Authentication......................................125
VRRPv3 Advertisement Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
UnifiedISSUforVRRPv3.....................................125
Improving the Convergence Time for VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Chapter14 ConfiguringVRRP ................................................129
Configuring the Startup Period for VRRP Operations . . . . . . . . . . . . . . . . . . . . . . 129
ConfiguringBasicVRRPSupport......................................130
Configuring VRRP Authentication (IPv4 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Configuring the Advertisement Interval for the VRRP Master Router . . . . . . . . . . 135
Modifying the Advertisement Interval in Seconds . . . . . . . . . . . . . . . . . . . . . 136
Modifying the Advertisement Interval in Milliseconds . . . . . . . . . . . . . . . . . . 136
Configuring a Backup Router to Preempt the VRRP Master Router . . . . . . . . . . . 138
Modifying the Preemption Hold-Time Value for the VRRP Master Router . . . . . . 138
Configuring the Asymmetric Hold Time for VRRP Routers . . . . . . . . . . . . . . . . . . 139
Configuring an Interface to Accept All Packets Destined for the Virtual IP Address
ofaVRRPGroup...............................................140
Configuring a Logical Interface to Be Tracked for a VRRP Group . . . . . . . . . . . . . 141
Configuring a Route to Be Tracked for a VRRP Group . . . . . . . . . . . . . . . . . . . . . . 143
Configuring Inheritance for a VRRP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Configuring the Silent Period to Avoid Alarms Due to Delay in Receiving VRRP
AdvertisementPackets..........................................146
Configuring Passive ARP Learning for Backup VRRP Routers . . . . . . . . . . . . . . . . 147
Enabling the Distributed Periodic Packet Management Process for VRRP . . . . . 148
Configuring VRRP to Improve Convergence Time . . . . . . . . . . . . . . . . . . . . . . . . . 149
ConfiguringVRRP..................................................150
ConfiguringVRRPforIPv6...........................................152
ConfiguringVRRPRouteTracking.....................................153
TracingVRRPOperations............................................154
Part 6 Performing Unified In-Service Software Upgrade (ISSU)
Chapter 15 Understanding How Unified ISSU Enables Software Upgrades with
MinimalTrafficDisruption.........................................159
Upgrading Routers Using Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Getting Started with Unified In-Service Software Upgrade . . . . . . . . . . . . . . . . . 159
Chapter 16 Unified ISSU System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
UnifiedISSUSystemRequirements....................................161
General Unified ISSU Considerations for All Platforms . . . . . . . . . . . . . . . . . 162
Unified ISSU Considerations for MX Series Routers . . . . . . . . . . . . . . . . . . . . 163
Unified ISSU Considerations for PTX Series Routers . . . . . . . . . . . . . . . . . . . 163
Unified ISSU Considerations for T Series Routers . . . . . . . . . . . . . . . . . . . . . 164
UnifiedISSUPlatformSupport....................................164
Unified ISSU Protocol Support for M Series, MX Series, and T Series Routers
andEX9200Switches.......................................166
UnifiedISSUFeatureSupport.....................................166
Copyright © 2017, Juniper Networks, Inc.vi
High Availability Feature Guide for EX9200 Switches

Unified ISSU PIC Support Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
PICConsiderations..........................................168
SONET/SDHPICs...........................................168
Fast Ethernet and Gigabit Ethernet PICs . . . . . . . . . . . . . . . . . . . . . . . . . 170
Channelized PICs ...........................................173
TunnelServicesPICs........................................174
ATMPICs..................................................174
SerialPICs.................................................175
DS3,E1,E3,andT1PICs......................................175
EnhancedIQPICs...........................................176
Enhanced IQ2 Ethernet Services Engine (ESE) PIC . . . . . . . . . . . . . . . . 176
Unified ISSU FPC Support on T4000 Routers . . . . . . . . . . . . . . . . . . . . . 177
Unified ISSU Support on MX Series 3D Universal Edge Routers . . . . . . . 177
Chapter17 PerformingaUnifiedISSU.........................................183
Best Practices for Performing a Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
BeforeYouBeginaUnifiedISSU......................................183
Verify That the Master and Backup Routing Engines Are Running the Same
SoftwareVersion...........................................185
BackUptheRouterSoftware.....................................185
Verify That Graceful Routing Engine Switchover and Nonstop Active Routing
AreConfigured.............................................186
Disable Inline Flow Monitoring Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Example:PerformingaUnifiedISSU...................................188
VerifyingaUnifiedISSU.............................................214
Managing and Tracing BFD Sessions During Unified ISSU Procedures . . . . . . . . 215
Part 7 Monitoring High Availability
Chapter18 RoutineMonitoring...............................................219
ResettingLocalStatistics............................................219
Tracing Restart Signaling-Based Helper Mode Events for OSPF Graceful
Restart.......................................................220
Verifying Graceful Restart Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Graceful Restart Operational Mode Commands . . . . . . . . . . . . . . . . . . . . . . 221
VerifyingBGPGracefulRestart....................................221
Verifying IS-IS and OSPF Graceful Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Verifying CCC and TCC Graceful Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Part 8 Troubleshooting
Chapter 19 Troubleshooting Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Troubleshooting Unified ISSU Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Part 9 Configuration Statements and Operational Commands
Chapter 20 Configuration Statements: GRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
graceful-switchover ................................................231
viiCopyright © 2017, Juniper Networks, Inc.
Table of Contents

Chapter 21 Configuration Statements: Graceful Restart . . . . . . . . . . . . . . . . . . . . . . . . . 233
disable ..........................................................234
graceful-restart (Enabling Globally) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
helper-disable (Multiple Protocols) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
maximum-helper-recovery-time......................................237
maximum-helper-restart-time (RSVP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
maximum-neighbor-reconnect-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
maximum-neighbor-recovery-time ...................................239
no-strict-lsa-checking..............................................240
notify-duration ....................................................241
reconnect-time ...................................................242
recovery-time.....................................................243
restart-duration ...................................................244
restart-time (BGP Graceful Restart) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
stale-routes-time..................................................246
traceoptions(Protocols)............................................247
Chapter 22 Configuration Statements: NSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
nonstop-bridging..................................................249
Chapter 23 Configuration Statements: NSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
synchronize.......................................................252
nonstop-routing...................................................254
traceoptions......................................................255
Chapter 24 Configuration Statements: VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
accept-data......................................................260
advertise-interval ..................................................261
asymmetric-hold-time..............................................262
authentication-key.................................................263
authentication-type................................................264
bandwidth-threshold...............................................265
delegate-processing (VRRP) ........................................266
failover-delay.....................................................266
fast-interval ......................................................267
global-advertisements-threshold.....................................268
hold-time(VRRP).................................................269
inet6-advertise-interval.............................................270
interface..........................................................271
preempt(VRRP)...................................................272
priority(ProtocolsVRRP)............................................273
priority-cost (VRRP) ...............................................274
priority-hold-time..................................................275
route(Interfaces)..................................................276
skew-timer-disable.................................................277
startup-silent-period ...............................................278
traceoptions(ProtocolsVRRP).......................................279
track(VRRP)......................................................281
version-3.........................................................282
virtual-address....................................................283
Copyright © 2017, Juniper Networks, Inc.viii
High Availability Feature Guide for EX9200 Switches

virtual-inet6-address...............................................283
virtual-link-local-address ...........................................284
vrrp-group .......................................................285
vrrp-inet6-group...................................................287
Chapter 25 Configuration Statements: Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
bfd .............................................................290
no-issu-timer-negotiation...........................................292
traceoptions(ProtocolsBFD)........................................293
Chapter26 OperationalCommands..........................................295
request system software in-service-upgrade (MX Series 3D Universal Edge
RoutersandEX9200Switches)..................................296
request system software validate in-service-upgrade . . . . . . . . . . . . . . . . . . . . . 313
showsystemswitchover............................................316
ixCopyright © 2017, Juniper Networks, Inc.
Table of Contents

Copyright © 2017, Juniper Networks, Inc.x
High Availability Feature Guide for EX9200 Switches

List of Figures
Part 1 Configuring Graceful Routing Engine Switchover (GRES)
Chapter 1 Understanding How GRES Enables Uninterrupted Packet Forwarding
DuringaRoutingEngineSwitchover..................................3
Figure 1: Preparing for a Graceful Routing Engine Switchover . . . . . . . . . . . . . . . . . 6
Figure 2: Graceful Routing Engine Switchover Process . . . . . . . . . . . . . . . . . . . . . . . 7
Part 2 Configuring Nonstop Bridging
Chapter 4 Understanding How Nonstop Bridging Preserves Layer 2 Protocol
Information During a Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . 25
Figure 3: Nonstop Bridging Switchover Preparation Process . . . . . . . . . . . . . . . . . 26
Figure 4: Nonstop Bridging During a Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Part 3 Configuring Nonstop Active Routing (NSR)
Chapter 7 Understanding How Nonstop Active Routing Preserves Routing Protocol
Information During a Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . 35
Figure 5: Nonstop Active Routing Switchover Preparation Process . . . . . . . . . . . . 36
Figure 6: Nonstop Active Routing During a Switchover . . . . . . . . . . . . . . . . . . . . . . 37
Part 4 Configuring Graceful Restart
Chapter12 ConfiguringGracefulRestart........................................75
Figure 7: Layer 3 VPN Graceful Restart Topology . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Part 5 Configuring Virtual Router Redundancy Protocol (VRRP)
Chapter 13 Understanding How the VRRP Router Failover Mechanism Prevents
NetworkFailures..................................................119
Figure8:BasicVRRP...............................................120
Part 6 Performing Unified In-Service Software Upgrade (ISSU)
Chapter17 PerformingaUnifiedISSU.........................................183
Figure 9: Unified ISSU Example Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
xiCopyright © 2017, Juniper Networks, Inc.

Copyright © 2017, Juniper Networks, Inc.xii
High Availability Feature Guide for EX9200 Switches

List of Tables
AbouttheDocumentation..........................................xv
Table1:NoticeIcons................................................xvii
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Part 1 Configuring Graceful Routing Engine Switchover (GRES)
Chapter 1 Understanding How GRES Enables Uninterrupted Packet Forwarding
DuringaRoutingEngineSwitchover..................................3
Table 3: Effects of a Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter2 GRESSystem Requirements........................................11
Table 4: Graceful Routing Engine Switchover Feature Support . . . . . . . . . . . . . . . 12
Part 3 Configuring Nonstop Active Routing (NSR)
Chapter 8 Nonstop Active Routing System Requirements . . . . . . . . . . . . . . . . . . . . . . . 39
Table 5: Nonstop Active Routing Platform Support . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 6: Nonstop Active Routing Protocol and Feature Support . . . . . . . . . . . . . . 41
Part 5 Configuring Virtual Router Redundancy Protocol (VRRP)
Chapter 13 Understanding How the VRRP Router Failover Mechanism Prevents
NetworkFailures..................................................119
Table 7: VRRPv2 to VRRPv3 Transition Steps and Events . . . . . . . . . . . . . . . . . . 124
Chapter14 ConfiguringVRRP ................................................129
Table 8: Interface State and Priority Cost Usage . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Part 6 Performing Unified In-Service Software Upgrade (ISSU)
Chapter 15 Understanding How Unified ISSU Enables Software Upgrades with
MinimalTrafficDisruption.........................................159
Table 9: Locating the Information You Need to Work With ISSU . . . . . . . . . . . . . 159
Chapter 16 Unified ISSU System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table 10: Unified ISSU Support for Dual Routing Engine Platforms . . . . . . . . . . . 165
Table 11: Unified ISSU PIC Support: SONET/SDH . . . . . . . . . . . . . . . . . . . . . . . . . 169
Table 12: Unified ISSU PIC Support: Fast Ethernet and Gigabit Ethernet . . . . . . . 171
Table 13: Unified ISSU PIC Support: Channelized . . . . . . . . . . . . . . . . . . . . . . . . . 173
Table 14: Unified ISSU PIC Support: Tunnel Services . . . . . . . . . . . . . . . . . . . . . . 174
Table 15: Unified ISSU PIC Support: ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Table 16: Unified ISSU Support: Enhanced IQ2 Ethernet Services Engine (ESE)
PIC ..........................................................176
xiiiCopyright © 2017, Juniper Networks, Inc.

Table 17: Unified ISSU Support: MX Series Router MPCs . . . . . . . . . . . . . . . . . . . . 178
Table 18: Unified ISSU Support: MX Series Router MICs . . . . . . . . . . . . . . . . . . . . 179
Chapter17 PerformingaUnifiedISSU.........................................183
Table 19: Routing Engine Status Before Upgrading . . . . . . . . . . . . . . . . . . . . . . . . 194
Table 20: Routing Engine Status After Upgrading and Rebooting Both Routing
Engines.......................................................197
Table 21: Routing Engine Status After Upgrading, Rebooting, and Switching
Mastership....................................................198
Table 22: Routing Engine Status Before Upgrading and Manually Rebooting the
BackupRoutingEngine..........................................201
Table 23: Routing Engine Status After Upgrading and Before Manually Rebooting
theBackupRoutingEngine......................................203
Table 24: Routing Engine Status After Upgrading, Manually Rebooting, and
BeforeSwitchingMastership.....................................205
Table 25: Routing Engine Status After Upgrading, Manually Rebooting, and
SwitchingMastership...........................................206
Table 26: Routing Engine Status Before Upgrading and Rebooting One Routing
Engine .......................................................207
Table 27: Routing Engine Status After Upgrading One Routing Engine and Before
Upgrading the Other Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Table 28: Routing Engine Status After Upgrading, Manually Rebooting, and
SwitchingMastership............................................213
Part 9 Configuration Statements and Operational Commands
Chapter26 OperationalCommands..........................................295
Table 29: show system switchover Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 318
Copyright © 2017, Juniper Networks, Inc.xiv
High Availability Feature Guide for EX9200 Switches

About the Documentation
•Documentation and Release Notes on page xv
•Supported Platforms on page xv
•Using the Examples in This Manual on page xv
•Documentation Conventions on page xvii
•Documentation Feedback on page xix
•Requesting Technical Support on page xix
Documentation and Release Notes
To obtain the most current version of all Juniper Networks®technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
If the information in the latest release notes differs from the information in the
documentation, follow the product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject
matter experts. These books go beyond the technical documentation to explore the
nuances of network architecture, deployment, and administration. The current list can
be viewed at http://www.juniper.net/books.
Supported Platforms
For the features described in this document, the following platforms are supported:
•EX Series
Using the Examples in This Manual
If you want to use the examples in this manual, you can use the load merge or the load
merge relative command. These commands cause the software to merge the incoming
configuration into the current candidate configuration. The example does not become
active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple
hierarchies), the example is a full example. In this case, use the load merge command.
xvCopyright © 2017, Juniper Networks, Inc.

If the example configuration does not start at the top level of the hierarchy, the example
isasnippet. In this case, use the load merge relative command. These procedures are
described in the following sections.
Merging a Full Example
To merge a full example, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration example into a
text file, save the file with a name, and copy the file to a directory on your routing
platform.
For example, copy the following configuration to a file and name the file ex-script.conf.
Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system {
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
2. Merge the contents of the file into your routing platform configuration by issuing the
load merge configuration mode command:
[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
Merging a Snippet
To merge a snippet, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration snippet into a text
file, save the file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file
ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory
on your routing platform.
commit {
file ex-script-snippet.xsl; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following
configuration mode command:
Copyright © 2017, Juniper Networks, Inc.xvi
High Availability Feature Guide for EX9200 Switches

[edit]
user@host# edit system scripts
[edit system scripts]
3. Merge the contents of the file into your routing platform configuration by issuing the
load merge relative configuration mode command:
[edit system scripts]
user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see CLI Explorer.
Documentation Conventions
Table 1 on page xvii defines notice icons used in this guide.
Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Indicates a situation that might result in loss of data or hardware damage.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
Indicates helpful information.Tip
Alerts you to a recommended use or implementation.Best practice
Table 2 on page xvii defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
To enter configuration mode, type the
configure command:
user@host> configure
Represents text that you type.Bold text like this
xviiCopyright © 2017, Juniper Networks, Inc.
About the Documentation

Table 2: Text and Syntax Conventions (continued)
ExamplesDescriptionConvention
user@host> show chassis alarms
No alarms currently active
Represents output that appears on the
terminal screen.
Fixed-width text like this
•A policy term is a named structure
that defines match conditions and
actions.
•Junos OS CLI User Guide
•RFC 1997, BGP Communities Attribute
•Introduces or emphasizes important
new terms.
•Identifies guide names.
•Identifies RFC and Internet draft titles.
Italic text like this
Configure the machine’s domain name:
[edit]
root@# set system domain-name
domain-name
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
Italic text like this
•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.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy levels;
or labels on routing platform
components.
Text like this
stub <default-metric metric>;Encloses optional keywords or variables.< > (angle brackets)
broadcast | multicast
(string1 |string2 |string3)
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.
| (pipe symbol)
rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the
same line as the configuration statement
to which it applies.
# (pound sign)
community name members [
community-ids ]
Encloses a variable for which you can
substitute one or more values.
[ ] (square brackets)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Identifies a level in the configuration
hierarchy.
Indention and braces ( { } )
Identifies a leaf statement at a
configuration hierarchy level.
; (semicolon)
GUI Conventions
•In the Logical Interfaces box, select
All Interfaces.
•To cancel the configuration, click
Cancel.
Represents graphical user interface (GUI)
items you click or select.
Bold text like this
Copyright © 2017, Juniper Networks, Inc.xviii
High Availability Feature Guide for EX9200 Switches

Table 2: Text and Syntax Conventions (continued)
ExamplesDescriptionConvention
In the configuration editor hierarchy,
select Protocols>Ospf.
Separates levels in a hierarchy of menu
selections.
>(bold right angle bracket)
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:
•Online feedback rating system—On any page of the Juniper Networks TechLibrary site
at http://www.juniper.net/techpubs/index.html, simply click the stars to rate the content,
and use the pop-up form to provide us with information about your experience.
Alternately, you can use the online feedback form at
http://www.juniper.net/techpubs/feedback/.
•E-mail—Send your comments to [e-mail]. Include the document
or topic name, URL or page number, and software version (if applicable).
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 Partner Support Service
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 policies—For 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 warranties—For product warranty information, visit
http://www.juniper.net/support/warranty/.
•JTAC hours of operation—The 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/
xixCopyright © 2017, Juniper Networks, Inc.
About the Documentation

•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:
http://kb.juniper.net/InfoCenter/
•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.
Copyright © 2017, Juniper Networks, Inc.xx
High Availability Feature Guide for EX9200 Switches