NetXMS Support Forum

Hi,

are you using TimescaleDB?

Best regards,
Victor

We just published patch release 5 for version 4.3! Changes since previous patch release:

- Fixed bug in X.509 certificate subject and issuer decoding
- Agent tunnel listener will not start if server certificate is not loaded
- Fixed WEB service configuration import with multiple headers
- Fixed login issues in new web UI
- Small fixes and improvements in new management client application
Fixed issues:
   - NX-2272 (Session is not closed if user cancel 2FA auth initialization)
   - NX-2276 (Warn user when adding too wide mask to active discovery)
   - NX-2388 (Modify default templates - filesystem with type "ahafs" should be excluded from discovery)
   - NX-2404 (Integer division by zero in NXSL crashes server)
   - NX-2406 (Entering maintenance mode on cluster does not trigger maintenance mode on nodes within cluster)

I just fixed certificate subject parsing, fix will be included into next release.

Best regards,
Victor

Hi!

It could be related to LLDPv2 MIB support that we have added in 4.3. Could you please check if device responds to OID .1.3.111.2.802.1.1.13.1.3.2.0? If yes, could you provide result of SNMP walk on .1.3.111.2.802.1.1.13.1.4.1.1 and .1.0.8802.1.1.2.1.4.1.1?

Best regards,
Victor

So H3C returns non-standard value 6 for dot1qTpFdbStatus. Interestingly they don't mention this value even in their own documentation on Q-Bridge-MIB (found it here: https://www.h3c.com/en/d_202211/1719268_294551_0.htm).
Can you please explain what is the difference between "secure" and "learned" state?

We just published patch release 4 for version 4.3. Changes since previous patch release:

- Fixed bug in ICMP ping implementation introduced in 4.3.3
- Added agent configuration option for setting file mode creation mask (umask)
- Bundled SQLite updated to version 3.41.2
- Multiple fixes and improvements in new management client application
- Fixed issues:
   - NX-2137 (File delivery policy times out of big files when saved)
   - NX-2386 (Object Category custom node icon covers object browser status icon)
   - NX-2395 (Output of PATCH Web Service call is ignored)
   - NX-2396 (Web Service Definition timeout not displayed correctly)

Best regards,
Victor

Hi,
could you please share SNMP walk output on .1.3.6.1.2.1.17.7.1.2.2.1?
Best regards,
Victor

Multiple proxies within one zone intended for load balancing and HA - so all proxy nodes should be able to communicate with all nodes within zone. Server will distribute load between proxy nodes, and yes, this process is not subnet-aware (and is not intended to be).
If two subnets you have are actually in two different locations, you can split them into separate zones and assign correct proxies.
Overriding proxy on subnet level can be implemented relatively easy if load balancing and HA functionality is not required - i.e. only one proxy set on a subnet, it overrides any zone setting, and if this proxy is not functioning, communication with the subnet s lost. Replicating full zone proxy functionality on subnet level will significantly increase complexity of necessary changes, and in my opinion will be unnecessary duplication of functionality that is already exist.

Best regards,
Victor

Hi,

from the dump it looks like bug within SQLite. I updated bundled SQLite to latest version (3.41.2) - if this will not help, we will need to investigate further.
It also worth trying to use matching agent package from deb repository - it will have dependence on SQLite version built for that particular distribution.

Best regards,
Victor

Hi,

I was unable to reproduce it on my test system either. However, there is one path that could potentially lead to such crash. I've made changes to DCI value processing method, they will be included in upcoming patch release 4.3.4.

Best regards,
Victor

We just published patch release 3 for version 4.3. Changes since previous patch release:

- Improved database migration procedure when TimescaleDB is target (GitHub issue 83)
- Fixed bug in handling "verify-peer" option for network service metrics
- Fixed server crash when doing RADIUS authentication using MS-CHAP
- Fixed columns for 'Find switch port' search result
- Added additional information to debug message about event with incorrect source id
- Added ZoneUIN for Cluster's overview page
- Small fixes and adjustments to new management client
- Close DCI config view message not shown on DCI copy
- Dashboard element "Table Value" works in context dashboards
- Fixed issues:
   -  NX-2387 (SQL errors when saving OSPF neighbor list)

FindNodeByIPAddress is a function, so you should not add "Objects." in front of it. Dot is string concatenation operation in NXSL (we plan to change that in 5.0, but that's another story) - so Objects . FindNodeByIPAddress concatenates null value converted to empty string from non-existent variable "Objects" with object returned by FindNodeByIPAddress converted to string - so result is a string.
Correct script will be something like this:
node = FindNodeByIPAddress($1, null);
if (node == NULL) {
   println("Error: node not found.");
   return;
}

println(node->name);
println(node->executeSSHCommand("ip address print"));

Best regards,
Victor

We just published patch release 2 for version 4.3. Changes since previous patch release:

-  Fixed stacked line charts in new UI
-  Fixed timeout inconsistencies in netsvc subagent
-  Added web API calls for managing alarm comments
-  More functionality migrated to new management client

Fixed issues:

-  NX-677 (Dashboard editor: accelerators are duplicated in Line chart -> Data sources)
-  NX-2377 (Copy-paste of rules not working in EPP editor)
-  NX-2348 (Show active threshold event name in Last Values)
-  NX-2376 (Agent restart is not working correctly on RedHat based Linux OS)
-  NX-2379 (REST API to force poll DCI)
-  NX-2383 (Ignore systemd synthetic records when resolving node IP address to hostname)

Recording of webinar is available on YouTube: https://www.youtube.com/watch?v=KKPmv5GfJag

Make sure you have debug level set to 6 for tag ncd.telegram, then look for messages with this tag that precedes line "Telegram API call failed, driver configuration could be incorrect" - there should be more information about failure reason.

Best regards,
Victor