NetXMS Support Forum

Yes, it would be great. So far I'm not sure that it is possible to create just a "builder" for new drivers (except for some simple cases probably), bit it could be possible to allow drivers written in NXSL. It already has functions to access SNMP, we only need to add classes representing interfaces, VLANs, etc.

Best regards,
Victor

Debug level for server. How do you set it? You can also change debug level in runtime from server's debug console (accessible in management console via Tools -> Server console) by entering command

debug 5

make sure that you set logging to file (not Windows event log or syslog).

Rules are processed from top to bottom.

Best regards,
Victor

Strange, it should be there. I didn't change the installer. If this helps, we are using InnoSetup as installer (http://www.jrsoftware.org/isinfo.php).

Best regards,
Victor

Hi!

There are two problems:

1. Enable agent registration on server by setting configuration parameter EnableAgentRegistration to 1.
2. Seems that agent registration is broken - I'll fix it in 1.2.12 release.

Best regards,
Victor

Hi!

Try to set debug level to 5 and look for messages started with *actions* and RunCommandThread.

Best regards,
Victor

Hi!

UseDNSNameForDiscoveredNodes set to 1 should help. However, you must ensure that reverse DNS is working correctly. When network discovery is working, NetXMS server got an IP address. If UseDNSNameForDiscoveredNodes set to 1, server tries to resolve IP address to DNS name. If succeeds, it tries to resolve this DNS name back into IP address. If resolved IP matched with originally discovered IP, DNS name accepted as node's primary host name. If any of these steps fails, IP address will be sued as primary host name.

Best regards,
Victor

Hi!

Actually, autodiscovery is off be default. You can configure network discovery in console (Configuration->Network Discovery). It is also possible to define nodes using external program. There are few options for that - you can use nxshell for creating Python script with access to NetXMS API, or you can create simple Java app using NetXMS API.

Best regards,
Victor

Hi!

They work on some controllers (mostly ATA and SATA). If they are working (you got response from agent), then SMART status could be following:
0 - OK
1 - Bad
2 - Unknown

Best regards,
Victor

Hi!

LogFile = {syslog} in nxagentd.conf and netxmsd.conf does not relate in any way to built-in syslog server enabled with EnableSyslogDaemon parameter. Setting log file to {syslog} only means that serevr or agent will use system logging facility for logging (syslog call in UNIX). It is up to you (or server admin) to configure syslog on that particular server for remote logging to NetXMS server's syslog server. Here is an example of how to configure rsyslogd for sending messages to remote server: http://www.rsyslog.com/sending-messages-to-a-remote-syslog-server/. You should check what syslog server is used on your servers.

In short, message flow for remote agent is like following:

nxagentd -> syslogd ---------------> netxmsd syslog server
-----------------------                        -------------------------
  remote host               network            netxms server


If you want local netxmsd log to be catch by netxms syslog:

netxmsd -> syslogd ---------------> netxmsd syslog server
                                 loopback

Best regards,
Victor

Hi!

To disable SNMP for node go to node properties, then "Polling" page, and check "Disable SNMP".

Best regards,
Victor

Hi!

It's a bug in a server. I just fix it, 1.2.12 patch release will include this fix.

Best regards,
Victor

Quote from: Marco Incalcaterra on January 30, 2014, 01:42:27 PM
Is there a particular size to be observed?

No, login form will resize as needed.

Best regards,
Victor

Are all stack traces identical?

Best regards,
Victor

Yes, it's what I was interested in. Thank you!

Best regards,
Victor

Yes, exactly. I can possibly suggest some if you tell me how you want to use those events.

Best regards,
Victor