Troubleshooting custom OID scanning issues

Custom OID scanning is a feature introduced in Lansweeper 7.0. If you are using an older Lansweeper release, you will need to update by following the instructions in this knowledge base article.
Not all Lansweeper licenses support custom OID scanning. If your particular license does not support this feature, please visit this page for more information.

Do you have Custom OID scanning issues? SNMP is one of the protocols through which Lansweeper can retrieve data from network devices like printers, switches, routers etc. By default, Lansweeper retrieves various properties from these devices via SNMP. This includes basic details like serial number and description, but also more advanced details like interface and printer toner information. A device that has been successfully scanned via SNMP can be identified by the device OID listed in its Summary tab.

In addition to this, the custom OID scanning feature allows you to retrieve any other information that is stored in an SNMP OID on the device. Custom OID scanning lets you specify one or more OIDs to be scanned for a specific group of devices, giving you the ability to gather even more device data. Any device that has been successfully scanned via SNMP can be scanned further via custom OID scanning. This article explains how to troubleshoot if custom OIDs you've submitted are not being scanned.

If you've submitted custom OIDs for scanning but data is not being returned, do the following:

  1. Make sure your Lansweeper license allows access to the custom OID scanning feature.
    Not all Lansweeper licenses support custom OID scanning. If your particular license does not support this feature, please visit this page for more information.
  2. Make sure there is an OID listed in the device's Summary tab, indicating that Lansweeper is able to access the SNMP protocol on the device. If there isn't, troubleshoot the SNMP access issue by following the instructions in this knowledge base article. Custom OID scanning cannot retrieve data if the SNMP protocol in general is not accessible on the device.
    SNMP OID in Summary tab
  3. Make sure the Enabled checkbox for your OID target is ticked under Scanning\Custom OID Scanning
    enabling custom OID scanning target
  4. Make sure your OID target is applied to the correct assets. If you choose Asset Type as your Target Type for instance, make sure the chosen asset type corresponds with the asset type of your device.
     If you choose Asset Type as your Target Type, you must submit the asset type Lansweeper detects for your devices during scanning. If you manually edit a device's asset type, custom OID scanning does not take this into account.
  5. Make sure your OID target's Manufacturer and Model are either empty or correspond exactly with what is listed on the device's Lansweeper webpage.
    Manufacturer in custom OID configuration
    Manufacturer on asset page
  6. Make sure the OID submitted in your OID target is correct and contains data. You can use the tool below, found on your Lansweeper server, for troubleshooting. Run the tool from your Lansweeper server and submit your device's IP address and SNMP scanning credential. In the SNMP Custom OIDs field, submit the OIDs you'd like to test. Multiple OIDs can be submitted, separated with commas.
    Program Files (x86)\Lansweeper\Actions\Devicetester.exe
    testing custom OIDs in Devicetester
  7. Rescan the network device, e.g. by hitting the Rescan Asset button on the device's Lansweeper webpage.
  8. Check the Scanned OIDs tab on individual asset pages or built-in or custom reports in the Reports tab for the retrieved data.
    checking the Scanned OIDs tab

Related Articles