
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 07:06 AM
Hi Team,
I have a scan target in my config like 10.0.0.1 - 10.0.30.254 but found some of my servers are not being detected.
To troubleshoot added the individual IP to scan target 10.0.0.115 and manually triggered scan. The server was scanned and the asset was listed with details of hardware, software etc.,
After sometime the asset was automatically removed, while checking the issue found that the asset gets removed after the full scan target "10.0.0.1 - 10.0.30.254" is run as per daily schedule.
Tested twice and the same scenario happens again. The server which was scanned using individual IP as target gets removed after the scheduled full network scan.
I am just setting up my installation and after POC we will be purchasing the product. Please help to resolve this issue.
Thanks,
Praveen E
I have a scan target in my config like 10.0.0.1 - 10.0.30.254 but found some of my servers are not being detected.
To troubleshoot added the individual IP to scan target 10.0.0.115 and manually triggered scan. The server was scanned and the asset was listed with details of hardware, software etc.,
After sometime the asset was automatically removed, while checking the issue found that the asset gets removed after the full scan target "10.0.0.1 - 10.0.30.254" is run as per daily schedule.
Tested twice and the same scenario happens again. The server which was scanned using individual IP as target gets removed after the scheduled full network scan.
I am just setting up my installation and after POC we will be purchasing the product. Please help to resolve this issue.
Thanks,
Praveen E
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 01:25 PM
Hi Praveen,
The issue you're experiencing is likely caused because there is another asset that shares a MAC address with the asset that is disappearing. When Lansweeper finds a MAC when scanning an asset that is already part of another asset's record, it assumes it is dealing with the same asset and will merge the asset into the existing one, to avoid duplication. In most cases this is the correct action, and this functionality is crucial for scanning assets that have many interfaces and associated MAC addresses such as switches. There are some cases where this action is incorrect though. For instance certain virtual network adapters will employ non-unique MAC addresses and cause this kind of unwanted merging behavior. We do have a procedure available to blacklist these types of generic MAC addresses though:
The issue you're experiencing is likely caused because there is another asset that shares a MAC address with the asset that is disappearing. When Lansweeper finds a MAC when scanning an asset that is already part of another asset's record, it assumes it is dealing with the same asset and will merge the asset into the existing one, to avoid duplication. In most cases this is the correct action, and this functionality is crucial for scanning assets that have many interfaces and associated MAC addresses such as switches. There are some cases where this action is incorrect though. For instance certain virtual network adapters will employ non-unique MAC addresses and cause this kind of unwanted merging behavior. We do have a procedure available to blacklist these types of generic MAC addresses though:
- Determine which MAC addresses appear in multiple assets, if you rescan the asset you can go to the Config\Network\Network tab on the asset page to check for any virtual adapters, these usually cause this kind of issue.
- Go to Configuration\Database Scripts and copy/paste the script below. Replace the generic MAC address value in the script with your duplicate MAC address, you can run this script multiple times for multiple MACs. You can alter the comment highlighted in yellow with any text value you prefer for future reference.
<script removed> - Click on 'Execute SQL Script'.
- Rescan the IP Range in question.
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 03:25 PM
Thanks Bruce,
The DB Script did the Magic. The assets are reporting now.
The issue was with the MAC address of Docker network interface which was same for all servers.
Thanks,
Praveen E
The DB Script did the Magic. The assets are reporting now.
The issue was with the MAC address of Docker network interface which was same for all servers.
Thanks,
Praveen E
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 01:25 PM
Hi Praveen,
The issue you're experiencing is likely caused because there is another asset that shares a MAC address with the asset that is disappearing. When Lansweeper finds a MAC when scanning an asset that is already part of another asset's record, it assumes it is dealing with the same asset and will merge the asset into the existing one, to avoid duplication. In most cases this is the correct action, and this functionality is crucial for scanning assets that have many interfaces and associated MAC addresses such as switches. There are some cases where this action is incorrect though. For instance certain virtual network adapters will employ non-unique MAC addresses and cause this kind of unwanted merging behavior. We do have a procedure available to blacklist these types of generic MAC addresses though:
The issue you're experiencing is likely caused because there is another asset that shares a MAC address with the asset that is disappearing. When Lansweeper finds a MAC when scanning an asset that is already part of another asset's record, it assumes it is dealing with the same asset and will merge the asset into the existing one, to avoid duplication. In most cases this is the correct action, and this functionality is crucial for scanning assets that have many interfaces and associated MAC addresses such as switches. There are some cases where this action is incorrect though. For instance certain virtual network adapters will employ non-unique MAC addresses and cause this kind of unwanted merging behavior. We do have a procedure available to blacklist these types of generic MAC addresses though:
- Determine which MAC addresses appear in multiple assets, if you rescan the asset you can go to the Config\Network\Network tab on the asset page to check for any virtual adapters, these usually cause this kind of issue.
- Go to Configuration\Database Scripts and copy/paste the script below. Replace the generic MAC address value in the script with your duplicate MAC address, you can run this script multiple times for multiple MACs. You can alter the comment highlighted in yellow with any text value you prefer for future reference.
<script removed> - Click on 'Execute SQL Script'.
- Rescan the IP Range in question.
