NetXMS Support Forum

Currently there are no way to do this. I'm also facing this problem, so next version will definitely have this feature

Best regards,
Victor

Hi!

It's not implemented yet.

Best regards,
Victor

Hi!

Current version of Java console does not support saving graph as predefined, it is only possible from legacy console. We will fix it in 1.2.1.

Best regards,
Victor

Hi!

Are you sure that you recompile everything? Also, check protocol version number in netxms-version.h and in Java client (in class NXCSession).

Best regards,
Victor

Hi!

Windows 2000 is not supported by 1.1.x and 1.2.0 agents. You can try to use agent version 1.0.13 on Windows 2000 (it is compatible with newer server versions).

Best regards,
Victor

One correction - you don't need to set EnableProxy = yes on agent for this configuration to work. It's a bit confusing, but it's a different things - agent proxy and proxy DCI. Agent proxy (configured on communication tab in node properties) is connecting to remote agent via proxy agent. Proxy DCI - displaying DCI on one node but really collecting data from another (proxy) node. It could be any type of DCI, including internal.

As for Icmp.Ping, it's more about using preconfigured targets in ping subagent (configured via Target = xxx parameter in PING section of nxagentd.conf) and then Icmp.AvgPingTime instead of Icmp.Ping for collecting data. But if you have hundreds of ping targets, then separating them between several nodes could be a good idea too.

Best regards,
Victor

Hi!

It will be possible in 1.2.1. We have added NXSL functions for SNMP (http://wiki.netxms.org/wiki/NXSL:SNMPSet for example). Then you will be able to put SNMPSet call into DCI's transformation script.

Best regards,
Victor

Hi!

This feature will be implemented in Java console in version 1.2.1. It was planned to be there in 1.2.0, but somehown was forgotten

Best regards,
Victor

Hi!

Expected interface state can be set in interface object's properties, on "Polling" tab. There are 3 possible values:

UP (default) - interface expected to be up. If not, interface object goes to CRITICAL state and SYS_IF_DOWN event generated.
DOWN - interface expected to be down. If it is up, interface object goes to CRITICAL state and SYS_IF_UNEXPECTED_UP event generated.
IGNORE - interface status is of no interest. Interface object will always be in NORMAL state, regardless of link status.

Please note that administratively down interface will still be placed into DISABLED state, regardless of expected state setting.

Best regards,
Victor

Hi!

Windows 2000 is not supported by 1.2.0 agent. I got unexpectedly high number of complains regarding this, so I'll check if it is possible to made agent compatible with Win2000 again. Currently, you can use agent version 1.0.13 for Windows 2000. It's available here: https://www.netxms.org/download/archive/agent_packages/nxagent-1.0.13.exe.

Best regards,
Victor

Hi!

It's definitely should not be like this. I'll try to reproduce this on my test system.

As for bug tracker, we use Jira internally, but because we have very limited number of licenses, we cannot open it to the public. And public bug tracker is very inactive, but I see those issues and will fix them. I have added 1.2.0 and 1.2.1 versions to public bug tracker.

Best regards,
Victor

В WinPerf субагенте есть возможность использования английских названий счетчиков, но только для параметров, определенных в субагенте (через Counter =). Я добавлю в TODO сделать то-же самое для PDH.CounterValue.

Hi!

Currently you can do this using PING subagent. You can load it on agent on management server itself, and configure Icmp.Ping parameters for all nodes you want to ping. If you wish to have those parameters on each target node and not on management server node, you can do this by configuring Icmp.Ping parameters on target nodes and setting proxy node to management server node.

Best regards,
Victor

Это довольно странно - протокол используется один и тот-же и в старой консоли, и в новой. А когда ошибки бывают чаще - при открытии графика или при обновлении?

Hi!

Yes, it's problem in version 1.2.0. It is fixed in upcoming 1.2.1 release.

Btw, why you still using legacy console?

Best regards,
Victor