NetXMS Support Forum

yes, of course. Otherwise wake-on-LAN with managed node would not be possible. That works now.
But if the (same) node is set 'unmanaged' in NetXMS, wake-on-LAN is not possible. But that would be helpful.

Hi Tatjana

I can confirm, Wake-On-LAN is now working on the node- and on the interface-object.
One appendix:
If the node is 'unmanaged' in NetXMS you still get the error "Cannot send wake-on-LAN packet to node: No interface for sending magic packet". I don't know whether this is intended. It would be nice to use it however.

The package deploy problem with watchdog enabled (Windows) is fixed in V2.0-M2, I just tested. Thanks.

is the package deploy problem with watchdog enabled reproducible? It looks like the same problem I reported for an older version of NetXMS.

it works in 2.0-M1 release, thanks!

both doesn't work for me. With other WakeOnLAN-Tool it works.

We just built up a new storage cluster which we want to monitor by NetXMS. So I created a cluster object and 2 nodes. Unfortunately the Section 'Monitoring Clusters' is still not available in the administration guide. So I have a few questions:

• Where can I see the 'Last Values' of cluster object DCIs (associated to cluster ressources or not)? In 'Object Details' of the cluster object 'Last Values' is empty.
• There is no 'Performance' tab in Object Details of cluster objects
• Will the Admin Guide section for Cluster be published soon?
• in 'Data Collection Configuration' of cluster objects it would be good to have a column 'Cluster Ressource' in the table
• DCIs on Cluster Object with no associated cluster ressource will be polled to which IP address?
• How can we use templates for cluster objects? The problem is the name of the cluster ressource to associate. Assign templates to cluster nodes directly, thats clear.
• What is the meaning of 'Cluster Networks' in cluster object properties?

Thansk for any help.

Strange. Here the update (by NetXMS package deploy) worked for WinXP SP3 (without whatchdog). Version 1.2.17 was installed before.

Thanks Victor for the fast fix.
Manual upgrade install local on a node is working now (Win x64).

But deploy from NetXMS server to a node where agent V1.2.17 is installed does' not work.
The two agent processes (agent and watchdog) are terminated but no update. In Windows eventlog is an error with Event-ID 10006, Source: RestartManager, 'Application or service 'nxagnetd' could not be shut down.

edit1:
I don't see any updated files and in Windows Control Panel V1.2.17 is still installed. In 'Services' the NetXMS agent is in 'running' state, but in Task Manager I cannot see any running 'nxagnetd' processes.
Then I  'stopped' the NetXMS agent in 'Services' and started again, service is than in state 'running' but still no 'nxagentd' processes running, and NetXMS server cannot connect to agent.

edit2:
I also tested the agent upgrade by package deploy on a Win-x64 node with 'EnableWatchdog=no', that works! So the problem only exists with 'EnableWatchdog=yes'

edit3:
Agent install path is 'C:\Program Files\NetXMS'

I just tested this issue in V2.0-M1. Still not working.
Error Message:
'Wakeup node' has encountered a problem.
Cannot send wake-on-LAN packet to node: Communication failure

We also get an error on Windows2012R2 server with NetXMS V2.0M1 agent. Here in Eventlog:

Faulting application name: nxagentd.exe, version: 0.0.0.0, time stamp: 0x54afa34c
Faulting module name: libnxsnmp.dll, version: 6.3.9600.17476, time stamp: 0x54516b13
Exception code: 0xc0000135
Fault offset: 0x00000000000ec5a0
Faulting process id: 0xdb8
Faulting application start time: 0x01d02dab874d8b4d
Faulting application path: C:\Program Files\NetXMS\bin\nxagentd.exe
Faulting module path: libnxsnmp.dll
Report Id: c4fa1742-999e-11e4-8129-00155d0a6422
Faulting package full name:
Faulting package-relative application ID:

In agent install directory (bin) is no such DLL 'libnxsnmp.dll'

ok, thank you tomaskir!

I know that but only in descovery.
But this affected node is an existing node. SNMP was switched off on this node but later I set SNMP to SNMPv3 with credentials (explicit on this node) and activated snmp polling for this node.
Then after a while (I think after the first configuration poll) the settings where resetted to SNMPv2 and 'public'. So NetXMS changed my explicit settings on this node. That is the surprise for me.
I think it also based on a bug in the physical node (switch), as the switch answered suddeny only on SNMPv2 and 'public' and not on SNMPv3 as before (no configuration change).

Thanks for your fast reply.

The DefaultCommunityString in server configuration is something different.
Network Discovery is disabled but there is still one of the community strings 'public'.

I tested the affected node with nxsnmpwalk and SNMPv2 community string 'public'. And yes I was surprised this node replyed to SNMPv2 and public too!
I have two other switches (the same modell, same software, same SNMP-configuration but different port number), these other switches do not reply to SNMPv2 and 'public'. That part of the problem must be a bug in the switch software.

Than I deleted 'public' from Network Discovery and waited a few minutes. Till now no change to 'public' in the affected node. Is this a bug or a feature? And if it is a feaure, is it in documentation?

Then I restarted the SNMP feature in the switch. The next test with nxsnmpwalk and 'public' doesn't worked anymore.

A little bit strange. It must be a combination between a bug in the switch and the part in NetXMS where I don't know is it a bug or feature :-)

thanks
Dani

we have a strange phenomena:
We have a node in NetXMS which losts his SNMP conficuration. I set the SNMP settings in 'Communications' to SNMPv3 with authentication and encryption in the java console. Then I finish with 'ok'. When I just reopen the node properties the settings are still there. A few minutes later I open the properties again and the SNMP settings are reseted to SNMP version 2c community string 'public'.
Very strange, I never saw that on other nodes before. How is this possible? and how can I fix this. Please help.

thanks
Dani

(NetXMS 2.0M1 installed from sources on linux 64bit, but also saw this on V1.2.17)