cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Overly-aggressive switch merging

JimCaldwell
Engaged Sweeper
I've been having trouble with Lansweeper's scanning of my switches. I first noticed that some switches were just not showing up. Upon further review, I noticed that some switches have "Comments" saying that they received merged info from other assets because they had similar MAC addresses. Unfortunately, it's being far too aggressive about this, and merging different switches on different IP ranges (meaning essentially in different buildings) and with non-overlapping MAC ranges, and I'm missing important information.

As background, many years ago, after my urging that we needed to upgrade and standardize our switches, my boss went out and bought 52 NetGear FS728TP switches (Unfortunately we still have most of them, despite the fact that Netscape Navigator is the only way to manage them, and only works reliably on the same subnet as the management interface). Each port naturally has its own MAC. The problem with buying 52 at a time is that they have pretty close MAC addresses. LANSweeper seems to ignore the actual MAC addresses the switch itself has, just assumes that because they're close, they must be on the same switch. What I'm seeing is this:

05/31/2022 12:07:11 [MERGE] Removing duplicate asset with id 2155 and unique E0:91:F5:07:08:59 while scanning 192.168.10.12, writing to asset with id 1039 and unique E0:91:F5:07:08:51 instead.
05/15/2022 12:07:19 [MERGE] Removing duplicate asset with id 1804 and unique E0:91:F5:07:08:51 while scanning 192.168.10.12, writing to asset with id 1039 and unique E0:91:F5:07:08:59 instead.

Asset 1039 has IP 192.168.25.13, MAC addresses E0:91:F5:07:08:58 through 74. 51 is not between 58 and 74.

Why is LANSweeper merging these assets when they very obviously don't have overlapping MAC addresses? This is not the only switch where it's happening - we have one switch that is getting two other switches merged into it, and the last one on the scanning list has ONE HUNDRED AND FIFTY TWO merge notifications (!!!) despite it being the one at our smallest location with the least number of devices plugged into it.

We're hoping to replace all of these switches late this year, but we're a non-profit, and still trying to recover from COVID economic conditions. It seems like there's a huge bug in the merge code.
4 REPLIES 4

cswroe
Engaged Sweeper II
I just went through my switches as we upgraded last year, and my devices are similar and have close MAC addresses with consecutive 5th Octet and they are not being combined. You may want to email support to see if they can help.

In Scanning Setup do you have "Merge Windows computers based on serial number and model only (not MAC address)" enabled? I can see that being an issue too. https://www.lansweeper.com/knowledgebase/windows-rename-detection/

cswroe wrote:
I just went through my switches as we upgraded last year, and my devices are similar and have close MAC addresses with consecutive 5th Octet and they are not being combined. You may want to email support to see if they can help.

In Scanning Setup do you have "Merge Windows computers based on serial number and model only (not MAC address)" enabled? I can see that being an issue too. https://www.lansweeper.com/knowledgebase/windows-rename-detection/


I do not have that setting enabled. I don't think it would apply to this anyway, since that's an option specifically
referring to Windows Computers, not assets in general.

JimCaldwell
Engaged Sweeper
The two merge notes do indeed. But the device they were merged into is 192.168.25.13. Sorry, I thought I had included that, but it may have gotten snipped during editing.

For further example, take a look at the Comments on switch 192.168.50.10, which has MAC addresses E0:91:F5:12:2F:12-2E - I mean it's even changing the "unique" MAC associated with that asset throughout this log.

