News:

We really need your input in this questionnaire

Main Menu

Recent posts

#31
General Support / Need Help - NetXMS 6.1.3 Alarm...
Last post by justrest - June 09, 2026, 03:26:24 AM
Thank you so much for taking the time to reply to my post and offer your help!

I'm trying to set up reliable alarm and recovery notifications for my monitoring setup, and I was hoping you could advise me on the best way to achieve this using **native EPP rule configurations** in NetXMS 6.1.3, without needing to write custom NXSL scripts.

The core functionality I need is:
1.  **Alarm deduplication**: Only send one notification for the same issue within a 2-hour window, to avoid spamming
2.  **Proper alarm-recovery pairing**: Ensure recovery notifications are only sent for issues that actually triggered an alarm earlier
3.  **Targeted device filtering**: Only send notifications for devices I've marked as "focused" (not all devices in the system)

I did try writing my own NXSL scripts to implement this, but I got stuck on one critical part: I couldn't figure out how to design a **universal key value that works across all types of events and alarms** (similar to what I've seen others refer to as an "alarm key") to properly link alarm events with their corresponding recovery events. Without this, I can't reliably ensure that a recovery notification is only sent if an alarm notification was actually sent for that specific issue first.

I've looked through the EPP rule settings but I'm not sure how to combine these three requirements correctly using the built-in options. Could you walk me through how to configure the EPP rules to achieve this, or point me to the relevant documentation sections?

Thanks again for your time and generosity.

#32
General Support / Re: Logparser Windows Event lo...
Last post by DW2 - June 08, 2026, 06:59:38 PM
Hi, thank you for your answer - sorry i was on holidays.

Now i tested it again:

406 is creating a warning - this is working
251 should trigger a Critical warning - i have triggers for: 251 without level, 251 with Level 1 and 2 and 3

But nothing with 251 is working. 406 is triggering fine everytime.
#33
Сервер стартанул, 3 дня в логи спамило записями по синхронизации и удалению выполненных задач распространения пакетов и таки завелся. С версии 6.1.1 что-то изменилось в последовательности старта? Файлы логов с момента запуска до старта сервера я сохранил, если нужно - могу скинуть. Прикрепил сюда момент старта сервера
#34
Announcements / Re: NetXMS 6.1 patch release 2
Last post by lhpaladin - June 06, 2026, 03:19:43 AM
The Portuguese translation is much better now.
Congratulations to everyone!
#35
General Support / Integration of Oxidized with N...
Last post by lhpaladin - June 05, 2026, 05:35:58 AM
Hi,

I'm trying to integrate NetXMS with Oxidized, but it seems the module isn't loading completely.

Adding the settings to the netxmsd.conf file results in the following message during system initialization:

[backup] Network device backup interface is not available
The URL and credential settings are all correct.

Thank you for your attention.
#36
General Support / Server Initialization Errors -...
Last post by lhpaladin - June 05, 2026, 03:04:47 AM
Server Initialization Errors

I'm encountering some errors during initialization. In principle, they don't prevent the system from functioning.

[snmp.mib] Failed to load MIB tree from /var/lib/netxms/netxms.cmib: Invalid or corrupted file data
The MIB compiles successfully on the frontend, but the MIB Explorer doesn't work. This message appears in the server logs during the MIB file compilation.

The second error is this:

[config] Configuration loading error: XML parser error in file ":memory:" at line 1 (no element found)
I can't identify the cause of this message, but it appears constantly.

Could someone offer some guidance on how to fix this?
#37
General Support / Re: Information about the 802....
Last post by lhpaladin - June 05, 2026, 02:28:54 AM
Quote from: Victor Kirhenshtein on May 16, 2026, 05:23:24 PMJust closed issue 3023 (former NX-2821) - will be part of release 6.2.0.
Thank you, Victor!
#38
Ага, т.е. полностью он так и не стартанул - не было таких записей в логах за сутки от перезапуска
На 4-ом дебаге запустил
Node::syncDataCollectionWithAgent:
Node::syncDataCollectionWithAgent:
Node::syncDataCollectionWithAgent:
Node::syncDataCollectionWithAgent:
по нодам идет.
Причем как минимум некоторые ноды не по одному разу повторяются
Что имеет смысл проверить? На конкретном дебаг уровне мб
Грешил на алерты - ранее все скопом падало, но нет, в базе их всего 87 было
#39
General Support / Changing MAC address
Last post by WSallade - June 03, 2026, 08:15:38 PM
In the v6.0 release notes, fixed issues there is:

NX-2437 (Ability to change MAC address on an interface)

How exactly would I do this?  I have a couple old devices with interface MACs coming in as 00:00:00:00:00:00 and would like to set manually.
#40
Проверю. Отпишу