NetXMS Support Forum

Hi,

I would expect that these devices support SNMP. If this is so, you need to enable snmp on the device and run configuration poll in NetXMS to check if SNMP capablitiy is detected (it's visible on node's Overview page). When this is done, you can use MIB explorer to walk available OIDs and add data collection items.

The other possible approach is to use ssh - in node properties you can specify ssh password or key. Or, if you have many devices, credentials can be specified in Configuration -> Network credentials - these will be auto-probed. If ssh credentials are ok, on configuration poll SSH capability should become "YES".

And, finally, if your device runs under linux, you can try generic NetXMS agents - but this depends on platform/cpu and not necessarily would work

Hello,
I'm new to NetXMS.
Someone can tell me if there are templates / method to monitor Storage SAN?

Any suggestion will be appreciated

Hello,

Q: Was it working on older versions or this is new setup?
A: Unknown. This is a new/clean setup. Specific is tunneled agent setup. And agent uptime monitoring (which pointed out issue).

Q: What exact version of openssl package you are using?
A: Package: libssl3, Version: 3.0.11-1~deb12u2, APT-Sources: http://deb.debian.org/debian bookworm/main amd64 Packages

Br, Ales

Tried clean test server install with just the node that do not work and it works on test server.
Tried renaming and then recreate the node that does not work and now snmp v3 works on the new node on production server.
Odd issue that only snmp v3 is not working on some old nodes.

I will recreate all nodes to be safe.

Agent crashes within OpenSSL library (specifically within EVP_PKEY_CTX_new) and I do not see any obvious problems with calling code. This part was not changed for quite some time. Was it working on older versions or this is new setup? What exact version of openssl package you are using?

Best regards,
Victor

nxshell is integration tool, that allows python code to interact with netxms server. For Windows GUI client you need to install this: https://netxms.com/download/releases/4.5/netxms-client-4.5.6-x64.exe

Current Windows WEB UI installer includes web api as well. It can be reached at http://127.0.0.1:4788/api/
War file itself is located in C:\NetXMS-WebUI\jetty-base\webapps\api.war

Yes, debug log on level 6 would be beneficial. Couple of options
 - use some netxms agent in proxy mode and take the log of it
- use some test installation of netxms server that has just a couple of SNMP nodes (it's also worth to unmanage the node that represents server itself to minimize logged stuff)

Hi,

Any known issues with connecting to snmp v3 agents?
Have odd issue where some nodes work and some don't with the exact same auth configuration.

The node that netxms can't connect to agent with v3 is verified that the agent is running and v3 auth information works in other snmp explorer software.

The node can connect with v2c if enabled, just v3 having issues.

Tried debug logs but since it is the server very hard with spammed debug log, set snmp.discovery to level 6 and it shows SnmpCheckV3CommSettings trying then fail.

When i do full config poll on a node that V3 works on there is no SnmpCheckV3CommSettings in logs it just connects and polls.

The nodes that V3 work on and the nodes that does not have exact same config no question since the snmp is set with nxshell script on all nodes in the container.

Upgraded to v4.5.6 but the problem with maps persists.