NetXMS Support Forum

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

We finally released NetXMS version 4.2 (build number 4.2.395)!

Highlights of this release are context dashboards, improved OSPF topology discovery, port forwarding in object tools, measurement unit support in DCI, and almost complete new UI. Full change log is following:

- Context dashboards
- Out of the box access to OSPF information on routers
- Automatic OSPF topology maps
- TCP port forwarding for object tools of type "local command" and "URL"
- "Spread" operation for arrays in NXSL
- New methods executeAgentCommand and executeAgentCommandWithOutput in NXSL class "Node"
- Simplified data collection configuration for MQTT sources
- Notification channel driver for MQTT
- Automatic binding on configuration poll works again (but can be switched off in configuration)
- Added driver for Teltonika modems
- Improved database write performance on TimescaleDB and PostgreSQL
- Reduced memory consumption by server's background database writer
- Improved UI for two-factor authentication
- Impoved D-Link driver
- Agent saves backup copy of it's ID on file system
- Reworked general data collection object property page
- Added internal monitoring metrics for server certificate expiration date
- Built-in TFTP support
- Fixed network map issues with link duplicates on auto populated maps
- Fixed network map clone
- NXSL function JsonParse correctly handles JSON documents with array as top level element
- Custom error message can be provided in NXSL statement \"abort\"
- Operator "new" in NXSL can be omitted
- NXSL VM preloads module named \"stdlib\" if available
- Improved DCI format strings (usage of unit names and multipliers can be controlled)
- Agent manager view updates automatically on tunnel open or close
- Added Organizationally Unique Identifier lookup
- Fixed issues:
        NX-648 (DCI units and binary prefix)
        NX-702 (DCI option - "Store only if value changes")
        NX-708 (Add map option to make all labels non-transparent)
        NX-1279 (WebUI does not support ServerName/ServerColor options)
        NX-1474 (Execute server script - replace error message box with alternative way)
        NX-1527 (Option to hide DCIs from templates or created by instance discovery)
        NX-1560 (List of custom agent ports to be used during network discovery and configuration polls)
        NX-1632 (NetXMS agent service is disabled after installing netxms-agent deb package on Debian 9)
        NX-1809 (Center Map Background Image)
        NX-2044 (Object Tool to run against container)
        NX-2078 (Add the ability to specify an alias when creating an object)
        NX-2103 (Add ability to push values to Push DCIs from log file parser)
        NX-2140 (Export result of the package deployment to CSV)
        NX-2234 (With a drop-down menu with a choice of DCI metrics, swap the display of Description and Name (Parameter))
        NX-2237 (Add the ability to set height for passive elements in rack and use custom picture)
        NX-2251 (Add 'conflict' marker to inherited custom attributes)
        NX-2259 (Configurable server's SNMPv3 engine ID)
        NX-2261 (Access to Mikrotik metrics via network driver metrics)
        NX-2266 (Add agent metric similar to System.IO.Devices but including sub-devices)
        NX-2273 (2FA method can't be removed in user editor)
        NX-2274 (2FA - unable to add failed method in user editor - it's silently ignored)
        NX-2281 (Action message should be multiline field)
        NX-2288 (External parameter redirect issue on Ubuntu 22.04 LTS)
        NX-2302 (NXSL function PollerTrace is not working in template auto-apply poll)
        NX-2304 (Improved script execution options for nxadm)
        NX-2306 (Node configuration poll don't update information about interfaces type)
        NX-2308 (LDAP user sync login error should be logged at lower level)
        NX-2309 (No scrolling or resize for ports part in VLAN view)

Best regards,
Victor

Looks like server incorrectly builds topology based on STP data. Could you please set sertver debug level to 6 for the tags poll.topology and topology.*, run topology polls on both switches, and provide server log file part for the duration of the poll?

Best regards,
Victor

I suppose you can query timescale directly. Data dictionary can be accessed here: https://www.netxms.org/documentation/datadictionary/
You are interested in table idata_sc_default (or view idata), and likely object_properties, items, and nodes.

Best regards,
Victor

Theoretically object label decorators could be switched off. Go to File -> Preferences -> Workbench -> Appearance -> Label Decorators and make sure that "NetXMS Objects Decorator" is on (see screenshot).

Best regards,
Victor

Please check if upcoming 4.2 will work better - I've fixed one bug in Juniper driver. If it won't help I'll keep investigating it.

Best regards,
Victor

Hello!

Could you please provide result of SNMP walk on the following OIDs:

.1.3.6.1.4.1.2636.3.48.1.3.1.1.2
.1.3.6.1.4.1.2636.3.40.1.5.1.5.1
.1.3.6.1.4.1.2636.3.40.1.5.1.7.1
.1.3.6.1.2.1.17.7.1.4.3.1.1
.1.3.6.1.2.1.17.7.1.4.3.1.2
.1.3.6.1.2.1.17.7.1.4.2.1.4

Best regards,
Victor

We' re at Gitex, Dubai, as we're writing this. Are you planning on being here too? Come to our stand (we' re exhibiting on Latvia' s national stand in Hall 2) and let's catch up!

Hi,

something like this:
result = "";
for(i = 0; i < 8; i += 2)
{
  if (result->length > 0)
      result .= ".";
  result .= x2d($1[i : i + 2]);
}
return result;

This script assumes that 8 hex digits passed as input.

Best regards,
Victor

Do you get exception in web or desktop UI? Please find console log (for desktop it is in your home directory in .nxmc/data/.metadata/.log) and post it here.

Best regards,
Victor

Hi,

if database is external to the server, then yes, the only thing you need is to point new server to existing database. If database is on the same machine, and you plan to use new database, then database migration will help. Search the forum for "nxdbmgr migrate" - you should get few topics regarding database migration.

Best regards,
Victor