Server connects to agents. You need to open TCP port 4700 in direction from server to agents. Best regards, Victor

  It works~! I noticed that the 1.05 User Manual is out, hope to see the new version soon~

Hi Victor, Thank you very much for your prompt response I'll try. Regards, mulder

Yes deleting the netxms.mib worked. I can now see the vaules in MIB browser. Thanks for you help.

Ok, now I got it. First, I suggest you to got source code from subversion - https://svn.netxms.org/public/netxms/trunk. All Java sources located under src/java. Console is written on Eclipse platform, so plugin development is just a normal Eclipse plugin development process, which is well documented on Eclipse web site - www.eclipse.org. If you have questions, ask them on forum in development section. Best regards, Victor

great ! thanks for quick reply. Is there some log file where pingsubagent saves all pings times ? because I need to check it only temporary for some time, later will use avgresponsetime. don't know who can update this manual: https://www.netxms.org/documentation/ping_subagent.shtml but it will be great if packetrate parameter will be added it can save your time in the future Thanks and regards, Milan

Hi! It depends on your configuration. For node objects, status calculated based on two sources - statuses of child objects (interfaces and network services), and active alarms for the node. So, if you, for example, have outstanding critical alarm, node status will be critical even if it is reachable by management server. Also, default status calculation algorithm takes most critical status of child objects, so if you have managed device with multiple interfaces, one interface in down state will cause critical status for entire device, although it is still reachable via other interfaces. You can safely assume that critical status mean "node unreachable or down" only if you have configured system in that way. In default configuration this is not the case. Best regards, Victor

Hi! It means that event configured in threshold will be generated as soon as monitored value will be 0 or greater than 0. Best regards, Victor

First of all, you have to specify full path, not just Temp. Second, you have syntax errors in recursion and size parameters - you should use only digits here. So, parameter should looks like File.Count('C:\Temp', 'SAS*.txt', 1, 0, 90) to count number of files older than 90 seconds. Then, threshold by itself looks correct, but did you create appropriate rule in event processing policy? Also, take a look at this step-by-step configuration example: https://www.netxms.org/documentation/confexample/. It's quite old, and screens  will look a bit different, but you should get an idea. Best regards, Victor

Hi All, I am new to NetXMS, could any one give me one example like disk space monitoring Agent configuration. Thanks, REDRO

Hi! Database format has not been changed between 1.0.2 and 1.0.3, and so there was no changes in nxdbmgr. It was not supposed to be that way, nxdbmgr just was not rebuilt with new version string. It's inconvenient, but it does not affect operations of NetXMS server in any way. Best regards, Victor

Installation complete! Thanks for Your help, Victor.

winevet.h is a header file for Windows Events API, which was first appear in Windows Vista, so you probably need Windows Vista or Windows Server 2008 SDK. Best regards, Victor

Thank you It´s time for me to start using scripts on Netxms ... Thanks again.

Let's summarize in what environment this problem occurs in version 1.0.3: Windows + MS SQL FreeBSD with MySQL 5.1 (is it still an issue?) any other environments? Best regards, Victor

Hi! Did you configure SMTP server settings in NetXMS correctly? You have to set server's configuration variable SMTPServer to your SMTP server's IP address. Setting SMTPFromAddr to some correct value also recommended. Best regards, Victor

Hi! You can use filter scripts to do advanced filtering. Event SYS_SERVICE_DOWN contains 3 parameters: 1: service name; 2: service object id; 3: service type. So, for example, if you wish to execute action only for service named "httpd", you can use the following script: $1 == "httpd" or, in full form sub main() { return $1 == "httpd"; } Best regards, Victor

Microsoft can promise all they want, but reality is sometimes different. I couldn't find the msdn blog I was remembering, but I did find this kb article.  It appears they may have fixed a few things since this is considered retired now. http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q274323& I don't think they use the rdtsc counter in multi-core systems anymore, but they do still recommend to lock the timing thread to one processor since not all HAL implementations will give consistent readings between cores.  Closest thing my quick search returned is: http://msdn.microsoft.com/en-us/library/ee417693(v=VS.85).aspx BTW, I DO appreciate your timing changes and keep up the good work!!!  I just wanted to warn you that some odd hardware/os combos will probably fail to measure time correctly...

Hi! The most generic way is the following: Stop netxmsd on old server Export database using nxdbmgr: nxdbmgr export export_file Install same version of NetXMS on new server Create and initialize new database as usual Import data using nxdbmgr: nxdbmgr import export_file Run netxmsd on new server If you will use different IP address on new server, you must add it as master server in agent configuration files. If you are using external database which will not be migrated, you can just install NetXMS on new server and copy netxmsd.conf from old server - it should start working with same database without problems (don't forget to stop netxmsd on old server first). Also, if you are migrating to same database engine, using database migration tool from database engine could be more effective. Best regards, Victor

Hi! Agent cannot send SNMP traps. It is capable of sending NetXMS events to server, but it's an internal mechanism, available only as API to subagents. You can also use nxevent command line tool to send events from remote system to the server. Best regards, Victor