Because you are monitoring services using DCIs, you will not get service down events in case of entire node down, because there will be no new values for DCI, and therefore no events will be triggered. Btw, it is not recommened to use SYS_xxx events in thresholds - they are generated by server in various situations, and you can get unexpected results. SYS_SERVICE_DOWN and SYS_SERVICE_UP generated by server during status poll of network services. Until you are not using network service objects, you are fine, but if you eventually configure some, you will get unexpected events. Better approach is to create your own events. Best regards, Victor

Okay my fault, now works.

@evilclown said in Map/Service Question: Is it possible to manually connect servers in the map (Layer 2 and 3)? Yes, if you are talking about custom maps. You can select two objects, and press Ctrl+Alt+C (or select Map -> Create link between objects menu) - this will create labeled link. @evilclown said in Map/Service Question: How to integrate external service checks? By using agent's external paremets. One example is here: https://www.netxms.org/forum/configuration/how-to-countgraphcheck-tcp-connection-states-table-with-netxms/. But this is only for creating new DCIs,  it has no relation to network service objects. Best regards, Victor

Hi Victor, It re-tested. They are Cluster and Container. a result -- having been the same . Cliuster did not have a reaction by "check agent" by Cluster for about 5 minutes. Container did not have a reaction by "check agent" by NODE for about 10 minutes. Cluster nxadm -c "sh p" PT  TIME                  STATE S  07/Jan/2011 12:10:02  wait ------- cut ------- S  07/Jan/2011 12:04:45  poll: CLUSTER [89] - check agent S  07/Jan/2011 12:10:17  wait ------- cut ------- R  07/Jan/2011 12:05:32  poll: SERVER NODE [50] ------- cut ------- Container nxadm -c "sh p" PT  TIME                  STATE ------- cut ------- S  07/Jan/2011 12:36:57  wait S  07/Jan/2011 12:28:15  poll: SERVER NODE [50] - check agent ------- cut ------- R  07/Jan/2011 12:28:17  poll: SERVER NODE [50] ------- cut ------- I am using the DCI transformation scripts. However, it doesn't use it in the object node.

Is log file name represents current date and time? If yes, then for that pattern active log file can be identified as following: <file>AMS3AutoDealerLog%H%a%d%b%Y.AMS3</file> Logwatch will automatically switch to new file each hour. But if log file name contains past hour, not current, then you will need to create external script which will provide logwatch with file name to parse. To use script for generating log file name, use following syntax: <file>AMS3AutoDealerLog`my_script_name`.AMS3</file> Best regards, Victor

Yes, that means that you are running 1.0.8. I'll check this. Best regards, Victor

For SQLite, parameter DBName is database file name. So, if you specify just "netxms", it is relative to current directory. If you run netxmsd from different directory, it will pick wrong file. You should specify fully qualified file name in DBName. Best regards, Victor

Thanks Victor, After updated node.cpp compilation, I can now fetch MIB values in my management console. Shiv

Hi! You can add additional parameters to agent using ExternalParameter config file option. For example, you can add to nxagentd.conf on some node ExternalParameter = WebVersion:wget -qO- https://www.netxms.org/download | perl -e 'while(<>) { chomp $$_; if ($$_ =~ /stable version is ([0-9\.]+)\,/) { print "$$1\n"; } }' After that, agent will provide additional parameter named WebVersion. You can get value of this parameter by creating new DCI on this node, and create thresholds to detect value changes. Best regards, Victor

Hi! The only possible initialization of array is like monitornodes[1] = "system-1"; monitornodes[2] = "system-2"; monitornodes[2] = "system-3"; I like the idea of having array initializers, I will add it to NXSL. Also, your script has an error if for loop condition - it should be monitornodes[i] != NULL, not monitornodes != NULL. So, correct version of the script should looks like this: array monitornodes; monitornodes[1] = "system-1"; monitornodes[2] = "system-2"; monitornodes[2] = "system-3"; summary=0; for (i=1; monitornodes[i] != NULL ; i++) { inode = FindNodeObject($node, monitornodes[i]); ivalue = GetDCIValue(inode, FindDCIByDescription(inode, "TotalAuth")); summary += ivalue; } return summary; Best regards, Victor

Hi! Counter name must be enclosed in quotes, like this: PDH.CounterValue("\Web Service(Microsoft Dynamics CRM)\Total Method Requests") because counter name contains brackets, and without quotes agent cannot parse parameter correctly. Best regards, Victor

Dear all, I solve this problem by using WMI query WMI.Query(root\cimv2,select * from Win32_PerfRawData_PerfOS_Memory,PoolNonpagedBytes) Kelvin Sin

Hi, when you will find some time for "non critical" items, maybe you want to improve this small one: When you use the MIB Browser and select a node to get a value, if you want to change node you have to quit MIB Browser and restart it. Adding some flexibility by allowing to change all involved parameters (a.o. the IP address of the polled node) would be more user-friendly  ::) Best regards, JDamien

It's rather "known limitation" - it was implemeted that way. I agree that it's not best way and must be fixed, but I'm not sure I'll fix this in old console - I hope to switch to new console as soon as possible. New console already have line charts implemented, with correct zoom (on both axis). Best regards, Victor

Event log show events, and on "Alarms" tab shown active (not terminated) alarms. In short, alarms is an events which requires operator attention. They are created from events in event processing policy. Main difference from event is that alarms has state (outstanding, acknowledged, or terminated) and repeat count - so if for example you have repeated events coming every minute, in alarm browser you will only see one alarm with increasing repeat counter. Alarms described in more details in user manual, section 6.3. Best regards, Victor

Hi Victor,  Many thanks for the info. The problem was corrupted performance counter data on the monitored server, I've managed to partially fix the counters, which has got the basic graphs back in NetXMs. Happy Christmas, David

Great! I've tested it, it worked like a charm! thank you Joël

It's a value reported by SNMP agent on target node for standard SNMP OID .1.3.6.1.2.1.1.2.0 (sysObjectID), which is described as following: The vendor's authoritative identification of the network management subsystem contained in the entity.  This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed.  For example, if  vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'. Best regards, Victor

Hi Victor, Thanks for your support. Kind regards, Maurice

Hi! Unfortunately, there are no predefined checks for protocols other then you listed. You can either use "custom" check, which just checks connectivity to TCP port, or write external scripts and call them via external parameters for protocol checking. For a long time I wish to rewrite port checker subagent as an engine which runs NXSL scripts doing protocol checks, so it can be easily extended, but still cannot find enough free time to do that Best regards, Victor