How to stop IP Device Tracking on certain ports when provisioning

[DJW487]

We have some Cisco Webex units (RoomEQ type) that have all the ancillaries like mics on a seperate vlan back to the RoomEQ where they get a 169.x.x.x address from the RoomEQ unit. Then the RoomEQ unit has a second connection which has internet connection.

We realised that IP Device tracking that is implemented when provisioning through Catalyst Centre stops the RoomEQ from working.

I delete the device tracking from the port but every time we re-provision, it puts it back on.

How can I tag a port to stop it getting device tracking?

[Enes Simnica]

@DJW487 . and man u're right, because ip device tracking can interfere with setups like your Cisco Webex RoomEQ units, especially when they assign internal 169.x.x.x addresses to connected mics and ancillaries. IPDT tries to track all connected IPs, and when it sees those self-assigned addresses or non-routable traffic, it can block or disrupt normal function.

Since u're using Catalyst Center (formerly DNA Center) and it's re-provisioning the port with IPDT every time, the best approach is to customize the port's intent or template in Catalyst Center.

but the thing is that there’s no per-port command to “tag” it to skip IPDT, but u can try some stuff liKe; 

1. Create a custom interface template or modify the existing one in Catalyst Center that doesn’t include IP Device Tracking.
2. Assign that template to the RoomEQ port before provisioning.
3. Alternatively, if you can’t avoid provisioning, manually remove IPDT again after provisioning, all u have to do here is use the:
   no ip device tracking command .... but this is only a temporary fix unless the template is changed.

as i know so far, Cisco doesn’t currently have a “do not apply IPDT” tag per port via Catalyst Center, so template customization is the reliable way.

https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2025/pdf/CISCOU-3004.pdf

hope the text is not that long LOOOOL, ping me if u have more questions...

-Enes

[DJW487]

Hi Enes,

Thanks for the reply. We don't have to provision often, but we did recently change to update ISE cluster which required a reprovision. Which then we started receiving reports of the RoomEQ systems not working and it brought back memories from a year ago when we installed them and it took a while to figure out why it wouldn't work the first time

I think I am going to create a custom IPDT rule that has Glean and not Drop as the action and assign that to the RoomEQ ports and hope Cat Centre doesn't overwrite it on those ports in a future provision.

Do you know if it has to be applied to all the ancillary ports or just the RoomEQ ports? I removed device tracking from all the ports to be safe but not sure what is the minimum requirement

[fabienB]

Hello,

To skip IPDT interface (not wanted) refresh, you can also desactivate telemetry before provisioning, and reactivate after. Go in Network settings / Telemetry / Disable Catalyst Center Wired Endpoint Data Collection.

We found that when updating templates. But if templates could do only what we want and nothing else, that would be much better!