NetXMS Support Forum

Repeat events for table thresholds not implemented yet.

Best regards,
Victor

Hi,

I'll try to test it in a next few days. Can you please try to delete base DCI, check that instance DCIs disappear in GUI, and check if they are in database (table "items"). You can select all DCIs for node with query


SELECT * FROM items WHERE node_id=?;


(replace ? with actual node ID). If they will be there, try to change something in node properties (rename it for example), and after some time check DB again.

Best regards,
Victor

Hi,

error 15027 means "the message resource is present but the message is not found in the string/message table". So application logs message with code that is not present in message table. It looks like a bug in some application.

Best regards,
Victor

Hi,

currently not. You can add feature request for that.

Best regards,
Victor

Hi,

server connects to agents (on port 4700 by default, but it can be changed). You can also have one agent on remote site working as a proxy for other agents - in that case you only need to open port 4700 to one machine on remote site from management server. Agent can also be used as proxy for SNMP, so you can monitor network devices via agent without direct SNMP requests from management server.

Best regards,
Victor

DSN должен быть системным. При проверке DSN, используете пользователя sa и пароль?

Попробуйте приложеную версию драйвера.

Hi,

can you please try with == OK and != OK?

Best regards,
Victor

Hi,

situations are not persistent - this is actually a bug. We plan to simplify situation usage a bit in 2.1 and will fix persistence issue as well. The only workaround currently is to use node's custom attributes instead of situations - they are persistent.

Best regards,
Victor

There is an issue in bug tracker: https://dev.raden.solutions/issues/976. I'll try to implement it in 2.1 branch.

Best regards,
Victor

Hi,

what views you have open at time of freeze?

Best regards,
Victor

Hi,

were those DCIs instance discovery DCIs? If yes, 2.0.5 most likely will fix it - possible deletion of wrong DCIs when deleting instance discovery DCIs was one of the bugs fixed in instance discovery code.

Best regards,
Victor

Hi,

do you use instance discovery in those templates? If yes, try version 2.0.5 - there were fixes in instance discovery.

Best regards,
Victor

Hi,

from the screenshots and exported config everything seems to be correct. I cannot reproduce this myself - I don't have iLO 3 board to test your template on, but I create sample table with same transformation and threshold works just fine. What NetXMS version you are using? Also, please try to modify event by adding script call like this: "%[TableData]" and create script called TableData in script library as following:


table = GetDCIValue($node, $event->parameters[3]);
row = $event->parameters[4];
return table->get(row, table->getColumnIndex("Smart Status"));


and change to not like to trigger event. You should see actual value for the cell in place of %[TableData]. It will be possible to check if it is actually correct.

Best regards,
Victor

Hi,

LVM monitoring extension for Linux agent is currently in development, and likely will be part of 2.1-M1 release. You can wait a bit and use NetXMS agent when this function will be available. Currently the only alternative is to create wrapper scripts for lvdisplay and use them as external parameters in agent.

Best regards,
Victor