Victor - sorry for wasting your time.  :-[ I had looked at those OID's over and over again yesterday and could not spot the typo. Of course now i have corrected it, everything works fine. I have been looking at a bunch of software in this area and NetXMS has been head and shoulders above everything else I have tried. I am looking forward to what you have planned for future releases. Thanks.

 I 've been fiddling around with the conditions and condition.status(*) and it works like a charm. What still might be a nice feature is that a condition could take another condition as a data-value (Now it can only take a host/dci). But I work around by using an intermediate DCI. (This takes an extra delay, but is not really a problem...) Also thank you for the tip about the trusted nodes part, because I would never have figured that out! Apparently you get an "not supported" error then... 

I didn't play much with new NNM 8i, but NNM 6.x and 7.x uses a slightly different approach - status of a node is depending on number of interfaces being down - for example if less than half of interfaces is down node status will be Minor, and if more than half is down - Major. If talking anout HP management products, we use approach similar to OpenView Operations - by default parent object's status equal to most critical child status, but you can change this by changing status propagation and/or calculation properties for either parent or child object. For example, setting status calculation mode for switch node object to "multiple thresholds" and setting thresholds to Warning 0.1, Minor 0.2, Major 0.5, Critical 0.9 will give you kind of NNM-like status calcualtion for switch node. Best regards, Victor

Thank you, I will try to get a better understanding of that counter.  On one of our servers, we are seeing regular valures around 200 - 250 for that paramater and spikes over 600. Thanks again, Kevin

Thanks Victor...the first choice worked. I did have to modify the query to read the data for the current month and then apply the formula. It also now gives me the number of reboots done in a month.

It should be safe. Agent will accept connections only from hosts listed in configuration file. Connections from all other addresses will be closed immediatelly without sending or receiving any data. Also, you may configure agent to require additional authentication with shared secret, and to require encrypted connections. Best regards, Victor

I just experimented with using process.io.xxx with a transformation of "Average delta per second", and I compared it to the: Counter = UserProcess.SQLServer.IO.xxx:"\Process(sqlservr)\IO xxx Bytes/sec":60:A:INT:"Average I/O xxx Bytes for sqlservr.exe over past minute" Both graphs are virtually identical. I thought this might be helpful if anyone is reading this thread. Kevin

Thank you, I am starting to feel really dumb for all my little typo's.  It is working great. Thanks again, Kevin

Yes that file exists in the C:\netxms\bin directory.

For process counters in question, if process does not exist, counter will return 0. But in general, if you try to add non-existing performance counter, it may fail on agent startup, or may return error to data collection requests - depending on what PDH returns to agent. Best regards, Victor

Yes you may publish it.  Thank you for asking and I am glad I can help.

@rmz said in ICMP on Windows 2000 Server: 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

@kghammond said in Changing the name of switch ports: 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

Thank you the corrected MIB file worked perfectly. Kevin

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

Problem solved... well, not exactly solved, but the issue was not a netxms bug in any way.. I did a complete reinstall of the system.. a fresh windows XP works like a charm. No SNMP hickups of any kind.

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

We are in the process of testing out this program to use to help supplement our system monitoring and alerting.  One of the first things that we stumbled across was seeing if we could customize the performance tab. So far the program looks great, but customizable dashboard views for what is currently going on would definately be a nice plus. Thank you, Kevin

First of all, check if nxhttpd process is running. If not, you can run it from console with -D switch to check for possible startup problems. Best regards, Victor

Hello! You can clear password field in database for user admin with the following SQL query: UPDATE users SET password=' ' WHERE id=0 and restart NetXMS server. On startup, server will reset password for user admin to the default one - netxms. Best regards, Victor