Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SERVICE AVAILABILITY CONFIGURATION GUIDE 2010-10-08, JUNOSE 11.3 Configuration Manual

JunosE™ Software for E Series™ Broadband Services Routers

Service Availability Configuration Guide

Release

11.3.x

Published: 2010-10-08

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

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.

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 BOUNDBY THIS AGREEMENT.IF YOU DO NOT OR CANNOTAGREE TO THE TERMSCONTAINED 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 (ifthe Customer’s principal officeis locatedoutside the Americas) (suchapplicable entitybeing referred to herein as“Juniper”), and (ii)the personor organization that originallypurchased from Juniper or anauthorized Juniper reseller theapplicable 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 paymentof the applicable fees and thelimitations andrestrictions setforth 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 limitsto Customer’s useof the Software. Suchlimits may restrictuse to amaximum numberof 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, toany thirdparty; (d) remove anyproprietary notices, labels,or markson or inany copyof 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 inthe secondhand market; (f)use any ‘locked’ orkey-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

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 havinga 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 statementthat accompanies the Software (the“Warranty Statement”).Nothing inthis Agreementshall give riseto 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 ORPROCUREMENT OFSUBSTITUTE GOODSOR SERVICES,OR FORANY SPECIAL, INDIRECT,OR CONSEQUENTIALDAMAGES ARISING OUTOF THIS AGREEMENT,THE SOFTWARE,OR ANY JUNIPEROR JUNIPER-SUPPLIED SOFTWARE. IN NOEVENT SHALLJUNIPER 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.

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 licensorof 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)).

Abbreviated Table of Contents

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Part 1 Chapters

Chapter 1 Service Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2 Managing Module Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Chapter 6 Configuring VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Chapter 7 Managing Interchassis Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Part 2 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

JunosE 11.3.x Service Availability Configuration Guide

Table of Contents

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

E Series and JunosE Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . xix

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

E Series and JunosE Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . xix

Obtaining Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

Part 1 Chapters

Chapter 1 Service Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Service Availability Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Service Availability Versus High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Understanding Service Availability Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Module Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Stateful SRP Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Stateful Line Module Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Interchassis Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2 Managing Module Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Line Module Redundancy Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Line Module Redundancy Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

ERX7xx Models and ERX14xx Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

E120 and E320 Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

IOA Behavior When the Router Reboots . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Line Module Behavior When Disabling or Enabling IOAs . . . . . . . . . . . . . . 11

Understanding Automatic Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Limitations of Automatic Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Understanding Reversion After Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Configuring Line Module Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Managing Line Module Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Installing a Redundant SRP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

JunosE 11.3.x Service Availability Configuration Guide

Managing SRP Module Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Switching to the Redundant SRP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Determination of Redundancy Status for Line Modules and SRP Modules Using

Status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Stateful SRP Switchover Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Stateful SRP Switchover Platform Considerations . . . . . . . . . . . . . . . . . . . . . . . . 36

Module Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Stateful SRP Switchover Redundancy Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

File System Synchronization Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

High Availability Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Stateful SRP Switchover States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Disabled State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Initializing State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Active State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Pending State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Application Support for Stateful SRP Switchover . . . . . . . . . . . . . . . . . . . . . . . . . 42

Application Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Guidelines for Activating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Activating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Guidelines for Deactivating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Deactivating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Guidelines for Setting the IP Interface Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Setting the IP Interface Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Guidelines for Upgrading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Monitoring the Redundancy Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Monitoring the Redundancy Status of Applications . . . . . . . . . . . . . . . . . . . . . . . . 59

Monitoring the Redundancy History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Monitoring the Redundancy Status of Line Modules . . . . . . . . . . . . . . . . . . . . . . . 62

Monitoring the Redundancy Status of SRP Modules . . . . . . . . . . . . . . . . . . . . . . . 63

Monitoring the Redundancy Switchover History . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Clearing the Redundancy History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 4 Managing Stateful Line Module Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Stateful Line Module Switchover Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Benefits of Stateful Line Module Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

