NetXMS Support Forum

At least one Nexus user reported is as fixed, so probably yes (we were unable to reproduce it locally).

Best regards,
Victor

Hello!

Probably easiest way is to create two rules in event processing policy, one for critical nodes and one for everything else, and set different severity to generated alarms. See attached screenshot for an example.

Best regards,
Victor

It's strange - there are no errors on either side, server reports normal connection closure:

2020.12.16 16:35:57.592 *D* [client.session.0   ] readSocket: connection closed

Timestamps are also quite old and not in sync between server and client - do you have correct time on server and client? If yes, are those logs latest for version 3.7? Also, are they in same time zone?

Best regards,
Victor

Hi,

you can change format string for them. It is basically Java format string with one addition - format %*s will scale value automatically and display it as k, M, G, etc. So for traffic counters you can use format string

%*sbps

It will produce something like 1.37 Mbps for original value like 1370024.

Best regards,
Victor

Preferably you should use


not $node->isPrinter

or

!$node->isPrinter


although your form will work too, because isPrinter will contain boolean value TRUE or FALSE, and if it is false then isPrinter != TRUE will produce expected result.

Best regards,
Victor

So it is deleted as duplicate:

2021.01.11 07:59:49.527 *D* [event.proc         ] EVENT SYS_DUPLICATE_NODE_DELETED [100] at {0} (ID:30074352 F:0x0001 S:1 TAGS:"") FROM NetXMS Server: Duplicate node Haas HP DL380 Gen9 (iLO) is deleted (Primary IP address 10.59.204.205 of node Haas VMWareHostB [118318] found on interface HP Ethernet 1Gb 4-port 331T Adapter of node Haas HP DL380 Gen9 (iLO) [135819])

What is node "Haas VMWareHostB" and do it really have same IP address?

Best regards,
Victor

It is not possible to configure server to use only SNMP sysName for resolving node name. However, you can synchronize node name with SNMP sysName by adding the following code to configuration poll hook script:


if (($node != null) && $node->isSNMP && ($node->name != $node->snmpSysName))
{
$node->rename($node->snmpSysName);
}


It will update node name according to SNMP sysName on each configuration poll.

Best regards,
Victor

Hi,

you can add new image to image library and then assign this image to your objects (can also do that automatically in configuration poll hook script based on node OID for example).

Yes, you can add interface traffic data - right click on any link on the map, go to "Data collection" settings, and add whatever DCIs you want to be displayed.

Best regards,
Victor

Hi,

UseDNSNameForDiscoveredNodes controls assignment of primary host name (DNS name or address used for communications), not node name (the one you see in object tree, etc.). Resolving node names from IP address is controlled by Objects.Nodes.ResolveNames.

Best regards,
Victor

Hi,

this is caused by introduction of boolean type in NXSL. If you change

if ($node->isRouter == 1)

to

if ($node->isRouter)

it will work correctly. As those attributes are boolean by nature and all our examples use only second form we didn't expect that they are used with == operator (and == 1 was unreliable anyway because it could have happen to be any non-zero number).

Best regards,
Victor

Try to turn debug to level 6 (be aware that it will generate lot of output if you setup is big), and after node disappear again filter all messages containing name or ID of that node and post them.

Best regards,
Victor

Hi,

could you please provide enable debug level 6 for tag client.* on server, and provide server log after next disconnect along with client application log?

Best regards,
Victor

Hi,

does it disappear after server restart or while server is running? If former then it could be that because of SQL errors node is not saved to DB at all. If latter then it could be due to deduplication if it is turned on (you can check it in server configuration - parameter NetworkDiscovery.MergeDuplicateNodes).

Best regards,
Victor

Hi,

discovery via agent behind tunnel should work if you are using zones, and node with agent is set as proxy for remote zone.

Best regards,
Victor

Hello all!

We just published patch release 3.7.116 for version 3.7. Changes since previous release:

- New methods "appendAll" and "insertAll" in NXSL arrays
- DCI transformation test can be run from template data collection configuration
- Fixed bug in remote agent configuration update
- Fixed bug in object selection dialog in UI
- Fixed server hang on shutdown if initiated from remote GUI session
- Fixed issues NX-1875 (Error message is not cleared in list of notification channels)

Best regards,
Victor