LMS 3.1 - UT Discovery + Trunk-Port + CDP enabled

[lo.mueller]

Hi there,

as far as I know UT Disco does not discover End-Hosts on CDP-enabled-(Trunk)-Ports (prior CM 5.0)

With CM 5.0.x End-Hosts can now be discovered on Trunk-Ports.

What is the behavior of CM5.0.x with cdp-enabled trunk-ports, but no CDP-Neighbor?

Is there an option (config-file) to tell UT-Discovery handling of CDP-enabled port?

Thanks for any feedback

Lothar

[Joe Clarke]

If you enable trunk port acquisition for a given trunk port, and that port is not part of the Campus Topology, then end hosts will be acquired on it. However, if the trunk port is part of the Topology (i.e. it has a CDP neighbor which shows up on the Topology Map) then users will not be acquired on it as the port is considered a Link Port.

[lo.mueller]

Hi Joe,

thanks for your feedback.

And how about trunk-ports connected to devices other than cisco (not sending CDP-Packets) but the Cisco-switch-port has CDP enabled, so no CDP-neighbor is seen?

Does CM fetch information about CDP-configuration of switch-ports and therefore decide how to handle the endhost addresses?

Thanks

[Joe Clarke · Accepted solution]

If there are no CDP neighbors on a trunk port, and trunk port acquisition is enabled, then end hosts will be acquired on the port.