NetXMS Support Forum

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

Hi!

Can you please send me output of command

nxsnmpwalk -c your_community switch_ip .1.3.6.1.2.1.2

Best regards,
Victor

Hi!

Maybe it's wrong scintilla version. We use quite old version of it.
Btw, what is your final goal? Why you are trying to compile NetXMS for Windows?

If you don't need to change 1.0.x branch for any reason, I would recommend using 1.1.x branch for all new development. It is actively developed, and among other bonuses, it requires Visual Studio 2005, and all third-party libraries except OpenSSL are bundled and built as part of NetXMS. This can greatly simplify build process.

Best regards,
Victor

Hi!

Error 1 - most likely you have outdated Windows SDK.
Errors 2 and 3 - you need scintilla to build nxlexer dll.

Best regards,
Victor

Hi!

You should use Java console for this - just go to the properties of node and enter new IP address as "primary host name".

Best regards,
Victor

Hi!

What NetXMS version you are using?

Best regards,
Victor

Hi!

For threshold violation events, it is:

   1) Parameter name
   2) Item description
   3) Threshold value
   4) Actual value
   5) Data collection item ID
   6) Instance

For threshold rearm event:

   1) Parameter name
   2) Item description
   3) Data collection item ID
   4) Instance
   5) Threshold value
   6) Actual value

For standard events, you can find list of event-specific parameters in event description (accessible via event configuration view).

Best regards,
Victor

Esli vse pojdet kak namecheno, to v konce etoj nedeli.

Hi!

It's a bug. I'll made a patch and post it here.

Best regards,
Victor

You can write a simple NXSL script which will return DCI value and use it in message template via %[] macro. For example, you can create script called "LastValue" with the following code:


return GetDCIValue($node, $event->parameters[5]);


and then use macro %[LastValue] in message template to insert last value of associated DCI in threshold violation events.

Best regards,
Victor