NetXMS Support Forum

Please check again, this should be now fixed

NXSL functions accept OIDs both with and without the leading dot. Returned values are without the dot. So both of below lines will print "System description: 1.3.6.1.4.1.14988.1"

println("System description: " .. $node.createSNMPTransport()?.getValue(".1.3.6.1.2.1.1.2.0") );
println("System description: " .. $node.createSNMPTransport()?.getValue("1.3.6.1.2.1.1.2.0") );

?. is safe dereference which appeared in 5.0 - should createSNMPTransport() return null, this will not produce script error.

We will discuss internally, if background image size can be considering when opening map.

As for now, if size in map properties is 0, 0 then default values are taken from server configuration settings Objects.NetworkMaps.DefaultHeight (or ...Width), or coordinates of farthest objects are taken as size, if they are bigger then default values. So you can increase these default values to the size of your biggest background image.

Also, there's a difference between desktop and web version - in the latter background image is not cropped to map size.

We just found a bug in DCI loading from database, they could be randomly marked as "anomaly detected". Next patch release will contain fix for that

Quote from: Egert143 on May 08, 2024, 11:12:57 AMWhat do the yellow DCI mean? they collect data but are yellow.

Might be a bug. Can you share a screenshot of this?

Quote from: Egert143 on May 08, 2024, 11:12:57 AMalso script says function "CreateSNMPTransport" and "SNMPGetValue" are deprecated, what are replacements?

We are moving from functions to object methods wherever possible, check this example in the docs:
https://www.netxms.org/documentation/nxsl-latest/#_read_snmp_value_from_node

This is intended change. We keep list of breaking changes in the documentation, it's worth checking prior to upgrade:
https://www.netxms.org/documentation/adminguide/installation.html#major-changes-between-releases

If these are out-of-the-box templates, you can re-import them via Configuration -> Import configuration. Template files are here: https://github.com/netxms/netxms/tree/master/contrib/templates

It's planned to fix this so that if object is present somewhere else (e.g. under subnet tree) it won't be displayed in the root. But in cases when user does not has access to any container/subnet containing a node, but has access rights to the node itself, it would be display in the the root.

Currently you can have "Unbound stuff" container somewhere with this auto-bind script, it will pick objects that are not present in any other containers:

for(p : $object.parents) {
  println(classof(p));
  if ((classof(p) == "Container") and p.id != $container.id) return false;
}
return true;

Also, there's no more need to use nxmibc as there's interface for adding mib files via the client (Configuration -> SNMP MIB Files)

Still free, why did you get this feeling?

This feature might not have been transferred from the old client to the new one. Will be fixed.

You can check raw values in history of a DCI and do the calculation manually, but I am afraid that's just the data that this switch provides.

More experienced people might correct me, but as long as I remember, reading status of link duplex was pretty non-standard thing that differed accross device make and models. For your specific devices you can create SNMP DCIs. If you need to check across peer devices, it's possible in nxsl as interface class has peerInterface attribute.

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