NetXMS Support Forum

Filipp,

Thank you for the clarification I appreciate it. I will look into using Execute.Script

This is internal mechanism used for delayed action execution from a EPP rule. You can configure action in EPP with a delay, e.g. in Maintenance Start rule and you'll see what params this scheduled task gets. Nothing strictly forbids from scheduling your own action executions, but since this is internal mechanism, params or anything may change in the future.
Minimal set of params looks like this:
action=1;event=51385
so you need to know ID of action (it's not visible in the GUI) and you need to specify some event.

More recommended way is to use Execute.Script, in this case param field is just script name from script library (and script parameters in bracket if these are needed).

Hello,

thank you very much. I'm sure something can be arranged, would this be about snmp access or something more.
In the meanwhile I've uploaded the info asked for, I've used nxsnmpwalk/get if that ok, data is from a fortiswitch 1024E.

thank you,
regards

There seems to be new task schedule options but not documentation on how to use them. I am curious about Execute.Action and if this allows us to run any existing actions we may have defined.


Thanks

We just published patch release 3 for version 6.1.

Changes since previous release:
-   Improved AI assistant access to DCI thresholds
-   Improved AI assistant access to alarms
-   AI assistant can initiate polls
-   Improved Qtech driver
-   Improved Cisco SB driver
-   Added driver for Lenovo switches
-   Added driver for BDCOM switches
-   Added driver for Bulat switches
-   Added driver for Origo switches
-   Server no longer attempts to retry agent package deployment after non-transient errors
-   Configurable page size in log viewer
-   Fixed small issues in SNMP printer template

Fixed issues:
-   #3202 (Problems with audit log filtering condition)
-   #3205 (Cropped login form on first run of nxmc on RPi)
-   #3230 (New and changed device drivers)
-   #3232 (Disabled push DCI continues accepting newly pushed data)
-   #3233 (Commands on Overview Windows are shown like gray rectangles)
-   #3234 (.apkg package fails to install under dash due to bash-only [[ ]])
-   #3235 (Display switch IP address in IP/MAC search results)
-   #3236 (Server name is shown in black in GUI header)
-   #3237 (Agent should verify installer signature when upgrading itself on Windows)
-   #3238 (Server crash on shutdown due to use-after-free in the notification channel worker thread)
-   #3239 (Filter values are not set when popping out log viewer)
-   #3240 (Windows agent breaks Store app launches by loading UsrClass.dat of logged-on users)
-   #3245 (AI assistant: add composite 'operational-status' triage tool)
-   #3246 (Threshold line not shown on chart if threshold value is bigger then maxint)
-   #3247 (Thresholds values should be inverted on chart if "invert values" is selected for a data source)
-   #3248 (Filter in Status Map dashboard element is slow)
-   #3250 (Agent tunnel bind fails with error 923 on OpenSSL 3.5.x)
-   #3253 (Empty f-string in NXSL script result in data stack underflow)
-   #3255 (Node without IP address and connected by agent tunnel only never marked as unreachable or down)
-   #3260 (C:\ in file manager incorrectly expanded to C:\Windows\system32)
-   #3267 (Script contents are deleted when dragging "Execute script" view from one docking area to another)
-   #3270 ("Do not show this message again" in "This DCI was added by instance discovery" dialog is not persisted across console restarts)
-   #3272 (No option to configure automatic column resize in DCI summary tables)
-   #3275 (Package deployment jobs should be cancelled if corresponding package is deleted from server)
-   #3276 (Send updates to Package deployment jobs view)
-   #3279 (Cannot upload file to server from nxmc if web server is running on Windows)

Перечитал внимательно изначальное сообщение с логами событий - там на ноде не возникало события SYS_AGENT_UNREACHABLE, a было только SYS_NODE_UNREACHABLE - сервер понимает что из-за отсутствия прокси нода недоступна и не генерит отдельные события про агента.
Поэтому таймер не заводился и поэтому ничто не ограничивало отправку нотификации когда пришло SYS_AGENT_OK

1. установить пакеты netxms-dbg и gdb
2. распаковать креш дамп:
apport-unpack /var/crash/YOUR_CRASH_FILE TARGET_DIRECTORY
3. перейти в эту директорию
cd TARGET_DIRECTORY
4. запустить gdb
gdb /usr/bin/netxmsd CoreDump
5. в gdb дать команду
bt

и покажите вывод

Hi,

Is it possible that you could provide remote access to some lab fortiswitch so our developers could talk to it to improve the drivers?

Or at least please share output of
  snmpwalk -v2c -c <community> <switch_ip> 1.0.8802.1.1.2.1.3.7.1
  snmpwalk -v2c -c <community> <switch_ip> 1.3.6.1.2.1.17.1.4.1.2
  snmpwalk -v2c -c <community> <switch_ip> 1.3.6.1.2.1.2.2.1.2
  snmpget -v2c -c <community> <switch_ip> 1.3.6.1.2.1.1.2.0

What NetXMS version are you using?

Pls show screenshot of properties of a specific subnet in network discovery.

Do you use proxies in these zones or server has direct connectivity to nodes in these zones?

I've created tickets covering above-mentioned issues:


https://github.com/netxms/netxms/issues/3278
https://github.com/netxms/netxms/issues/3277
https://github.com/netxms/netxms/issues/3276