LLDP probe has undesired behavior with Cisco Nexus switches

[tu-pm]

As stated here, Cisco Nexus switches send different chassis IDs through different ports in LLDP messages. This causes metadata on the switch node to be constantly changing every time an LLDP message arrives in an interface. This is an undesired behavior, because naturally IDs shouldn't change, and also any new metadata assigned to the switch nodes from a different source (from analyzer probes or clients) will be replaced the next time it is updated.

This problem occurs when there's a Cisco Nexus switch connecting to a host through more than one layer2 link, typically when interfaces on host are bonded to each other.

I'd suggest to eliminate the chassis ID field out of switch's metadata or any other mechanisms to work around this particular problem.