NetXMS Support Forum

For version 4.3 we have also added new metric File.Type, which returns 0 if file does not exist, 1 if it is a directory, 2 if it is a device, and 3 if it is a regular file.

Best regards,
Victor

Hi!

most likely server does not have certificate. If this is the case than you can safely ignore this error, or delete problematic DCI.

Best regards,
Victor

We just published patch release 4.2.433. It fixes critical bug in release 4.3.432 (non-working hook scripts).

We just published patch release for version 4.2 - 4.2.432. Changes since previous release:

- Driver for Juniper Networks devices retrieves product information from vendor MIB
- Empty source/tag is processed as match any source/tag for Windows Event Log and syslog parser
- Configurable maximum message size for client connections
- "Follow location" option for web services
- Fixed server crash after DB connection loss
- Fixed server deadlock within topology poll
- Fixed web application property reading from JNDI and properties file
- Fixed issues:
        NX-2278 (Support for hexadecimal encoding of OCTET STRING in nxsnmpset)
        NX-2298 (Alphabetize Source Objects in Event Processing Policy)
        NX-2315 (Chained import in NXSL is not working)
        NX-2321 (History for a Table DCI value shown as empty)
        NX-2333 (Data collection error thresholds show up as "error(1) < 0")

Best regards,
Victor

It is known issue, will be fixed in upcoming patch release.

Best regards,
Victor

Обновил nxsnmpset, теперь у него появился ключ -H для указания hex строки. Будет в следующем патч релизе 4.2.

I've updated Juniper driver to use this MIB if available. Changes will be included into next patch release.

Best regards,
Victor

New Windows installer just published.

Best regards,
Victor

Quote from: lindeamon on October 22, 2022, 10:41:38 AMthank you for all the hard work and for giving us this awesome piece of software.
when can we expect the completion of the new UI  ?

Functionality wise it is mostly complete, most likely we will move remaining functionality during 4.2 patch releases.
As for UX (interaction with views, menus, etc.) - we are still experimenting, and major changes are still possible. Feedback from users also very important.

We just published repackaged Windows installer for web UI (version 4.2.398) with Jetty 10 inside.

Best regards,
Victor

Currently NetXMS uses Entity MIB for getting hardware information for Juniper devices. Looks like those models does not support Entity MIB.
Do you know if Juniper priovides model and serial number information via private MIB? If yes, we can update Juniper driver to use it.

As for retaining old hardware information - it is a bug (or rather flawed logic). Existing hardware information kept in place if server cannot read it from the device to avoid erasing it because of read error. I think that best solution will be device replacement detection (likely based on MAC address change and probably also hardware model change) and running full poll if it is detected. Added it as feature in our tracker: https://track.radensolutions.com/issue/NX-2314

It is not possible without changes in log parser code. Named capture groups also not supported. I've added feature requests for both:

https://track.radensolutions.com/issue/NX-2312
https://track.radensolutions.com/issue/NX-2313

Best regards,
Victor

Tomcat 10 uses Servlet API 5.0 (with Java package names switched from javax.servlet to jakarta.servlet). Framework we are using is not compatible with Servlet API 5.0, so you should use Tomcat 9 or Jetty 10.

Yes, we will update Windows installer.

MIB file as such will not add VLAN information, we have to make changes to device driver so it read non-standard MIB. If you can provide SNMP access to test device we can implement necessary changes in D-Link driver for reading VLAN information.

Best regards,
Victor