NetXMS Support Forum

Hi!

You need to control communication with the site somehow, by pinging router for example. Then you can use situation objects to do manual event correlation. Also, if NetXMS server knows the whole route from itself to managed nodes and has all routers entered as managed nodes as well, it tries to do automatic event correlation based on network topology.

Best regards,
Victor

Hi!

I have two Debian Linux nodes called netxms-1 (10.0.0.11) and netxms-2 (10.0.0.12) with heartbeat and DRBD. Database engine is PostgreSQL, with database on shared disk. There are also virtual IP 10.0.0.10 used for client connection. Configuration files looks like following:

/etc/ha.d/ha.cf

keepalive 1
deadtime 5
warntime 3
initdead 20
bcast eth0
bcast eth1
auto_failback no
node netxms-1
node netxms-2
crm no


/etc/ha.d/haresources

netxms-1 IPaddr::10.0.0.10/24 drbddisk::netxmsdb Filesystem::/dev/drbd0::/postgresql::reiserfs postgresql-8.3 netxmsd


/etc/drbd.conf

global {
        usage-count no;
}

common {
        syncer {
                rate 10M;
        }
}

resource netxmsdb {
        protocol B;
        handlers {
                pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f";
                pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f";
                local-io-error "echo o > /proc/sysrq-trigger ; halt -f";
                # outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater -t 5";
        }

        startup {
                wfc-timeout 0;
                degr-wfc-timeout 120;
        }

        disk {
                on-io-error   detach;
        }

        net {
                cram-hmac-alg "sha1";
                shared-secret "*********";
                after-sb-0pri disconnect;
                after-sb-1pri disconnect;
                after-sb-2pri disconnect;
                rr-conflict disconnect;
        }

        syncer {
                al-extents 257;
        }

        on netxms-1 {
                device /dev/drbd0;
                disk /dev/sdb;
                address 10.10.10.1:7788;
                meta-disk  internal;
        }

        on netxms-2 {
                device /dev/drbd0;
                disk /dev/sdb;
                address 10.10.10.2:7788;
                meta-disk internal;
        }
}


/etc/netxmsd.conf

DBDriver = /usr/lib/libnxddr_pgsql.so
DBServer = 127.0.0.1
DBName = netxms_db
DBLogin = netxms
DBPassword = ******
LogFailedSQLQueries = yes
LogFile = /var/log/netxmsd


File /etc/postgresql/8.3/main/postgresql.conf is quite big, so I don't see any reason to put it here entirely. The only non-default setting there is

data_directory = '/postgresql/main'


PostgreSQL and netxmsd removed from auto-start, as they should be started by heartbeat.

Each node has NetXMS agent running instantly. Agent's configuration file looks like following:


MasterServers = 127.0.0.1, 10.0.0.11, 10.0.0.12
LogFile = /var/log/nxagentd
FileStore = /tmp
SubAgent = /usr/lib/libnsm_portCheck.so


Note that IP addresses of both nodes listed in MasterServers parameter.

Best regards,
Victor

Hi!

I've fixed this bug. Next release will contain the fix.

Best regards,
Victor

Sejchas proveril u sebja na 1.0.10 - rabotaet. Vozmozno problema pojavljaetsja pri kakoj-to specifichnoj konfiguracii. Vi mogli bi prislat', kak vigljadit konfiguracija problemnogo DCI?

Not in a straight way. You can achieve this by generating event via logwatch for each record and use situation object for counting (there was an example of how to use situations for counting events on the forum), but probably it will be easier to write external script for this.

Best regards,
Victor

Hi!

It is possible to create active-passive cluster using any clustering software, like Heartbeat or Microsoft Cluster. As NetXMS server stores all configuration in database, and configuration file contains almost only information necessary to connect to database, you just need to ensure database availability (by using replication or clustering software) and configure cluster software to start netxmsd. You also will need to add addresses of both cluster nodes to agents configuration files, because even if you are using virtual IP, outgoing connections will be made from primary addresses on the nodes.
I have NetXMS HA solution based on Heartbeat and DRBD (with database residing on shared DRBD device), and it works without problems for more than a year now. I can post configuration files for this configuration if it will help.

