NetXMS Support Forum

Hi,

why do you have more than one MAC on a port? Does firewall use multiple MACs?

Best regards,
Victor

Hi,

it is know issue with table DCI performance when accessing historical data. We change the way how table DCIs data is stored in 2.1, so upgrade may help.

Best regards,
Victor

Hi,

there should be no changes in sorting order. I'll check it.

Best regards,
Victor

Hi,

you have to configure ping target in agent configuration file. See ping subagent description for details: https://www.netxms.org/documentation/adminguide/icmp-ping.html

Best regards,
Victor

Yes, we miss this bug again... I'll try to fix it before 2.1.1 patch release.

Best regards,
Victor

Hi,

from the log it seems that address range filter is not passed. Could you show how address filter is configured?

Best regards,
Victor

Hi,

yes, you need to create separate user with limited access rights. Workstation itself is not important - access control is done on user level.

Best regards,
Victor

Hi,

what do you mean by "configure client workstation"? Configure it for what?

Best regards,
Victor

Hi,

it's a bug, already fixed in development branch.

Best regards,
Victor

Hi,

very weird. Please check server queues and try to run server with debug level 6 fr some time and check messages with prefix DiscoveryPoller.

Best regards,
Victor

So it should be:

<config>
   <core>
      <MasterServers>XX.XX.XX.XX</MasterServers>
      <ConfigIncludeDir>C:\NetXMS\etc\nxagentd.conf.d</ConfigIncludeDir>
      <LogFile>{syslog}</LogFile>
      <FileStore>C:\NetXMS\var</FileStore>
      <SubAgent>winperf.nsm</SubAgent>
   </core>
</config>


<config>
   <core>
      <SubAgent>logwatch.nsm</SubAgent>
   </core>
   <logwatch>
      <Parser>c:\netxms\var\logwatch_win_eventlog_system_parser.xml</Parser>
      <Parser>c:\netxms\var\logwatch_win_eventlog_application_parser.xml</Parser>
   </logwatch>
</config>

Also, it is not necessary to use XML format - you can use key-value format as well.

Best regards,
Victor

Hi,

currently it's not possible. We definitely can fix column sizes not being saved in dashboards. Regarding to column order configuration - it sounds useful, I will check how big efforts it will require to implement.

Best regards,
Victor

Hi,

currently it's not possible. And what do you mean by "current user" - it is current to what?

Best regards,
Victor

Hi,

yes, proxy is not supported.

Best regards,
Victor

Hi,

as seen from output SubAgent entry for logwatch still in "agent" section, but should be in "CORE". Could you show me how your policy looks like now?

Best regards,
Victor