1:1 Redundancy Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Table of Contents

Rebooting of the System When Line Module High Availability Is

Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Stateful SRP Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Line Module Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Forwarding Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Mirroring Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

ICCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Stateful Line Module Switchover Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Stateless Switchover Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

High Availability Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Stateful Line Module Switchover States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Disabled State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Initializing State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Active State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Guidelines for Activating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Activating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Guidelines for Deactivating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Deactivating High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Stateto Active

State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Log Messages Displayed During the Transition from Active State to Pending

or Disabled State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Log Messages Displayed During the Transition from Pending or Disabled

State to Active State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Log Messages Displayed During the Transition from Active or Pending State

to Disabled State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Log Messages Displayed for Stateful SRP and Line Module Switchover

When HA Is Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Log Messages Displayed for Stateful SRP and Line Module Switchover

When HA Is Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

JunosE 11.3.x Service Availability Configuration Guide

Preservation of Statistics During Stateful Line Module Switchover . . . . . . . . . . . . 93

PPP Accounting Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Unified ISSU Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Unified ISSU Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Unified ISSU References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Unified ISSU Phases Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Unified ISSU Initialization Phase Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Application Data Upgrade on the Standby SRP Module . . . . . . . . . . . . . . . . 109

SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Unified ISSU Upgrade Phase Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Exceptions During the Upgrade Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Verifications of Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Upgrade Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Line Module Arming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Line Module Control Plane Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

SRP Module Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

ILMI Sessions Not Maintained . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

OAM CC Effects on VCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Link Aggregation Interruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Port Data Rate Monitoring Halted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

VLAN Statistics Monitoring Halts Unified ISSU Progress . . . . . . . . . . . . . . . . 126

Unexpected File Transfer Protocol Server Behavior During Unified ISSU . . . . . . . 127

Table of Contents

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

Chapter 6 Configuring VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

VRRP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

VRRP Platform Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

VRRP Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

VRRP References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

VRRP Implementation in E Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

VRRP Router Election Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Example: Basic VRRP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Example: Commonly Used VRRP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Example: VRRP Configuration Without the Real Address Owner . . . . . . . . . . . . . 155

Before You Configure VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Configuring VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Changing the Object Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

ICR Platform Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Interface Specifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

ICR Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

JunosE 11.3.x Service Availability Configuration Guide

ICR References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

ICR Scaling Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

1:1 Subscriber Redundancy in a 4–Node ICR Cluster . . . . . . . . . . . . . . . . . . . 173

Interaction with RADIUS for ICR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

ICR Partition Accounting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Configuring an ICR Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Configuring the Interface on Which the ICR Partition Resides . . . . . . . . . . . . . . . 176

Configuring VRRP Instances to Match ICR Requirements . . . . . . . . . . . . . . . . . . . 177

Naming ICR Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

List of Figures

Part 1 Chapters

Chapter 1 Service Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 1: JunosE Software Service Availability Layers . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2 Managing Module Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Figure 4: High Availability States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 4 Managing Stateful Line Module Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 5: Stateful Line Module Switchover States . . . . . . . . . . . . . . . . . . . . . . . . . 85

Chapter 6 Configuring VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Figure 6: Basic VRRP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Figure 7: Commonly Used VRRP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Figure 8: VRRP Configuration Without the Real Address Owner . . . . . . . . . . . . . 156

Chapter 7 Managing Interchassis Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Figure 9: ICR Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Figure 10: Sample 1:1 Subscriber Redundancy in a 4–Node ICR Cluster . . . . . . . . 173

JunosE 11.3.x Service Availability Configuration Guide

List of Tables

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Part 1 Chapters

Chapter 2 Managing Module Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Table 6: show hardware Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

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

Table 22: Recommended Routing Protocol Timer Settings . . . . . . . . . . . . . . . . . 138

Table 23: show issu Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Chapter 6 Configuring VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Table 24: VRRP Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

JunosE 11.3.x Service Availability Configuration Guide

