NetXMS Support Forum

Hi!

This bug is inside console application - it is not related to server. I also have console hang from time to time, but still unable to find the source of the problem.

About logarithmic option: I have added functions log, log10, and exp to NXSL - they will be available in next release. I will also add logarithmic scale option to graph window in console.

Best regards,
Victor

Hi all!

Version 1.0.0 is out. It fixes some bugs found in 1.0.0-rc2, and contains minor improvements in server and Windows management console. Also, DRBD monitoring code in Windows subagent was rewritten to use proc file system and now should be compatible with modern DRBD versions.

Full list of changes since 0.2.31:

- System configuration (events, SNMP traps, templates, event processing rules) can be exported and imported in XML format - this solves various problems with old NXMP files
- NXSL improvements:
        - New functions: GetDCIObject, GetInterfaceName, FindNodeObject, trace
        - Added built-in constants TRUE and FALSE
- Added support for encrypted DB passwords in netxmsd.conf
- Improved SNMPv3 support
- Windows management console: implemented object search by comments
- Linux subagent: DRBD monitoring rewritten
- Fixed issues: #62, #278, #283, #290, #292

Best regards,
Victor

Spasibo, ispravil.

Hello!

I assume you have Windows workstations. There are no built-in mechanisms for initial agent deployment (but there are centralized upgrade feature). For initial deployment, you should use Active Directory functionality or some third party product for software distribution. To assist in this task, agent installer can run in unattended mode. Agent installer has various command line options for unattended installation. These options are following:

/SILENT Don't show installation wizard, only a progress bar;
/VERYSILENT Don't show anything;
/SUPPRESSMSGBOXES Don't ask user anything;
/DIR=path Set installation directory (default is C:\NetXMS);
/SERVER=address Set address of master server (will be written to generated agent's configuration file as value for MasterServers parameter);
/SUBAGENT=name Enable subagent name;
/NOSUBAGENT=name Disable subagent name.

Valid subagent names are ECS, LOGWATCH, PING, PORTCHECK, WINPERF, and UPS. By default WINPERF is enabled and all others are disabled.
For example, to install agent silently (without any messages or progress bars), use Windows Performance and PING subagents, and set NetXMS management server address to 10.0.0.1, run the following command:

nxagent-1.0.0-rc2.exe /VERYSILENT /SUPPRESSMSGBOXES /SERVER=10.0.0.1 /SUBAGENT=PING

Best regards,
Victor

Hi!

For System.ServiceState parameter, you should specify service name - don't be confused with display name you see in "Services" in MMC. Service name can be seen in service properties. System.ServiceState returns service status code, which can be one of the following:

0 - service running;
1 - service paused;
2 - service starting (start pending);
3 - service pausing (pause pending);
4 - service starting after pause (continue pending);
5 - service stopping (stop pending);
6 - service stopped;
255 - unable to get current service state.

So in threshold you have to check if status code not equal 0 and if it is, generate appropriate event. The following discussion could also be useful:
https://www.netxms.org/forum/index.php/topic,166.0.html

Best regards,
Victor

There are no limitations on client IP addresses. What exact error you get when connecting from remote PC?

Best regards,
Victor

V nastrojkah kazdogo DCI est' punkt "retention time" - eto srok hranenija sobrannih dannih v dnjah. Znachenie po umolchaniju pri sozdanii novogo DCI - 30 dnej.

It's a bug. I've fixed it for next release.

Best regards,
Victor

Hi!

Currently I suppose that problem is in incorrect device response when using SNMP version 2c (or probably incorrect request from NetXMS, but I've never seen such behavior with any other devices). I'll add an option to disable automatic SNMP version detection during configuration poll so you will be able to force usage of SNMP version 1 and we will see if this helps.

Best regards,
Victor

Dobrij den'!

Vneshne pohoze na problemu, opisannuju zdes': https://www.netxms.org/bugtrack/view.php?id=279. Mozno li prislat' config.log s etoj mashini?

Best regards,
Victor

It's very strange. From the dumps I see that getif uses SNMP version 1, but NetXMS - version 2c. Could you try to change node configuration in NetXMS to use version 1 and do configuration poll?

Best regards,
Victor

Hello!

Could you please run nxsnmpwalk on your switch for OID .1.3.6.1.2.1.4.20.1, like this:

nxsnmpwalk <switch_ip> .1.3.6.1.2.1.4.20.1

and post output here?

Best regards,
Victor

Hello!

You should not install x64 agent into same directory as x86 server - it will replace some common DLLs (like libnetxms.dll) with 64bit version. You should stop and remove x86 agent service created by server installer (by running nxagentd -R command), and then install x64 agent into separate directory, then copy nxagentd.conf from server's etc to agent's etc directory.

We do not plan to build 1.0.x branch for x64 platform, but 1.1.x will have x64 version.

Best regards,
Victor

Hi!

Quote from: borislavl on March 17, 2010, 09:07:06 PM
1. Export for the NetXMS actions, event processing rules and script library

Agree.

Quote from: borislavl on March 17, 2010, 09:07:06 PM
2. Or backup of the entire server configuration

In fact, you can do this by backing up database or exporting it using nxdbmgr. If you wish to backup only server configuration without collected data, you can just skip idata_xx, event_log, alarms, snmp_trap_log, and audit_log tables.

Quote from: borislavl on March 17, 2010, 09:07:06 PM
3. Actions to be able to return a value(response from the command) to a specified DCI.

How this is different from DCI with external parameter as a source?

Quote from: borislavl on March 17, 2010, 09:07:06 PM
4. Or to call action from NXSL and receive/not receive value as response

I'm not sure that this is needed in DCI transformation and event filtering scripts. Main concern here is performance - for example, if event filtering script calls external action and waits for it's completion, it potentially could block event processing for significant amount of time.

Quote from: borislavl on March 17, 2010, 09:07:06 PM
5. From NXSL to be possible to set DCI values (activating their Thresholds as configured)

Could be implemented, but probably for "push" DCIs only (I mean allow to set value only for push DCIs).

Quote from: borislavl on March 17, 2010, 09:07:06 PM
6. Updated version for the DRBD subagent

This is one of priority changes - we have support request for this, so it should be ready soon.

Best regards,
Victor

I kak vigljadit konfig agenta?