Hi Victor,  It was an upgrade and I upgraded the server first then I uninstalled the agent and ran the downloadable agent installer, I will know to just run the server installer next time !  Many thanks for your prompt help on this. David

Try to delete both subnets (this will not delete nodes unless the subnet is the only parent object for a node) and do configuration poll on nodes. Server should create one subnet object. Best regards, Victor

Answered part of my own question.  For switches the Index is what I use and it is template-able.  (I just need a 48 port and 24 port template) That makes it much easier, originally when I noticed the problem was on servers that I am monitoring with agents and they are VMs so the indexes seem off (and varies between one and many interfaces).

Hi! NetXMS by itself is working on Windows 7 (I do most of development and testing on Windows 7), but mssql database driver uses very old and deprecated API called DB-library, which may be incompatible with modern Windows versions. It will be removed in 1.1.x branch. For connecting to MS SQL, it is now recommended to use ODBC. Best regards, Victor

By default, server check configuration of each node every hour - it's called "configuration poll". You can forcibly execute configuration poll by right-clicking node in console and then selecting Poll->Configuration. Or you can just wait one hour. Best regards, Victor

Thanks a lot. I really appreciate you work on this. One more question. Is it safe to amend the script directly by editing the database table event_policy?

Hi! I can reproduce such problem in a Cisco A.S.A. firewall. NetXMS reports "Unable to get interface list from node" from Poll -> Interfaces names. Snmpwalk command retrieve interfaces names from NetXMS server: [root@GesRed2 ~]# snmpwalk -v 1 -c xxxxxxx 10.1x.xxx.xxx | grep -i ifName    IF-MIB::ifName.1 = STRING: port1 IF-MIB::ifName.2 = STRING: port2 IF-MIB::ifName.3 = STRING: port3 IF-MIB::ifName.4 = STRING: port4 IF-MIB::ifName.5 = STRING: port5 IF-MIB::ifName.6 = STRING: port6 IF-MIB::ifName.7 = STRING: port7 IF-MIB::ifName.8 = STRING: port8 IF-MIB::ifName.9 = STRING: port9 IF-MIB::ifName.10 = STRING: port10 IF-MIB::ifName.11 = STRING: ssl.root IF-MIB::ifName.12 = STRING: SLB_LexWeb IF-MIB::ifName.13 = STRING: FirePass_Ext IF-MIB::ifName.14 = STRING: SLB_LexWebAdmin IF-MIB::ifName.15 = STRING: ABO_IREGES IF-MIB::ifName.16 = STRING: MUGEJU_sede_ele IF-MIB::ifName.17 = STRING: SLB_PortalesExt [root@GesRed2 ~]# snmpwalk -v 2c -c  xxxxxxx 10.1x.xxx.xxx | grep -i ifName  IF-MIB::ifName.1 = STRING: port1 IF-MIB::ifName.2 = STRING: port2 IF-MIB::ifName.3 = STRING: port3 IF-MIB::ifName.4 = STRING: port4 IF-MIB::ifName.5 = STRING: port5 IF-MIB::ifName.6 = STRING: port6 IF-MIB::ifName.7 = STRING: port7 IF-MIB::ifName.8 = STRING: port8 IF-MIB::ifName.9 = STRING: port9 IF-MIB::ifName.10 = STRING: port10 IF-MIB::ifName.11 = STRING: ssl.root IF-MIB::ifName.12 = STRING: SLB_LexWeb IF-MIB::ifName.13 = STRING: FirePass_Ext IF-MIB::ifName.14 = STRING: SLB_LexWebAdmin IF-MIB::ifName.15 = STRING: ABO_IREGES IF-MIB::ifName.16 = STRING: MUGEJU_sede_ele IF-MIB::ifName.17 = STRING: SLB_PortalesExt [root@GesRed2 ~]# Best Regards. UnableGetInterfaceListSNMP_1.png UnableGetInterfaceListSNMP_2.png

Hi! Try to use SQL server authentication and ODBC driver. MSSQL driver uses very old and outdated client library, which may now work as expected on WIndows Server 2008. Best regards, Victor

If it is not here, you just need to create new variable with that name. Best regards, Victor

Hi! You need to control communication with the site somehow, by pinging router for example. Then you can use situation objects to do manual event correlation. Also, if NetXMS server knows the whole route from itself to managed nodes and has all routers entered as managed nodes as well, it tries to do automatic event correlation based on network topology. Best regards, Victor

Thanks a lot Victor, I will give it a try Genady

Hi! I've fixed this bug. Next release will contain the fix. Best regards, Victor

Not in a straight way. You can achieve this by generating event via logwatch for each record and use situation object for counting (there was an example of how to use situations for counting events on the forum), but probably it will be easier to write external script for this. Best regards, Victor

Thanks, I am using Windows platform, I will try it out.

Hi! First of all, I'm not an expert in WMI - so maybe I'm wrong. But what I understand it, it's not possible to call WMI methods using WQL - and WMI.Query is based on executing WQL queries. It is possible to create another parameter for WMI subagent, WMI.Call, which will return result of calling given WMI method. I add this to my to-do list, but because WMI is almost unknown area for me, it may take some time until I implement this. Best regards, Victor

No. But this is a good idea, I'll think if I can implement it.

Hi! Yes, it is possible. You should create third DCI with the solurce set to "Internal" and parameter name set to "Dummy". This will generate zeros on given interval. Then, in transformation script you can access both DCIs you have configured and calculate value for your new DCI. Example transformation script: value1 = GetDCIValue($node, FindDCIByDescription($node, "My DCI #1 description")); value2 = GetDCIValue($node, FindDCIByDescription($node, "My DCI #2 description")); return value1 + value2; Best regards, Victor

Hi! You should set "Repeat event" option for threshold to value less or equal 10800 - this will cause server to resend event on every poll. It doesn't matter what event you set for "when condition becomes false again" if this will never happen. Best regards, Victor

hi! Nxagentd.log was confirmed. The following messages appeared. The log file doesn't rotate. The target log file is frequently written. nxagentd.log ------------------------- [11-Mar-2011 13:45:05] LogParser: file size differs for stat(8 ) and fstat(/var/log/test.log), assume file rename [11-Mar-2011 13:45:05] LogParser: file "/var/log/test.log" (pattern "/var/log/test.log") successfully opened ------------------------- Best regards.

I figured this out.  I placed the externalparameter line below the *PING line in the config.  Moving it above this line and it works perfectly. Love this app btw, great work.