
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-26-2015 01:11 AM

Solved! Go to Solution.
- Labels:
-
Archive
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2015 04:26 PM
As Lansweeper uses MACs to uniquely identify non-Windows assets, the best solution is to blacklist common MACs (which should be a rare occurrence). A number of MACs known to be shared by devices are automatically blacklisted.
INSERT INTO tsysMacBlacklist (Mac, Comment) VALUES ('00:14:BF:5F:AC:F1', 'SWR2048')
GO
UPDATE tsysupdate SET MacBlacklist = GETDATE()
GO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2015 02:39 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-05-2015 10:55 AM
The switches don't just share 00:14:BF:5F:AC:F1. They share a whole bunch of other MAC addresses as well. You'll need to blacklist all of these common MACs, with the script attached to this email. Rescan both switches afterwards by hitting the Scan All Enabled IP Ranges Now button under IP Address Range Scanning.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-05-2015 01:46 AM
I sent the information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-04-2015 08:39 AM
If the issue persists, please send the information requested in my initial post to support@lansweeper.com

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-03-2015 10:55 PM
This does not work as expected, in fact, it didn't work at all. The MAC was entered in the tsysMacBlacklist table but is not blocked from scans.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2015 01:08 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2015 04:26 PM
As Lansweeper uses MACs to uniquely identify non-Windows assets, the best solution is to blacklist common MACs (which should be a rare occurrence). A number of MACs known to be shared by devices are automatically blacklisted.
INSERT INTO tsysMacBlacklist (Mac, Comment) VALUES ('00:14:BF:5F:AC:F1', 'SWR2048')
GO
UPDATE tsysupdate SET MacBlacklist = GETDATE()
GO

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-26-2015 07:54 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-26-2015 07:45 PM
02/26/2015 09:11:10: Removing duplicate asset with id 580 and unique 192.168.1.250\1 while scanning 192.168.1.250, writing to asset with id 575 and unique 00:14:BF:5F:AC:F1 instead.
02/26/2015 09:31:18: Removing duplicate asset with id 581 and unique 192.168.1.251\1 while scanning 192.168.1.251, writing to asset with id 575 and unique 00:14:BF:5F:AC:E4 instead.
After running the scan tool, it has revealed that there are duplicate mac addresses in play at the port level (assigned per port by the switch). The switches unique mac addresses (above) are so close, when 5F:AC:E4 distributes port mac assignments, they over lap with 5F:AC:F1. Could the asset scan utility in Lansweeper not properly deal with this?
This is from the switch who's primary MAC is 00:14:BF:5F:AC:E4. Int 13 matches the primary MAC for the second switch.
Interface 13:
Description: Ethernet Interface
MAC: 00 14 BF 5F AC F1
Uplink: False
MTU: 1500
Speed: 1000000000
Type: 6
Vlans: Vlan 1
Adminstatus: 1
Status: 2
