NetXMS Support Forum

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

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

Добрый день!

Делали ли настройки на закладке "Performance tab"? В особенности привязку к другой метрике на графике?

When you use "Select" button for DCI configuration, it get parameters supported by node you are configuring it on, not by proxy node (which actually an interface bug). When you do it in template, it shows all parameters supported on at least one node.

You can use any approach for splitting - whatever is easier for you. In NXSL often most efficient way to split string is to use regular expressions. For example, for string like this:

DISK OK - free space: / 961 MB (50% inode=84%);| /=951MB;1995;2005;0;2015

it could be


if ($1 match "^DISK ([A-Za-z]+).*free space:.*([0-9]+) .*")
{
    // here $1 will contain status ("OK" in example)
    // $2 will contain free space (961 in example)
}


Best regards,
Victor

Btw, is it intended to create all nodes with SNMP access disabled?

Best regards,
Victor

Ошибка 2 означает "access denied". Попробуйте поставить дебаг уровень 4 или выше и посмотрите что сервер будет писать в лог при логине.

Hi,

value of external parameter is whatever is written to stdout by command. So you can simply remove redirection to /dev/null:


ExternalParameter=Nagios(*):/etc/netxms/plugins/$1 -H $2 -c $3 -a $4 / 2>&1


Best regards,
Victor

Hi!

SNMP version constants are a bit illogical (for historical reasons). They are following:

0 = SNMP v1
1 = SNMP v2
3 = SNMP v3

2 is an invalid value, so it falls back to v1 (as any invalid value will do). You can use constants from AbstractNode class:

AbstractNode.SNMP_VERSION_1, AbstractNode.SNMP_VERSION_2C, AbstractNode.SNMP_VERSION_3

Best regards,
Victor

Quote from: possamai on May 10, 2015, 03:53:12 PM
Tried to update the agent by deploying it to a Windows 8.1 x64 machine.
Update kept failing, apparently some DLL was still in use by the session-agent.. that one was still running while the nxagent service was stopped.

That's quite strange - installer runs taskkill before start copying files. Can you  please run manually command

taskkill.exe /IM nxsagent.exe /F /T

and check that session agent was terminated?

Best regards,
Victor

Hi,

first of all, mail notification is not related to alarm generation, so it will continue to work. DCI ID provided for all events generated by thresholds - other events will not contain it (although they may have %3 or %5 - it's just numbered event-specific parameters). You can also use named parameter dciId as %<dciId> to avoid misunderstanding. It is always recommended to include DCI ID into alarm key for threshold-based alarms. You can change all existing rules safely - the only problem is that you'll have to terminate currently active alarms manually.

Best regards,
Victor

It is not related to database housekeeping, but to in-memory object cache inside NetXMS. It seems that after move/delete object still stuck in internal index, and so adding new object/moving it back is not working. I'll try to reproduce this issue on my test system.

Best regards,
Victor