Intent Baseline Data Decoding Service
This chapter provides a detailed explanation of the baseline decoding service and intent decoding service. Once a Network Intent Template (NIT) is defined and installed in the Intent Based Automation Center, the seed intent will be decoded and installed in the qualified target devices. This process involves two key procedures:
- Device Qualification: Devices in the live network are evaluated to determine their eligibility.
-
Seed Device Matching: Qualified devices are matched against seed devices defined in the NIT.
For example: If the seed NI includes two seed devices, a Cisco IOS device and a Juniper device, the decoding service determines which set of commands (Cisco or Juniper) should be applied to the qualified device. If a qualified device does not match any seed device, it is excluded from further processing.
You can configure the frequency of baseline data updates for the NIT using an intent timer. This updated baseline data is used when cloning new intents. During intent decoding, the system establishes mappings between the target devices and the seed devices defined in the NIT. This chapter covers the following decoding-related processes:
If the intent baseline service is applied either to a common intent or to a cloned intent derived from an NIT, the baseline data is validated and updated during intent execution to ensure the most recent baseline is used. The following table summarizes how baseline data is verified during execution for different types of Network Intents (NIs).
| Intent Execution Mode | Intent Baseline Data Checking |
| Interactive Execution | When one or more intents are executed as a Runbook node, the intent baseline data is directly updated. |
| TAF Triggered Execution | Intent baseline data is directly checked and updated during intent execution. |
| PAF Triggered Execution | Intent baseline data is directly checked and updated during intent execution. |