NetXMS Support Forum

64 битные счетчики добавлены в 2.0.5 и 2.1-М1.

Hi,

I've fixed that, fix will be included in 2.0.5 release.

Best regards,
Victor

Hi,

proper solution will include changes on agent side. I'll change the agent so it will save parameter names in local database so if server request comes before provider first run agent will respond with collection error instead of unsupported parameter.

Best regards,
Victor

Hi,

currently it is not possible.

Best regards,
Victor

Hi,

currently it's possible only by replacing normal DCIs with script DCIs (script DCI call SNMPGet and on failure returns something to indicate a failure). I'll add feature request to make this functionality simpler.

Best regards,
Victor

Hi,

basically in a same way, just use different file names:

C:\NetXMS\bin\nxmibc.exe -z -d C:\NetXMS\share\mibs -o C:\NetXMS\var\netxms.mib

(assuming NetXMS is installed into C:\NetXMS).

Best regards,
Victor

Hi,

you can mark DCI to be shown in object tooltips (on "Other options" page in DCI properties). You can also add DCI display information to network map using "DCI container" or "DCI image" decorations.

Best regards,
Victor

Hi,

could you please be more specific? What is your configuration file, what errors you get?

Best regards,
Victor

Hi,

added as feature request: https://dev.raden.solutions/issues/1247. I'll try to implement it in 2.1 branch.

Best regards,
Victor

Hi,

I see that there are 7340 parameters configured for collection. Strange enough some seems to be duplicates, because there are only 6966 distinct names - but all have different DCI IDs. Is it really that much DCIs on this node? Most of them seems to be external parameters. How long this script executes? Because if there are enough long-running scripts it can overload data collection thread pool and possibly cause other strange effects. I will try to simulate collection of that many external parameters and see if I will be able to reproduce strange behavior you observed.

Best regards,
Victor

Hi,

so nodes are created but subnet is not, or nodes not created as well? If nodes not created, can it be that you also have discovery filters that prevents creation of these nodes?

Best regards,
Victor

Hi,

currently max number of threads is hard-coded (64). I can make it configurable. Still it looks like a bug that agent do not keep polling interval. Can you please provide agent's log on debug level 7 along with content of dc_config table from agent's local database?

Best regards,
Victor

Hi,

sorry for late reply! Portuguese translation would be awesome. Attached is archive with Portuguese language files.

Best regards,
Victor

Hi,

from log it seems that loader considers your Java environment incompatible. Try to run it with openjdk-8 or openjdk-7. If you don't want to change system default JRE, you can set nxms to use specific JRE by creating link named "jre" on bisides nxmc executable. For example, to use openjdk 1.8 on my machine it will be

ln -s /usr/lib/jvm/java-8-openjdk-amd64/jre jre

Best regards,
Victor

Попробуйте поставить уровень дебага 5 и посмотрите в логе сервера записи с префиксом SMS: - драйвер должен написать какой именно шаг отсылки не прошел.

Еще вопрос - а собственно nxsms никаких ошибок не сообщает?