NetXMS Support Forum

Today we have published patch release 5.0.8. Changes since previous patch release:

- Fixed error in web console on package deployment
- Implemented refresh for Event Processing Policy view
- Fixed Arp Cache view refresh when data is not available
- Implemented find mac in Web APIs
- NXSL function "trace" handles objects and arrays in a same way as "print"
- New methods "print" and "trace" in NXSL class "Table"
- Added workaround for incorrect LLDP information returned by Alpha Bridge switches
- Fixed bug in network map link styling script processing
- Fixed issues:
   - NX-1311 (Table DCIs ignoring table configuration)
   - NX-2567 (ExternalMetricProvider does not work on Windows)
   - NX-2570 (Use monotonic clock instead of system time for calculating agent uptime)
   - NX-2572 (Problem creating PostgreSQL database during installation on Windows)

SNMP is enough for testing the driver.

I suggest upgrading to latest version from 5.0 branch if possible. We did lot of changes in network maps in version 5.0, that issue could be also solved. I just double checked on 5.0.6 - DCI data is shown on map in this version.

Best regards,
Victor

We just published patch release 6 for version 5.0. Changes since previous patch release:

- Added notification channel driver for Mattermost
- Topic support in notification channel driver for Telegram
- Fixed incorrect client IP address reported by Windows agent in table System.ActiveUserSessions
- Fixed bug in output of nxget -U
- Fixed web UI crash when opening dashboard in kiosk mode
- Fixed issue NX-2550 (Errors in desktop client log (Widget is disposed))

Just fixed it, fix will be included into next patch release.

Best regards,
Victor

Are you using autologin to open dashboard or map in kiosk mode?

Best regards,
Victor

Hi!

Did you try version 5.0.4? We made changes in LLDP handling on Huawei devices.

Best regards,
Victor

It is new feature that is (somehow) working. If you check this box, server will use Isolation Forest algorithm to check if new value is an outlier within two set of data points - all values within 30 minutes of current time of the day for last 30 days, and all values within 30 minutes around current time of the day on the same day of the week for last 10 weeks. Currently it has arbitrary score threshold 0.75, depending on testing results we may adjust it or made configurable. If new data point classified as outlier in both data sets, DCI will be marked as having anomalous value. If you want to generate event, you can use special threshold function "anomaly".

Best regards,
Victor

I changed map size logic a bit - now map will not be smaller than background image size if it's size set to default (0 values for width and height). This change will be included into upcoming release 5.0.5.

Best regards,
Victor

Fixed in upcoming 5.0.5. MIB compiler is now case-insensitive when selecting files by extension, and server ensures that MIB files upload via GUI have extension .mib.

Best regards,
Victor

I registered this as a bug:
https://track.radensolutions.com/issue/NX-2543

We will discuss internally what could be the best approach to fix it.

Best regards,
Victor

Could you get application log with stack trace for this exception? Actual log location depends on your Java application server.

Best regards,
Victor

Hi!
Just fixed that, fix will be in upcoming patch release 5.0.5.
Best regards,
Victor

I think I found the bug (it was really introduced in version 5). Fix will be included into upcoming patch release.

Best regards,
Victor

Server reads VLAN names from 1.3.6.1.2.1.17.7.1.4.3.1.1, then ports from 1.3.6.1.2.1.17.7.1.4.2.1.5 and 1.3.6.1.2.1.17.7.1.4.2.1.4, optionally also 1.3.6.1.2.1.17.7.1.4.3.1.2. For all those 3 tables index is VLAN ID and value is byte string, where each bit represent port membership in VLAN. You can check what values are actually returned. Below is description from Q-BRIDGE-MIB:

Each octet within this value specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port.  Thus, each port of the bridge is represented by a single bit within the value of this object.  If that bit has a value of '1' then that port is included in the set of ports; the port is not included if its bit has a value of '0'.

Also note that "port number" in this context is bridge port number (as obtained from 1.3.6.1.2.1.17.1.4.1.2), not interface index.

Best regards,
Victor