Best regards,
Victor

Quote from: inspirit on March 05, 2011, 09:38:17 PM
1) например как сделать что бы он коммутаторы опрашивал на предмет их живости например ну раз 5 минут. для диагностики этого вполне достаточно..

Это можно сделать только глобально, поменяв значение параметра сервера StatusPollingInterval на 300.

Quote from: inspirit on March 05, 2011, 09:38:17 PM
2) что нибудь про количество пулеров

Нельзя просто сказать, какое количество пулеров необходимо, надо смотреть на параметры сервера. У каждого типа пулеров есть своя очередь, и надо подбирать такое их количество, чтобы размер соответствующей очереди стремился к 0. Отдельные кратковременные пики - это нормально, но вот если размер очереди постоянно больше 0, то стоит увеличить количество соответствующих пулеров.

Quote from: inspirit on March 05, 2011, 09:38:17 PM
3) что нибудь про EventStorm и как это работает

Если event storm detector включен, то система отслеживает количество событий в секунду, и если оно больше чем значение, заданное параметром EventStormEventsPerSecond в течении послених EventStormDuration секунд, то обработка всех последующих событий прекращается до тех пор, пока количество событий в секунду не станет меньше EventStormEventsPerSecond.

Quote from: inspirit on March 05, 2011, 09:38:17 PM
напишите о том как нужно сконфигурировать netxmsd для сети с 500 и выше количеством коммутаторов.

сложно дать исчерпывающий ответ - надо смотреть на состояние сервера и менять настройки для устранения узких мест. Что обязательно стоит сделать - увеличить количество статус пулеров до ~ 50, если собирается много параметров - то скорее всего понадобится увеличить значения параметров NumberOfDataCollectors и NumberOfDatabaseWriters.

А какая версия сервера используется? Я попробовал на 1.0.10 - вроде все работает. И мне кажется, что я такой баг исправлял уже, не помню только в какой версии.

Hi!

Yes, x64 Debian packages will be released soon.

Best regards,
Victor

Permission sytem is already here - each tool has ACL, and only users/groups listed in tool's ACL will see it.

I'll think how I can add more detailed filtering for tools.

Best regards,
Victor

Hi!

I'll try to test this on my win2008 in a few days. Hard to tell something without tests.

Best regards,
Victor

Hi!

First of all, I'm not an expert in WMI - so maybe I'm wrong. But what I understand it, it's not possible to call WMI methods using WQL - and WMI.Query is based on executing WQL queries. It is possible to create another parameter for WMI subagent, WMI.Call, which will return result of calling given WMI method. I add this to my to-do list, but because WMI is almost unknown area for me, it may take some time until I implement this.

Best regards,
Victor

Hi!

Yes, it's possible, but you will have to carefully configure some things:

1. Each instance should have own database (or schema, depending on how particular database calls it);
2. Port numbers - you should change to non-standard port for client connections, port for SNMP traps, and port for syslog messages if syslog server is enabled;
3. If you are using web interface, you should also run second instance of web server, and change it's port to non-standard, as well as correctly configure server's communication port in nxhttpd.conf;
4. If you are running NetXMS on Windows, installer and command line option -I for netxmsd always create Windows service with standard name - you will have to use registry editor to create second service.

Best regards,
Victor

No. But this is a good idea, I'll think if I can implement it.

Hi!

Yes, it is possible. You should create third DCI with the solurce set to "Internal" and parameter name set to "Dummy". This will generate zeros on given interval. Then, in transformation script you can access both DCIs you have configured and calculate value for your new DCI. Example transformation script:


value1 = GetDCIValue($node, FindDCIByDescription($node, "My DCI #1 description"));
value2 = GetDCIValue($node, FindDCIByDescription($node, "My DCI #2 description"));
return value1 + value2;


Best regards,
Victor