NetXMS Support Forum

Hello!

No, it's not possible (without C programming). I'll add this to feature requests.
Currently, you can start actions when new node added to the system (by handling SYS_NODE_ADDED event), but to change node attributes from action, you have to write your own C (or Java) program which will access NetXMS server via client API.
I'll add appropriate functions to NXSL so you will be able update object attributes from internal scripts.

Best regards,
Victor

Sintaksis vigljadit pravil'nim. A v loge agenta est' chto-nibud'?

A versija konsoli s versiej servera sovpadaet? poskol'ku na drugih kompah vse v porjadke, to problema ili v samoj konsoli, ili v nesovmestimosti versij. Esche prishlite esli mozno 2 screenshota - tam gde vse horosho, i tam gde problemi.

Hello!

You should use == for compare operation. = is an assignment operation.

For example:


a = 1


means "assign value 1 to variable a"

and


a == 1


means "test if variable's value is 1".

Second error is that $node variable is an object, and you need to compare it's name attribute. To access it, use


$node->name


And compare always returns 1 or 0, so you can omit ? 1 : 0 part and simply use


left($node->name,6) == "FG100A"


So, correct script will looks like


sub main()
{
   return left($node->name, 6) == "FG100A";
}



Best regards,
Victor

Hi all!

I think that we can consider this project as abandoned.

As for better network maps, we are now actively working on completely new management console, which is based on Eclipse platform and written in Java. It will have network map plugin, which should be better. And, if someone has experience in Java/Eclipse development, you are welcome to develop plugins for this new console.

Best regards,
Victor

It's not very difficult - mostly UI change. Also, for escalation you can simply replace alarms (but this depends on how you create your alarm keys). Alarm key is also used by server to identify duplicate alarms, so if you generate new alarm with same key as existing one, server will update all fields in existing alarm except creation time, and increase repeat count.

Best regards,
Victor

Zavel issue v bugtracker chtobi ne zabit' ispravit'. Spasibo

https://www.netxms.org/bugtrack/view.php?id=254

Quote from: jdl on May 11, 2009, 06:12:41 PM
By the way, is there no way to define "terminate alarm" while keeping the message in the event list?
So having access to both "terminate alarms" and "Generate new alarm" sections?

I'm not sure I understand correctly - you wish to terminate alarm and then generate new alarm immediately? Then you have to define two rules with identical matching part, first will terminate alarm, and second create new alarm.

Best regards,
Victor

Quote from: jdl on May 11, 2009, 05:55:43 PM
In user manual, last page lists all macros available for building key and message in event processing.
Is there a way to do some regexp in the field where we define the pattern for terminating several alarms?

A kind of EVENT_ERROR_(.*) or event EVENT_[ERROR|WARNING]_%i etc.

No, it is not possible (but idea is very good, I'll try not to forget it and implement). Currently you have to define multiple rules to terminate each kind of alarms.

Best regards,
Victor

Sorry, zabegalsja Dobav'te pozalujsta parametri


CreateCrashDumps = yes
DumpDirectory = <some_dir>


v netxmsd.conf. Kogda on sledujuschij raz upadet, v kataloge ukazannom kak DumpDirectory pojavjatsja faili .mdmp i .info - prishlite ih na [email protected]. Budu razbiratsja.

Quote from: Alex on May 07, 2009, 08:42:29 AM

Quote from: Victor Kirhenshtein on May 05, 2009, 10:14:24 PM
Еще один вариант - в 0.2.25 появился экспорт бызы

А можно подробности? Где чего и как?

Все делается через nxdbmgr. И при импорте, и при экспорте сервер должен быть остановлен.

Для экспорта базы надо запустить


nxdbmgr export <file>


nxdbmgr создаст файл, в котором будет содержаться вся информация из базы.


Для импорта надо запустить


nxdbmgr import <file>


nxdbmgr очистит существующую базу и зальет информацию из файла.

Версии форматов при импорте и экспорте должны совпадать, а сами базы могут быть разными, т.е. импорт/экспорт базы можно использовать для миграции, скажем, с MySQL на Oracle.

Для фильтрации по этим полям в тэге <rule> можно указывать следующие тэги:

<id>event code range</id> - код события или диапазон, например <id>10</id> или <id>21-28</id>

<level>severity level</level> - уровень серьезности (тип) события. Здесь надо указывать маскуб составляемую из следующих значений:

1 error
2 warning
4 information
8 audit success
16 audit failure

если требуется несколько уровней, то эти значения суммируются - например для соответствия уровням error и information надо использовать значение 5 (1 + 4).

<source>event source pattern</source> - шаблон для имени источника события. Это не регулярное выражение, а именно шаблон, где можно использовать символы * и ?. Например, для всех имен, начинающихся на VNC, надо использовать VNC*.

Вот вроде и все.

It is possible that nxagentd.exe from previous version is in use by operating system. For example, if you have event log opened, it will use nxagentd.exe because it contains message texts. Try to close all mmc instances.

Best regards,
Victor

Da, moja oshibka. Unmanaged voobschem-to i dumalos' kak priznak togo, chto sostojanie hosta nas ne interesuet, poetomu vse sobitija dlja nego ne prohodjat cherez event policy. Nado budet sdelat' atribut "external node" - togda vse budet logichno - esli noda pomechena kak external, to server ee ne monitorit, no prinimaet sobitija i processit ih kak nado. Nu i ee toze mozno delat' unmanaged, chto vikljuchaet priem sobitij do teh por, poka ne vernit v sostojanie managed.

Hello!

Most likely node with given IP address already exist in NetXMS database. Check Entire Network tree - it should be under appropriate subnet, or try search by IP adress (press Ctrl+F in object browser, and type ip:ip_address in search string).

Best regards,
Victor