Hi, looks like a bug in dashboard layout code. Could you please export your dashboard and send to me? Best regards, Victor

Hi, Earlier today I created a network map and noticed that some of the configured labels on switches were incorrect, so I went ahead and reconfigured those on the switches. I then ran an interface name poll and assumed the map would update its link labels. But it did not. The old labels remained. I ran configuration and topology polls as well, same result. Do link labels not get updated? Is this a one-off thing that maps do when they create a new connection between devices (i.e. check the interface names, then statically store the current value as part of the connection object itself)? This is an automated L2 map, so I can of course recreate it, but doing so just because a link label needs an update seems excessive? Or is that something that's updated as part of housekeeping once a day? Cheers

I did what you told me. with debugging I could realize that "$dci->instance" was returning the name of the iface instead index(returned in instance discovery) I have to create another function that return iface index by providing ifname. Thanks for your help

It looks like there wasn't any fix for this in 2.1.  Any ideas?

Wonderful, thanks alot had a feeling this was feature related so been looking around

Hi, Looks to me like negative lookahead regular expressions are not working (I tested a bit and got the same result you did). Not sure if there's some syntax difference or if the ?! is being interpreted by something else. You could change your if ($1 ~= "^([0-9]+) .*") to this if ( ($1 ~= "^([0-9]+) .*") && ( ! ( $1 ~= "^[0-9]+ (127|::1|fe80).*" ) ) ) { It should work and remove the need for the additional if statement you added, but in the end, it's still just a workaround for the negative lookahead not working properly. Cheers

Hi, Just a FYI: The issue persisted with the release of 2.1, but has now been resolved in the latest development build. A huge thank you to Victor for logging into our system, determining the underlying cause (related to Active Agent Tunnels) and fixing it. Cheers

OK, good news: This command worked, with more parameters: du -h --max-depth=1 | sort -n I see now the problem is in /var/lib/mysql/ 110516876 netxxx.millerxxx.com.err This seems to be an error file, that is now massive? -Kevin C.

need to upgrade database, run 'nxdbmgr upgrade'

Hi Victor, Is the behavior of logwatch changed in version 2.1 when agent sends parameters to the server? As per my test seems that a new parameter is added at the end of the list (up to ver 2.0.8 I had 10 params sent and now I have 11, in my specific sample the new parameter added has value of '1'). Regards, Marco

Hi, Once you create a Layer 2 map, you can enter the map's properties and add more seed nodes (at least in 2.1 you can, I don't recall if that's a new feature or not). You can also configure a custom discovery radius for the map. Cheers

@staj said in SSL/TLS for WebUI (Jetty): Running NetXMS on Windows. Probably not exactly the answer you are looking for, but on Windows I managed to do in the way described here: https://www.netxms.org/forum/configuration/netxms-webui-with-http-ssl/msg13453/#msg13453 Hope it helps. Regards, Marco

Hi, Things I'd check in such a case: Ensure port 4700 on your Ubuntu server is indeed reachable from the NetXMS server, i.e. there is no firewall in between or on the Ubuntu server blocking access. A simple telnet test to port 4700 should do. Check if Agent Polls are disabled on the node. Run a Full(!) Configuration Poll against the node. Enable some debug logging on the server and/or agent. Run polls and check the logs for potential issues. Cheers

Hi, it seems to be missing in deb packages. We will check and re-package them to include SSH subagent. On Windows SSH subagent is included. Best regards, Victor

Hi, no, only one group per DCI is possible. Best regards, Victor

Hi all, is there any way to diable event SYS_PACKAGE_UPDATED on version 2.1 ? Already disable it in event processing policy but not work... And turn off Flag to write to event log too. Already try to delete it, but is Access denied

Hello. As spoken in the Telegram group, after the update of the NetXms version to 2.1, two DCIs we used stopped working. On linux machines, with the agents in version 2.0.6 ECS.HttpLoadTime and Servicecheck.HTTP work perfectly. In version 2.1 they give an error. NOTE: In our environment we need the sites to be in the hosts of each machine. We did another test on Windows machines, using Agent 2.1: Without hosts locally, doing a query by DCI, occurs, "Communication failure" [image: rQw6KYy.png] With the hosts locally, the query returns: "Operation can not be completed due to agent error" [image: pXzqz5l.png] Any help?

Hi, Passive Network Discovery works via agent. So if the network you're trying to discover has managed switches with LLDP/CDP and no unmanaged devices in the mix, it should provide some results. Ensure to set the correct zone ID in the proxy agent's configuration. Active Discovery via agent still does not work (for all I know). Cheers

Victor replied on a different thread: Hi, default templates re-imported from file system on server startup. You can disable this behavior by setting server configuration parameter ImportConfigurationOnStartup to 0. Best regards, Victor

Got it thank you. I'll put this over on my other thread that I started.