NetXMS Support Forum

Hi!

Looks like it is not possible with current implementation of WMI.Query. I'll take a closer look at it in a few days - looks like this functionality can be added with simple changes in WMI subagent.

Best regards,
Victor

Hi!

Last error is ok if you do not have DRBD installed. It cannot affect agent's communications. When you do configuration poll for node in NetXMS, did you get anything in agent's log? You should see at least lines like this:

[01-Nov-2011 09:48:34] Incoming connection from 127.0.0.1

If you don't, that means that server cannot even establish TCP session with the agent, and problem is on the network layer - firewall, routing, etc.

Best regards,
Victor

Hi!

They are still not implemented. Agent shows them, but always returns an error.

Best regards,
Victor

It should automatically add node object on management server, to simplify deployment of agents. You can register agent at any time from command line:

nxagentd.exe -r server

Best regards,
Victor

I plan to release stable version till end of the year. Key points to be achieved before release of 1.2.0 is to implement all functionality of legacy console in Java console and made application stable.

Best regards,
Victor

Yes, you have to add all other nodes to trusted nodes list on  ISP_gateway. So in your case it's probably easier to disable trusted nodes checking.

Best regards,
Victor

You can use function FindNodeObject and then use attribute status of that node. For example, if you have node named ISP_gateway, your script to check if it is down may looks like following:


gw = FindNodeObject($node, "ISP_gateway");
return gw->status == 4;


This script will return true if node named ISP_gateway has status "critical". DOn't forget to add node for which this script executes to the list of trusted nodes for node ISP_gateway, or disable trusted nodes checking completely by setting server configuration variable CheckTrustedNodes to 0.

Best regards,
Victor

Hi!

No, it contains only those 3 fixes listed in change log. I plan to close 1.0.x branch completely as soon as I made 1.1.x stable (it will becomes 1.2.0 then).

Best regards,
Victor

Hi!

I've made a fix for nxalarm. Unfortunately it involves changing server code, so I create a new maintenance release 1.0.13 which includes this change as well as few other fixes.

Best regards,
Victor

Hi all!

NetXMS version 1.0.13 is out. It's a maintenance release for 1.0.x branch. Changes includes:

- New NXSL functions: GetDCIValueByName, GetDCIValueByDescription
- New attribute "comments" in NXSL classes "Node" and "NetObj"
- Fixed non-working macros in nxalarm

Best regards,
Victor

Hi!

Basically you have two ways:

1. Use situations. Create situation which will reflect connection A status, and in rule for processing SYS_NODE_DOWN event add additional filtering script which will check the status of situation, and only pass event through if connection A status is up.
2. Just find a local node/DCI reflecting current state of connection A in filtering script for SYS_NODE_DOWN, and use it to choose if event should pass or not.

How do you monitor state of connection A?

Best regards,
Victor

You need flex and bison from msys. Directory with them should be added to binary directories in visual studio options.

Best regards,
Victor

Looks like incorrect handling of unicode characters during export. There are some lines looking like this:

<message>%6 : Le Batch Farmsat sur la machine %n ne fonctionne plus suite ࿿ cette erreur : %4</message>

How does this message looks in it's original form?

Best regards,
Victor

Hi!

You can get them from subversion repository. Root of 1.1.x branch is http://svn.netxms.org/public/netxms/trunk. If you wish to get just Java sources (this will include management console), you can use URL http://svn.netxms.org/public/netxms/trunk/src/java. If you need sources from specific version, you can use URL in form http://svn.netxms.org/public/netxms/tags/version-x.y.z (for example, http://svn.netxms.org/public/netxms/tags/version-1.1.5).

Best regards,
Victor

Hi!

Sounds like a bug in either export or import code. Could you please post or send to my email exported file?

Best regards,
Victor