NetXMS Support Forum

Hi,

server do not expect two values within one second. You can try to put sleep call (https://wiki.netxms.org/wiki/NXSL:sleep) between two push calls to guarantee at least second interval between values.

Best regards,
Victor

Now I understand. The problem is that when mapping of trap to event happens, only values are copied, not OIDs (value of $event->parameters[3] will be "[GRE-FW01][INFO][005]" in your example). But, if you have two parameter mappings on different OIDs, and only one of them can be present in actual trap, that means that other parameter will be empty. So, if you have mapped .1.3.6.1.4.1.9789.1500.1.5 to parameter #2 and .1.3.6.1.4.1.9789.1500.2.5 to parameter #3, you can simply check if parameter 2 is empty - if it is, you have .1.3.6.1.4.1.9789.1500.2.5, otherwise .1.3.6.1.4.1.9789.1500.1.5.

Best regards,
Victor

Hi,

currently it is not possible. I've just added new methods to NXSL class "Event": setMessage, setSeverity, setUserTag. They will be included in release 2.0-M5. Then you'll be able to use script like this:


$event->setSeverity(2);  // change severity to minor


Best regards,
Victor

Можно поставить threshold на data collection error. Он сработает при ошибке получения данных для DCI.

Теоретически можно сделать отчеты примерно повторяющие дашборды - но работы будет я подозреваю много. Отчеты можно рассылать по таймеру.

Hi,

basically you write it correctly (with one type):

if ($2 == ".1.3.6.1.4.1.9789.1500.1.5") return 1;

or simply

return $2 == ".1.3.6.1.4.1.9789.1500.1.5";

Best regards,
Victor

Hi,

so far we plan to make stable release in late June.

Best regards,
Victor

We re-generate javadoc: https://www.netxms.org/documentation/javadoc/latest/. Now it is for actual development branch (you can consider it 2.0-M4 as there was no changes in API since last release).

Best regards,
Victor

It's not possible to specify multiple classes, but usually it's not needed. You should specify most specific class that covers all objects that you need - in your case it will be "posixAccount" for users and "posixGroup" for groups.

Best regards,
Victor

Then it seems to be a bug in a server. What NetXMS version you are using?

Best regards,
Victor

Still, classes and attributes looks wrong: https://www.netxms.org/documentation/adminguide/user-management.html#open-ldap (check values of parameters LdapMappingName, LdapMappingFullName, LdapMappingDescription, LdapGroupClass, LdapUserClass).

Best regards,
Victor

Hi,

problem is that javadoc is outdated. In version 2.0-M4 NXCObjectCreationData.setIpAddress expects object of type InetAddressEx. You can create it as follows:

InetAddressEx(InetAddress.getByName(objectIp), 0)

but preferred way for creating node objects is to use setPrimaryName instead:

cd.setPrimaryName(objectIp)

Best regards,
Victor

Hi,

usually node should get status 4 (critical) when it's down. It can get unknown status if server decides that it's a network failure. Do you receive SYS_NODE_DOWN or SYS_NODE_UNREACHABLE event when it goes down? Also, can it be that node has dynamic IP address and it changes when node goes up again?

Best regards,
Victor

I guess you are connecting to Active Directory? If yes, class and attribute names are wrong. Please set them as described here: https://www.netxms.org/documentation/adminguide/user-management.html#active-directory.

Best regards,
Victor

Скорее всего. Я попробую воспроизвести проблему у себя.