Validation of Template Configuration Before and After Application of Template on Device

Validation of template configuration is done before and after application of the template on the device.

The following validation checks are performed at the start of the task to apply the template on the device:

• Ensure that the target device model and version are supported.

• Cluster and container checks -The device must not be part of a cluster or multi-instance.

• Model mapping validation - Model mapping for the target device model exists and is valid.

• Sanity check of template parameter values. For example, two variables used as IP addresses of interfaces must not have the same value.

The following validation checks are performed at the end of the task to apply the template on the device to ensure that the applied configurations are valid:

• Interface configuration validation. For example, variables used for the IP address fields of two or more interfaces must not have the same IP address values.

• Routing policy validation. For example, the IPv4 address in BGP neighbor configurations must not overlap with the IP address of any interface.

If the validation checks that are done at the end of the task to apply the template on the device fail, any applied configurations are rolled back and the device is restored to it’s original state.