NetXMS Support Forum

If you have enabled watchdog, maybe it's the same as here:
https://www.netxms.org/forum/configuration/problem-with-centralized-agent-upgrade/msg14300/#msg14300

Good information Victor. I was never happy with the different order of the parameters. I will change my configuration in the near future.
Please add this also to the documentation (Wiki and Admin Guide).

When I try to start a physical linux node by 'Tools - Wakeup node' I get this error in NetXMS Management Console (on Windows 64bit):

'Wake node' has encountered a problem
Cannot send wake-on-LAN packet to node: No MAC address on interface

But there is a MAC address on interface eth0 in NetXMS and other Wake-on-LAN tools can start the same target machine.
(NetXMS 1.2.17)

After update to NetXMS V1.2.17 I tested the new feature to use environment variables in agent config for windows agents.
So I replaced in Agent Config Manager "C:\Program Files" thrue "%ProgramFiles%". Than I restarted the agent on a Win2012R2 node. The local 'nxagnetd.conf'-File was updated and contains now "%ProgramFiles%". But the agent doesn't start after that.

for a more elegant methode (in NetXMS V1.2.17) see this thread:
https://www.netxms.org/forum/configuration/node-with-question-mark-on-the-icon-of-object-browser/

ok. I made my tests to this new feature:

• node created with no interfaces (for an unmanagable device)
• in polling properties of this node I deactivated all except 'Disbale data collection'
• DCI created on this node which checks the status of the switch port (gives back 4 for down and 0 for up) and 'use this DCI for node status calculation' = ON

Now when I switch off the device, I get an event 'SYS_NODE_CRITICAL'. When I switch on the device again, I get a 'SYS_NODE_NORMAL' event.
But for my existing event processing policy I need 'SYS_NODE_DOWN' and 'SYS_NODE_UP' events. So I created a threshold on the DCI (!=0 -> SYS_NODE_DOWN, deactivation event SYS_NODE_UP) and everything works as expected.
I will first use it for unmanageble provider-modems and switches.
Maybe this helps someone.

For me it seems also fixed. No old topology info anymore. Thanks Victor.

I see this feature is in V1.2.17. But how we can use it. I didn't found a documentation.

will this fix definitely be in V1.2.17?

Hi Victor

I just made my tests, works absolutely like expected. Thanks a lot, that helps us very much.

Thanks
Dani

Any chance for a fix before V1.2.17? Maybe a fixed souce file.

Hi Victor

Thank you. So I await the next release

Dani

Very good. It would be very helpful and I can test for you. Thanks

This bug generates a lot of SYS_IF_PEER_CHANGED events on every topology poll (every 15min).
Beside the out-dated LLDP topology information I also see out-dated FDB information.

Hi Victor

Sorry for my impatience. But would it be possible to fix/change this before V1.2.17?

thanks
Dani