Baseline Configuration is the most stable configuration version which when uploaded into a faulty device, brings it back to optimum performance. Whenever a change is made in a device configuration, Network Configuration Manager instantly triggers a backup of that particular device. The backed up configurations are then stored as incremental versions. This creates several versions of configuration files for the same device. Among these versions, the network admin chooses the most stable configuration and labels it as the 'Configuration Baseline Version'.
Want to learn how to setup a fallback mechanism for your network? Learn for free from our technical expert!
Network Admins choose the Configurations's baseline version based on the following criteria:
In short, the admin chooses a configuration version which is flexible, stable and versatile in nature.
To Label a configuration as the Baseline version, select the configuration from Inventory and click on the three dots icon on the top right corner of the UI, then select the "Label Configuration" option, and select the label as "Baseline" to associate it to the device.
A running configuration is the current or the latest configuration version and any change made in it will not be saved, unless it is synced with the startup configuration or the Baseline configuration.
Thus, Whenever there is a baseline-running configuration conflict, network configuration manager immediately shows the conflict in red, denoting non-sync between the two configurations. In that case, if the admin finds the running configuration more stable than the Baseline Configuration, he can label the running configuration as the new Baseline Configuration.
If the running configuration is critical and if the admin feels that it might harm the device and cause mishaps, he can upload the Baseline Configuration that was chosen earlier.
When a sudden network outage happens, it often leads to down time in network devices. This downtime in devices affect the availability of crucial network devices leading to a chain reaction of negative events, including data loss, decreased employee productivity, high recovery cost and overall network performance degradation. The time taken to identify the root cause of the outage will prolong the unavailability of devices.
In that case, a Baseline configuration acts as a fall back mechanism as the admin can directly upload the Baseline configuration to bring back the devices to running state. Thus, Baseline configuration not only reduces device down time but also gives admins enough time to identify the cause of a network outage without affecting productivity.
Baseline configurations can be labelled in multiple devices by choosing the best performing configuration versions for both running and startup configurations. When there is a network outage, the baseline configuration versions can be uploaded in bulk in the network devices. Uploading configuration's Baseline version can be done instantaneously and can reduce downtime in more than 1000 network devices real quick.
The quality of a network configuration plays a major role in determining the performance of any network device. Faulty configuration changes often lead to performance degradation and might even cause heavy losses in some cases. This can be avoided by thoroughly scrutinizing the configurations and making necessary changes to improve its performance. Let us see how configuration Baseline versions help to improve the quality of configurations
When one device configuration is similar to another configuration but does not produce the desired output as that configuration, the network admin can improve the quality of the under-performing configuration by comparing it with the Baseline version of the configuration. By doing so, the admin can check where he can improve the configuration to make it perform better, thereby improving the quality of the configuration.
Thus, a Baseline configuration can be used for averting network disasters and for improving the performance of existing configurations as well.