NetXMS Support Forum

Quote from: stevenlamb on April 14, 2015, 05:44:02 PM
I now feel double silly. it works with the correct version. thank you for your attention on this.

to be clear. i followed the instructions on the youtube video and made a mistake assuming that the devel version was the same as what i got from apt. once i found the same version in the archives it worked as expected.

SOLVED

The NetXMS apt repo is currently being migrated to a singed repo and there are a few issues, causing 2.0-M3 to not be present in the apt repo yet.

Should be resolved soon (hopefully).

Sorry for the issues it caused you

If you look at the raw communication (wireshark / tcpdump), do you actually see SNMP responses in there as well, or just SNMP requests?

Which NetXMS version are you using?

Are you using SNMP v2c or v3?

Do you have the proper SNMP communities/credentials configured in Configuration > Network Discovery?

Need more information:

What NetXMS version?
What database used?
How many DCIs in the graph?
What collection interval for each DCI?
What graph refresh interval?

In your example
global GlobalStringConstant = "String Value";
Is never executed

Please read this article:
https://wiki.netxms.org/wiki/UM:NetXMS_Scripting_Language_(NXSL)#Script_entry_point

You implicit main is never executed, since you have an explicit main.
Therefore, the variable "GlobalStringConstant" is never initialized.

If its enough to see if the proper processes are running, you can use this to monitor the Exchange processes on the server using SNMP:
https://wiki.netxms.org/wiki/OS_process_monitoring_using_SNMP

You can also do this using the Agent.

You can also monitor the the node is accepting SMTP, using a service check if needed.

Hi,

1) You can do this by monitoring the logs on the DC.
The agent can monitor the Windows logs, so when in the logs you find a user logging on, generate an event and do whatever you want to do then.

2) Regarding SMTP auth, see this thread:
https://www.netxms.org/forum/feature-requests/smtp-authentication/

Please post your /etc/nxagentd.conf

There is no OID for memory usage percentage.
Using SNMP, calculating memory usage is always:

MemUsedPercentage = ((MemTotal / MemUsed) * 100)

There are multiple way to achieve this in NetXMS.
Easies is probably:

1) Create DCI for MemTotal.
2) Create DCI for MemUsed.
3) Create DCI for MemUsedPercentage (dummy type)
Use a transform script that does the calculation above.
Take the values from the DCIs you created above.

You have to do it like this in every other NMS, this is not a NetXMS defect.

First thing I would try is specify the DB server address as a FQDN.

Let us know if that helped.

Show us the netxmsd.conf please (feel free to remove sensitive info).

2.0M2 is actually more stable and bug-free then 1.2.17.
You can see from the change-logs that M1 and M2 dont have critical system changes.

I would definitely recommend M2 over 1.2.17 because of bug fixes that are in there.

M3 will have major changes tho, so your point is valid for M3.

It depends on what the printer can do, and what kind of data the printer provides over SNMP.

We monitor all supply levels on our printers (toner, fuser, transfer kit, etc...) - these are higher model HP LaserJets.

This topic is stickied in General Support:
https://www.netxms.org/forum/general-support/netxms-video-tutorial-series/

This series should give you all you need to get started.

Any chance you have "Do not save collected data to database" checked for that particular DCI?

Is it just one DCI or all DCIs?