NetXMS Support Forum

Скоро должна выйти. Если хочется, я могу сегодня собрать и выложить release candidate. Заодно и бета-тестеры появятся...

В версии 0.2.20 реализована поддержка определенных пользователем названия интерфейсов (interface aliases). Использование контролируется параметром сервера UseInterfaceAliases. Могут быть следующие значения:
0 - не использовать
1 - в качестве имени интерфейса использовать алиас
2 - конкатенировать алиас и имя интерфейса

Currently, the only thing you can easily monitor is interface up/down. System detect all interface state changes and send predefined events: SYS_IF_DOWN and SYS_IF_UP. You can filter and process these events in event processing policy, so you will need to configure only a few rules in EPP.
For other things, there are some work to do

Best regards,
Victor

Quote from: rmz on February 06, 2008, 05:10:30 AM
One more quick question.  Using the object map, I can watch the various managed nodes for their status.  In the case of an unmanaged node is it possible to some how use this data collection point (icmp.ping values) with an unmanaged node on the object map, so I can verify status for them as well? 

You can just switch them to managed - if node doesn't have neither SNMP agent nor NetXMS agent, server will just ping it regularly and change status accordingly. Alternatively, you can define DCI for ICMP.ping(unmanaged_node_adderess) parameter on node with PING subagent loaded. But in this case, status of the unmanaged node object will not be changed.

Best regards,
Victor

Actually I create one table per node, not per DCI.

Best regards,
Victor

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