NetXMS Support Forum

Hi,

I will take a look at it in the next few days. Will you be able to run test build to verify changes to Jira connector?

Best regards,
Victor

I've added processing of FDB record status 6 - next patch release should process them in a same way as status 3 (dynamic).

Best regards,
Victor

I probably do not completely understand what the issue is. Configuration looks correct, you set "Name" column as instance column, not an "Index". But it should work both ways.

You should create local SQL account. It should be also possible to login with the same AD user NetXMS agent runs under (in that case you should specify * as login name and password is not needed). 

Best regards,
Victor

Hi,

can you show exact errors you are getting?

Best regards,
Victor

Can you check if you actually have tables maintenance_journal and maintenance_journal_v43_9, and if table maintenance_journal is a hypertable?

If you are not using maintenance journal functionality you can safely ignore this error, just make sure that hypertable maintenance_journal exists.

Best regards,
Victor

Hi,

are you using TimescaleDB?

Best regards,
Victor

We just published patch release 5 for version 4.3! Changes since previous patch release:

- Fixed bug in X.509 certificate subject and issuer decoding
- Agent tunnel listener will not start if server certificate is not loaded
- Fixed WEB service configuration import with multiple headers
- Fixed login issues in new web UI
- Small fixes and improvements in new management client application
Fixed issues:
   - NX-2272 (Session is not closed if user cancel 2FA auth initialization)
   - NX-2276 (Warn user when adding too wide mask to active discovery)
   - NX-2388 (Modify default templates - filesystem with type "ahafs" should be excluded from discovery)
   - NX-2404 (Integer division by zero in NXSL crashes server)
   - NX-2406 (Entering maintenance mode on cluster does not trigger maintenance mode on nodes within cluster)

I just fixed certificate subject parsing, fix will be included into next release.

Best regards,
Victor

Hi!

It could be related to LLDPv2 MIB support that we have added in 4.3. Could you please check if device responds to OID .1.3.111.2.802.1.1.13.1.3.2.0? If yes, could you provide result of SNMP walk on .1.3.111.2.802.1.1.13.1.4.1.1 and .1.0.8802.1.1.2.1.4.1.1?

Best regards,
Victor

So H3C returns non-standard value 6 for dot1qTpFdbStatus. Interestingly they don't mention this value even in their own documentation on Q-Bridge-MIB (found it here: https://www.h3c.com/en/d_202211/1719268_294551_0.htm).
Can you please explain what is the difference between "secure" and "learned" state?

We just published patch release 4 for version 4.3. Changes since previous patch release:

- Fixed bug in ICMP ping implementation introduced in 4.3.3
- Added agent configuration option for setting file mode creation mask (umask)
- Bundled SQLite updated to version 3.41.2
- Multiple fixes and improvements in new management client application
- Fixed issues:
   - NX-2137 (File delivery policy times out of big files when saved)
   - NX-2386 (Object Category custom node icon covers object browser status icon)
   - NX-2395 (Output of PATCH Web Service call is ignored)
   - NX-2396 (Web Service Definition timeout not displayed correctly)

Best regards,
Victor

Hi,
could you please share SNMP walk output on .1.3.6.1.2.1.17.7.1.2.2.1?
Best regards,
Victor

Multiple proxies within one zone intended for load balancing and HA - so all proxy nodes should be able to communicate with all nodes within zone. Server will distribute load between proxy nodes, and yes, this process is not subnet-aware (and is not intended to be).
If two subnets you have are actually in two different locations, you can split them into separate zones and assign correct proxies.
Overriding proxy on subnet level can be implemented relatively easy if load balancing and HA functionality is not required - i.e. only one proxy set on a subnet, it overrides any zone setting, and if this proxy is not functioning, communication with the subnet s lost. Replicating full zone proxy functionality on subnet level will significantly increase complexity of necessary changes, and in my opinion will be unnecessary duplication of functionality that is already exist.

Best regards,
Victor

Hi,

from the dump it looks like bug within SQLite. I updated bundled SQLite to latest version (3.41.2) - if this will not help, we will need to investigate further.
It also worth trying to use matching agent package from deb repository - it will have dependence on SQLite version built for that particular distribution.

Best regards,
Victor