NetXMS Support Forum

Hi!

No, I didn't change anything in SNMP trap mapping. Can you please send me detailed screenshots of your configuration with problematic trap and event?

Best regards,
Victor

It will be easy since version 1.2.2 I have added new function GetObjectChildren, which can be used for node enumeration. See also example: http://wiki.netxms.org/wiki/Script_Example:_Enumerate_All_Nodes.

For 1.2.1, one possible way could be to add handler for SYS_NODE_UNMANAGED event, and unmanage all (or required) nodes, then manage them again.

Best regards,
Victor

I agree that this could be useful. I have added this as feature request.

Best regards,
Victor

Похоже deb пакет собрали без lmsensors Я попозже сделаю сборку с lmsensors - сейчас не успеваю.

Скорее всего уже существует объект с таким IP адресом. Попробуйте поиск по адресу (>адрес в строке фильтра).

Hi!

There are previously undocumented function SetCustomAttribute. I have added appropriate wiki page: http://wiki.netxms.org/wiki/NXSL:SetCustomAttribute. To set custom attributes for new nodes, you can handle SYS_NODE_ADDED event in event processing policy and start a NXSL script which will populate custom attributes.

Best regards,
Victor

Functionality of web console is almost the same as in desktop console. Some parts in web console may not work as good as in desktop console, especially charts and network maps, you cannot save perspectives yet (actually any preferences - we are working on that), and copy to clipboard function is not working.

Best regards,
Victor

Hi!

Try this solution: https://www.netxms.org/forum/installation/nxmc-access/msg7762/#msg7762.

Best regards,
Victor

Hi!

It looks like new database does not contain NetXMS tables. Other possible problem could be that tables in new database has schema name different from NetXMS database user's schema (maybe I'm using wrong terminology here, I'm not a MS SQL expert - I mean that full table names could be dbo.config for example in new database, but server uses only short names, like config, so it can search for netxms.config instead of dbo.config).

Best regards,
Victor

Pohoze eto takaja-ze problema: https://www.netxms.org/forum/general-support/nxdbmgr-exe-upgrade-x/msg6645/#msg6645. Poprobujte variant 1 - rukami sozdat' tablicu i potom upgrade s kljuchom -X.

A kakaja baza ispol'zuetsja?

Hi!

System.CPU.Usage.IoWait measures how much time CPU spent waiting for I/O completion (or, more precisely, it's a percentage of time that the CPU was idle during which the system had an outstanding disk I/O request), while System.IO.DiskTime measures time disk system was busy processing requests. Not all systems can provide both parameters, and if some do, they can be very different. One example is that if you have two processes - one is I/O intensive and one is CPU intensive, your iowait % will be low, because CPU will not idling, but execute CPU intensive process while I/O intensive process waits for I/O completion.

Best regards,
Victor

Value in thresholds can be only constant. You should create DCI which will use correct values and then use constants in thresholds. You can use transformation script to convert absolute value into percentage, like this:

$1 * 100 / GetDCIValueByDescription($node, "MaxAssociations")

Best regards,
Victor

P.S. It is planned to add scripting support to thresholds, but this functionality most likely will be available in version 1.2.3 only.

Hi!

I have added Dell PowerConnect driver. I think taht I'll be able to add other one as well.

Best regards,
Victor

Configuration is correct. Changes made in this screen will be activated only when you save them. You will be prompted to save if you close this screen or you can save it by selecting "Save" from view's menu. Unsaved changes indicated by asterisk in tab name.

Best regards,
Victor