NetXMS Support Forum

Setting interface to "unmanaged" state means that it's status is not of any interest, and effectively excludes interface from status polls. Status of unmanaged interface will never change unless it will be returned to "managed" state. However, it does not affect data collection related to this interface, so if you, for example, has DCI for traffic on this interface, it will continue to collect data.

Best regards,
Victor

You can set them to "unmanaged" state (right click -> select "Unmanage").

Best regards,
Victor

Could you please post config.log here?

Best regards,
Victor

I could change it in upcoming 1.0.5 version, which I plan to release this or next week, depending on resolving few serious issues (mostly issue 305).

Best regards,
Victor

Novij nxmibc v attache.

Hi!

Yes, it's possible, but that will involve a lot of manual work. You can create separate container somewhere in the service tree, bind all nodes to that container, and create new map with root object set to that container. Then you should open new map, turn off automatic layout, and manually layout nodes.

Best regards,
Victor

Hi!

You are right, most of the libraries must have LGPL license instead of GPL. One of the main ideas behind NetXMS is to make it a good platform for building customized solutions, so GPL license in each file is mostly because of copy-and-paste then intentional limitations. I'll do review of licensing and change license files appropriately, but anyway you can be sure that you can use all APIs under LGPL license.

Best regards,
Victor

Hi!

Most likely you have your DCI type set to 32bit integer, and resulting value is too large. Try to change DCI type to 64bit integer.

Best regards,
Victor

Hi!

In case of del c:\ok\ok.txt, the problem is that \ is an escape character (it is escape character in all event-related text strings: event message, alarm key, etc.). So you have to specify it as del c:\\ok\\ok.txt.

Best regards,
Victor

Hi!

How did you check the results of the ping? As it configured now, server will just execute ping command - you only will be able to notice thos pings by capturing packets or looking at server's debug output.

Best regards,
Victor

How you action configuration looks like? You should set something like

%n: %m

as message body to get meaningful texts in e-mails.

Best regards,
Victor

What I can see from this that most likely you have set small repeat interval for DCI polling apache2 process, and those repeating events floods event log. Try to turn repeat off. Also, it is not possible to tell if DCIs are polling or not from event log - you should enable debug on server and see server log file. Also, you can check last values for DCI - if they are collected, then most likely problem is with incorrect threshold and/or event processing policy configuration.

Best regards,
Victor

Hi!

I would suggest to change alarm key in your configuration for %m (message text) to DC_%i_%5 - that would create separate alarms for different nodes, even if they have same message text. But anyway, that is not important for sending e-mails. From information you have sent it is not clear why you getting e-mail only for 1 DCI - I should see configuration and values of all 4 DCIs. Also, was it your intention to send e-mails every minute as long as there are files matching filter?

Best regards,
Victor

Hi!

If NetXMS cannot communicate with the node, it consider node as down. It is not possible to distinguish between situations when only interface communicating with NetXMS server or entire node is down, if other interfaces are not reachable by NetXMS server. However, if they are reachable at least by ICMP ping, server will correctly detect that only interface is down. There are other possible scenarios to distinguish between those two cases, but they are dependent on your actual network topology.

Best regards,
Victor

Server connects to agents. You need to open TCP port 4700 in direction from server to agents.

Best regards,
Victor