Getting Null values when trying to SNMP to a device from the probe

Last Modified

Tue Dec 01 22:23 GMT 2020

Description

  • Discovery job does not discover the SNMP properties of a device.
  • When we try to discover the device from the probe we get no information on the system information and we get NULL values on the OID we trying to get from the device.

Environment

  • N-able N-central

Solution

  1. Search in the NAAssetDiscovery.log on the agent log folder you will find an output similar to the following:
    [STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr CimData[0].CimRecords[]: 1 items[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr CimRecords[0].Recordid: 00[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr CimRecords[0].ContentHash: fe447d14[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr CimRecords[0].CimValueFields[]: 15 items[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr NetbiosName=cisco-capwap-controller[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr Domain=novadic-kentron.local[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr TotalPhysicalMemory={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr AMT_UUID={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr Version={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr Manufacturer={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr Model={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr SerialNumber={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr AMT_Version={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr wirelessmanagementstate={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr SystemType={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr PopulatedMemory_Slots={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr TotalMemory_Slots={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr ChassisType={NULL}[STP SmartThreadPool Thread #9] 2016-03-11 13:30:08,092 DEBUG com.nable.agent.module.asset.NAAssetMgr UUID={NULL}
  2. Take a look at the NAAsset probe.log and locate the error similar to the following:
    [STP SmartThreadPool Thread #11] 2016-03-16 15:51:25,104 ERROR com.nable.agent.probe.NASnmpProbe SNMP Discovery for device 10.200.1.26 is stopped due to: Not able to scan the OID 1.3.6.1.2.1.1.2.0(sysDescr) with port:community as 0:[STP SmartThreadPool Thread #11] 2016-03-16 15:51:25,104 ERROR com.nable.agent.probe.NASnmpProbe 10.200.1.26 The exception is System.ArgumentNullException: Value cannot be null.Parameter name: sat Mao.DotNet.NetString2Chars(String s)at Org.Snmp.Snmp_pp.UdpAddress.CreateUdpAddress(String ip, Int32 port)at Org.Snmp.Snmp_pp.UdpAddress..ctor(String ip, Int32 port)at com.nable.agent.module.snmp.v3support.SnmpV2V1Client.snmpGet(String oidStr, Boolean bTreatAsNormalString)at com.nable.agent.probe.NASnmpProbe.InitialTest()
  3. Use an SNMP tool of your choice, such as SNMPGet (http://www.snmpsoft.com) to get the OID that appears in the NAAssetProbe.log through a scheduled task. Most probably it will show another OID as below:
    OID=.1.3.6.1.2.1.1.2.0Type=OIDValue=1.3.6.1.4.1.9.1.163
  4. Try to SNMP get the OID that appeared in the previous step using the below:
    snmpget.exe -r:10.200.1.26 -c:nksnmp594378ap -v:2c -o:.1.3.6.1.4.1.9.1.1631SnmpGet v1.01 - Copyright (C) 2009 SnmpSoft Company[ More useful network tools on http://www.snmpsoft.com ]OID=.1.3.6.1.4.1.9.1.1631Type=Value=

  5. You now have proof to the partner that the problem is the target device and not N-able N-central (null values were returned to SNMPGet also, confirming device issue).