NetXMS Support Forum

Hi!

Are you using PostgreSQL client installed separately or bundled with NetXMS server? Database driver built against PostgreSQL client library version 8.4.1, and it may be incompatible with 9.0.1 client.

Best regards,
Victor

Da, tam tol'ko kosvennoe upominanie (str. 45):

It is possible to manually convert variable to a certain type, using a special function, named
depending on the variable type. For example, string(4). That way it is also possible to convert
NULL type variables. Therefore, to avoid runtime exceptions while processing NULL type variables,
it is advised to use manual conversion.

Imelos' vvidu, chto est' funkcii s imenami, sootvetstvujuschimi tipam: int32, int64, string, etc. dlja javnoj konvertacii. Ja dobavlju ih opisanija v javnom vide.

Slow, but implemented finally However, it's not complete implementation yet - there are some limitations:
1. All agents must support same SNMP version;
2. All agents must use same community string or USM credentials;
3. Agents on ports other than node's default not checked for availability during status polls (you can however detect DCI collection errors).

I plan to add full per-agent configuration (version, credentials, etc.) in future versions.

Best regards,
Victor

Mozno napisat' transformation script, naprimer takoj:


sub convert_smart_value(value)
{
if (length(value) != 12)
return 0;

i = 11;
rvalue = "";
while(i > 0)
{
rvalue = rvalue . substr(value, i, 2);
i -= 2;
}
return int64("0x" . rvalue);
}

sub main()
{
   return convert_smart_value($1);
}


Esli convertacija nuzna v neskol'kih DCI, to funkciju convert_smart_value mozno vinesti v script library.

Best regards,
Victor

Hi!

I've checked this, and yes, there is a bug - alarm message for repeating alarm updated only in memory and not stored in database. Fixed in 1.0.8.

Best regards,
Victor

Hi!

Did you load portcheck subagent on agent running on NetXMS server? Default service polling connection scheme is following:

NetXMS_Server ---> NetXMS_Agent on NetXMS Server Machine ---> service to check

unless you change poller node in network service configuration. If you are running your server on Linux, you should have something like


SubAgent = /opt/netxms/lib/libnsm_portCheck.so


in nxagentd.conf on NetXMS server machine.

Best regards,
Victor

Добрый день!

Пропустил эот пост Проблема все еще актуальна?

В текущей версии этого сделать нельзя. Я попробую реализовать это в каком-то виде в следующей версии.

Если есть SNMP, то проблем быть не должно. Надо только найти MIB для конкретной модели ибп и все правильно настроить. Стандартный UPS MIB входит в инсталляцию NetXMS.

Hi!

You can use situations in conjunction with dummy DCI. For example, you can update situation object each time you got line from a log, setting situation's attribute to current time stamp. Then, create dummy DCI with transformation script, check situation's attribute, and return different values depending on how long time was passed since last situation update, and set thresholds as usual. And starting from 1.0.8, you will be able to generate new event directly from transformation script.

Best regards,
Victor

Hi!

It's a bug in a server. I have fixed it, and version 1.0.8 should work fine. If you are running server on UNIX, I can post a patch. Also, as a workaround, you can use function GetSituationAttribute to get attribute's value instead of directly accessing it.

Btw, you should specify attribute name without quotes in configuration dialog.

Best regards,
Victor

Da, v min i max bila oshibka pri rabote s raznimi tipami dannih. Ispravil, v 1.0.8 etoj problemi ne budet.

Hi!

Please replace file dbinit_mssql.sql with attached one and run nxconfig.exe again. It should initialize database properly.

Best regards,
Victor

Hi!

Fixed that, thank you!

Best regards,
Victor

Hi!

I have updated NetXMS user manual. Now it contains up-to-date information about all available NXSL functions and classes (Event, Node, and DCI). Also I have implemented NXSL function PostEvent (will be included in 1.0.8 release) which could be used to generate events on behalf of any node (according to security settings, as with FindNodeObject).

Best regards,
Victor