NetXMS Support Forum

Try to stop IPSEC Services if they are running and are not needed. I can't remember exactly, but probably I've seen that running IPSEC Services interfere with custom programs working with ICMP while system ping works fine. Anyway, I'll try to find more information.

Best regards,
Victor

Thank you for spreadshit. I'll test it tomorrow, when I'll have MS Office at hands.

Quote from: kghammond on February 05, 2008, 07:00:24 PM
Also on a side note, are you creating a clustered index or any non-clustered indexes on the tables that store the rows of data?

For each table there are one clustered and one non-clustered index.

Best regards,
Victor

Also, Microsoft has document for estimating table size:

http://msdn2.microsoft.com/en-us/library/aa933068(SQL.80).aspx

NetXMS stores collected data in individual tables for each node, and each table has three fields: two integer and one varchar(255). However, if you collect mostly numerical data, you can assume that varchar field is used for about 10% of it's full capacity.

Best regards,
Victor

All collected data stored in varchars, as a textual representation of appropriate data type. I don't now how much space takes each record in database, but can provide some real life statistics.

My own NetXMS server runs on MS SQL 2005, I have 101 node with 1769 DCIs configured, almost all of them configured for collection every 60 seconds and retention time of 30 days (some configured for 3600 seconds and 365 days). Database size now is around 6.5 GB. For your situation, you will have about 400 DCIs for 100 switch interfaces and about 300 to 500 (depending on number of partitions, required parameters, etc.) for 40 servers - so probably your database size for 60 seconds/30 days configuration will be about 4GB in size.

I will try to collect data for some other MS SQL installations and post them here.

Best regards,
Victor

Quote from: kghammond on February 05, 2008, 04:30:50 PM
Any rough idea when you may finish the next release?

It should be very soon. Actually, I have plans to release it in January, but I have stuck on one required functionality (advanced event correlation), so release was postponed. The good side of it is that I will be able to include additional minor features like this.

Best regards,
Victor

Some additional questions:
1. Is there a firewall on a server?
2. Does NetXMS agent running under "Local System" account?

Best regards,
Victor

Unfortunatelly, it's still not implemented But still in TODO list...

Best regards,
Victor

About custom port names: I have similar request from Cisco users, and will definitely add it to the next release. Looks like using OID .1.3.6.1.2.1.31.1.1.1.18 should be universal way for all standard-compliant platforms.

Best regards,
Victor

Hello!

Error is because RFC forbids MIB module name to be started from lowercase letter, and our MIB compiler is more or less RFC compliant. Attached is corrected MIB file.

Best regards,
Victor

NetXMS checks interface configuration during configuration polls, which is every hour by default. You can force configuration poll for a node by right-clicking this node in object browser and then selecting Poll -> Configuration.

About DNS names: unfortunatelly, NetXMS will not re-check node names, so you will have to rename corresponding objects in NetXMS manually. If you need this feature, you can add it to wishlist on this forum.

Best regards,
Victor

Спасибо Опыта работы с Cisco мне явно не хватает...

Quote from: weec on February 04, 2008, 10:18:51 AM
что означает статус "wait" и какие другие есть статусы у poller-ов?

init - инициализация
wait - ожидание появления задания на опрос в очереди
poll - опрос хоста
finished - поток poller'a завершил работу

Hello!

It will be possible in upcoming version 0.2.20. Currently, you can run discovery with one community, accepting only devices with SNMP support (to avoid adding devices with different community with incorrect settings), then change the community and wait for next discovery cycle.

Best regards,
Victor

Just tested on my machine - 127.0.0.1 works fine, so it seems like a bug or misconfiguration. Could you please send me agent's configuration from the host where you define DCI with ServiceCheck.Custom(127.0.0.1,xx) and output of netstat -an from this host?

Best regards,
Victor

Всем добрый день! Я решил попробовать свести воедино все планы и идеи по развитию системы, чтобы и самому не забыть, и комментарии услышать.

В ближайшее время планируется выпустить версию 0.2.20. В нее войдет:

• Возможность продвинутой корреляции событий с использованием "ситуаций"
• Функциональность "proxy node" для DCI
• Макросы в шаблонах DCI
• Поддержка UNICODE в клиентской части на UNIX
• Обновленный Alarm Viewer
• Различные мелкие исправления и улучшения

Постараюсь учесть как можно больше уже высказанных пожеланий, но в основном небольших. Если у кого-то есть простые в реализации пожелания, которые очень хотелось бы видеть в новом релизе, пишите.

Версия 0.2.20 планируется быть последней в ветке 0.2.x. Если все будет в порядке, то я собираюсь ее пригладить и выпустить версию 1.0.0. После зтого разработка должна разделиться на две ветки - stable 1.0.x и development 1.1.x. Основные большие изменения будут происходить в 1.1.x.

Основные планы на 1.1.x следующие:
1. Новая консоль - модульная и кросс-платформенная (прототип уже можно будет увидеть в 0.2.20);
2. Нормальные карты сети - топологии 2 и 3 уровня, а так-же user-defined;
3. web interface (уже очень давно пора);
4. Полноценная работа с логами NetXMS (event log, syslog, audit log);
5. Обработка лог-файлов на хостах;
6. Улучшение network discovery;
7. Ну и в соответствии с пожеланиями и предложениями сообщества.