CHAPTER 28
Host Redundancy Overview
•
Checklist for Host Redundancy on page 563
•
Understanding Redundancy for the Routing Engine, Host Module, and Host
Subsystem on page 565
•
M10i Router Redundant Routing Engines and HCMs on page 566
•
M20 Router Redundant Routing Engines and SSBs on page 566
•
M40e and M160 Router Redundant Host Modules on page 567
•
M120 Router Redundant Host Subsystems on page 567
•
M320 Router, T320 Router, T640 Router, and T1600 Router Redundant Host
Subsystems on page 568
•
TX Matrix and TX Matrix Plus Redundant Host Subsystems on page 569
•
Routing Engine, Host Module, and Host Subsystem Redundancy Connections on page 570
•
Redundancy Connection for an M10i Router on page 571
•
Redundancy Connection for an M20 Router on page 571
•
Redundancy Connection for an M40e or M160 Router on page 572
•
Redundancy Connection for an M120 Router on page 573
•
Redundancy Connection for an M320 Router on page 574
•
Redundancy Connection for a T320 Router, T640 Router, and T1600 Router on page 574
•
Determine Which Routing Engine You Are Logged In To on page 575
•
Determining Routing Engine Mastership on page 577
•
Manually Configue Master and Backup Routing Engines on page 578
•
Manually Switching Routing Engine Mastership on page 581
•
Determining Why Mastership Switched on page 582
•
Configuring the Backup Routing Engine to Assume Mastership on Failure of
Keepalives on page 585
•
Avoid Redundancy Problems on page 586
Checklist for Host Redundancy
Purpose You monitor redundant Routing Engines, host modules, and host subsystems to provide
a standby Routing Engine and controller component that will switch from standby to
active, assuming mastership, with limited running downtime when a failure occurs.
563Copyright © 2012, Juniper Networks, Inc.
To Next Page
