NetXMS Support Forum

Hi!

scilexerd.lib is a debug version of Scintilla lexer library. Look at Scintilla web site http://scintilla.org/ for more information/downloads/etc.

Best regards,
Victor

Hello all!

NetXMS version 0.2.23 is released.

Changes from previous release:

- Implemented event forwarding between NetXMS servers
- Added new subagent LOGWATCH for log monitoring
- Implemented syslog message monitoring on built-in syslog server
- New agent configuration parameter: WaitForProcess
- Number of consecutive polls can be specified for "last value" threshold
- Implemented "Clear DCI data" function
- Management packs improved
- Usage of ifXTable for interface naming made configurable
- NXSL: added new attribute "status" for node objects
- Implemented resending of failed e-mails
- Database checking procedure improved
- Windows console:
   - Added support for negative values on graphs
   - Implemented editing of predefned graphs
   - Implemented cut/copy/paste in event policy editor
- Java API introduced
- Fixed issues: #31, #74, #146, #218, #228, #235, #236, #237, #238

Best regards,
Victor

Файлы уже лежат на web-сервере. Надо их подписать, посчитать MD5, и тогда будет официальный анонс. Самые нетерпеливые могут скачивать неподписанные файлы:

https://www.netxms.org/download/netxms-0.2.23.exe
https://www.netxms.org/download/netxms-0.2.23.tar.gz

Hello!

Actually, there are requirements page and step-by-step installation instruction for Windows inside NetXMS Installation Guide - https://www.netxms.org/documentation/netxms_install_guide.pdf.

In fact, list of requirements for NetXMS server on Windows platform is very short:

1. x86 or x64 machine with at least 512MB RAM (1GB if you wish to monitor large number of nodes; + additional memory if database engine will be on same machine). NetXMS server is not very RAM-consuming - for example, server monitoring of 150 nodes takes about 90MB of RAM.
2. Windows 2000, XP, Vista, or 2003 operating system. Should run on 2008 as well, but I have not tested it.
3. Compatible SQL database, either local or remote. Currently supported databases:

MS SQL - 2000 and 2005
Oracle
PostgreSQL
MySQL
SQLite (not recommended for production environment, only for testing)

All additional necessary components are included into Windows installation package.

Best regards,
Victor

Quote from: isherim on December 10, 2008, 05:06:41 PM
т.е. с параметрами по умолчанию один потерянный пакет дает 25% потерь за минуту?

да

Hi!

1. Looks like inconsistent source package. I will publish 0.2.23 tomorrow, try these sources.

2. Looks like you don't have scilexer.lib in nxlexer project library list.

3. Looks like you have sapi.lib incompatible with VC6. Try to find compatible one.

Best regards,
Victor

Hi!

You need flex version 2.5.33.

Best regards,
Victor

По умолчанию PING subagent посылает 4 пакета в минуту, размером 46 байт и с тайм-аутом 3 секунды. Процент потерь рассчитывается за минуту. Количество пакетов в минуту можно изменить параметром PacketRate, а размер - параметром DefaultPacketSize. Кроме того, для каждого проверяемого хоста можно настроить свой размер пакета, указав его после адреса и имени. Тайм-аут меняется параметром Timeout, задается в миллисекундах.

Пример: посылаем 10 пакетов в минуту, для хоста 10.0.0.2 устанавливаем размер пакета 500 байт, для всех остальных - 100, тайм-аут полторы секунды:


*PING
PacketRate = 10
DefaultPacketSize = 100
Timeout = 1500
Target = 10.0.0.1:host1
Target = 10.0.0.2:host2:500
Target = 10.0.0.3:host3


Quote from: czimmermann on December 10, 2008, 01:07:17 AM
I was able to follow your steps and monitor one drive successfully. Is it possible to monitor multiple drives in one Data Collection Item? Such as if you put C:,D: in the argument section of the Parameters would it monitor the C and D drives to 75% capacity? Or is there a command to monitor all possible drives in the same DCI?

You can create DCI which summarizes values of two DCIs via transformation script.

Quote from: czimmermann on December 10, 2008, 01:07:17 AM
Is there a way to send a DCI to multiple but not all nodes? I need this exact DCI to go to about 23.

You can use templates for this. Create template with required DCIs, and then apply it to nodes you wish these DCIs to appear on. Any future changes in template will also reflects on nodes this template applies to. To simplify DCI creation in template, you can create empty template, open data collection configuration fr node where you have already configured DCIs, and then move DCIs to template by right-click and selecting "Convert to template item".

Best regards,
Victor

All these Crypt functions are from advapi32.dll. Ensure that advapi32.lib is in library list for libnetxms and that you are using latest Windows Platform SDK.

Best regards,
Victor

Hi!

Did you compile crypto.cpp as part of libnetxms?

Best regards,
Victor

Синтаксически скрипт правильный. Проблема в том, что в текущей версии статус узла через аттрибуты недоступен. Я добавил соответствующий атрибут, он называется status, и в 0.2.23 такой скрипт можно будет использовать:

sub main()
{
   return ($node->status == 4) ? 0 : 1;
}

Еще один комментарий - а если у узла уже будет статус CRITICAL, например из-за того, что один из интерфейсов в статусе CRITICAL? Тогда и первое письмо не будет отослано. Для таких задач можно использовать ситуации - при получении трапа от упса выставлять атрибут соответствующей ситуации в 1, а в скрипте проверять состояние этого атрибута.

P.S. Маленький пример использования ситуаций (на английском) - https://www.netxms.org/forum/index.php/topic,321.0.html

Most likely you should have OpenSSL compiled with VC6. You can get headers and libs that I use at https://www.netxms.org/download/dev/openssl-0.9.8b-vc6.tar.gz.

Best regards,
Victor

Hi all!

I have moved all topics related to compilation of NetXMS for Windows platform to the development board, because compilation is not a part of normal installation process on Windows. From now on, please post all such topics into appropriate development board.

Best regards,
Victor

Hi!

Server connects to agent, by default using port 4700.

It should be safe - first, agent accepts connection only for explicitly listed IP addresses (usually you will have only one address - of your NetXMS server). In addition, you can configure NetXMS to use encrypted connections between server and agent, and configure shared secret authentication on agent, so it will acccept connections not only from specific addressm but also only if valid shared secret was provided.

Best regards,
Victor