NetXMS Support Forum

Added it as feature request: https://track.radensolutions.com/issue/NX-1931

Best regards,
Victor

Quote from: TOLeg on August 11, 2020, 07:15:15 AM
То что нужно. - GetDCIValue($node, FindDCIByName($node, "DCI_NAME"))

Небольшой комментарий - два вложенных вызова можно упростить до GetDCIValueByName($node, "DCI_NAME")

Попробуйте обновить агент до версии 3.4.310 и поменять кодировку скрипта на UTF-8.

Hi,

at first glance it looks like issue with data source plugin. Somebody from the team will take a look.

Best regards,
Victor

Hi all!

NetXMS 3.4 patch release 3 is published. Changes since previous release:

- Added driver for SAF Tehnika Integra devices
- Improved handling of UNICODE characters in external parameter output on Windows
- Fixed UI crash when object query dashboard element is incorrectly configured
- Fixed topology display issues in UI
- Fixed issues:
        NX-1916 (Device could be marked as supporting ENTITY MIB when it is in fact not supported)
        NX-1920 (Save deleted DCIs between restarts to delete it's data on housekeeper after restart)
        NX-1921 (SQL query failed into alarm_events: 22001 ERROR: value too long for type character varying(2000))
        NX-1922 (Spelling mistakes in Java API)

Best regards,
Victor

Hi,

they match. If %6 expands to empty string it means that "instance" attributre in DCI is not set. Are those DCIs created by instance discovery or manually? If manually, did you set "instance" field?

Best regards,
Victor

For reference, for LLDP based topology working correctly with Mikrotik router software should be at least 6.46 (so current LTS version will not work).

Best regards,
Victor

/var/lib/tomcat8/webapps is where application is deployed. But working directories for applications are in /var/lib/tomcat9/work/Catalina/localhost - try to delete them.

Best regards,
Victor

Hi,

it's not a step-by-step guide, but basic information is available in administration manual: https://www.netxms.org/documentation/adminguide/ssh-monitoring.html

Best regards,
Victor

Try to change DCI data type to "String" and request history - will it show something?

Best regards,
Victor

Hi,

we are using LDAP client provided by Windows (Wldap32.dll), so I suppose it has to use Windows certificate store for root CA certificate. There are no mention in documentation about any specific requirements for LDAP client to work over TLS. Are you sure that your LDAP server picks up correct certificate and actually supports secure connection? As I remember it is quite tricky process to setup Windows LDAP server for TLS. Did you check LDPAS connection with other tools (ldp.exe for example)?

Best regards,
Victor

Hi,

try to set debug level 6 for tag obj.netmap and check server log if objects and/or links are actually removed or added when layout changes.

Best regards,
Victor

Response time for community support is really not guaranteed, and depends on multiple factors, mostly complexity of the issue and available resources. We always try to do our best but we cannot cannot promise fast handling for all issues. This bug will be looked at when someone from the team will have time.

Best regards,
Victor

Sometimes it helps to undeploy application, stop Tomcat, clean Tomcat's working directory, and deploy application again.

Best regards,
Victor

Hi,

syntax for accessing event parameters within filter script is different from macro expansion. You can access event object via global variable $event. It has attribute "parameters" which is array of all event parameters. You can either use this attribute or you can use expandString method to expand standard macros. So your filter script could be in one of two forms:


return $event->parameters[6] ilike "C:\\";


or


return $event->expandString("%6") ilike "C:\\";


Best regards,
Victor