Ok, I will try this. Thanks for the quick response.

Hello! Here are translation of mentioned post, should be enough to setup shared resource monitoring. It's an example of cluster monitoring configuration. Case: We have two cluster nodes: NODE_A and NODE_B. Cluster itself is called CLUSTER. Both nodes have NetXMS agents installed. Nodes are connected to public network 192.168.1.0/24, node A has address 192.168.1.11, node B - 192.168.1.12. Also, both nodes has private network 10.0.0.0/8, node A has address 10.0.0.1, node B - 10.0.0.2. There are 3 resource groups: Cluster group, name: ClusterGroup, virtual IP 192.168.1.10 Shared disk, name SharedDisk, virtual IP 192.168.1.20. On active node seen as drive X: Exchange server group, name: Exchange, virtual IP 192.168.1.30. On active node run Exchange services and drive E: contains shared Exchange data. Requirement: Monitoring service availability and disk space. Configuration steps: Create object of type "Cluster", call it CLUSTER (it is no necessary to match AD cluster object name) In CLUSTER object properties add cluster interconnect network 10.0.0.0/8 In CLUSTER object properties on "Resources" page define resources (name - IP pairs):     ClusterGroup 192.168.1.10     SharedDisk 192.168.1.20     Exchange 192.168.1.30 Now we can create nodes A and B. They should be created under CLUSTER object. As Ip addresses for new nodes should be used their fixed IP addressesd (192.168.1.11 and 192.168.1.12 in our example). Check configuration of new nodes - virtual addresses of cluster resources should not appear as interfaces. If you select CLUSTER object in object browser, on "Cluster" page should be displayed correct position and status of cluster resources. Now DCIs for cluster resources can be defined. Select "Data Collection" for CLUSTER object, and create DCIs as usual, except one: you should select correct cluster resource in "Associate with cluster resource" field. Fo example, for monitoring disk space on shared disk X:, you should set "Associate with cluster resource" to "SharedDisk" in our example. DCIs configured that way will be collected only from node which is current owner of associated resource. All other configuration for cluster nodes can be done as usual. There are also some predefined events related to cluster monitoring: SYS_CLUSTER_DOWN SYS_CLUSTER_UP SYS_CLUSTER_RESOURCE_DOWN SYS_CLUSTER_RESOURCE_UP SYS_CLUSTER_RESOURCE_MOVED You can process them as usual in event processing policy. Best regards, Victor

Hello! Most likely nxagentd.exe is locked and therefore cannot be deleted - because it contains message texts for Windows Event Log, it can be opened by mmc.exe if someone leave Event Viewer open. It also can be any other process which uses Event Log. As a workaround, rename nxagentd.exe, and then run installation again. Best regards, Victor

Thank you again. Very helpful. I created templates and I am currently monitoring drives without any problem.

Some additional comments: Nagios plugin API is very simple - basically, plugin is an executable which return code indicates status of tested service (0 = OK, 1 = WARNING, 2 = CRITICAL, 3 = UNKNOWN), and one or more lines of text. So, you can run any nagios plugin from NetXMS agent as external parameter, and get either status code or first line of text output. For example, to get status code, add following line to nxagentd.conf: ExternalParameter = NagiosTest1:nagios_plugin > /dev/null ; echo $? and for capturing first line of plugin's text output simply ExternalParameter = NagiosTest2:nagios_plugin Best regards, Victor

Awesome!  Thanks Victor!

@victor said in Can NetXMS import private MIBs?: Is this what you asking for? - https://www.netxms.org/forum/index.php/topic,21.0.html Best regards, Victor Yeah! Jus what I was looking 4. Ty very much. Best Regards geekton

@victor said in Re: Pre-requisites for Windows Server 2003 Install: 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: 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. Windows 2000, XP, Vista, or 2003 operating system. Should run on 2008 as well, but I have not tested it. 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 Thanks my bad, I guess I missed it, I appreciate it very much.

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

Below are working SQL commands to extract the latest value for a DCI. Note - the DCI as named for the node is queried not its ID The following SQL will list all of the idata_value’s for the DCI named 'SQL Cache Memory KB' for node 201 SELECT  TOP 1  items.item_id, items.node_id, idata_201.idata_timestamp, idata_201.idata_value FROM        items INNER JOIN                       idata_201 ON items.item_id = idata_201.item_id WHERE    (items.description = 'SQL Cache Memory KB') AND (items.node_id = 201) ORDER BY idata_201.idata_value DESC, idata_201.idata_timestamp ASC The following SQL code will list the latest idata_value for the DCI named 'SQL Cache Memory KB' for node 201 select A.item_id,A.ts,D.idata_value,I.description from (       select item_id,max(idata_timestamp) as ts from idata_201 group by item_id ) A join idata_201 AS D on A.item_id=D.item_id and D.idata_timestamp = A.ts join items AS I on I.item_id = A.item_id where description = 'SQL Cache Memory KB'

Use admin as login name and netxms as password.

Victor, thanks!

Now I'm understand In fully correct way - it's only supported since 0.2.23, where you can specify thresholds like last() > 90 for 10 polls. However, you can get approximately the same result by giving average() > 90 for 10 polls. Best regards, Victor

Hello again, I wanna ask a question... I tried several things to solve but couldnt figured out yet Let's say i am monitoring a windows server and several windows services on it... I configured all monitoring stuff and they work perfectly but what i am trying to do when this windows server completeley gets down (shut down, restarted) i dont want to receive alarms for its services.. I hope there is a solution for this situations Thanks

Victor - the 2.23 version of wmi works well, however, the 64bit wmi needs the new version as well. Can you please provide me with the 2.23 version of wmi? many thanks Geoff

Excellent !! with your help problem is solved :)) Thank you very much

Hello! It's in our wish list. I have some ideas of how to implement this, and will try to do it in one of next releases. Unfortunately, I cannot define precise time frame for implementing this feature right now. Best regards, Victor

oh, ok than. thank you very much

Thanks, that worked perfectly.  I then had to do quite a bit of modifications to get the MIB to compile, so I'd like to post my mib file for others. trend.mib.txt

Hello! libnxsnmp.so is not a subagent - it's just our SNMP client implementation used internally by NetXMS server and SNMP-related command line tools (nxsnmpget, nxsnmpset, and nxsnmpwalk). Names of subagent modules always starts with libnsm_. Best regards, Victor