NetXMS Support Forum

We need more information.

What version of NetXMS are you using?
What OS?

Are you compiling from source using using .deb packages?

Of course, this is one of the most basic functions NetXMS provides.

You of course need to be able to read this over SNMP from a network device terminating that connection.

Yes, several objects can have the same name (name is more like description really).

IP address of 2 objects can NOT be the same however.

Did you change the IP address of AD2008 by any chance?

No, I mean from here http://git.netxms.org/public/netxms.git?js=1
I am running both the client and the server from newest commits in develop.

Please be aware these are development builds, and may contain bugs and/or issues.
I would recommend running only release versions in production, unless you are prepared to deal with all that comes with running latest development builds in production.

That said, nothing was really touched in DCIs and Perf. tab since 2.0.3 release (atleast not that I remember), so your issue is probably somewhere else.

Here is the configuration for the perf. tab graph I attached in the previous post.

Server is running from newest commit in develop (which is not too far ahead of 2.0.3) on Ubuntu Server 14.04.
Client is running on Win 7.

Template DCIs binding to perf. tab works fine for me.

For example, this is 3 DCIs on perf. tab from a template.

The 2 "used" DCIs are attached to the "size" DCI.


nxdbmgr -h
...
Valid commands are:
...
migrate <source>   : Migrate database from given source
...
Valid options are:
...
-s          : Skip collected data during migration or export.


Backup your old config file to for example "netxmsd.conf.old".
Configure your "netxmsd.conf" with new database.

Then run: "nxdbmgr -s migrate netxmsd.conf.old"

It works fine for me from those packages

root@raspberrypi:/etc# nxagentd -f -D5
[10-May-2016 13:39:12.363] [INFO ] Additional configs was loaded from /etc/nxagentd.conf.d
[10-May-2016 13:39:12.363] [INFO ] Debug level set to 5
...
[10-May-2016 13:39:12.468] [DEBUG] Thread pool SNMPPROXY initialized (min=2, max=128)
...
[10-May-2016 13:39:14.589] [DEBUG] SNMP Trap sender thread started
[10-May-2016 13:39:14.592] [DEBUG] Data collection scheduler thread started
[10-May-2016 13:39:14.594] [DEBUG] Data sender thread started
[10-May-2016 13:39:14.594] [DEBUG] Database writer thread started
[10-May-2016 13:39:14.594] [DEBUG] Data reconciliation thread started
...
[10-May-2016 13:39:14.598] [DEBUG] SNMPTrapReceiver: listening on 0.0.0.0:162
[10-May-2016 13:39:15.599] [INFO ] NetXMS Agent started
Agent running. Press Ctrl+C to shutdown.
...


What is not working for you?

Here are compiled armhf packages.

From 2.0 and onwards, the Status DCI is not created by default anymore.

You can always just create a template with autobind script as "return true;" to have the old functionality.

I think a removal of this is a bug, however, Victor should probably confirm if it was intentional or a bug.

Sounds like a bug, please create a ticket at:
https://dev.raden.solutions/projects/netxms/issues

It of course depends on the hardware resources your NetXMS server and your database server have available.
Database layer is the most taxed one (as is usual in applications like this), NetXMS server in itself doesnt require that much resources.

You will find plenty of 3k+ monitored node NetXMS deploys here on the forums.
There is no problem to support 10k monitored nodes or more tho.

The way is described here on the wiki as well:
https://wiki.netxms.org/wiki/UM:Data_Collection#Macros_in_template_items

You can not currently access node's Custom Attributes directly from the DCIs, but with an intermediary script you can do it.

So in your DCI, you would define it like this:

MyDCI.Name("string_abbrib", %{script:get_node_attrib})


Then create the script "get_node_attrib" in the Script Library that will return the Custom Attribute you desire.