[
Contents]
[
Prev]
[
Next]
[
Index]
[
Report an Error]
Table of Contents
- About This Guide
-
- JUNOS Documentation and Release Notes
- Objectives
- Audience
- Supported Routing Platforms
- Using the Indexes
- Using the Examples in This Manual
- Documentation Conventions
-
- Documentation Feedback
- Requesting
Technical Support
- Overview
-
- High Availability Overview
-
- Introducing High Availability Features on Juniper Networks
Routing Platforms
-
- Routing Engine Redundancy
- Graceful Routing Engine Switchover
- Nonstop Bridging
- Nonstop Active Routing
- Graceful Restart
- Nonstop Active Routing Versus Graceful Restart
- Effects of a Routing Engine Switchover
- VRRP
- Unified ISSU
- High Availability-Related Features in JUNOS
- Routing Engine and Switching
Control Board Redundancy
-
- Routing Engine and Switching Control Board Redundancy Overview
-
- Understanding Routing Engine Redundancy on JUNOS Routers
-
- Routing Engine Redundancy Overview
- Conditions That Trigger a Routing Engine Failover
- Default Routing Engine Redundancy Behavior
- Routing Engine Redundancy on a TX Matrix Platform
- Situations That Require You to Halt Routing Engines
- Switching Control Board Redundancy
-
- Redundant CFEBs on the M10i Router
- Redundant FEBs on the M120 Router
- Redundant SSBs on the M20 Router
- Redundant SFMs on the M40e and M160 Routers
- Routing Engine and Switching Control Board Redundancy Configuration
Guidelines
-
- Chassis Redundancy Hierarchy
- Initial Routing Engine Configuration Example
- Copying a Configuration File from One Routing Engine to the
Other
- Loading a Software Package from the Other Routing Engine
- Configuring Routing Engine Redundancy
-
- Modifying the Default Routing Engine Mastership
- Configuring Automatic Failover to the Backup Routing Engine
-
- Without Interruption to Packet Forwarding
- On Detection of a Hard Disk Error on the Master Routing Engine
- On Detection of a Loss of Keepalive Signal from the Master
Routing Engine
- When a Software Process Fails
- Manually Switching Routing Engine Mastership
- Verifying Routing Engine Redundancy Status
- Configuring CFEB Redundancy on the M10i Router
- Configuring FEB Redundancy on the M120 Router
- Example: Configuring FEB Redundancy
- Configuring SFM Redundancy on M40e and M160 Routers
- Configuring SSB Redundancy on the M20 Router
- Summary of Routing Engine and Switching Control Board Redundancy
Statements
-
- cfeb
- description
- failover on-disk-failure
- failover on-loss-of-keepalives
- failover other-routing-engine
- feb
-
- feb (Creating a Redundancy Group)
- feb (Assigning a FEB to a Redundancy Group)
- keepalive-time
- no-auto-failover
- redundancy
- redundancy-group
- routing-engine
- sfm
- ssb
- Graceful Routing Engine Switchover
-
- Graceful Routing Engine Switchover Overview
-
- Understanding Graceful Routing Engine Switchover in the JUNOS
Software
-
- Graceful Routing Engine Switchover Concepts
- Effects of a Routing Engine Switchover
- Graceful Routing Engine Switchover System Requirements
-
- Graceful Routing Engine Switchover Platform Support
- Graceful Routing Engine Switchover Feature Support
- Graceful Routing Engine Switchover DPC Support
- Graceful Routing Engine Switchover and Subscriber Access
- Graceful Routing Engine Switchover PIC Support
- Graceful Routing Engine Switchover Configuration Guidelines
-
- Configuring Graceful Routing Engine Switchover
-
- Enabling Graceful Routing Engine Switchover
- Synchronizing the Routing Engine Configuration
- Verifying Graceful Routing Engine Switchover Operation
- Requirements for Routers with a Backup Router Configuration
- Resetting Local Statistics
- Summary of Graceful Routing Engine Switchover Configuration
Statements
-
- graceful-switchover
- Nonstop Bridging
-
- Nonstop Bridging Overview
-
- Nonstop Bridging Concepts
- Nonstop Bridging System Requirements
-
- Platform Support
- Protocol Support
- Nonstop Bridging Configuration Guidelines
-
- Configuring Nonstop Bridging
-
- Enabling Nonstop Bridging
- Synchronizing the Routing Engine Configuration
- Verifying Nonstop Bridging Operation
- Summary of Nonstop Bridging Statements
-
- nonstop-bridging
- Nonstop Active Routing
-
- Nonstop Active Routing Overview
-
- Nonstop Active Routing Concepts
- Nonstop Active Routing System Requirements
-
- Nonstop Active Routing Platform Support
- Nonstop Active Routing Protocol and Feature Support
- Nonstop Active Routing BFD Support
- Nonstop Active Routing BGP Support
- Nonstop Active Routing Layer 2 Circuit and LDP-Based VPLS Support
- Nonstop Active Routing PIM Support
- Nonstop Active Routing Support for RSVP-TE LSPs
- Nonstop Active Routing Configuration Guidelines
-
- Configuring Nonstop Active Routing
-
- Enabling Nonstop Active Routing
- Synchronizing the Routing Engine Configuration
- Verifying Nonstop Active Routing Operation
- Tracing Nonstop Active Routing Synchronization Events
- Resetting Local Statistics
- Example: Configuring Nonstop Active Routing
- Summary of Nonstop Active Routing Configuration Statements
-
- commit synchronize
- nonstop-routing
- traceoptions
- Graceful Restart
-
- Graceful Restart Overview
-
- Graceful Restart Concepts
- Graceful Restart System Requirements
- Aggregate and Static Routes
- Graceful Restart and Routing Protocols
-
- BGP
- ES-IS
- IS-IS
- OSPF and OSPFv3
- PIM Sparse Mode
- RIP and RIPng
- Graceful Restart and MPLS-Related Protocols
-
- LDP
- RSVP
- CCC and TCC
- Graceful Restart and Layer 2 and Layer 3 VPNs
- Graceful Restart on Logical Systems
- Graceful Restart Configuration Guidelines
-
- Configuring Graceful Restart for Aggregate and Static Routes
- Configuring Routing Protocols Graceful Restart
-
- Configuring Graceful Restart Globally
- Configuring Graceful Restart Options for BGP
- Configuring Graceful Restart Options for ES-IS
- Configuring Graceful Restart Options for IS-IS
- Configuring Graceful Restart Options for OSPF and OSPFv3
- Configuring Graceful Restart Options for RIP and RIPng
- Configuring Graceful Restart Options for PIM Sparse Mode
- Tracking Graceful Restart Events
- Configuring Graceful Restart for MPLS-Related Protocols
-
- Configuring Graceful Restart Globally
- Configuring Graceful Restart Options for RSVP, CCC, and TCC
- Configuring Graceful Restart Options for LDP
- Configuring VPN Graceful Restart
-
- Configuring Graceful Restart Globally
- Configuring Graceful Restart for the Routing Instance
- Configuring Logical System Graceful Restart
-
- Configuring Graceful Restart Globally
- Configuring Graceful Restart for a Routing Instance
- Verifying Graceful Restart Operation
-
- Graceful Restart Operational Mode Commands
- Verifying BGP Graceful Restart
- Verifying IS-IS and OSPF Graceful Restart
- Verifying CCC and TCC Graceful Restart
- Example: Configuring Graceful Restart
- Summary of Graceful Restart Configuration Statements
-
- disable
- graceful-restart
- helper-disable
- maximum-helper-recovery-time
- maximum-helper-restart-time
- maximum-neighbor-reconnect-time
- maximum-neighbor-recovery-time
- no-strict-lsa-checking
- notify-duration
- reconnect-time
- recovery-time
- restart-duration
- restart-time
- stale-routes-time
- traceoptions
- Virtual Router Redundancy Protocol
-
- VRRP Overview
-
- Understanding VRRP
- VRRP Configuration Guidelines
-
- VRRP Configuration Hierarchy
- VRRP for IPv6 Configuration Hierarchy
- Configuring the Startup Period for VRRP Operations
- Configuring Basic VRRP Support
- Configuring VRRP Authentication (IPv4 Only)
- Configuring the Advertisement Interval for the VRRP Master
Router
-
- Modifying the Advertisement Interval in Seconds
- Modifying the Advertisement Interval in Milliseconds
- Configuring a Backup Router to Preempt the Master Router
- Modifying the Preemption Hold-Time Value
- Configuring an Interface to Accept Packets Destined for the
Virtual IP Address
- Configuring a Logical Interface to Be Tracked
- Configuring a Logical Interface to Be Tracked
- Configuring a Route to Be Tracked
- Tracing VRRP Operations
- Configuring the Silent Period
- Configuring Passive ARP Learning for Backup VRRP Routers
- Example: Configuring VRRP
- Example: Configuring VRRP for IPv6
- Example: Configuring VRRP Route Tracking
- Summary of VRRP Configuration Statements
-
- accept-data
- advertise-interval
- authentication-key
- authentication-type
- bandwidth-threshold
- fast-interval
- hold-time
- inet6-advertise-interval
- interface
- no-accept-data
- no-preempt
- preempt
- priority
- priority-cost
- priority-hold-time
- route
- startup-silent-period
- traceoptions
- track
- virtual-address
- virtual-inet6-address
- virtual-link-local-address
- vrrp-group
- vrrp-inet6-group
- Unified ISSU
-
- Unified ISSU Overview
-
- Unified ISSU Concepts
- Unified ISSU Process on TX Matrix Platform
- Unified ISSU System Requirements
-
- Unified ISSU JUNOS Software Release Support
- Unified ISSU Platform Support
- Unified ISSU Protocol Support
-
- Unified ISSU Support for Layer 2 Control Protocol Process (L2CPD)
- Unified ISSU Feature Support
- Unified ISSU PIC Support
-
- PIC Considerations
- SONET/SDH PICs
- Fast Ethernet and Gigabit Ethernet PICs
- Channelized PICs
- Tunnel Services PICs
- ATM PICs
- Serial PICs
- DS3, E1, E3, and T1 PICs
- Enhanced IQ2 Ethernet Services Engine (ESE) PIC
- Unified ISSU DPC Support
- Unified ISSU Configuration Guidelines
-
- Best Practices
- Before You Begin
-
- Verify That the Master and Backup Routing Engines Are Running
the Same Software Version
- Back Up the Router's Software
- Verify That Graceful Routing Engine Switchover and Nonstop
Active Routing Are Configured
- Performing a Unified ISSU
-
- Upgrading and Rebooting Both Routing Engines Automatically
- Upgrading Both Routing Engines and Rebooting the New Backup
Routing Engine Manually
- Upgrading and Rebooting Only One Routing Engine
- Verifying a Unified ISSU
- Troubleshooting Unified ISSU Problems
- Managing and Tracing BFD Sessions During Unified ISSU Procedures
- Unified ISSU Configuration Statements Summary
-
- no-issu-timer-negotiation
- traceoptions
- Index
-
- Index
- Index of Statements and Commands
[
Contents]
[
Prev]
[
Next]
[
Index]
[
Report an Error]