When Ive upgraded to 2.07 and I saw couple of hosts on L2 map(map Ive created before) without changing anything in their config. All hosts have similiar configuration, and software version. Yesterday Ive upgraded NetXMS to newest BETA and all host dissapeared from map. This post is only info(version 2.07 started to discover network). Im waiting for LLDP in MT(now in release candidate). When Ive tried to pull L2 from Nexus Ive got info about problem retrieving FDB. My Nexus was discovered with driver Generic.

Thak You Sir. It is working. Before answer Ive resolved problem other way(file without 001 ending i attachments). Ive attached my MikroTik templates(file with 001 is corrected as Mr Victor suggested to deal with that voltage OID) for everyone. Template's DCI's: -CPU usage -MEM Usage -Voltage -Count of Wireless Clients -Speed/Packets of all interfaces(interfaces with "vl" and "br" in names are not included) -RouterOS and Firmware version -Board Name -Ping netxms-mt-template-back-2016-12-29.xml netxms-mt-template-back-2016-12-29-001.xml

Hi, agent installer is build using InnoSetup. There is MSI wrapper that can wrap installer exe into MSI suitable for GPO deployment - http://www.exemsi.com/inno-setup-and-msi, although I didn't try it myself. You may need to specify installer options for unattended installation - they described here: https://wiki.netxms.org/wiki/Agent_Installation_Guide#Unattended_installation_of_NetXMS_Agent_on_Windows. Best regards, Victor

Hi, in map options (map object properties -> "Map Options" page) turn on "Include end nodes" checkbox. Best regards, Victor

Thanks Victor, Best regards, Tomislav

Just one comment: code block if (found_process == true) { return true; // process has been found } else { return false; // process has not been found } could be replaced with simple return found_process; Best regards, Victor

Fixed in version 2.1-M2. Best regards, Victor

Hi, yes, default auth method changed from PAP (the only one supported before) to CHAP. You can change it back by setting server configuration parameter RADIUSAuthMethod to value PAP. Best regards, Victor

Another note on having external IP address from router set as primary address for proxy node - you can try to set option "This is address of remote management node" in communications options for proxy node. That way server will not consider primary IP part of proxy node. Best regards, Victor

Switching to postgres fixed the issue.

Hi Victor, thank you. I wanted to add that some nodes did not registered under the relevant /24 subnet even after 2 full configuration polls. the only thing that helped is deleting the /32 subnet and the node registered correctly. thank you very much and hope you will find the problem Best regards, Lindeamon

Hi, "Force poll" for push DCI is meaningless, but it definitely should not change state to "not supported". I've registered it as a bug (https://dev.raden.solutions/issues/1366). Best regards, Victor

Hi, currently it is not possible. Feel free to fill feature request, it should not be hard to implement. Best regards, Victor

Hi, I have installed the v2.0.7 sw successfully. In this also is included the bugfix what is important for me. Thank you very much. BR, Zsolt

Thanks Victor ! I would never think of that. Best Regards, Adrian

Hi, I think it is good to have those rights separated. Added it as feature request: https://dev.raden.solutions/issues/1360. Best regards, Victor

Hi, before 2.0.7/2.1-M2 NetXMS only supported PAP for RADIUS authentication. As we added support for other authentication methods default was set to CHAP, which is probably wrong because it breaks backward compatibility. Best regards, Victor

I created a threshold on the DCI (!=0 -> SYS_NODE_DOWN, deactivation event SYS_NODE_UP) as per this thread: https://www.netxms.org/forum/configuration/node-with-question-mark-on-the-icon-of-object-browser/ and it is working now.

severity is the attribute, setSeverity is the method

sorry I forgot to tell about the reconfigure part of postfix