Table 28: show ip vrrp tracked-objects Output Fields . . . . . . . . . . . . . . . . . . . . . 166

Chapter 7 Managing Interchassis Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Table 29: ICR Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Table 30: show icr-partition Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Table 31: show icr-partitions Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

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 Routersin an Internet accessenvironment.

E Series and JunosE Text and Syntax Conventions

Table 1 on page xx defines notice icons used in this documentation.

JunosE 11.3.x Service Availability Configuration Guide

Table 1: Notice Icons

Table 2 on page xx defines text and syntax conventions that we use throughout the E Series and JunosE documentation.

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: Text and Syntax Conventions

Representscommands andkeywords intext.Bold text like this

Fixed-width text like this

Italic text like this

Plus sign (+) linking key names

Syntax Conventions in the Command Reference Guide

Representsinformation as displayed onyour terminal’s screen.

•

Emphasizes words.

•

Identifies variables.

•

Identifies chapter, appendix, and book names.

keys simultaneously.

ExamplesDescriptionConvention

•

Issue the clock source command.

•

Specify the keyword exp-msg.

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)

•

There are two levels of access: user and privileged.

•

clusterId, ipAddress.

•

Appendix A, System Specifications

Press Ctrl + b.Indicates that you must press two or more

terminal lengthRepresents keywords.Plain text like this

mask, accessListNameRepresents variables.Italic text like this

Table 2: Text and Syntax Conventions (continued)

About the Documentation

ExamplesDescriptionConvention

| (pipe symbol)

or variable to the left or to the right of this symbol. (The keyword or variable can be either optional or required.)

[ ]* (brackets and asterisk)

that can be entered more than once.

Represent required keywords or variables.{ } (braces)

Obtaining Documentation

To obtain the most current version of all Juniper Networks technical documentation, see the Technical Documentation page on the Juniper Networks Web site at

http://www.juniper.net/.

To download complete sets of technical documentation to create your own documentation CD-ROMs or DVD-ROMs, see the Portable Libraries page at

http://www.juniper.net/techpubs/resources/index.html

diagnostic | lineRepresents a choice to select one keyword

[ internal | external ]Represent optional keywords or variables.[ ] (brackets)

[ level1 | level2 | l1 ]*Represent optional keywords or variables

{ permit | deny } { in | out }

{ clusterId | ipAddress }

Copies of the Management Information Bases (MIBs) for a particular software release are available for download in the software image bundle from the Juniper Networks Web site athttp://www.juniper.net/.

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation to better meet your needs. Send your comments to

techpubs-comments@juniper.net, or fill out the documentation feedback form at

https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include

the following information with your comments:

•

Document or topic name

•

URL or page number

•

Software release version

Requesting Technical Support

Technical productsupport is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,

JunosE 11.3.x Service Availability Configuration Guide

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/

•

Download the latest versions of software and review release notes:

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

•

Search technical bulletins for relevant hardware and software notifications:

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

•

Join and participate in the Juniper Networks Community Forum:

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

•

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

To verify service entitlement by product serialnumber, 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 .

PART 1

Chapters

•

Service Availability on page 3

•

Managing Module Redundancy on page 9

•

Managing Stateful SRP Switchover on page 35

•

Managing Stateful Line Module Switchover on page 67

•

Configuring a Unified In-Service Software Upgrade on page 101

•

Configuring VRRP on page 149

•

Managing Interchassis Redundancy on page 169

JunosE 11.3.x Service Availability Configuration Guide

CHAPTER 1

Service Availability

This chapter explains what service availability is and discusses the features of service availability. It alsodiscusses Juniper Networks multi-layered service availabilityapproach for uninterrupted delivery of services.

•

Service Availability Overview on page 3

•

Understanding Service Availability Features on page 5

Service Availability Overview

In a conventional network, router outages can occur because of denial of service (DoS) attacks, line module failure, switch route processor module failure, software defects, feature upgrades, orcompleterouter failure.These outages result insubscriber downtime.

