Assets with different MACs/IPs getting merged

[Martin1999]

Hi there,

we are running the latest LanSweeper version 8.0.130.17 and having the issue the a couple of devices getting always merged even so they have different MAC- and IP-addresses.

Attached are screenshots of two example devices which getting merged. In the comments section I find a lot of these entries:

22/10/2020 14:14:18
[MERGE] Removing duplicate asset with id 15511 and unique 172.20.48.167\1 while scanning 172.20.48.167, writing to asset with id 15273 and unique 80:96:21:ED:D9:01 instead. Merged asset with asset unique 80:96:21:ED:E5:01 and MAC address 80:96:21:ED:E5:01 into asset 15511 with asset unique 172.20.48.167\1 and MAC address .
Lansweeper Delete comment
21/10/2020 12:25:01
[MERGE] Removing duplicate asset with id 15475 and unique 172.20.48.167\1 while scanning 172.20.48.167, writing to asset with id 15273 and unique 80:96:21:ED:AF:01 instead. Merged asset with asset unique 80:96:21:ED:E5:01 and MAC address 80:96:21:ED:E5:01 into asset 15475 with asset unique 172.20.48.167\1 and MAC address .
Lansweeper Delete comment
21/10/2020 12:24:03
[MERGE] Removing duplicate asset with id 15474 and unique 172.20.48.164\1 while scanning 172.20.48.164, writing to asset with id 15273 and unique 80:96:21:ED:DC:01 instead. Merged asset with asset unique 80:96:21:ED:AF:01 and MAC address 80:96:21:ED:AF:01 into asset 15474 with asset unique 172.20.48.164\1 and MAC address .
Lansweeper Delete comment
21/10/2020 12:24:02
[MERGE] Removing duplicate asset with id 15473 and unique 172.20.48.165\1 while scanning 172.20.48.165, writing to asset with id 15273 and unique 80:96:21:ED:E2:01 instead. Merged asset with asset unique 80:96:21:ED:DC:01 and MAC address 80:96:21:ED:DC:01 into asset 15473 with asset unique 172.20.48.165\1 and MAC address .
Lansweeper Delete comment
21/10/2020 12:24:01
[MERGE] Removing duplicate asset with id 15476 and unique 172.20.48.166\1 while scanning 172.20.48.166, writing to asset with id 15273 and unique 80:96:21:ED:D9:01 instead. Merged asset with asset unique 80:96:21:ED:E2:01 and MAC address 80:96:21:ED:E2:01 into asset 15476 with asset unique 172.20.48.166\1 and MAC address .
Lansweeper Delete comment
17/10/2020 12:17:29
[MERGE] Removing duplicate asset with id 15442 and unique 172.20.48.167\1 while scanning 172.20.48.167, writing to asset with id 15273 and unique 80:96:21:ED:E2:01 instead. Merged asset with asset unique 80:96:21:ED:E5:01 and MAC address 80:96:21:ED:E5:01 into asset 15442 with asset unique 172.20.48.167\1 and MAC address .
Lansweeper Delete comment
14/10/2020 13:32:27
[MERGE] Removing duplicate asset with id 15419 and unique 80:96:21:ED:E5:01 while scanning 10.255.222.167, writing to asset with id 15273 and unique 80:96:21:ED:AF:01 instead. Merged asset with asset unique 80:96:21:ED:D9:01 and MAC address 80:96:21:ED:D9:01 into asset 15419 with asset unique 80:96:21:ED:E5:01 and MAC address 80:96:21:ED:E5:01.
Lansweeper Delete comment
14/10/2020 13:32:27
[MERGE] Removing duplicate asset with id 15418 and unique 80:96:21:ED:DC:01 while scanning 10.255.222.167, writing to asset with id 15273 and unique 80:96:21:ED:AF:01 instead. Merged asset with asset unique 80:96:21:ED:D9:01 and MAC address 80:96:21:ED:D9:01 into asset 15418 with asset unique 80:96:21:ED:DC:01 and MAC address 80:96:21:ED:DC:01.
Lansweeper Delete comment
14/10/2020 13:32:26
[MERGE] Removing duplicate asset with id 15417 and unique 80:96:21:ED:E2:01 while scanning 10.255.222.167, writing to asset with id 15273 and unique 80:96:21:ED:AF:01 instead. Merged asset with asset unique 80:96:21:ED:D9:01 and MAC address 80:96:21:ED:D9:01 into asset 15417 with asset unique 80:96:21:ED:E2:01 and MAC address 80:96:21:ED:E2:01.
Lansweeper Delete comment

Any idea why this is happening here?

Thanks
Martin

[mateussantos73]

Dear support, very good!

But do it for 200 switches is very causative. Thank you very much.

[mateussantos73]

Dear support,

Having to do this for a connection of IPs doesn't seem like the best solution to me. Now in 2022, do we have something better to solve this problem?

[FrankSc]

Hello,

An asset can have multiple MAC addresses, but for switches the duplicate address can be also picked up from an interface that was found during scanning.
To prevent the merging to take place, you can add the duplicate addresses to a table in the database. This is described in the Forum post below.

https://www.lansweeper.com/forum/yaf_postst19704_Device-Duplicates.aspx#post63502