NetXMS Support Forum

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

Poslednie dni bil sil'no zanjat, poetomu tak dolgo S problemoj razobralsja. Ja mogu vilozit' patch, ili podozdite vihoda 1.1.6. No bazu pridetsja brat' s backup'a i zanogo delat' upgrade. Problema ne v samom upgrade, a v servere, no esli v baze uze isporchennie teksti, to ih uze ne vosstanovit'. Kak variant - sdelat' update iz backup'a tol'ko tekstovim poljam - v osnovnom eto budet name i comments v tablice object_properties.

Hi!

All except %m, %M, and %A. Technically speaking, you can use them in event templates, but they will always expand into empty string.

Best regards,
Victor

Hi!

There are two entities: event parameters and snmp trap varbinds. Each received trap converted to NetXMS event. This event always gets SNMP trap object ID (OID) as first parameter, so %1 in event template will always be expanded to trap OID. You can map varbinds to event parameters. First mapping will be for parameter number 2, because number 1 already taken. You can identify varbinds within trap in two ways - by position (starting from 1) or by varbind OID. You are not needed to map all varbinds or map them to parameters in same order - you can map varbind #5 to parameter #2 and varbind #1 to parameter #3, for example.

Hope this makes things more clear!

Best regards,
Victor

Hi!

You mean export rules of event processing policy?

Best regards,
Victor

Hi!

Currently it's the only piece of information about NXCP protocol. All other information can be found only by examining source code. Feel free to ask me about specific commands you need - I'll either answer you in forum or update documentation for them. Btw, why you not using client library (libnxcl) but work directly with NXCP protocol?

Best regards,
Victor

P.S. And please ask development related questions in "Development" section of the forum