NetXMS Support Forum

Try to run the following command on management server:

nxget <agent_ip> Test

What result you get?

Best regards,
Victor

Yes, I plan that next release will be 1.2.0. Current 1.1.x branch is stable enough to consider it new production version and drop 1.0.x branch.

Best regards,
Victor

Hi!

Not all. I think that NXSL script should not access external files or programs. If you need that in actions, you can run external script as an actiopn. But access to other objects are possible now. There are few functions which allows you to search for nodes and other type of objects.

Best regards,
Victor

Hi!

No, it isn't. Actually I don't touch this file for years. Many of featrures listed in that file already implemented, but some really important still not Currently I maintain my ToDo in internal Jira. Current list of open issues scheduled for 1.2.0 release looks like this:

Bug

    [NX-75] - Button "Test" is not working on DCI transformation property page
    [NX-80] - Reports not working on Windows
    [NX-89] - Cannot delete non-existent object from event processing policy

Improvement

    [NX-3] - Ability to set native agent port on node creation
    [NX-4] - Add support for INFORM messages in trap receiver
    [NX-7] - Apply policy to node by clicking on node and selecting policies from list
    [NX-18] - Improve dashboard configuration tools
    [NX-57] - Add certificate authentication to Java console
    [NX-85] - Implement drop column functionality for SQLite
    [NX-87] - Add web interface to WIndows installer

New Feature

    [NX-2] - Autodiscovery: user should be able to set default settings for discovered nodes (e.g. no agent, no snmp)
    [NX-5] - automatically create ChildStatus DCI when Network Service object created for Node
    [NX-10] - Use Spanning Tree data for network discovery
    [NX-33] - Implement configuration export in Java console
    [NX-35] - Implement concept of "normal" interface state
    [NX-38] - Add additional page for containers where threshold violations for underlying nodes are shown
    [NX-43] - Allow per-DCI SNMP version settings
    [NX-50] - Add possibility to add parameters and/or specify entry point in scripts called via %[] macro
    [NX-51] - Ability to copy/paste scripts in script library
    [NX-63] - Timed alarm acknowledgement
    [NX-71] - Add new policy type for distributing log parsers
    [NX-88] - Implement data export from log viewer
    [NX-90] - Implement alarm comments

Best regards,
Victor

I'm actually slowly moving towards ultimate goal - be able to do all this from NXSL scripts. Starting from 1.1.10 you already can run NXSL script as an action. Now I just need to add all necessary Create... functions.

Best regards,
Victor

Do this node have correct IP address on interface object too?

Hi!

From this log I can see that command executes for too long, and command execution timeout expires first. Default timeout is 2 seconds. You should increase both ExecTimeout parameter on agent and AgentCommandTimeout configuration variable on server.

Best regards,
Victor

Hi!

Because delta calculation is done by server after data obtained from node as part of DCI processing. When you do queryParameter call, it just reads raw value from end node - it is not related to any DCI. You either have to do delta calculation by yourself or use another API call to get last values of particular DCI.

Best regards,
Victor

Can you please provide as much information about this object as possible: IP address, operating system, device type, list of interfaces. etc.?

Best regards,
Victor

Hi!

The main problem with driver development is access to appropriate equipment for testing. Unfortunately I cannot have access to Cisco Nexus devices. If somebody can help with access to test equipment it will greatly improve and speed up driver development process. There are also plan to create framework for drivers written in NXSL - it probably will allow users to create drivers by themselves.

Best regards,
Victor

Hi!

Unfortunately there are no normal way to locate object by ID. You should manually check all objects with that name. Added that to feature requests.

Best regards,
Victor

No, it's not related. Poller thread will start only if you have one or more ExternalParametersProvider options. Please give more details about your configuration - agent config, DCI configuration, etc. Also, did you restart agent after you specify new external parameter?

Best regards,
Victor

Origin should be set to "NetXMS agent". And yes, parameter name should be company.ParameterChecke

Best regards,
Victor

Povtorit' problemu u sebja mne ne udalos', tak chto skoree vsego eto svjazano so sborom kakogo-to konkretnogo parametra. Mogli bi prislat' polnij log agenta s kljuchom -D 9 s momenta zapuska i do momenta, kogda on nachinaet zagruzat' CPU? Mozno slat' na [email protected].

As seconds part of timestamp is in range 02-06, and never 00, I assume that it's an execution timeout problem. There are two places where additional information may appear:

1. Server log. If you turn on debug to level 7, you should see in server log something like this:

Node(node_name)->GetItemFromAgent(parameter_name): timeout; resetting connection to agent...

But turning on debug level 7 on server will produce a really huge amount of records in the log.

2. Agent log. If you run agent with debug level 4, you should see debug messages related to command execution - these messages will be prefixed with text "H_ExternalParameter".

I would start with agent log. Please note that you should change logging to file before running agent in debug mode, otherwise it will flood system log.

Best regards,
Victor