To reduce subscriber downtime, a network must have the following capabilities:

•

Reliability—A network that does not crash often and recovers from failure very rapidly. During recovery, the network maintains user sessions and forwards data with little or no impact on the delivery of services.

•

Resiliency—A network component or network that responds to failure, resists failure, and handles failure with little or no impact on the delivery of services.

•

Redundancy—A network whose reliability is enhanced by the addition of a backup component.

•

High Availability—A network that is both reliable and resilient.

JunosE Software uses a multi-layered service availability approach that enables you to provide uninterrupted delivery of services with the help of reliable, highly available, and redundant hardware and software components.

Figure 1 illustrates the multiple layers of JunosE Software service availability.

Security

Protects infrastructure against DoS attacks

Network Resiliency

Protects against port, link (fiber cuts), and network node failures

Software Availability

Protects against software crashes and minimizes downtime from software upgrades

Hardware Redundancy and Design

1:1 or N:1 component-level protection

g016518

99.999%

JunosE 11.3.x Service Availability Configuration Guide

Figure 1: JunosE Software Service Availability Layers

The security layer protects the network from DoS attacks.

The network resiliency layer protects against port, link, and node failures. You can configure IEEE 802.3 ad link aggregation for Ethernet, and Virtual Router Redundancy Protocol (VRRP) to improve network resiliency.

The software availability layer protects against software failures by using hot-fixes or installing a higher-numbered software release. You can perform a unified in-service software upgrade (ISSU)instead of the conventional software upgradeto reduce outage. You can eliminateor reduce single points of failureby configuring stateful SRPswitchover (high availability). Any network component with an uptime of 99.999 percent is considered highly available with a downtime of less than 5 minutes in a year.

The hardware redundancy and design layer introduces redundancy in the network in the form of multiple power supplies, cooling devices, line modules, and sometimes even a router. For instance, you can install a backup line module in your router to protect against line module failure. You can also configure a router as a backup router that accepts subscriber login requests when the master router fails.

Service Availability Versus High Availability

High availability is a measure ofthe uptime of a network or network component. A network component that has a downtime of 5 minutes is accessible or available 99 percent of the time. If a failure occurs, a backup component is available within 5 minutes. A highly available network is a network that has components that either have high reliability or have the ability to recover very quickly from a failure, or both.

Service availability refers to the ability to provide uninterrupted delivery of services. For example,from the time when a component failsto the time when the backup component is accessible, the delivery of services is interrupted. To provide uninterrupted delivery of services, highly available components must maintain session details and other data across failures. Service availability can thus be defined as the ability to provide uninterrupted delivery of services using a highly available network.

Documentation

Understanding Service Availability Features on page 5•

Understanding Service Availability Features

Service availability refers to ability of a network or a network component to provide uninterrupted delivery of services using highly available, redundant, and reliable components. This topic provides brief overviews of the benefits of using the following service availability features:

•

Module Redundancy on page 5

•

Stateful SRP Switchover on page 5

•

Stateful Line Module Switchover on page 5

•

Unified ISSU on page 6

•

VRRP on page 6

•

Interchassis Redundancy on page 6

Module Redundancy

Chapter 1: Service Availability

For hardware components, Juniper Networks provides redundancy solutions to ensure that the router continues to operate in the event of a hardware fault. Redundancy also enables you to hot-swap various components within your E Series router.

Stateful SRP Switchover

Stateful SRP switchover (high availability) enables you to reduce or eliminate single points offailure in your network. Stateful SRP switchover provides both hardware-specific and software-specific methods to ensure minimal downtime and ultimately improve the performance of your network.

Stateful SRP switchover minimizes the impact to therouter of a stateful switchover from the active SRP module to the standby SRP module. Stateful SRP switchover maintains user sessionsand data forwarding through the router duringthe switchover,thus improving the overall availability of the router.

