Book Image

JUNOS Automation Cookbook

By : Adam Chappell
Book Image

JUNOS Automation Cookbook

By: Adam Chappell

Overview of this book

The JUNOS Automation Cookbook is a companion guide for the complex field of automating tasks on JUNOS devices. With a foundation in industry-standrd XML, JUNOS provides an ideal environment for programmatic interation, allowing you to build upon the capabilities provided by Juniper, with your own original code. You will begin by learning about, and setting up, the industry-standard NETCONF remote procedure call mechanisms on your device. After initial setup, you'll walk through SLAX - Juniper's foundation scripting language - for manipulating XML representations of JUNOS concepts and elements. You'll learn how to write your own SLAX scripts to customise the operating environment, and also how to write proactive event handlers that deal with situations as they happen. You'll then delve into PyEZ - Juniper's bridging framework to make automation accessible to Python code - allowing you to build automation applications in the popular scripting language. You'll witness some examples of how to write applications that can monitor configuration changes, implement BGP security policies and implement ad-hoc routing protocols, for those really tricky situations. You'll also leaarn how asynchronous I/O frameworks like Node.js can be used to implement automation applications that present an acceptable web interface. Along with way, you'll explore how to make use of the latest RESTful APIs that JUNOS provides, how to visualize aspects of your JUNOS network, and how to integrate your automation capabilities with enterprise-wide orchestration systems like Ansible. By the end of the book, you'll be able to tackle JUNOS automation challenges with confidence and understanding, and without hassle.
Table of Contents (10 chapters)

Dealing with a flapping OSPF neighbor

In this recipe, we'll look at the situation of a flapping internal OSPF neighbor, possibly caused by a flapping physical layer interface. In contrast with the previous recipe, where we simply trapped multiple instances of a flapping interface and shut the interface down, in this scenario, we'll deal with the situation slightly differently.

What we'll do is trap multiple sequential occurrences of an OSPF neighbor going away --for whatever reason—and, so long as he's the only OSPF neighbor on the link (which is a common situation in large ISP backbones where point-to-point WAN links are the norm), we'll poison the associated OSPF interface cost in order to influence traffic away from the link.

The underlying issue that is causing the degraded communication to the OSPF neighbor will remain, which means that we...