Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SERVICE AVAILABILITY CONFIGURATION GUIDE... User manual

JunosE™ Software for
E Series™ Broadband
Services Routers
Service Availability Configuration Guide
Release
11.3.x
Published: 2010-10-08
Copyright © 2010, Juniper Networks, Inc.

Juniper Networks, Inc.
1194 North Mathilda Avenue
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.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are
owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,
6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
JunosE™ Software for E Series™ Broadband Services Routers Service Availability Configuration Guide
Release 11.3.x
Copyright © 2010, Juniper Networks, Inc.
All rights reserved. Printed in USA.
Writing: Krupa Chandrashekar, Sairam Venugopalan
Editing: Benjamin Mann
Illustration: Nathaniel Woodward
Cover Design: Edmonds Design
Revision History
October 2010—FRS JunosE 11.3.x
The information in this document is current as of the date listed in the revision history.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. The 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.
Copyright © 2010, Juniper Networks, Inc.ii

END USER LICENSE AGREEMENT
READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE.
BY DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS
CONTAINED HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO
BIND THE CUSTOMER) CONSENT TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED
HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS
REGARDING LICENSE TERMS.
1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or
Juniper Networks (Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred
to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable
license(s) for use of the Software (“Customer”) (collectively, the “Parties”).
2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for
which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by
Juniper in equipment which Customer purchased from Juniper or an authorized Juniper reseller. “Software” also includes updates, upgrades
and new releases of such software. “Embedded Software” means Software which Juniper has embedded in or loaded onto the Juniper
equipment and any updates, upgrades, additions or replacements which are subsequently embedded in or loaded onto the equipment.
3. License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer
a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the
following use restrictions:
a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by
Customer from Juniper or an authorized Juniper reseller.
b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units
for which Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access
Client software only, Customer shall use such Software on a single computer containing a single physical random access memory space
and containing any number of processors. Use of the Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines
(e.g., Solaris zones) requires multiple licenses, regardless of whether such computers or virtualizations are physically contained on a single
chassis.
c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may
specify limits to Customer’s use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints, concurrent
users, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of
separate licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide throughput,
performance, configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may restrict the use
of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software.
Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable licenses.
d. For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the
Software. Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not
extend or create an additional trial period by re-installing the Software after the 30-day trial period.
e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s
enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the
Steel-Belted Radius software to support any commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase
the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees
not to and shall not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized
copies of the Software (except as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the
Software, in any form, to any third party; (d) remove any proprietary notices, labels, or marks on or in any copy of the Software or any product
in which the Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper
equipment sold in the secondhand market; (f) use any ‘locked’ or key-restricted feature, function, service, application, operation, or capability
without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service, application,
operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the
iiiCopyright © 2010, Juniper Networks, Inc.

Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i)
use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that
the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking
of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly
provided herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper,
Customer shall furnish such records to Juniper and certify its compliance with this Agreement.
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper.
As such, Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence,
which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software
for Customer’s internal business purposes.
7. Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to
the Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance
of any right, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies
of the Software.
8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty
statement that accompanies the Software (the “Warranty Statement”). Nothing in this Agreement shall give rise to any obligation to support
the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services
agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA,
OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THIS AGREEMENT, THE SOFTWARE, OR ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. IN NO EVENT SHALL JUNIPER
BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE.
EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY
AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES
JUNIPER WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT
ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Juniper’s or its suppliers’
or licensors’ liability to Customer, whether in contract, tort (including negligence), breach of warranty, or otherwise, exceed the price paid
by Customer for the Software that gave rise to the claim, or if the Software is embedded in another Juniper product, the price paid by
Customer for such other product. Customer acknowledges and agrees that Juniper has set its prices and entered into this Agreement in
reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same reflect an allocation of risk between
the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss), and that the same
form an essential basis of the bargain between the Parties.
9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination
of the license granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related
documentation in Customer’s possession or control.
10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from
the purchase of the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction
shall be provided to Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All
payments made by Customer shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in
connection with such withholding taxes by promptly: providing Juniper with valid tax receipts and other required documentation showing
Customer’s payment of any withholding taxes; completing appropriate applications that would reduce the amount of withholding tax to
be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply with
all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related to any
liability incurred by Juniper as a result of Customer’s non-compliance or delay with its responsibilities herein. Customer’s obligations under
this Section shall survive termination or expiration of this Agreement.
11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any
applicable foreign agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such
restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the
Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without
an export license.
Copyright © 2010, Juniper Networks, Inc.iv

