C9300-M client tracking limitations

[cmr]

I just saw in the documentation update that the C9300-M and MS390 switches cannot track clients connected to the high speed ports:

Note: The following ports don't support Client Tracking features on MS390/C9300-M.

1. Ports with supported max speeds 25G, 40G, 100G.

2. Link Aggregation ports

If a server, or 3rd party switch with clients, is connected to one of these ports, will the device(s) simply not be seen, or will the be reported as being on another port?  Surely the devices connected to those ports must be in the switches mac address table, so I am not sure why they would not be reported???  Hopefully it is a limitation of the current container architecture and the native IOS-XE version will fix it!

[DarrenOC]

Interesting. Subscribed to see if we get an official response as to why.

[GIdenJoe]

Hmm, well MAC address table won't be an issue but client tracking uses more like device sensor and Netflow/IPFIX data.  Maybe there is a limitation in passing that data on to the container.

[ozzieb]

This is still a major problem and the IOS-XE version does not fix.

[cmr]

In fact it got worse, in Device Configured mode at least, the 10G ports don't show clients now (when running at 10G) and the old restrictions of needing DNA advantage remain as well.  Nothing like making sure the "Meraki simple" message is totally messed up when you include Catalyst devices... :sigh: <- we need this emoji 😈