NetXMS Support Forum

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

Hello everyone!

We are making a new (unrelated to NetXMS) SaaS product Textok (https://textok.com/). It's on Product Hunt today — 
https://www.producthunt.com/posts/textok-2. We will be grateful for your upvotes!

Best regards,
Victor

We just published patch release 4 for version 5.0. Changes since patch release 3 are following:

- New SNMP DCI option "Interpret raw value as IPv6 address"
- Added driver for GE MDS Orbit devices
- Added driver for EtherWan switches
- Added driver for Siemens RuggedCom switches
- Mikrotik driver reports RSSI for wireless clients
- RSSI is displayed in "Wireless Stations" view
- Added "move object" item to object context menu
- Optional context selector for dashboards in dashboard perspective
- Seed node propery page removed for custom network maps
- Fixed server crash when accessing alarm category list from NXSL
- Fixed drawing issues of line charts with logarithmic scale
- Fixed incorrect line numbers in NXSL error messages
- Fixed bug in "Go to object" action in UI
- Fixed bug in D-Link driver
- Fixed interface utilization information sychronization
- Fixed network map color source selection
- Fixed historical line chart pop-out on web
- Fixed save of network map object position
- Fixed tables display glitch on Windows
- Fixed data type of configuration variable "Objects.NetworkMaps.UpdateInterval"
- Fixed issues:
   - NX-2489 (Read list of performance counters only when needed)
   - NX-2536 (SNMP DCI "interpret raw value as MAC address" does not support EUI-64)
   - NX-2537 (Double links on maps)

Hi,

do you refer to old or new client? In new client you can change status colors via custom theme and it seems to work (at least in version 5.0, I didn't check 4.5, but I don't remember changes in that area between 4.5 and 5.0).

Best regards,
Victor

Does legacy client experience same issue? I was under impression that this is specific to new client.

Best regards,
Victor

Hello!
I suppose it is about network maps with geo map as background layer?  Because there is also pure geo map view, which will show location of objects based on their location property, but it will not show any links, data, etc.
Best regards,
Victor

Hi,

is this:
String::right("Test", 2);
really in documentation somewhere? Or some text/example that suggests this is the correct way? Because it is incorrect and never was.
Module::function syntax is supported since 4.x, and some functions were indeed moved to system packages in version 5, but there never been module "String".

Best regards,
Victor

We have published patch release 3 for version 5.0. It fixes yet another (hopefully last one!) bug in database upgrade procedure, as well as few other less important issues. Full change log is following:

- Notification channel driver "Shell" escapes single quote character during exec-type command line expansion
- Priority inclusion rules in UI element filter
- Macro expansion in API call executeLibraryScript works for all object classes
- Improved handling of large number of simultaneous ICMP ping requests
- Fixed bug in database upgrade procedure
- Fixed deadlock in web UI
- Fixed issues:
   - NX-2521 (ICMP.PacketLoss internal DCI collects 0 after server restart)
   - NX-2529 (Option to enable/disable Version Number on Web interface)

Windows server binaries for version 5.0.3 already in archive, we will update web site and publish deb packages during the day.

Best regards,
Victor

Windows server binaries for version 5.0.3 already in archive, we will update web site and publish deb packages during the day.

Best regards,
Victor