When applying cfg template, see add'l commands called "intent config"?

[mat_rouch]

There is a config fix I need to apply to some of our switches.  I created a template under "Design/Config Templates" and attached it to a tag.  Then I associated the tag with (in this example) four switches and select "Actions/Provision/Provision Device".  So far so good.  I get to the "Advanced Configuration" screen and I see my template associated with the devices I selected.  Nothing else shows up for deployment other than my template.  I click through the next few screens.  

NOTE: All four of these devices are very similar catalyst 9300 switches. All are running the same IOS version.

When I get to the "Provision Device" screen I see something I do not expect.  For three of the four switches, there is a *second* configuration source in addition to the template I specified.  The additional source is called "Intent Config".  Under "configuration to be deployed" I see that "intent config" is adding a domain lookup source and two name servers.  This is not config from my template.  I do not know where it came from.

I checked - none of the four switches have pre-existing domain lookup sources or name servers.

So, two questions: first, what is intent config and how do I disable it, and second, why is it only attempting to apply it to some of my switches?

Thanks in advance,

-Mathew Rouch

[mat_rouch]

correction: the first device DOES have domain lookup sources, so I see why Catalyst Center did not deploy new ones.  But the other question stands: how can I prevent Catalyst Center from executing Intent Config, deploying config I did not specifically tell it to deploy?

-Mat

[Stefan Mihajlov · Accepted solution]

@mat_rouch 

Intent Config" in Cisco Catalyst Center is a system-generated configuration based on network profile or site design settings. It includes automatic configurations such as DNS, domain lookup, and other global settings defined for a specific site or network profile. This is why you're seeing the additional configuration applied to some of your switches. The reason it's only affecting some devices could be due to differences in the profiles or tags assigned to those switches, or the configuration may already match the devices' current settings, so it's not applied to others.

To disable it, review the network profile under Design > Network Settings and remove any unwanted settings like DNS or domain lookup. You should also check Design > Sites to ensure no additional configurations are set at the site level. After making these changes, reprovision the devices to apply the updated configuration. If you're still unsure about the changes being applied, use the "Preview Config" option before deploying to confirm exactly what will be pushed to each device.

If this post was helpful, please click Helpful. If it resolved your query, select Mark as Solution from the dropdown menu in the top-right corner of this reply.