06-03-2025 07:35 AM
Hi all,
My team has currently been running into an issue in Catalyst Center. I'm currently trying to go through our switch inventory and clear up any compliance violations on any switches. I'm running into quite a few devices that are marked non-compliant due to IP Device tracking being disabled or not configured on trunk ports on switches.
From my knowledge and some quick reassuring research, it's been best practice to have device tracking off on trunk ports. However, Catalyst Center seems to insist that they should have this configured.
However, when trying to deploy the recommended compliance fix from catalyst center via the compliance summary dashboard, it seems to do basically nothing and then return to being marked non-compliant.
Ideally, we'd like to be able to clear any compliance issues we have on our network devices, without having to "acknowledge" them just because they can't be fixed. Finding a way for catalyst center to accept no device tracking on trunk ports would be ideal.
So, if anyone has any insight into what can be done to clear this compliance violation, that would be incredibly appreciated!
(pictures and examples attached)
06-03-2025 11:17 PM
- FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvm59016
M.
06-04-2025 12:04 AM - edited 06-04-2025 12:05 AM
I suspect that this is mostly cosmetic. AFAIK you shouldn't have IPDT configured for trunks except for when facing endpoints. If you do have such devices that require a trunk you should just configure it manually as the compliance remediation clearly doesn't work and acknowledge it for the remaining devices.
If you have a large amount of devices making acknowledging the issue not feasible you should create a TAC case
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide