NetXMS Support Forum

Hi,

I'm wondering how the merge duplicate nodes is intended to work?  I have an Isilon (SNMP discovered), whose discovery appears as a large range of IP addresses. There are more IPs than nodes.  This is part of the architecture to distribute the load and rebalance for node maintenance/failure.   But each IP appears as it's own node.  For simplicity I have explained a scaled down example below.

4 physical nodes (where node is a server) in a cluster.  The cluster manages 20 IPs that are distributed across the nodes.  Each node may have 5 IPs for clients to connect too.  The Isilon distributes clients across the IP's via integrated DNS server and DNS delegation for the service name.  Should a node fail, the IPs are re-distributed across the remaining nodes.

NetXMS will discover all 20 IPs and create nodes for each IP.  But I don't have 20 nodes, in my example, I have 4.  I have set NetworkDiscovery.MergeDuplicateNodes to 1, but still the nodes are duplicated for every IP in the cluster.  "Sys Description" is unique for each node, so during discovery I end up with many IPs with the same "Sys Description" as a unique object in NetXMS.  See the image below of Object Details -> Nodes list view.  My Image shows an 8 node cluster.  Notice that in the Sys Description column, the names are identical for each unique node.  I have some obfuscation in the IPs and node "Sys Description" columns, but the point is that I have a unique ID for each IP, instead of for each node.

Image: See attachment.

I'm not sure how the Merge Duplicates works, but I would like there to be only one node with many IPs.  I like that the subnets view under "Entire Network" shows each IP, but for this type of cluster each IP should point to the appropriate unique nodes object ID.  In other words, merged.

Cheers,

I have some data which is slightly delayed from the source application.  The data has it's own, and more accurate timestamp, that I would like to use when adding my DCI values in NetXMS.  The reason for using this timestamp, is that the delay can vary from 30 seconds to up to 2 minutes.  Also, this data can be delivered in large batches.  I'm pre-processing the data, but need to use the applications timestamp for accurate data reporting.

I'm looking at nxpush and/or using the agent with a script to collect these as DCI values.  I can't see anywhere if we are able to provide our own timestamp as opposed to NetXMS providing time.

Any thoughts or suggestions on this scenario?

Cheers,

Hi,

Thank you for a great product.

I'm setting up some Disk IO monitoring for some Linux hosts.  I've been successful in pulling the data, using an explicit disk name.

In my Data Collection Configuration, on the General Tab, in Data->Parameter I'm using...

System.IO.ReadRate("xvda")

I'm wanting to make this dynamic in my Template.  I've been reviewing the wiki and the forum, looking for the right way to do Instance Discovery for a List of Disks.  At the present, I've only setup the Agent on a Linux host, and I've not configured any SNMP on servers yet.  I've been unable to find anything that points to a List/Table from the agent with this data.  If nothing native exists, then I'm thinking that I'll need to leverage an "External List".

1.  For this type of Data Collection, is Agent best, or should I examine SNMP?  What are others doing here?
2.  Am I correct in assuming that there isn't an Agent List/Table with a list of 'Disks'?
3.  Are 'External Lists' my best option?

Thank you and Kind Regards.

Cheers,
Tim