NetXMS Support Forum

Должны быть доступны сетевые устройства - маршрутизаторы для карт 3-го уровня, коммутаторы для карт 2-го уровня. Сервер должен видеть их интерфейсы и данные по топологии (FDB, LLDP, и т.д.)

This is done in upcoming 3.0 - policies combined with templates and can be exported and imported.

Best regards,
Victor

Hi,

you have to wrap message (and anything that can have space in it) into double quotes, like this:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe c:\scripts\create-inc-from-alarm.ps1 -device  "%n" -sev %s -tyme %c -pd "%(pass)" -msg "%m"

then you should have full message text in msg.

Best regards,
Victor

Hi,

Do you have minidump file generated that you can share?

Best regards,
Victor

Hi,

such situation usually can happen when NetXMS server cannot get interface list from node. How interface tab for such node looks like? Does those devices support interface MIB and IP MIB?

Best regards,
Victor

Hi,

looks like a bug in GUI. What version you are using?

Best regards,
Victor

Hi,

those errors should not cause service to not start. Please try to run netxmsd from shell with -D9 option and post last lines of output.

Best regards,
Victor

Hi,

yes, if you want average per minute then you put 60 as sample count. You do not need to collect it from agent every second - agent will return average for last 60 seconds whenever value is requested.

Best regards,
Victor

Try this filter script:


snmp = CreateSNMPTransport($node);
return SNMPGet(snmp, ".1.3.6.1.2.1.31.1.1.1.6." . $1) != null;


It will filter out all instances where SNMP-GET on .1.3.6.1.2.1.31.1.1.1.6.{instance} fails.

Best regards,
Victor

Did you add

EnableTCPProxy = yes

to config of proxy agent? Also, server has to be listed as master server on a proxy.

Best regards,
Victor

Hi,

one possible option is to create fake nodes without IP address to represent different units and use status DCIs to set unit status. I will also think about implementing some sort of built-in mechanism for representing units of distributed stack as that seems to be quite common task. If you wish you can follow on this ticket: https://track.radensolutions.com/issue/NX-1657

Best regards,
Victor

Actually, nxpush/nxapush was not designed with "update" option in mind. Server expects that each new push will contain new data. If you don't mind please create feature request in our tracker for "update" functionality for push DCIs.

Best regards,
Victor

Hi,

there is an option in node communication settings called "Prevent automatic SNMP configuration changes".

Best regards,
Victor

Hi,

we have request for simplifying SNMP trap configuration so there should be improvements in 3.x branch in July/August.

Best regards,
Victor

Yes, unmanaged state prevents SNMP transport creation. As possible workaround you can set node as managed from the script, create transport, and set it back to unmanaged. If you don't want any poll to start, you can disable polling before setting node to managed state.

Best regards,
Victor