12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use,
duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS
227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer
with the interface information needed to achieve interoperability between the Software and another independently created program, on
payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use
such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products
or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement,
and such licensor or vendor shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party
software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent
portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such
portions publicly available (such as the GNU General Public License (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper
will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to three
years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA
94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL
at http://www.gnu.org/licenses/lgpl.html .
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws
principles. The provisions of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes
arising under this Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal
courts within Santa Clara County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer
with respect to the Software, and supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written
(including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an
authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained
herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing
by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity
of the remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the
Parties agree that the English version will govern. (For Canada: Les parties aux présentés confirment leur volonté que cette convention de
même que tous les documents y compris tout avis qui s'y rattaché, soient redigés en langue anglaise. (Translation: The parties confirm that
this Agreement and all related documentation is and will be in the English language)).
vCopyright © 2010, Juniper Networks, Inc.

Copyright © 2010, Juniper Networks, Inc.vi

Abbreviated Table of Contents
AbouttheDocumentation.........................................xix
Part 1 Chapters
Chapter1 Service Availability .................................................3
Chapter2 ManagingModuleRedundancy......................................9
Chapter 3 Managing Stateful SRP Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 4 Managing Stateful Line Module Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Chapter 5 Configuring a Unified In-Service Software Upgrade . . . . . . . . . . . . . . . . . . . 101
Chapter6 ConfiguringVRRP................................................149
Chapter 7 Managing Interchassis Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Part 2 Index
Index ...........................................................189
viiCopyright © 2010, Juniper Networks, Inc.

Copyright © 2010, Juniper Networks, Inc.viii
JunosE 11.3.x Service Availability Configuration Guide

Table of Contents
AbouttheDocumentation.........................................xix
E Series and JunosE Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . xix
Audience..........................................................xix
E Series and JunosE Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . xix
ObtainingDocumentation............................................xxi
DocumentationFeedback............................................xxi
RequestingTechnicalSupport........................................xxi
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
OpeningaCasewithJTAC........................................xxii
Part 1 Chapters
Chapter1 Service Availability .................................................3
ServiceAvailabilityOverview...........................................3
Service Availability Versus High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Understanding Service Availability Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
ModuleRedundancy..............................................5
StatefulSRPSwitchover..........................................5
StatefulLineModuleSwitchover....................................5
UnifiedISSU ....................................................6
VRRP..........................................................6
InterchassisRedundancy..........................................6
Chapter2 ManagingModuleRedundancy......................................9
LineModuleRedundancyOverview.....................................9
Line Module Redundancy Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
ERX7xxModelsandERX14xxModels................................10
E120andE320Routers...........................................10
IOA Behavior When the Router Reboots . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Line Module Behavior When Disabling or Enabling IOAs . . . . . . . . . . . . . . 11
UnderstandingAutomaticSwitchover...................................12
Limitations of Automatic Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Understanding Reversion After Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
ConfiguringLineModuleRedundancy...................................13
ManagingLineModuleRedundancy....................................13
Example: Forcing the Router to Switch from Primary Line Module to Spare Line
Module ........................................................14
Interoperation of Redundancy and Stateful Switchover for Line Modules . . . . . . . 15
Understanding SRP Module Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Understanding Configuration of SRP Modules for Redundancy . . . . . . . . . . . . . . . 19
InstallingaRedundantSRPModule....................................20
ixCopyright © 2010, Juniper Networks, Inc.

ManagingSRPModuleRedundancy....................................21
Switching to the Redundant SRP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Determination of Redundancy Status for Line Modules and SRP Modules Using
StatusLEDs....................................................22
Monitoring Redundancy in Installed Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Monitoring Redundancy in Line Module and SRP Modules . . . . . . . . . . . . . . . . . . 27
Monitoring Redundancy Status on E320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chapter 3 Managing Stateful SRP Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
StatefulSRPSwitchoverOverview.....................................35
Stateful SRP Switchover Platform Considerations . . . . . . . . . . . . . . . . . . . . . . . . 36
Module Requirements ...........................................36
Stateful SRP Switchover Redundancy Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
FileSystemSynchronizationMode..................................37
HighAvailabilityMode............................................37
StatefulSRPSwitchoverStates.......................................38
DisabledState..................................................39
Initializing State ................................................40
ActiveState....................................................40
Pending State ..................................................41
Application Support for Stateful SRP Switchover . . . . . . . . . . . . . . . . . . . . . . . . . 42
ApplicationSupport.............................................42
Guidelines for Activating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
ActivatingHighAvailability............................................52
Guidelines for Deactivating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
DeactivatingHighAvailability.........................................53
Guidelines for Setting the IP Interface Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
SettingtheIPInterfacePriority........................................54
GuidelinesforUpgradingSoftware.....................................55
MonitoringtheRedundancyStatus.....................................56
Monitoring the Redundancy Status of Applications . . . . . . . . . . . . . . . . . . . . . . . . 59
MonitoringtheRedundancyHistory.....................................61
Monitoring the Redundancy Status of Line Modules . . . . . . . . . . . . . . . . . . . . . . . 62
Monitoring the Redundancy Status of SRP Modules . . . . . . . . . . . . . . . . . . . . . . . 63
Monitoring the Redundancy Switchover History . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
ClearingtheRedundancyHistory......................................65
Chapter 4 Managing Stateful Line Module Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Stateful Line Module Switchover Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Benefits of Stateful Line Module Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
1:1RedundancyModel...........................................69
Seamless Preservation of Subscriber Sessions . . . . . . . . . . . . . . . . . . . . . . . . 69
Stateful Line Module Switchover Platform Considerations . . . . . . . . . . . . . . . . . . 70
Guidelines for Configuring Stateful Line Module Switchover . . . . . . . . . . . . . . . . . 70
System Operations When Stateful Line Module Switchover Is Enabled . . . . . . . . 74
Stateful Line Module Configuration Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
High Availability Configured and Enabled on the Line Module . . . . . . . . . . . . 75
High Availability Configured and Disabled on the Line Module . . . . . . . . . . . . 76
High Availability Configured and the Switchover State Is Active or
Disabled ...................................................76
Copyright © 2010, Juniper Networks, Inc.x
JunosE 11.3.x Service Availability Configuration Guide

Rebooting of the System When Line Module High Availability Is
Configured .................................................76
StatefulSRPSwitchover.........................................76
LineModuleRedundancy.........................................77
UnifiedISSU....................................................77
Replacement of Line Modules When Stateful Line Module Switchover Is
Enabled .......................................................77
Reloading the Primary Line Module in Response to Failures . . . . . . . . . . . . . . 77
Reloading the Secondary Line Module in Response to Failures . . . . . . . . . . . 78
Disabling the Primary and Secondary Line Module Slots . . . . . . . . . . . . . . . . 78
Reloading the Router When Line Modules Enabled for HA Are Installed . . . . 78
Removing IOAs Without Powering Down from Line Modules . . . . . . . . . . . . . 78
Cold and Warm Switchovers of Line Modules In a High Availability Pair . . . . 78
Application Support for Stateful Line Module Switchover . . . . . . . . . . . . . . . . . . . 79
Policy Management .............................................79
QoS..........................................................80
Connection Manager and Queue Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
PPP ..........................................................80
L2TP..........................................................81
ForwardingController............................................81
MirroringSubsystem.............................................82
UnifiedISSU ...................................................82
ICCP..........................................................83
Stateful Line Module Switchover Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
StatelessSwitchoverMode.......................................83
HighAvailabilityMode...........................................83
Stateful Line Module Switchover States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Disabled State .................................................85
Initializing State ................................................86
ActiveState....................................................86
Guidelines for Activating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
ActivatingHighAvailability...........................................88
Guidelines for Deactivating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
DeactivatingHighAvailability.........................................89
Switching Over from a Primary Line Module to Secondary Line Module . . . . . . . . 90
Log Messages Generated for Stateful LM Switchover . . . . . . . . . . . . . . . . . . . . . . . 91
Log Messages Displayed During the Transition from Disabled State to Active
State ......................................................91
Log Messages Displayed During the Transition from Active State to Pending
orDisabledState............................................91
Log Messages Displayed During the Transition from Pending or Disabled
StatetoActiveState.........................................92
Log Messages Displayed During the Transition from Active or Pending State
toDisabledState............................................92
Log Messages Displayed for Stateful SRP and Line Module Switchover
WhenHAIsEnabled.........................................92
Log Messages Displayed for Stateful SRP and Line Module Switchover
WhenHAIsDisabled.........................................93
xiCopyright © 2010, Juniper Networks, Inc.
Table of Contents

Preservation of Statistics During Stateful Line Module Switchover . . . . . . . . . . . . 93
PPPAccountingStatistics........................................93
Policy Statistics ................................................94
Performance Impact and Scalability Considerations . . . . . . . . . . . . . . . . . . . . . . . 94
Use of Status LEDs to Monitor the High Availability States of Line Modules . . . . 95
Monitoring the Redundancy Status of Line Modules in a Specific Slot . . . . . . . . . 95
Monitoring the Redundancy History of Line Modules in a Specific Slot . . . . . . . . . 97
Chapter 5 Configuring a Unified In-Service Software Upgrade . . . . . . . . . . . . . . . . . . . 101
UnifiedISSUOverview..............................................102
Router Behavior During a Unified In-Service Software Upgrade . . . . . . . . . . 103
Unified ISSU Platform Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Hardware and Software Requirements Before Beginning a Unified ISSU . . . . . . 104
Hardware Requirements for Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Software Requirements for Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
UnifiedISSUTerms................................................106
UnifiedISSUReferences.............................................107
UnifiedISSUPhasesOverview........................................107
Unified ISSU Initialization Phase Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Application Data Upgrade on the Standby SRP Module . . . . . . . . . . . . . . . . 109
SNMPTraps...................................................110
Unified ISSU Upgrade Phase Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Exceptions During the Upgrade Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
VerificationsofRequirements.....................................112
UpgradeSetup.................................................112
LineModuleArming..........................................113
Line Module Control Plane Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
SRPModuleSwitchover......................................113
Line Module Forwarding Plane Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 114
Unified ISSU Service Restoration Phase Overview . . . . . . . . . . . . . . . . . . . . . . . . . 115
Application Support for Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Unexpected AAA Authentication and Authorization Behavior During Unified
ISSU .........................................................124
Unexpected ATM Behavior During Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . 124
ILMISessionsNotMaintained.....................................124
OAMCCEffectsonVCC.........................................124
OAM VC Integrity Verification Cessation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Port Data Rate Monitoring Cessation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
VC and VP Statistics Monitoring Halts Unified ISSU Progress . . . . . . . . . . . . 125
Unexpected DHCP Behavior During Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . 125
DHCP Packet Capture Halted on Line Modules . . . . . . . . . . . . . . . . . . . . . . . 125
Unexpected Denial-of-Service Protection Behavior During Unified ISSU . . . . . . 125
Unexpected Ethernet Behavior During Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . 126
ARP Packets Briefly Not Sent or Received . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
LinkAggregationInterruption.....................................126
PortDataRateMonitoringHalted..................................126
VLAN Statistics Monitoring Halts Unified ISSU Progress . . . . . . . . . . . . . . . . 126
Unexpected File Transfer Protocol Server Behavior During Unified ISSU . . . . . . . 127
Copyright © 2010, Juniper Networks, Inc.xii
JunosE 11.3.x Service Availability Configuration Guide

IS-IS Effects on Graceful Restart and Network Stability During Unified ISSU . . . 129
Configuring Graceful Restart Before Unified ISSU Begins . . . . . . . . . . . . . . . 129
Configuring Graceful Restart When BGP and LDP Are Configured . . . . . . . . 130
Routing Around the Restarting Router to Minimize Network Instability . . . . 130
Unexpected L2TP Failover of Established Tunnels During Unified ISSU . . . . . . . . 131
OSPF Effects on Graceful Restart and Network Stability During Unified ISSU . . 132
Configuring Graceful Restart Before Unified ISSU Begins . . . . . . . . . . . . . . . 132
Configuring Graceful Restart When BGP and LDP Are Configured . . . . . . . . 132
Configuring a Longer Dead Interval Than Normal . . . . . . . . . . . . . . . . . . . . . 132
Routing Around the Restarting Router to Minimize Network Instability . . . . 133
Unexpected Suspension of PIM During Unified ISSU . . . . . . . . . . . . . . . . . . . . . . 133
Unexpected Suspension of Subscriber Login and Logouts During Unified
ISSU .........................................................134
Subscriber Statistics Accumulation or Deletion . . . . . . . . . . . . . . . . . . . . . . . 134
Unexpected SONET and SDH Behavior During Unified ISSU . . . . . . . . . . . . . . . . 134
Unexpected T3 Behavior During Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Unavailability of TACACS+ Services During Unified ISSU . . . . . . . . . . . . . . . . . . . 135
Interruption in Traffic Forwarding for Layer 3 Routing Protocols During Unified
ISSU .........................................................135
Recommended Settings for Routing Protocol Timers During Unified ISSU . . . . . 138
Upgrading Router Software with Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Halt of Unified ISSU During Initialization Phase Overview . . . . . . . . . . . . . . . . . . 142
Halting Unified ISSU During Initialization Phase . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Halt of Unified ISSU During Upgrade Phase Overview . . . . . . . . . . . . . . . . . . . . . 143
Halting Unified ISSU During Upgrade Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Monitoring the Status of the Router During Unified ISSU . . . . . . . . . . . . . . . . . . . 144
Chapter6 ConfiguringVRRP................................................149
VRRPOverview....................................................149
VRRPPlatformConsiderations.......................................150
VRRPTerms.......................................................151
VRRPReferences...................................................151
VRRP Implementation in E Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
VRRPRouterElectionRules..........................................152
Example:BasicVRRPConfiguration...................................153
Example: Commonly Used VRRP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Example: VRRP Configuration Without the Real Address Owner . . . . . . . . . . . . . 155
BeforeYouConfigureVRRP..........................................156
ConfiguringVRRP..................................................157
ChangingtheObjectPriority.........................................159
Monitoring the Configuration of VRIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Monitoring the Configuration of VRRP Neighbors . . . . . . . . . . . . . . . . . . . . . . . . . 162
Monitoring the Statistics of VRRP Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Monitoring the Configuration of VRRP Tracked Objects . . . . . . . . . . . . . . . . . . . . 166
Chapter 7 Managing Interchassis Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
ICR Overview .....................................................169
ICRPlatformConsiderations..........................................171
InterfaceSpecifiers..............................................171
ICRTerms.........................................................172
xiiiCopyright © 2010, Juniper Networks, Inc.
Table of Contents

ICR References ....................................................172
ICRScalingConsiderations...........................................172
1:1 Subscriber Redundancy in a 4–Node ICR Cluster . . . . . . . . . . . . . . . . . . . 173
InteractionwithRADIUSforICR.......................................173
ICR Partition Accounting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
ConfiguringanICRPartition..........................................175
Configuring the Interface on Which the ICR Partition Resides . . . . . . . . . . . . . . . 176
Configuring VRRP Instances to Match ICR Requirements . . . . . . . . . . . . . . . . . . . 177
NamingICRPartitions...............................................178
Grouping ICR Subscribers Based on S-VLAN IDs . . . . . . . . . . . . . . . . . . . . . . . . . 178
Grouping ICR Subscribers Based on VLAN IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Example: Configuring ICR Partitions That Group Subscribers by S-VLAN ID . . . . 180
Using RADIUS to Manage Subscribers Logging In to ICR Partitions . . . . . . . . . . . 182
Monitoring the Configuration of an ICR Partition Attached to an Interface . . . . . 183
Monitoring the Configuration of ICR Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Part 2 Index
Index ............................................................189
Copyright © 2010, Juniper Networks, Inc.xiv
JunosE 11.3.x Service Availability Configuration Guide

List of Figures
Part 1 Chapters
Chapter1 Service Availability .................................................3
Figure 1: JunosE Software Service Availability Layers . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter2 ManagingModuleRedundancy......................................9
Figure 2: SRP Module on ERX7xx Models and ERX14xx Models . . . . . . . . . . . . . . . 18
Figure 3: SRP Module on the E120 and E320 Routers . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 3 Managing Stateful SRP Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure4:HighAvailabilityStates.......................................39
Chapter 4 Managing Stateful Line Module Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 5: Stateful Line Module Switchover States . . . . . . . . . . . . . . . . . . . . . . . . . 85
Chapter6 ConfiguringVRRP................................................149
Figure6:BasicVRRPConfiguration....................................154
Figure 7: Commonly Used VRRP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 8: VRRP Configuration Without the Real Address Owner . . . . . . . . . . . . . 156
Chapter 7 Managing Interchassis Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure9:ICRDeployment............................................170
Figure 10: Sample 1:1 Subscriber Redundancy in a 4–Node ICR Cluster . . . . . . . . 173
xvCopyright © 2010, Juniper Networks, Inc.

Copyright © 2010, Juniper Networks, Inc.xvi
JunosE 11.3.x Service Availability Configuration Guide

List of Tables
AbouttheDocumentation.........................................xix
Table1:NoticeIcons.................................................xx
Table2:TextandSyntaxConventions...................................xx
Part 1 Chapters
Chapter2 ManagingModuleRedundancy......................................9
Table 3: Commands That Can Cause Automatic Switchover . . . . . . . . . . . . . . . . . 12
Table 4: Function of the Online and Redundant LEDs . . . . . . . . . . . . . . . . . . . . . . 22
Table 5: show environment Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table6:showhardwareOutputFields..................................29
Table 7: show redundancy Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 3 Managing Stateful SRP Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Table 8: Application Support for Stateful SRP Switchover . . . . . . . . . . . . . . . . . . 42
Table 9: show redundancy Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 10: show redundancy clients Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table 11: show redundancy history Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Table 12: show redundancy line-card Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 63
Table 13: show redundancy srp Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Table 14: show redundancy switchover-history Output Fields . . . . . . . . . . . . . . . . 65
Chapter 4 Managing Stateful Line Module Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 15: Module Configurations Supported for Stateful Switchover of LNS
Sessions ......................................................70
Table 16: show redundancy line-card slot slotNum Output Fields . . . . . . . . . . . . 96
Table 17: show redundancy history line-card slot slotNum Output Fields . . . . . . . 98
Chapter 5 Configuring a Unified In-Service Software Upgrade . . . . . . . . . . . . . . . . . . . 101
Table 18: Unified ISSU-Related Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Table 19: Router Response to Undesirable Events During the Upgrade Phase . . . 111
Table 20: Application Support for Unified In-Service Software Upgrades . . . . . . 116
Table 21: Behavior of Routing Protocols During a Unified In-Service Software
Upgrade ......................................................136
Table 22: Recommended Routing Protocol Timer Settings . . . . . . . . . . . . . . . . . 138
Table23:showissuOutputFields.....................................146
Chapter6 ConfiguringVRRP................................................149
Table24:VRRPDefinitions...........................................151
Table 25: show ip vrrp and show ip vrrp summary Output Fields . . . . . . . . . . . . . 160
Table 26: show ip vrrp neighbor Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Table 27: show ip vrrp statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
xviiCopyright © 2010, Juniper Networks, Inc.

Table 28: show ip vrrp tracked-objects Output Fields . . . . . . . . . . . . . . . . . . . . . 166
Chapter 7 Managing Interchassis Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Table29:ICRTerminology...........................................172
Table 30: show icr-partition Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Table 31: show icr-partitions Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Copyright © 2010, Juniper Networks, Inc.xviii
JunosE 11.3.x Service Availability Configuration Guide

About the Documentation
•E Series and JunosE Documentation and Release Notes on page xix
•Audience on page xix
•E Series and JunosE Text and Syntax Conventions on page xix
•Obtaining Documentation on page xxi
•Documentation Feedback on page xxi
•Requesting Technical Support on page xxi
E Series and JunosE Documentation and Release Notes
For a list of related JunosE documentation, see
http://www.juniper.net/techpubs/software/index.html .
If the information in the latest release notes differs from the information in the
documentation, follow the JunosE 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/.
Audience
This guide is intended for experienced system and network specialists working with
Juniper Networks E Series Broadband Services Routers in an Internet access environment.
E Series and JunosE Text and Syntax Conventions
Table 1 on page xx defines notice icons used in this documentation.
xixCopyright © 2010, Juniper Networks, Inc.

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
Table 2 on page xx defines text and syntax conventions that we use throughout the
E Series and JunosE documentation.
Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
•Issue the clock source command.
•Specify the keyword exp-msg.
Represents commands and keywords in text.Bold text like this
host1(config)#traffic class low-loss1Represents text that the user must type.Bold text like this
host1#show ip ospf 2
Routing Process OSPF 2 with Router
ID 5.5.0.250
Router is an Area Border Router
(ABR)
Represents information as displayed on your
terminal’s screen.
Fixed-width text like this
•There are two levels of access: user and
privileged.
•clusterId, ipAddress.
•Appendix A, System Specifications
•Emphasizes words.
•Identifies variables.
•Identifies chapter, appendix, and book
names.
Italic text like this
Press Ctrl + b.Indicates that you must press two or more
keys simultaneously.
Plus sign (+) linking key names
Syntax Conventions in the Command Reference Guide
terminal lengthRepresents keywords.Plain text like this
mask,accessListNameRepresents variables.Italic text like this
Copyright © 2010, Juniper Networks, Inc.xx
JunosE 11.3.x Service Availability Configuration Guide