Stateful Line Module Switchover

High availability of line modules increases the overall availability of the routerby ensuring that all the subscribers who were connected during a line module recovery continue to remain logged in and can access network resources during the switchover from the primary line module to the secondary line module. Forwarding of data through the fabric slice for those subscribers continues with a brief disruption of two minutes. If you configured stateful line module switchover on a router, when a switchover occurs, a message is displayed on the active SRP module after the secondary line module successfully takes over the role of the previously configured primary line module. If the primary line module fails, the secondary line module takes the role of the primary line module. Mirrored configuration data and any mirrored volatile data are already resident in memory. The protocols and other applications re-initialize from the mirrored data and resynchronize communications with the line modules (non-volatile configuration and volatile state). Data forwarding operation continues to function normally with the secondary line module operating on behalf of the primary line module (with a small loss

JunosE 11.3.x Service Availability Configuration Guide

of packets when the fabric is switched from the formerly active line module to the newly active line module). When resynchronization is completed, the router resumes normal operations, including updates ofany routingtables that result from changesthat occurred during the warm restart.

Unified ISSU

A conventional software upgrade—one that does not use the unified in-service software upgrade (ISSU) process—causes a router-wide outage for all users. Only static configurations(stored on the flash card) are maintained across theupgrade; all dynamic configurations are lost. A conventional upgrade can take 30-40 minutes to complete, with additional time required to bring all users back online.

Unified ISSU enables you to upgrade the router to a higher-numbered software release without disconnecting user sessions or disrupting forwarding through the chassis.

When an application supports unified ISSU, you can configure the application on the router and proceed with the unified in-service software upgrade with no adverse effect on the upgrade.

When you perform a unified ISSU on a router that has one or more modules that do not support unified ISSU, these modules are upgraded by means of the legacy, conventional upgrade process. The unsupported modules undergo a cold reboot at the beginning of the unified ISSU process, and are held down until the ISSU process is completed.

VRRP

Virtual Router Redundancy Protocol (VRRP) prevents loss of network connectivity to end hosts when the static default IP gateway fails. By implementing VRRP, you can designate a number of routers as backup routers in the event that the default master router fails. In case of a failure, VRRP dynamically shifts the packet-forwarding responsibility to a backup router. VRRP createsa redundancy scheme that enableshosts to keep a single IP address for the default gateway but maps the IP address to a well-known virtual MAC address. You can take advantage of the redundancy provided by VRRP without performing any special configuration on the end host systems.

Routers running VRRP dynamically elect master and backup routers. You can also force assignment of master and backup routers using priorities in the range 1–255, with 255 being the highest priority.

VRRP supports virtual local area networks (VLANs), stacked VLANs (S-VLANs), and creation of interchassis redundancy (ICR) partitions.

Interchassis Redundancy

ICR enables you to minimize subscriber downtime when the router or access interface on the edge router fails. ICR accomplishes this by re-creating subscriber sessions on the backup router that were originally terminated on the failed router. It also enables you to track the failure of uplink interfaces. In this way, ICR enables you to completely recover from router failure. ICR uses Virtual Router Redundancy Protocol (VRRP) to detect failures.ICR also enables youto track thefailure of uplink interfaces.ICR currentlysupports only PPPoE subscribers.

Chapter 1: Service Availability

Documentation

• Managing Module Redundancy on page 9

• Managing Stateful SRP Switchover on page 35

• Configuring a Unified In-Service Software Upgrade on page 101

• Configuring VRRP on page 149

• Managing Interchassis Redundancy on page 169

• Service Availability Overview on page 3

JunosE 11.3.x Service Availability Configuration Guide

+ 192 hidden pages

Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SERVICE AVAILABILITY CONFIGURATION GUIDE 2010-10-08, JUNOSE 11.3 Configuration Manual

Specifications and Main Features

Frequently Asked Questions

User Manual