Attached is just an idea for what could be useful to see in a final version of this tool, so that you could see the winning source for any given line of the running config. Thanks again! [image: running-config-mockup.jpg]

Awesome, thanks again!

@victor said in WMI.QUERY ON AGENT SOME QUERY COMMAND Has Problem: Agent reads registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to get list of installed products. I tested WMI query on Win32_Product on my Windows servers, and it seems to work, but is very slow (usually more than 10 seconds). Normally agent command timeout is less than that, so data collection end up in error. Could you use System.InstalledProducts table instead? Best regards, Victor hi After receiving your tip, I immediately looked for the agent timeout settings.  Sure enough, I found agentcommandtimeout in the server configuration.  The default value is 4000. For testing, I increased it to 20000.  After restarting the service, it worked magically. The content of the data table is displayed normally. Although I don’t know the reasonable value of timeout,  I will continue to pay attention to the difference in the increased timeout value. thx victor

Although the operation of the action is executed under the system account by default under the agent,  it is invisible under the Windows session of the user currently logged in,  which is a great advantage for background system management,  but it is not necessary for the operation that needs to be known to the user at the front desk. It is not easy to achieve, such as the agent's "send user support application notification",  other front-end operations such as opening a browser to connect to a website,  and the execution of programs that require GUI display. It would make netxms more complete if ACTION had an execution option for now logged in user session.

Hi. It is still in pipeline. We have not had a chance to work on this due to limited resources, but this is scheduled for early January. We will share more info as and when. Thank you for your patience.

Subnets are created on node configuration poll. Possible reason could be some node(s), which have interfaces with periodically changing IP address. Filtering can be done in Hook::CreateSubnet script in script library, but first of all you can add some debug there (before "return true;" line): trace(0, "In Hook::CreateSubnet | Conf poll on " .. $node.name .. " want to create subnet " .. $1.ipAddress); This will add messages to server's log. If you NetXMS version is older then 5.x, line should be a bit different: trace(0, "In Hook::CreateSubnet | Conf poll on " . $node.name . " wants to create subnet " . $1.ipAddr);

As per https://www.releases.ubuntu.com/, bionic is out of standard support and we don't publish these binaries to our public repository anymore. Please check this for options: https://netxms.com/commercial-support.

Hi Alessio We have raised this with the team and you can follow progress on https://track.radensolutions.com/issue/NX-2635 Thank you for your contribution!

Yes, that's correct.

To clarify this - we have two ways of dealing with windows event logs logwatch wineventsync Logwatch supports parsing of offline events, while wineventsync currently does not. There is an issue in our bug tracker on this, so some day this will be fixed: https://track.radensolutions.com/issue/NX-1997

Seems like setting MQTT proxy solved the problem. Thanks! Egert

Hi there, first thing to check would be the driver and for mssql, you would need to use odbc.drr and create database manually. There are several forum threads for similar setups, one of them here - https://www.netxms.org/forum/general-support/installation-of-netxms-problems-connection-to-ms-sql-server/msg33054/#msg33054 Hope this helps!

nodeid 76050 have a interface(objectId=76051) ifindex=5 mac address A0:36:BC:5B:19:A7 is physical link on the sw-203-dlink(dgs-1510-52) switch eth1/0/2 nodeid 76040 have a interface(objectId=76041) ifindex=5 mac address A0:36:BC:5B:18:D9 is physical link on the sw-203-dlink(dgs-1510-52) switch eth1/0/41 nodeid 76048 have a interface(objectId=76049) ifindex=5 mac address A0:36:BC:5B:1A:E0 is physical link on the sw-203-dlink(dgs-1510-52) switch eth1/0/42 my nodeid 76050 76040 76048 's operation The operating systems are completely cloned. Only the hardware information is slightly different, such as the network card mac address and ip. in netxms i use topology sw-203-dlink switch forwarding database list result ,It is also consistent with the actual interface between the computer and the switch. so i search in source code In lln.cpp I find I saw the relevant code below Also, I have also directly queried the lldp of the switch and I get this result Name/OID: .1.0.8802.1.1.2.1.4.1.1.7.306145956.42.9; Value (OctetString): A0-36-BC-5B-1A-E0 Name/OID: .1.0.8802.1.1.2.1.4.1.1.7.306145970.41.17; Value (OctetString): A0-36-BC-5B-18-D9 Name/OID: .1.0.8802.1.1.2.1.4.1.1.7.306146123.2.15; Value (OctetString): A0-36-BC-5B-19-A7 The information on lldp also confirms that the node is on the correct interface. so,Is it possible that some misjudgment or mistake occurred here? /** * Check if given information is duplicate */ bool LinkLayerNeighbors::isDuplicate(const LL_NEIGHBOR_INFO& info) {     for(int i = 0; i < m_connections.size(); i++)     {       LL_NEIGHBOR_INFO *n = m_connections.get(i);         if (n->ifLocal == info.ifLocal)         {           if ((n->ifRemote != info.ifRemote) || (n->objectId != info.objectId))           {               nxlog_debug_tag(DEBUG_TAG_TOPO_LINK, 5, _T("LinkLayerNeighbors::isDuplicate: inconsistent data: %s(ifLocal=%d remote=%d/%d) %s(ifLocal=%d remote=%d/%d)"),                           GetLinkLayerProtocolName(n->protocol), n->ifLocal, n->objectId, n->ifRemote,                         GetLinkLayerProtocolName(info.protocol), info.ifLocal, info.objectId, info.ifRemote);           }         return true;         }       if (n->ifRemote == info.ifRemote)       {         if ((n->ifLocal != info.ifLocal) || (n->objectId != info.objectId))         {             nxlog_debug_tag(DEBUG_TAG_TOPO_LINK, 5, _T("LinkLayerNeighbors::isDuplicate: inconsistent data: %s(ifLocal=%d remote=%d/%d) %s(ifLocal=%d remote=%d/%d)"),                         GetLinkLayerProtocolName(n->protocol), n->ifLocal, n->objectId, n->ifRemote,                         GetLinkLayerProtocolName(info.protocol), info.ifLocal, info.objectId, info.ifRemote);         }         return true;       }     }     return false; }

That was exactly what I needed. Thanks! Posting setup here for reference. Node goes down. 2 minutes later slack alert goes out 5 minutes later slack alert goes out 20 minutes later slack alert goes out If the node comes up prior to 2 minute alert, alarms are cleared and no alert is sent.  [image: 10-16-2024 2-15-56 PM.jpg]

I believe after messing around with this for some time it is working. Once I added all nodes on the routes between the server and the nodes, did "route from" to the Netxms server, initial testing is showing dependencies working properly. Even on the UBNT ap's and other devices without SNMP.  Big thank you to everyone who helped get me through this!

I figured out how to do that. Thank you! I also learned that SQL Server Express that comes with Netxms has a 10GB database size limit. Looks like we need to upgrade to Standard to get around that.

Added in 5.1 - nxshell now reads nxshell.properties if available in current directory or classpath. You can also specify path to properties file in command line. Best regards, Victor