About configurations and trails
This topic provides information aboutand , and how they are used by TrueSight Network Automation.
A configuration refers to a configuration file that defines the set of operating parameters for controlling the behavior or functioning of a device. The following table describes the standard configurations used by TrueSight Network Automation:
|Current Running||The current operating parameters resident in the device. These are the settings the device is actively using to perform its routing, switching, and/or security functions.|
|Current Startup||The operating parameters stored in the device that take effect when the device is booted.|
Past Running/Startup or other configuration files that have been superseded by the current Running or Startup or other current configuration.
For revision control, the current or a historical Running configuration designated as a stable, production baseline by the user. There is only one Trusted Running configuration per device.
For revision control, the current or a historical Startup configuration designated as a stable, production baseline by the user. There is only one Trusted Startup configuration per device.
|TSNA Device Attributes|
TrueSight Network Automation's internal device settings, containing the user-editable attributes of a device (all the attributes from the device edit page).
You can assign a Target configuration to each device containing base or ideal or desirable settings. Once assigned, the Target configuration can be modified and merged or restored to a device.
One or more CLI commands that are restored to the device's Startup configuration or merged with the device's Running configuration.
NEW IN 8.9.02Device End of Life
|Stores the board model IDs and End of Life dates for a Cisco device|
Only Running and Startup configurations support Trusted configurations. Devices that do not support Startup configurations do not have a Startup, Trusted Startup, or Historical Startup configuration.
Configurations are either in ASCII or binary format. Encoded binary configurations support a limited set of configuration actions. Some devices allow decoding of their binary configurations for display purposes. TrueSight Network Automation performs this decoding automatically.
The following figure shows configuration of a Cisco device that is stored in ASCII format:
A trail refers to a chronological sequence of configurations of the same kind, archived over time, representing the history of changes detected by TrueSight Network Automation. The newest configuration within a given trail is known as the current configuration. Older configurations are known as historical configurations.
Examples of trails: Startup, Running, and other arbitrary configuration files that are required to capture a complete snapshot of a device (such as a vlan.dat file for Cisco IOS).
TrueSight Network Automation includes, out-of-the-box, all of the trails necessary for the complete set of device types that it supports.