Cannot do SNMP MIB walk

Started by callanl, November 11, 2023, 01:02:41 AM

Previous topic - Next topic

callanl

MIBs have been successfully compiled.  However they do not display in the web interface or desktop client.  Here is the error when trying to Walk MIB: 

Cannot do SNMP MIB tree walk: Cannot invoke "org.netxms.client.snmp.SnmpObjectId.toString()" because the return value of "org.netxms.client.snmp.MibObject.getObjectId()" is null

The server is version 4.4.2 and running on Ubuntu 20.04

Any ideas would be much appreciated.

Filipp Sudanov

What version of client is that? Is it legacy or the new one? Have you tried latest 4.4.3?
What actions do you perform to get to that error - mib explorer on node or something else?

callanl

I have upgraded to the latest.  

Now I can see all the MIB in both versions of the Web Client and also on the new Windows interface. 

They are still missing on the Legacy Windows interface..... that's not a big deal. 

I am still getting the above error on both interfaces if you try to walk from the root. 
If you drill down into MIB tree and start your Walk from there it is now working. 

Nem0

Your device must have SNMP support enabled with correct credentials. And IP of your netxms server must have permission to query your device.

MIB files are used only to add textual representation of OID  and human readable description to OID. 

Please try to walk across SNMP tree  of your device in a CLI with util from net-snmp 
snmpwalk -v2c -c COMMUNITY 192.168.27.78  .1.3.6.1.2.1.1.1 
SNMPv2-MIB::sysDescr.0 = STRING: Device: QSW-4610-28T-AC
SoftWare Version 8.2.1.177
BootRom Version 2011.12.21
HardWare Version 1.0.2
  Serial No.:6210021120210459
Copyright (C) 2021 by QTECH LLC
All rights reserved

or with netxms server's CLI util

nxsnmpwalk -v2c -c COMMUNITY 192.168.27.78  .1.3.6.1.2.1.1.1
.1.3.6.1.2.1.1.1.0 [STRING]: Device: QSW-4610-28T-AC
SoftWare Version 8.2.1.177
BootRom Version 2011.12.21
HardWare Version 1.0.2
  Serial No.:6210021120210459
Copyright (C) 2021 by QTECH LLC
All rights reserved

You should get similar response indicating correct settings of your device