JUNOS High Availability

Automation Strategies

The main purpose of automating configurations across the network is to ensure that neither human error nor lack of configuration consistency affects network uptime. Using the information we’ve provided in this chapter, it is possible to model configurations and templates to be used by JUNOScript, or other tools, to deploy the configurations. This section contains examples of using JUNOScript and other tools to confirm the automation of network device configuration.

Global Strategies

The best way to ensure consistent configurations across a network is to have a single source for your configuration scripts. The repository for the scripts should serve as a Concurrent Versions System (CVS) to ensure that all changes are noted, and as a clearinghouse from which the scripts are pulled by the machines. If you remember from previous chapters, the JUNOScope software provides a built-in CVS for configurations.

Luckily, with JUNOScript, you can point network devices to the location of the source script and then reload with the refresh command:

system {
    scripts {
        commit {
            allow-transients;
            file infrastructure.slax {
                source http://engineering.example.com/infrastructure.slax;
            }
        }
    }
}

Deployment

One of the times high availability is most threatened is when you deploy new equipment or services in the network. The engineers are responsible for ensuring that the new systems do not impact the existing network. To do this, automated configuration can be used to guarantee that the proper ...