NetXMS Support Forum

Thank you for digging this! I just changed Juniper driver to use bridge port number instead of ifIndex to identify ports in VLANs. Fix will be included into release 4.3.1. If you want to test it before release I can provide intermediate build, just let me know what platform you are using.

Best regards,
Victor

Yes, we aware of it and will fix soon.

Best regards,
Victor

You cannot create SNMP transport because node object is not created yet. Currently community string used for discovery is not accessible to filtering script. Closest thing that you can do is to leave only one community string in network credentials and require SNMP support for newly discovered nodes. That way automatic discovery will only try that one community string, and devices that will not respond will not be marked as SNMP capable and will not pass filter. However, you will have to manually enter correct community string for devices that added manually and use different community string.

Best regards,
Victor

Correct, old subagent (portcheck) set host header and SNI separately. I just fixed netsvc in development branch so it use correct host name when called for network service object poll or via compatibility metrics, next patch release will contain fix.

Best regards,
Victor

Quote from: 2b2bff on January 27, 2023, 11:38:36 AMThanks a lot.

Sadly the DB upgrade for MSSQL fails because event_cfg.description is a TEXT column and the upgrade script compares it with VARCHAR in the WHERE clause.
Simple fix - please change all TEXT columns to VARCHAR(MAX). TEXT has been deprecated long time ago...
https://learn.microsoft.com/en-us/sql/t-sql/data-types/ntext-text-and-image-transact-sql

Cheers

Upgrade procedure is fixed in development branch, fix will be part of upcoming patch release 4.3.1. In version 4.4 we will also switch to varchar(max) from text.

Best regards,
Victor

Hi!

I was unable to reproduce telnet service check issue. "[  136] INT32      2" in response indicates connection problem, so agent was unable to connect to given address and port. Could it be that address is a loopback?

For HTTPS checks - it could be certificate issue. Unfortunately agent do not log exact failure reason (I fixed it already in development branch). Try to do same request with curl from command line (using URL exactly as logged - https://x.x.x.x:443/api/status) - will you get any errors?

Best regards,
Victor

If you are on Windows then I recommend to switch to version 4.3 - web UI installer for Windows also contains API which will be accessible under /api path. Starting with version 4.3 we also deploy complete Jetty server so you'll be able to properly setup SSL, etc.

Best regards,
Victor

Hi!

NetXMS server do walk on .1.3.6.1.4.1.2636.3.40.1.5.1.7.1.5 to collect port membership (but result should be the same as walking on .1.3.6.1.4.1.2636.3.40.1.5.1.7.1.3).

In your data port ge-0/1/3 has ifIndex=552, but I don't see it in VLAN port table (there should be entry with OID SNMPv2-SMI::enterprises.2636.3.40.1.5.1.7.1.3.nnn.552, where nnn is index in VLAN table).

Same for ge-0/0/16: it has ifIndex=534, and it has multiple entries in VLAN port table:
SNMPv2-SMI::enterprises.2636.3.40.1.5.1.7.1.3.2.534 = INTEGER: 3
SNMPv2-SMI::enterprises.2636.3.40.1.5.1.7.1.3.5.534 = INTEGER: 3
SNMPv2-SMI::enterprises.2636.3.40.1.5.1.7.1.3.14.534 = INTEGER: 3
SNMPv2-SMI::enterprises.2636.3.40.1.5.1.7.1.3.16.534 = INTEGER: 3
SNMPv2-SMI::enterprises.2636.3.40.1.5.1.7.1.3.17.534 = INTEGER: 3
SNMPv2-SMI::enterprises.2636.3.40.1.5.1.7.1.3.18.534 = INTEGER: 3
SNMPv2-SMI::enterprises.2636.3.40.1.5.1.7.1.3.23.534 = INTEGER: 3
which corresponds to VLANs CP-1, SSO-3, SSO-12, SSO-UnautenthicatedDevice, Example1, Example2, n9-2.

If this does not correspond to actual device configuration then it looks like device reports incorrect information via SNMP.

Best regards,
Victor

We are coming to Fosdem! If you're also visiting the event or are in Brussels on the 4-5 February, ping us. Let's meet (have a beer or a muffin) and talk about what's new in NetXMS and the open-source industry in general.

I'd suggest to upgrade to 4.3 if possible - it has improved algorithm for thread pool resizing. In any case you can try to increase min and max size for main thread pool, to say 64 (can be 16 for 4.3, it should expand it aggressively if needed) and 512.

Best regards,
Victor

Hi!

Can you provide agent log on startup?

Best regards,
Victor

Both old and new should work correctly in 4.3. Please let us know if you will still have problems.

Best regards,
Victor

It was added in 4.3 which is just published.

Best regards,
Victor

SDK как такового нет (исходники продукта по сути и есть SDK), проще всего взять какой-то существующий драйвер за основу. Напишите под какую платформу хотите делать сборку, я помогу настроить среду для компиляции.
Самый простой драйвер - dummy (он ничего не делает, только пишет сообщение в лог): https://github.com/netxms/netxms/tree/master/src/ncdrivers/dummy

We're excited to announce the release of version 4.3 of NetXMS! This new version brings a bunch of new features and improvements, including:

- Python-style format strings in NXSL;
- Inline action scripts in EPP;
- The ability to set and delete custom attributes in EPP rules;
- Column display names in object queries can be set using column metadata;
- New agent metrics for file type and file content;
- A brand new "File Monitor" dashboard element.

We've also fixed bunch of bugs and made several other improvements, like correctly reading LLDP information from devices that only support LLDP-V2 MIB and improving object queries.

We've also made a slight change to our versioning system. Similar to before, releases are defined by a major and minor version (like 4.3 in this case) and all components with the same major.minor version number are guaranteed to work together. However, we're now hiding the build number for regular releases. The third number in the version will indicate an official patch release, with 0 being the initial release for that version. Any builds in between official releases will be denoted by a fourth number, which indicates the build number after the patch release.

Full change log can be found here: https://netxms.com/release-notes

Thanks,
The NetXMS Team