06/06/2022 12:25:38
[MERGE] Removing duplicate asset with id 2224 and unique E0:91:F5:12:2F:0E while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2E:E8 instead.
Lansweeper Delete comment
06/06/2022 12:15:19
[MERGE] Removing duplicate asset with id 2217 and unique E0:91:F5:12:2E:D1 while scanning 192.168.17.12, writing to asset with id 991 and unique E0:91:F5:12:2F:02 instead.
Lansweeper Delete comment
06/06/2022 12:12:08
[MERGE] Removing duplicate asset with id 2222 and unique E0:91:F5:12:2E:F4 while scanning 192.168.14.14, writing to asset with id 991 and unique E0:91:F5:12:2F:12 instead.
Lansweeper Delete comment
06/06/2022 12:08:27
[MERGE] Removing duplicate asset with id 2220 and unique E0:91:F5:12:2E:E6 while scanning 192.168.11.11, writing to asset with id 2217 and unique E0:91:F5:12:2E:B8 instead.
Lansweeper Delete comment
06/05/2022 12:24:28
[MERGE] Removing duplicate asset with id 2218 and unique E0:91:F5:12:2F:0E while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2E:E8 instead.
Lansweeper Delete comment
06/05/2022 12:19:51
[MERGE] Removing duplicate asset with id 2219 and unique E0:91:F5:12:2E:B3 while scanning 192.168.21.10, writing to asset with id 2217 and unique E0:91:F5:12:2E:88 instead.
Lansweeper Delete comment
06/05/2022 12:13:51
[MERGE] Removing duplicate asset with id 2215 and unique E0:91:F5:12:2E:D1 while scanning 192.168.17.12, writing to asset with id 991 and unique E0:91:F5:12:2F:02 instead.
Lansweeper Delete comment
06/05/2022 12:13:05
[MERGE] Removing duplicate asset with id 2159 and unique E0:91:F5:12:2E:F4 while scanning 192.168.14.14, writing to asset with id 991 and unique E0:91:F5:12:2F:12 instead.
Lansweeper Delete comment
06/04/2022 12:25:41
[MERGE] Removing duplicate asset with id 2200 and unique E0:91:F5:12:2E:E8 while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2F:0E instead.
Lansweeper Delete comment
06/04/2022 12:17:28
[MERGE] Removing duplicate asset with id 2199 and unique E0:91:F5:12:2E:5D while scanning 192.168.17.14, writing to asset with id 2159 and unique E0:91:F5:12:2E:87 instead.
Lansweeper Delete comment
06/04/2022 12:08:26
[MERGE] Removing duplicate asset with id 2209 and unique E0:91:F5:12:2E:F4 while scanning 192.168.14.14, writing to asset with id 991 and unique E0:91:F5:12:2F:12 instead.
Lansweeper Delete comment
06/03/2022 12:24:24
[MERGE] Removing duplicate asset with id 2197 and unique E0:91:F5:12:2F:0E while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2E:E8 instead.
Lansweeper Delete comment
06/03/2022 12:20:50
[MERGE] Removing duplicate asset with id 2198 and unique E0:91:F5:12:2E:B3 while scanning 192.168.21.10, writing to asset with id 2159 and unique E0:91:F5:12:2E:88 instead.
Lansweeper Delete comment
06/03/2022 12:14:00
[MERGE] Removing duplicate asset with id 2196 and unique E0:91:F5:12:2E:D1 while scanning 192.168.17.12, writing to asset with id 991 and unique E0:91:F5:12:2F:02 instead.
Lansweeper Delete comment
06/03/2022 12:13:15
[MERGE] Removing duplicate asset with id 2191 and unique E0:91:F5:12:2E:62 while scanning 192.168.17.14, writing to asset with id 2159 and unique E0:91:F5:12:2E:87 instead.
Lansweeper Delete comment
06/03/2022 12:06:00
[MERGE] Removing duplicate asset with id 2192 and unique E0:91:F5:12:2E:CD while scanning 192.168.10.11, writing to asset with id 991 and unique E0:91:F5:12:2F:01 instead.
Lansweeper Delete comment
06/02/2022 12:25:20
[MERGE] Removing duplicate asset with id 2174 and unique E0:91:F5:12:2E:E8 while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2F:0E instead.
Lansweeper Delete comment
06/02/2022 12:20:39
[MERGE] Removing duplicate asset with id 2190 and unique E0:91:F5:12:2E:B3 while scanning 192.168.21.10, writing to asset with id 2159 and unique E0:91:F5:12:2E:89 instead.
Lansweeper Delete comment
06/02/2022 12:14:37
[MERGE] Removing duplicate asset with id 2188 and unique E0:91:F5:12:2E:D1 while scanning 192.168.17.12, writing to asset with id 2174 and unique E0:91:F5:12:2F:02 instead.
Lansweeper Delete comment
06/02/2022 12:13:51
[MERGE] Removing duplicate asset with id 2173 and unique E0:91:F5:12:2E:5D while scanning 192.168.17.14, writing to asset with id 2159 and unique E0:91:F5:12:2E:80 instead.
Lansweeper Delete comment
06/02/2022 12:07:22
[MERGE] Removing duplicate asset with id 2184 and unique E0:91:F5:12:2E:F4 while scanning 192.168.10.11, writing to asset with id 2174 and unique E0:91:F5:12:2E:CD instead.
Lansweeper Delete comment
06/01/2022 12:27:03
[MERGE] Removing duplicate asset with id 2130 and unique E0:91:F5:12:2E:E8 while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2F:13 instead.
Lansweeper Delete comment
06/01/2022 12:23:03
[MERGE] Removing duplicate asset with id 2172 and unique E0:91:F5:12:2E:B3 while scanning 192.168.21.10, writing to asset with id 2159 and unique E0:91:F5:12:2E:88 instead.
Lansweeper Delete comment
06/01/2022 12:14:28
[MERGE] Removing duplicate asset with id 2171 and unique E0:91:F5:12:2E:80 while scanning 192.168.17.14, writing to asset with id 2159 and unique E0:91:F5:12:2E:62 instead.
Lansweeper Delete comment
06/01/2022 12:09:24
[MERGE] Removing duplicate asset with id 2160 and unique E0:91:F5:12:2E:E6 while scanning 192.168.15.10, writing to asset with id 2130 and unique E0:91:F5:12:2E:B8 instead.
Lansweeper Delete comment
06/01/2022 12:07:17
[MERGE] Removing duplicate asset with id 2170 and unique E0:91:F5:12:2E:F4 while scanning 192.168.10.11, writing to asset with id 2160 and unique E0:91:F5:12:2E:CD instead.
Lansweeper Delete comment
05/31/2022 12:25:07
[MERGE] Removing duplicate asset with id 2157 and unique E0:91:F5:12:2F:0E while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2E:E8 instead.
Lansweeper Delete comment
05/31/2022 12:20:36
[MERGE] Removing duplicate asset with id 2158 and unique E0:91:F5:12:2E:B3 while scanning 192.168.21.10, writing to asset with id 2130 and unique E0:91:F5:12:2E:89 instead.
Lansweeper Delete comment
05/31/2022 12:14:26
[MERGE] Removing duplicate asset with id 2144 and unique E0:91:F5:12:2E:D1 while scanning 192.168.17.12, writing to asset with id 991 and unique E0:91:F5:12:2F:02 instead.
Lansweeper Delete comment
05/31/2022 12:13:39
[MERGE] Removing duplicate asset with id 2143 and unique E0:91:F5:12:2E:5D while scanning 192.168.17.14, writing to asset with id 2130 and unique E0:91:F5:12:2E:87 instead.
Lansweeper Delete comment
05/31/2022 12:08:21
[MERGE] Removing duplicate asset with id 2156 and unique E0:91:F5:12:2E:E6 while scanning 192.168.11.11, writing to asset with id 2144 and unique E0:91:F5:12:2E:B8 instead.
Lansweeper Delete comment
05/30/2022 12:23:45
[MERGE] Removing duplicate asset with id 2139 and unique E0:91:F5:12:2E:E8 while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2F:0E instead.
Lansweeper Delete comment
05/30/2022 12:19:14
[MERGE] Removing duplicate asset with id 2142 and unique E0:91:F5:12:2E:B3 while scanning 192.168.21.10, writing to asset with id 2130 and unique E0:91:F5:12:2E:88 instead.
Lansweeper Delete comment
05/30/2022 12:12:16
[MERGE] Removing duplicate asset with id 2138 and unique E0:91:F5:12:2E:5D while scanning 192.168.17.14, writing to asset with id 2130 and unique E0:91:F5:12:2E:87 instead.
Lansweeper Delete comment
05/30/2022 12:08:48
[MERGE] Removing duplicate asset with id 2140 and unique E0:91:F5:12:2E:F4 while scanning 192.168.14.14, writing to asset with id 991 and unique E0:91:F5:12:2F:12 instead.
Lansweeper Delete comment
05/30/2022 12:08:29
[MERGE] Removing duplicate asset with id 2141 and unique E0:91:F5:12:2E:C9 while scanning 192.168.15.10, writing to asset with id 2139 and unique E0:91:F5:12:2E:E6 instead.
Lansweeper Delete comment
05/29/2022 12:22:00
[MERGE] Removing duplicate asset with id 2136 and unique E0:91:F5:12:2F:0E while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2E:E8 instead.
Lansweeper Delete comment
05/29/2022 12:17:48
[MERGE] Removing duplicate asset with id 2137 and unique E0:91:F5:12:2E:B3 while scanning 192.168.21.10, writing to asset with id 2130 and unique E0:91:F5:12:2E:89 instead.
Lansweeper Delete comment
05/29/2022 12:13:05
[MERGE] Removing duplicate asset with id 2134 and unique E0:91:F5:12:2E:D1 while scanning 192.168.17.12, writing to asset with id 991 and unique E0:91:F5:12:2F:02 instead.
Lansweeper Delete comment
05/29/2022 12:12:12
[MERGE] Removing duplicate asset with id 2135 and unique E0:91:F5:12:2E:87 while scanning 192.168.17.14, writing to asset with id 2130 and unique E0:91:F5:12:2E:5D instead.
Lansweeper Delete comment
05/29/2022 12:07:36
[MERGE] Removing duplicate asset with id 2133 and unique E0:91:F5:12:2E:F4 while scanning 192.168.14.14, writing to asset with id 991 and unique E0:91:F5:12:2F:12 instead.
Lansweeper Delete comment
05/29/2022 12:07:35
[MERGE] Removing duplicate asset with id 2033 and unique E0:91:F5:12:2E:E6 while scanning 192.168.14.14, writing to asset with id 991 and unique E0:91:F5:12:2F:12 instead.
Lansweeper Delete comment
05/28/2022 12:27:26
[MERGE] Removing duplicate asset with id 2123 and unique E0:91:F5:12:2E:D1 while scanning 192.168.48.10, writing to asset with id 2033 and unique E0:91:F5:12:2E:B3 instead.
Lansweeper Delete comment
05/28/2022 12:18:07
[MERGE] Removing duplicate asset with id 2122 and unique E0:91:F5:12:2E:5D while scanning 192.168.17.14, writing to asset with id 2033 and unique E0:91:F5:12:2E:89 instead.
Lansweeper Delete comment
05/28/2022 12:17:43
[MERGE] Removing duplicate asset with id 2129 and unique E0:91:F5:12:2F:02 while scanning 192.168.19.11, writing to asset with id 991 and unique E0:91:F5:12:2F:24 instead.
Lansweeper Delete comment
05/28/2022 12:05:31
[MERGE] Removing duplicate asset with id 2124 and unique E0:91:F5:12:2F:02 while scanning 192.168.10.11, writing to asset with id 2123 and unique E0:91:F5:12:2E:CD instead.
Lansweeper Delete comment
05/27/2022 12:24:53
[MERGE] Removing duplicate asset with id 2104 and unique E0:91:F5:12:2E:E8 while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2F:0E instead.
Lansweeper Delete comment
05/27/2022 12:20:19
[MERGE] Removing duplicate asset with id 2121 and unique E0:91:F5:12:2E:B3 while scanning 192.168.21.10, writing to asset with id 2033 and unique E0:91:F5:12:2E:89 instead.
Lansweeper Delete comment
05/27/2022 12:14:29
[MERGE] Removing duplicate asset with id 2120 and unique E0:91:F5:12:2E:D1 while scanning 192.168.17.12, writing to asset with id 2104 and unique E0:91:F5:12:2E:F4 instead.
Lansweeper Delete comment
05/27/2022 12:13:45
[MERGE] Removing duplicate asset with id 2098 and unique E0:91:F5:12:2E:80 while scanning 192.168.17.14, writing to asset with id 2033 and unique E0:91:F5:12:2E:5D instead.
Lansweeper Delete comment
05/26/2022 12:23:19
[MERGE] Removing duplicate asset with id 2100 and unique E0:91:F5:12:2F:0E while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2E:E8 instead.
Lansweeper Delete comment
05/26/2022 12:18:49
[MERGE] Removing duplicate asset with id 2101 and unique E0:91:F5:12:2E:88 while scanning 192.168.21.10, writing to asset with id 2098 and unique E0:91:F5:12:2E:B3 instead.
Lansweeper Delete comment
05/26/2022 12:13:36
[MERGE] Removing duplicate asset with id 2097 and unique E0:91:F5:12:2E:D1 while scanning 192.168.17.12, writing to asset with id 991 and unique E0:91:F5:12:2F:02 instead.
Lansweeper Delete comment
05/26/2022 12:12:42
[MERGE] Removing duplicate asset with id 2086 and unique E0:91:F5:12:2E:80 while scanning 192.168.17.14, writing to asset with id 2033 and unique E0:91:F5:12:2E:62 instead.
Lansweeper Delete comment
05/26/2022 12:09:48
[MERGE] Removing duplicate asset with id 2089 and unique E0:91:F5:12:2E:F4 while scanning 192.168.14.14, writing to asset with id 991 and unique E0:91:F5:12:2F:12 instead.
Lansweeper Delete comment
05/25/2022 12:23:46
[MERGE] Removing duplicate asset with id 2088 and unique E0:91:F5:12:2F:0E while scanning 192.168.40.10, writing to asset with id 991 and unique E0:91:F5:12:2E:E8 instead.
Lansweeper Delete comment
05/25/2022 12:19:38
[MERGE] Removing duplicate asset with id 2087 and unique E0:91:F5:12:2E:88 while scanning 192.168.21.10, writing to asset with id 2086 and unique E0:91:F5:12:2E:B3 instead.
Lansweeper Delete comment
05/25/2022 12:14:18
[MERGE] Removing duplicate asset with id 2079 and unique E0:91:F5:12:2E:D1 while scanning 192.168.17.12, writing to asset with id 991 and unique E0:91:F5:12:2F:02 instead.
Lansweeper Delete comment
05/25/2022 12:13:27
[MERGE] Removing duplicate asset with id 2078 and unique E0:91:F5:12:2E:62 while scanning 192.168.17.14, writing to asset with id 2033 and unique E0:91:F5:12:2E:80 instead.
Lansweeper Delete comment
05/25/2022 12:13:15
[MERGE] Removing duplicate asset with id 2084 and unique E0:91:F5:12:2E:F4 while scanning 192.168.14.14, writing to asset with id 991 and unique E0:91:F5:12:2F:12 instead.
Lansweeper Delete comment
05/25/2022 12:07:54
[MERGE] Removing duplicate asset with id 2085 and unique E0:91:F5:12:2E:B8 while scanning 192.168.11.11, writing to asset with id 2079 and unique E0:91:F5:12:2E:E6 instead.
Lansweeper Delete comment
05/24/2022 12:27:47
[MERGE] Removing duplicate asset with id 2068 and unique E0:91:F5:12:2F:02 while scanning 192.168.50.10, writing to asset with id 991 and unique E0:91:F5:12:2F:24 instead.
Lansweeper Delete comment
05/24/2022 12:19:17
[MERGE] Removing duplicate asset with id 2077 and unique E0:91:F5:12:2E:B3 while scanning 192.168.21.10, writing to asset with id 2033 and unique E0:91:F5:12:2E:88 instead.
Lansweeper Delete comment
05/24/2022 12:14:50
[MERGE] Removing duplicate asset with id 2075 and unique E0:91:F5:12:2E:F4 while scanning 192.168.17.12, writing to asset with id 2068 and unique E0:91:F5:12:2E:D1 instead.
Lansweeper Delete comment
05/24/2022 12:13:53
[MERGE] Removing duplicate asset with id 2065 and unique E0:91:F5:12:2E:85 while scanning 192.168.17.14, writing to asset with id 2033 and unique E0:91:F5:12:2E:5D instead.
Lansweeper Delete comment
05/24/2022 12:08:49
[MERGE] Removing duplicate asset with id 2076 and unique E0:91:F5:12:2E:C9 while scanning 192.168.15.10, writing to asset with id 2068 and unique E0:91:F5:12:2E:E6 instead.
Lansweeper Delete comment
05/24/2022 09:53:28
[MERGE] Removing duplicate asset with id 2067 and unique E0:91:F5:12:2F:24 while scanning 192.168.50.10, writing to asset with id 991 and unique E0:91:F5:12:2F:01 instead.
Lansweeper Delete comment
05/24/2022 09:45:13
[MERGE] Removing duplicate asset with id 2066 and unique E0:91:F5:12:2E:88 while scanning 192.168.21.10, writing to asset with id 2065 and unique E0:91:F5:12:2E:B3 instead.
Lansweeper Delete comment
05/24/2022 09:44:45
[MERGE] Removing duplicate asset with id 2061 and unique E0:91:F5:12:2E:E8 while scanning 192.168.14.14, writing to asset with id 991 and unique E0:91:F5:12:2F:11 instead.
Lansweeper Delete comment
05/24/2022 09:39:14
[MERGE] Removing duplicate asset with id 2059 and unique E0:91:F5:12:2E:62 while scanning 192.168.17.14, writing to asset with id 2033 and unique E0:91:F5:12:2E:80 instead.
Lansweeper Delete comment
05/24/2022 09:34:55
[MERGE] Removing duplicate asset with id 2064 and unique E0:91:F5:12:2E:C9 while scanning 192.168.15.10, writing to asset with id 2061 and unique E0:91:F5:12:2E:E6 instead.
Lansweeper Delete comment
05/24/2022 09:27:56
[MERGE] Removing duplicate asset with id 2060 and unique E0:91:F5:12:2E:64 while scanning 192.168.3.11, writing to asset with id 2059 and unique E0:91:F5:12:2E:4F instead.
Lansweeper Delete comment

(More removed due to post size limit)

cswroe
Engaged Sweeper II
Your switches all have the same IP address? In your example, those two devices are 192.168.10.12