NetXMS Forum

https://github.com/netxms/docker/

Hello, we are using latest NetXMS on Debian, and using only Web console. Is it possible to have Single Sign On enabled, and configured to work with Azure Active Directory (Microsoft Entra ID / Office 365) users? If so, can somebody share configuration steps? This is not LDAP authentication nor RADIUS. As I understand it should be under > Central Authentication Service (CAS) single sign-on is supported in web interface only. User management — NetXMS Administrator Guide (4.2.433)  but i do not see way to enter URLs, application id, secret etc., for newly created Azure AD Application Registration Thank you for your support and great product.

Those errors should be gone once you upgrade all agents. There were bug in agent that cause it to report identical entries in software list. Best regards, Victor

Just pushed into repo, please check

Hi, I got similar requests from other users too. I'm currently considering adding "exclude from topology" option for nodes - then all topology functionality will be turned off, but node will be checked in status and conf poll using primary name and data collection will work. Best regards, Victor

Hi Any news about this request?

Hello. Sorry it took so long. Packages are pushed to public repository (both jessie/wheezy, 32 and 64 bit).

@victor said in Bug / SQL injection? Monitoring Windows Event Logs and NetXMS Server SQL errors: No, it's not due to apostrophe character and SQL injection is not possible here. You can see that SQL statement is a prepared statement with placeholders - it is not constructed dynamically from external data. Also, error message clearly states "Violation of PRIMARY KEY constraint 'PK__alarm_ev__E6249E6BFEDA1E4D'. Cannot insert duplicate key in object 'dbo.alarm_events'. The duplicate key value is (1704, 64513)" - actual problem is that system for some reason tries to insert duplicate record into table. It is definitely a bug, but not a security threat. Best regards, Victor Thank you for fast and correct response. Now I understand this is NOT SQL injection / security hole. Sometimes I also have: "String or binary data would be truncated", but there is lot of duplicate items. Something maybe about wrong collecting windows event logs on a agent/client maybe or event processing rules I do have latest available stable version.

Probably best to leave the events to be generated, and instead modify EPP (event processing policy) to not create alarms for these events from certain nodes where you know this is supposed to happen. This is better then disabling the event generation all together.

Victor, thank you very much!

@victor said in Network service HTTP/HTTPS monitor, check output and response time: Currently you cannot see what output agent was gathered nor measure response time. Feel free to fill feature request Best regards, Victor Ok, thank you. I am marking this as answered/solved. New feature request is here: https://www.radensolutions.com/chiliproject/issues/565 Thank you once again.

@victor said in DCI in template with {instance} parameter in WMI, WMI as tables?: NetXMS agent uses PDH API to access performance counters. You can add feature request to our bug tracker for instance discovery support for perf counter DCIs. Great, thank you, feature request is created here: https://www.radensolutions.com/chiliproject/issues/567

Description of node class is here: http://wiki.netxms.org/wiki/NXSL:Node and all scripting reference information is here: http://wiki.netxms.org/wiki/Scripting_Guide Best regards, Victor

To filter CD/DVD and Volume in the "Instance Detection" section, I use this script: type=AgentReadParameter($node, "FileSystem.Type(" . $1 . ")"); if ((type == null) || (type == "") || (type == "CDFS") || (type == "UDF")) { return false; } if ( type != null && ( type == "aufs" || type == "autofs" || type == "cgroup" || type == "configfs" || type == "debugfs" || type == "devpts" || type == "devtmpfs" || type == "fusectl" || type == "fuse.gvfsd-fuse" || type == "fuse.lxcfs" || type == "hugetlbfs" || type == "iso9660" || type == "mqueue" || type == "nfsd" || type == "overlay" || type == "proc" || type == "pstore" || type == "rpc_pipefs" || type == "securityfs" || type == "selinuxfs" || type == "squashfs" || type == "sysfs" || type == "tmpfs" )) { return false; } if (($1 == "/proc") ||     ($1 like "/proc/*") ||     ($1 == "/sys") ||     ($1 like "/sys/*") ||     ($1 == "/run") ||     ($1 like "/run/*") ||     ($1 == "/dev") ||     ($1 like "*Volume*") ||     ($1 like "/dev/*"))   return false; return true;

Hi, maybe you could solve it by filters in event processing policy ? Something along these lines: IF SYS_IF_DOWN and: parentNode = GetObjectParents($if); // not sure if "$if" (Get ObjectParents reference) if ((parentNode->status == 4) return 0; For more details see my solution of dependency based on infrastructure, if it helps... here With regards, MS

@victor said in Constantly - "Node capabilities changed": Hi! That means that flag NF_HAS_WINPDH (Node supports Windows PDH parameters) set and cleared periodically. Node considered to support PDH if it has NetXMS agent and agent responds correctly to PDH requests (PDH.Objects list and others). You can check server debug log (running with debug level 5 or higher) for error messages started with WinPerfObject::getWinPerfObjectsFromNode prefix. Best regards, Victor Great, thank you for correcting me ! I Windows Event Log , from NetXMS Agent I have: H_PdhCounterValue: PDH Error 00000102 in call to PdhOpenQuery (The wait operation timed out.) Please explain what to check futher ? I understand that it has something with disk / RAID ? Server is operating normally.

Hi, received SNMP traps cached in memory until connection with NetXMS server restored. However, they are not stored to local database so if agent is restarted any cached traps will be lost. Best regards, Victor

@victor said in NetXMS Agent use of UDP ports?: Hi! Agent cannot use UDP for communications. It's just standard practice to assign both tcp and udp port numbers - I didn't even request udp ports. Best regards, Victor Documentation says that it needs tcp and udp. Sometimes it is hard to port forward both (some ISPs charge by port etc.) Also, for example Windows Agent adds two firewall rules, seperate tcp and udp. So to resime, UDP is not needed at all. Thank you for info.

Hi! Changing database while server is running will not help, because most configuration information is cached and server do not expect outside modifications in DB. You can use nxshell scripts to change node parameters as needed. Also, if you are building server from sources, you'll be able to apply patch when we solve #566. Best regards, Victor

@hkusulja said in netxms agend and connection direction ?: Hi, Thank you for reply, I am aware of Agent proxy feature which is nice, however in some particular cases I do not have any option to forward / open any of ports, so this is reason why I am using this. Is there a way to automate push that you mentioned ? Or I should write this as new feature request ? Thank you once more Hi, I've automated it just writing a batch file that I run as a scheduled task. I'm not aware of a smarter way to do it but, honestly, it works fine in my case and I didn't spend any other time to find a smarter way Best regards, Marco