NetXMS Support Forum

Похоже что SNMP агент на устройстве дает неполную или некорректную информацию по портам. Пришлите пожалуйста результат SNMP walk по OID'ам .1.3.6.1.2.1.17.1.4.1 и .1.3.6.1.2.1.17.4.3.1.

Hi,

there is agent management chapter in admin guide: https://www.netxms.org/documentation/adminguide/agent-management.html

Best regards,
Victor

Hi,

I'm suppose ~ in ~\Downloads\ refers to home directory of the user - but if you run agent as a service it by default runs under local system account, so ~ points to completely different place.

Best regards,
Victor

Hi,

currently it's not possible. In fact tabular data support needs major improvements in NetXMS - we have plans to improve it at some point.

Best regards,
Victor

Т.е. в правиле несколько действий - terminate alarm плюс рассылка, и подавлять надо именно остальные действия.

Скриншот в аттаче, но я поторопился - bridge port number там не показан. Попробуйте запустить такой скрипт (через execute server script на ноде):


foreach(i : GetNodeInterfaces($node))
{
println i->name . " ifIndex=" . i->ifIndex . " bridgePortNumber=" . i->bridgePortNumber;
}


и прислать результат.

Hi,

you can pass desired timestamp to nxpush using -t or -T option. For example, to pass current timestamp on UNIX system, you can do it like this:

/opt/netxms/bin/nxpush -u admin -t `date +%s` 127.0.0.1 hp8570w:PushTest=1

Best regards,
Victor

Hi,

currently it's not possible (but we can add that in the future). As a workaround, you can use "execute server script" option for node or container. It requires more mouse clicks but still allows you to run scripts on node.

Best regards,
Victor

Maybe using script DCIs will be better solution in your case. You can create script in a library which will be called by data collector, and that script will have access to all attributes of a node and can read appropriate data from agent or SNMP using AgentReadParameter or SNMPGetValue functions.

Best regards,
Victor

Hi,

no, currently it's not possible.

Best regards,
Victor

Hi,

could you please provide results of SNMP walk on OID .1.3.6.1.2.1.2.2.1 for that switch?

Best regards,
Victor

There is section in manual on log monitoring (including Windows Event Log): https://www.netxms.org/documentation/adminguide/common-tasks.html#log-monitoring

Best regards,
Victor

Hi,

you cannot add another placeholder, but you can concatenate anything you need into {instance-name} in filter script. For example, to add prefix "instance" to every instance name return from script as following:

return %(true, $1, "instance: " . $1);

first element is acceptance indicator, second is instance ({instance} will be replaced by it), third is instance name. There should be examples on the forum for filtering scripts used to return meaningful interface names in {instance-name}.

Best regards,
Victor

Hi,

yes, you can define action in agent (using Action or ActionShellExec entries in nxagentd.conf) and then define object tool to run it manually or server side action of type "execute action on remote agent" to run it automatically from event processing policy.

Best regards,
Victor

Hi,

it seems that actual problem was cache load without locking: CacheLoadingThread calls updateDciCache on every node, which in turn calls updateCacheSize on every DCI, and there was no lock on DCI level inside, so any access to DCI at that moment may cause unpredictable results. And because you have NXSL scripts accessing DCI data running at same moment as well as templates removal it happens. I've changed cache loading to use proper locks on DCIs, that should solve this issue (changes already pushed to develop and stable-2.0 branches).
Btw, you could avoid template unbinding on startup by checking return value of GetDCIValue function for being null aborting auto-apply script (using abort statement) - system will make no change in current binding status if script completes with runtime error.

Best regards,
Victor