i already have it enabled.

by the way what are these... in ut.properties. can i use these to do the same.

duplicatemac.excludeports=

duplicatemac.excludeswitch=

The UT.DuplicateMac properties only come into play when DHCP support is enabled. They are designed to allow or disallow duplicates on a given switch. They will not solve the problem you are seeing switch the switches in question are different.

However, if both switches are showing up on the topology map, and the link between the two also shows up, then end hosts should not be acquired on that link. What type of switches are they?

My whole architecture runs on DHCP only.

i attached a sample scenario. the hosts of sw1 also shows in dist4507 on the red line port. the red lines are vl20 and is not routable withing the rest of the network. R1 is managed by vendor. and rest of the network is mine to control.

how can i manage this.

sorry. the scenario is attahced now.

What I said before still stands. Are both SW1 and Dist4507 showing up on the Campus Topology Map as green with proper icons? If so, then UT should not be showing the duplicates provided the link between the two switches is also on the Topology Map.

The way UT works is to poll the CAM/MAC table from each switch. It will then check the port on which each MAC was found. If the port is a trunk (and trunk port acquisition is not allowed on that port), then the MAC will be dropped. If the port is a topology link (i.e. it shows up on the map), then the MAC will be dropped. Else, the MAC will be learned, and added to the UT end host table.

The only way for a link to be a topology link is for CDP to be running across it, and both device end points are fully managed by Campus Manager.