Cargando…
JUNOS high availability /
Whether your network is a complex carrier or just a few machines supporting a small enterprise, JUNOS High Availability will help you build reliable and resilient networks that include Juniper Networks devices. With this book's valuable advice on software upgrades, scalability, remote network m...
| Clasificación: | Libro Electrónico |
|---|---|
| Otros Autores: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
[Sebastopol, Calif.] :
O'Reilly Media,
2009.
|
| Edición: | 1st ed. |
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
Tabla de Contenidos:
- Table of Contents; Preface; What Is High Availability?; How to Use This Book; What's in This Book?; Part I, JUNOS HA Concepts; Part II, JUNOS HA Techniques; Part III, Network Availability; Part IV, Appendixes; Conventions Used in This Book; Using Code Examples; Safari® Books Online; Comments and Questions; Acknowledgments; Part I. JUNOS HA Concepts; Chapter 1. High Availability Network Design Considerations; Why Mention Cost in a Technical Book?; A Simple Enterprise Network; Redundancy and the Layered Model; Redundant Site Architectures; Redundant Component Architectures.
- Combined Component and Site-Redundant ArchitecturesRedundant System Architectures; Combined System- and Site-Redundant Architectures; Combined System- and Component-Redundant Architectures; Combined System-, Component-, and Site-Redundant Architectures; What Does It All Mean?; Chapter 2. Hardware High Availability; Divide and Conquer; The Brains: The Routing Engine; RE comparison; M Series; MX Series; T Series; EX Series; SRX Series; The Brawn: The Packet Forwarding Engine; Hardware components; J Series; Model comparison; M Series; MX Series; T Series; EX Series; Packet Flows; M Series.
- MX SeriesT Series; EX Series; SRX Series; J Series; Redundancy and Resiliency; M Series; MX Series; T Series; J Series; SRX Series; EX Series; Chapter 3. Software High Availability; Software Architecture; Stable Foundations; Modular Design; Daemons; One OS to Rule Them; Single OS; Forks and trains; No reeducation through labor; One Release Architecture; Automation of Operations; Configuration Management; Application Programming Interfaces; Scripting; Commit scripts; Operation scripts; Event policy scripts; Chapter 4. Control Plane High Availability; Under the Hood of the Routing Engine.
- Routing Update ProcessStep 1: Verify that the RE and PFEs are up; Step 2: Verify that the socket is built; Step 3: Verify that there is a valid TNP communication; Step 4: Verify that BGP adjacencies are established; Step 5: Verify that BGP updates are being received; Step 6: Verify that route updates are processed correctly; Step 7: Verify that the correct next hop is being selected; Step 8: Verify that the correct copy of the route is being selected for kernel update; Step 9: Verify that the correct copy of the route is being sent to the forwarding plane.
- Step 10: Verify that the correct copy of the route is being installed into the forwarding plane on the PFE complexGraceful Routing Engine Switchover; Implementation and Configuration; Configuration examples; Troubleshooting GRES; Graceful Restart; Graceful Restart in OSPF; Configuration; Immunizing against topology change; Graceful Restart in IS-IS; Configuration; Graceful Restart in BGP; Restarting the node; Peers; Configuration; MPLS Support for Graceful Restart; Graceful Restart in RSVP; Configuration; Graceful Restart in LDP; Configuration; Graceful Restart in MPLS-Based VPNs.