NetXMS Support Forum

Hi!

Not automatically with agent's config. In version 1.1.x, you can put file on NetXMS server (into C:\NetXMS\var\files in default Windows installation), and then in console select "Upload file" for single node or container.

In the next versions I plan to implement feature similar to HP Operations "instrumentation", which will allow to deploy required scripts and configs automatically.

Best regards,
Victor

Hi!

Currently you have to search the forum. I'll try to summarize it's features later on and put into manual, but right now I don't have time for that.

Best regards,
Victor

Hi!

Zone in NetXMS is a completely separate network with possibly overlapping IP addresses. Typical example is service provider with multiple client sites, and each site has internal network 192.168.1.0/24. You can use different proxies to access servers and devices in each site, but without telling NetXMS server in some way that those networks are actually different networks, IP topology will be incorrect. With zoning enabled, you can put each remote site in separate zone, and NetXMS server will know that those networks are different networks, even if they have same IP address. See also this topic: https://www.netxms.org/forum/configuration/is-it-possible-to-have-two-networks-with-same-ip-subnet/.

Best regards,
Victor

Hi!

Unfortunately there are no built-in tolls for initial agent deployment. For Windows, you can slightly simplify agent deployment by using automated (silent) install mode, activated by /VERYSILENT command line option of agent installer. All possible command line options for installer described in installation manual. I'm not a big expert in WIndows domain administration, but probably you can use group policies to distribute and install agent in unattended mode on domain computers.

Best regards,
Victor

P.S. See also https://www.netxms.org/forum/installation/how-to-configure-and-deploy-netxms-agent/

Ja sdelal SYS_NODE_DOWN bol'she dlja primera. A tak ja vizu tri sposoba:

1. monitorit' sostojanie processa netxmsd i tcp porta 4701, esli to ili drugoe ne v porjadke, vistavljat' isDown;
2. Sdelat' na lokal'nom agente vtorogo servera external parameter, kotorij dergaet server cherez kakoj-nibud' klientskij tool, naprimer nxalarm, i esli tot daet failure, to schitae, chto server ne rabotaet;
3. Sdelat' na udalenom servere external parameter, kotorij zapuskaet nxadm -c "show status", esli ne otrabotal - znachit server ne rabotaet.

Nu ili ob'edinit' vse tri dlja nadeznosti. S tochki zrenija event processing policy prosto dobavjatsja novie sobitija k pervim dvum pravilam.

Hi!

Finally, zoning is implemented in version 1.1.1.

Best regards,
Victor

В аттаче исправленный MIB. Проблема здесь была в том, что по RFC названия типов данных должны начинаться с большой буквы. Я переименовал rmxStatus в RmxStatus, и вроде теперь все хорошо.

Комментарий к картинкам:

1. Идем в меню View -> Situations, там создаем новый объект "Primary Server Down". Получаем картинку 1.
2. Идем в event processing policy, создаем два правила с Source=NETXMS-PRIMARY, event=SYS_NODE_DOWN, и Source=NETXMS-PRIMARY, event=SYS_NODE_UP. Для первого правила поле "Situation" редактируем как на картинке 2, для второго - как на картинке 3.
3. Создаем правило с единственным условием в виде скрипта:


s = FindSituation("Primary Server Down", "default");
if (s != NULL)
{
return (s->isDown == 1);
}
return false;


и флагом "Stop processing". Все 3 правила видны на картинке 4.

Надеюсь стало понятней

Выложил версию 1.1.1. Попробуйте ее поставить, надеюсь что эта проблема исчезнет.

Hi all!

NetXMS version 1.1.1 is out. Changes from previous release:

- Network device drivers introduced
- Added drivers for Avaya ERS switches
- Added driver for Cisco Catalyst 2900XL, 2950, and 3500XL series switches
- New threshold function: SUM
- New NXSL functions: SetCustomAttribute
- Added support for zoning (dividing network into independent parts with possibly overlapped address ranges)
- OpenStreetMap integration for geolocation display
- New MIBs added: CISCO-CLUSTER-MIB, CISCO-HSRP-EXT-MIB, CISCO-HSRP-MIB,
  CISCO-MAC-NOTIFICATION-MIB, CISCO-STACKMAKER-MIB, CISCO-STP-EXTENSIONS-MIB,
  CISCO-SWITCH-CGMP-MIB, CISCO-VLAN-MEMBERSHIP-MIB, EMBEDDED-NGX-MIB
- nxpush now supports node identification by DNS name or IP address
- Configurable dashboards introduced

Please note that this is a development branch and should not be using in production without thorough testing.

Best regards,
Victor

Да, можно. Надо на втором сервере настроить мониторинг состояния первого, сделать ситуацию (например "Primary Server Down") c атрибутом, обозначающим текущий статус основного сервера (например "isDown"), и добавить следующие правила:

1. Если основной сервер не доступен или на нем нет необходимых процессов, выставляем isDown для ситуации "Primary Server Down" в 1;
2. Если основной сервер снова работает, выставляем isDown для ситуации "Primary Server Down" в 0;
3. Здесь два варианта:
3а. В самом начале делаем правило, которое проверяет, равно ли isDown для ситуации "Primary Server Down" 0, и если да, то делает stop processing - таким образом фактически события не обрабатываются пока первый сервер работает;
3b. К каждому правилу для отсылки алертов добавляется доп. проверка на равенство isDown для ситуации "Primary Server Down" 1.

Vozmoznost' gruppovih izmenenij statusa skoro pojavitsja.

Karti teper' sdelani v vide ob'ektov - pojavilas' novaja vetka v object browser'e - Network Maps. Tam mozno sozdavat' ob'ekti kart. Zavtra ja planiruju vilozit' reliz 1.1.1 - tam pri upgrade bazi starie karti budut skonvertirovani v novij format.

Dobrij den'!

Ja ne ochen' ponjal, kakoj rezul'tat hotelos' poluchit'? Chto tolzno bilo proizojti s testovoj nodoj? Agenta na nej net - eto vidno iz stranichki summary.

Viktor

Thanks for the review! It's always worth to see how product looks for others.

Best regards,
Victor

Hi!

Run command


nxdbmgr.exe upgrade


It will upgrade your database schema.

Best regards,
Victor