NetXMS Support Forum

Hi!

I've found a bug (or feature ). NetXMS expects that every node which have IP address is bound to at least one IP subnet. Usually this is done automatically during configuration poll. As you have configuration polls disabled, subnet bindings never occurs, and so on startup server considers these nodes as problematic (because they dos not have subnet binding) and fails to load them. I'll change this in next release. As a workaround for current version you can do manual configuration poll on each node once - this will create subnet object and bind nodes to subnet. Also, you can try to replace nxcore.dll and nxdbmgr.exe with attached patched version - this should allow server to load correctly even if nodes does not have subnet binding.

Best regards,
Victor

Could you please send me screenshots of your DCI configuration?

Best regards,
Victor

Hi!

Attached is modified portcheck.nsm, which uses same timeout value as for connect to wait for data available from server, so you can use ServiceCheck.SMTP parameter like following:

ServiceCheck.SMTP(host, mail@domain, 5000)

to use 5 seconds timeout on connect and waiting for data. Don't forget that NetXMS server by default waits obnly 2 seconds for results from agent, so if your check takes longer time, you need to increase value of server's configuration parameter AgentCommandTimeout.

Best regards,
Victor

Looks like database is damaged for unknown reason. If I understand correctly, you are running NetXMS server as a service, and database corruption occurs if you restart your PC. I suspect that during shutdown server process terminated before it completes database update, so database becomes inconsistent. To check it, could you please do the following:

1. Run nxdbmgr with debug level 6 (by adding -D 6 to netxmsd.exe command line)
2. Before restarting PC, stop NetXMS Core service manually
3. Restart PC and check database for correctness

If there will be same problem, send me debug log. If problem will disappear, try to restart PC as usual (without stopping NetXMS service), and if problem will appear, send me debug log.

Best regards,
Victor

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

Hi!

Looks like a serious bug. Could you please run netxmsd with full debug on (by adding option -D 9) and send me debug log?

Best regards,
Victor

Quote from: Sumit Pandya on December 06, 2010, 04:33:54 PM
Dear Victor, The script you shared did not worked. I tried to "Test" above transformation with Test value = 2(random), I get error "Error 14 in line 2: Left argument of -> must be a reference to object". I further added a check
if (node2 == null)
      return 0;   // No such node or access denied

and surprisingly I get this "0" returned. Please note that my nodes are part of cluster. Is that could be limitation?

Did you set trusted nodes as described here: https://www.netxms.org/forum/configuration/nxsl-and-dci/msg4633/#msg4633? Most likely it's an access control issue.

Quote from: Sumit Pandya on December 06, 2010, 04:33:54 PM
Using the approach you suggest, I may loose information of my one node. I just wonder if you can have some push method from scripting. Can I create a dummy node, define data collection with origion "Push Agent". Then define a schedule to run every minute "1 * * * *". Finally do something like below into Transformation?

node1 = FindNodeObject($node, "system-1");
value1 = GetDCIValue(node1, FindDCIByDescription(node1, "Auth-Req"));
node2 = FindNodeObject($node, "system-2");
value2 = GetDCIValue(node2, FindDCIByDescription(node2, "Auth-Req"));
return value1 + value2;

I'd even fine if database triger level of twick can be done as some very advance level.

You can create additional DCI with source "Internal" and name "Dummy" (of course description can be any). It will always have value of 0, and you can schedule it like any other DCI and use transformation script to get values from two "real" DCIs and sum them.

Best regards,
Victor

If everything is set up correctly (device responds to SNMP requests from NetXMS server and provides information via CDP MIB) you should see picture like attached.

Also, may be I didn't understand your question correctly - NetXMS is able to collect information from CDP-enabled devices (like switches or routers) and display it. NetXMS server or agents by itself does not work as CDP peers.

Best regards,
Victor

Hi!

You can use transformation scripts to get values from different nodes and sum them up to value of current DCI. For example, if you have DCIs named "Param1" on nodes node1 and node2, you can create the following transformation script on node1 to add up value from node2:


node2 = FindNodeObject($node, "node2");
value = GetDCIValue(node2, FindDCIByDescription(node2, "Param1"));
return $1 + value;


See also the following topics:
https://www.netxms.org/forum/configuration/findnodeobject-not-working-%28for-me%29/
https://www.netxms.org/forum/configuration/nxsl-and-dci/

Please also note that if you are using server older than 1.0.8, you must explicitly define main function in your script, i.e.


sub main()
{
   node2 = FindNodeObject($node, "node2");
   value = GetDCIValue(node2, FindDCIByDescription(node2, "Param1"));
   return $1 + value;
}


Best regards,
Victor

Yes, you can see topology information for CDP-enabled devices (on "Topology" tab).

Best regards,
Victor

Hi!

NetXMS server has it's own user database. Default login name is admin with password netxms.

Best regards,
Victor

Да, я так и понял. Я и имел ввиду, что даже на локальном по отношению к серверу агенте надо прописывать адрес его самого, не только 127.0.0.1.

Да, новая консоль рассчитана на работу с сервером 1.0.8.

Hi!

During configuration poll, NetXMS server tries to detect SNMP agent by sending requests for OID .1.3.6.1.2.1.1.2.0. If agent present, but does not respond to this request, it is considered as unavailable. Later during data collection, if node is not marked as SNMP-capable, SNMP DCIs not collected - the only exception is DCIs with custom SNMP ports. If you SNMP agent which does not support standard MIB-2 OIDs, then better way is to disable SNMP for given node and set port number explicitly for each SNMP DCI.

SNMP requests to port 260 generated during configuration poll in attempt to detect Check Point SNMP agent.

Best regards,
Victor

Выложил обновленную версию консоли (названия файлов не изменились). Попробуйте.