JUNOS High Availability

Configuration Change Types

When creating strategies for automating the configuration of your systems, it is not possible to take a one-size-fits-all approach. By examining the impact of configuration changes on various parts of the network architecture, as well as on various functional areas, it is possible to develop strategies that give the configuration automation the most impact in terms of improving and maintaining high availability. Separate strategies must be used when the automated configuration changes are designed, not to prevent human error in the configuration of the equipment, but rather to address outside forces that can reduce your network’s high availability.

Deployment

When deploying new equipment or services into your network, you must determine what changes the initial deployment of the configurations or the introduction of the service may have on your network high availability. Although it is sometimes impossible to deploy a new piece of equipment without network disruption, introduction of the equipment should not lead to network downtime for a wide range of customers or future network downtime because of incompatibility or misconfiguration. By planning how services and equipment are to be deployed and how the configurations to support the new services and equipment are to be automated, you can create a plan that results in the least impact for your customers, peering points, and infrastructure equipment.

Network equipment

One of the most common uses for automated ...