NetXMS Support Forum

Hello Victor ,

Hope you are doing well.

The database is:
~# mysql -V
mysql  Ver 14.14 Distrib 5.5.40, for debian-linux-gnu (x86_64) using readline 6.2

NetXMS server version is

:~# netxmsd -v
NetXMS Server Version 2.0.7 Build 8076 (2.0.7-RELEASE-5-g3f73792) (NON-UNICODE)
NXCP: 3.47.1.4 (AES-256, Blowfish-256, 3DES, AES-128, Blowfish-128)

NetXMS agent that collects the DCI is:

# nxagentd -v
NetXMS Core Agent Version 2.1-RC1 Build 9010 (UNKNOWN) (UNICODE)

The DCI is a simple Agent ping with source the NetXMS Agent server (screenshot attached).

Describe of the table attached as screenshot.

I haven't made any configuration changes on the DCI since i made this post, now i can see that the time stamps are not exactly the same as before. But the issue stays similar. Two values one 0 and one 100 in less interval than the configured (100 seconds).

Hello team ,

I am observing strange issue where every time a DCI for ping on a particular devices is polled it result in two values (example attached). Checked in the database, the values there are the same:

|  261543 |      1509960003 | 100         |
|  261543 |      1509960003 | 0           |
|  261543 |      1509960103 | 0           |
|  261543 |      1509960103 | 100         |
|  261543 |      1509960203 | 0           |
|  261543 |      1509960203 | 100         |
|  261543 |      1509960303 | 0           |
|  261543 |      1509960303 | 100         |


Any idea what is causing this or how can be fixed ?

Hello Victor, team,

I am using SNMP to collect this. The server version is 2.0.7 and the agents are NetXMS Core Agent Version 2.1-RC1 Build 9010 (UNKNOWN) (UNICODE).

Best regards,
Adrian

Hello Team ,

I am monitoring the up time of all my devices using NetXMS. During some circumstances NetXMS can't get any value from devices and fill that missing value with 0 (resulting in triggering false positive alarm for system reboot). Is this made by design and is there a way to fix this or some kind of workaround. Screenshot attached (in the database it looks like there is no value, but in the console application there is 0)

Best regards,
Adrian

Hello ,

I have a script which returns custom attribute to my devices. Now i made a script as external parameter which i am using as DCI. I set up everything and it seems to be working.
I am passing two parameters to the DCI first one is from the custom attribute script and the second one is the node_primary_ip. I am applying this in a template, as follows:

RStatus(%{script:CustomAttributeSetScript}, %{node_primary_ip})

This is returning the correct parameters in the DCI, but the DCI is not polling at all. If i want to get status for the DCI i must force poll it. If i give the Custom Attribute parameter value manually it is working with no issue and polling on the interval I set up.

Best Regards,
Adrian

Hey Tursiops,

As expected putting "return" statement in the script solved my issue. It is working like a charm now.

Again, thanks for the help!

Wish you all the best.

Hello Tursiops, team,

You made me think about it and i suppose you are right, in the script we are setting the value of the custom attribute, but doesn't "return" a value. Maybe this is the issue. This is not my script and since it is working I assumed the fault is not in it. Unfortunately i will not have time to check this today, but i am pretty sure you solved my issue. I will update when it is done!

Thanks very much for the time spent and the help!

Best regards,
Adrian

Hello Tursiops, team,

Thanks for the input mate. I saw your old post and tried this, unfortunately it is still not working even if i re-apply it on the device from the template.

Here is how it looks on the device itself:

RStatus(, 172.20.4.254)

So it is either not cool with my syntax or something else that i am missing. I am pretty sure the script is working as i am using it in another configurations.

As regards to changing the parameter "on the fly" It will be a nice feature, but in my case it would not be needed.

If you have any further advice i will be glad to hear.

Best regards,
Adrian

Hello Team,

I am using external parameter for DCI and script for custom attribute.

Now i am trying to use the custom attribute and node_ip variables in my templates, so i won't have to give the parameters on each DCI manually.

I am trying the following:

RStatus(%{script:CustomAttributeSetScript}, %{node_primary_ip})

The admin guide says that i cannot use the custom variable directly and i must get it from the script with syntax as above. Unfortunately this is the part i am failing on.

Any advice on what is wrong with my syntax will be highly appreciated.

Best Regards,
Adrian

Hello Team ,

Issue is solved. The problem was with the time for the SQLlite select query (it was taking too long 40-50 seconds). It was solved by backing up the local database. separating it in small pieces and import the pieces one by one.

Hello Team ,

It seems that only agent version 2.1-M1 supports:

DataReconciliationBlockSize = ****
DataReconciliationTimeout = ******

still I haven't had the chance to test all the versions. We noticed that the agent sends DataReconciliationBlockSize on every 30 seconds which means 2048 in a minute. Is there an easy way to make it send more often ?

I can solve the issue here only with deleting the local database of the agent. Once deleted everything starts working perfectly. However this is not suitable solution for us. What can be done in such situations where the agent must constantly sends big amounts of data and still flush the cache ?

I noticed that the agent send the cached data "1st in 1st out". In our situation it will be better to fill in the latest data first, this way we will kind of minimize the impact of the issue, as we will know what is happening in the monitoring in real time, not 2 days back as we are in the moment. Is there a way to control how the agent sends the data ?

Hello team ,

I have NetXMS server 2.0.7 installed and agent 2.1-M1. The issue:

The server crashed for some time and the agent cached all the data, its about 600MB, and now i can see that it is sending the data pretty much with the rate it is collecting. So this means it will never fill in all the data in the server. On version 2.1-M1 of the agent i can change parameter:

DataReconciliationBlockSize = ****

But the server wont receive block size bigger than 1024, in the change log of the version:

- Agent data reconciliation block size and timeout can be configured

1. Does this mean that server 2.1-M1 will accept blocksize bigger than 1024. Will this speed up the process of filling up the old data?
2. Is there any other way i can dump the data from the agent and manually insert it in the server database?
3. If not, is there any other way i can speed up the process.

any help would be greatly appreciated.

Best regards,
Adrian

Hello Team ,

I have a question for notwork discovery. I checked a lot of topics in the forum, but couldn't get my answers.
My server is 2.0.7 version and most of the agents are 2.1-M1 (the rest of them are 2.0.8 ).

1. Does the server tell all the agents to search for the subnets/addresses pointed in the network discovery configuration tab or the network discovery is working only for networks directly connected to the server. In short is the network discovery over agent supported ?
2. If Yes, can i tell to a specific agent to look for specific subnet/iprange with a specific snmp community (or indeed it will use only the default community).

3. Is there a way to manually start the network discovery or i depend on polling interval ?

4. If the discovery over agent is not supported, is there an easy way to add more than 200 nodes in netxms?

Best regards
Adrian

Thanks for the help !

Best Regards,
Adrian

Hey Tomas ,

Thanks for the fast response.

So it is better to use

migrate <source> | Migrate database from given source

which means:

nxdbmgr migrate <IPaddressOftheOldMachine>

Is it that simple or i need to follow this : https://wiki.netxms.org/wiki/How_to_migrate_to_another_database

I actually need the data and the database is about 170GB so i guess it will be a slow process.

Best Regards,
Adrian