NetXMS Support Forum

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

Hi!

Do you get two values in the DCI history or only one? It could be possible if command executes for too long on first run, server gets timeout error, and retry. But then there should be at least two seconds between runs.

Best regards,
Victor

Perechital kuchu informacii, pohoze chto v Windows takoj parametr v principe poluchit' nel'zja.

Viktor

Poprobuju u sebja povtorit'. A mozete zapustit' agenta s kljuchom -D 9? I kakaja eto systema - 32 ili 64 bit?

Viktor

Da, ja dumal uze ob etom. Esli est' zelanie pisat' draivera na scriptah, to poprobuju sdelat'.

Hi!

Try to add lines

IMPORTS
   enterprises               FROM SNMPv2-SMI;

after line

HP-LASERJET-COMMON-MIB DEFINITIONS ::= BEGIN

Then it should compile.

Best regards,
Victor

Hi!

NetXMS Wiki is working. Address is http://wiki.netxms.org. I will try to import existing manuals into it. Anybody willing to contribute to it are very welcome I have created section called "Solutions" on main page intended for documenting specific solutions (like monitoring some specific equipment, services, etc.). Share your knowledge!

Best regards,
Victor

Hi!

Try to recompile MIBs without compression (by omitting -z key in nxmibc call) - I've seen few times that Java console has troubles unpacking compressed MIB file.

Best regards,
Victor