NetXMS Support Forum

Are you monitoring any other SNMP devices (just to exclude general server problem regarding SNMP like closed ports on firewall)?

Check SNMP version in node properties and community string. Try doing Full configuration poll. If there were problems communicating with node via SNMP when the node was added, netxms will not set isSNMP flag and will not try communicating via SNMP. This flag can be visible in Object Details on the right-hand-side under Capabilities.

There are two ways of doing ICMP pinging.
- Collecting parameter from agent. Agent should have ping.nsm subagent enabled. E.g. Icmp.PacketLoss(target) - origin in DCI properties should be "Agent".
- Server periodically pings nodes and collects statistics. This statistics are available via DCIs of origin "Internal".

See for more information https://www.netxms.org/documentation/adminguide/icmp-ping.html

Для VLANов что-то может быть просто не реализовано.
Чтоб лучше понять, что происходит - в Tools->Sever console можно дать команду
trace <id одной ноды> <id другой ноды>

Do you monitor Cisco Nexus devices?
If yes, this could be related to a bug with recent changes in Nexus driver. That bug is fixed, fix will be included in next patch release.

You can set expected states of interfaces to "IGNORE". This could be done automatically from HOOK::ConfigurationPoll - it's a script that is launched on each configuration poll.
interfaces = GetNodeInterfaces($node);
foreach(i : interfaces)
{
SetInterfaceExpectedState(i, "IGNORE");
}

Obviously you need to add some filters - you can check if node has agent ($node->isAgent), etc.

Hi!

It can be a script, but only one filename in it's output is accepted. Usually, when we need to monitor an application, this application writes data to only one log file at a time. If we need to monitor several applications, we specify several files or log parser definitions.
Documentation was updated with possible ways of using macros and scripts to get file name - https://www.netxms.org/documentation/adminguide/log-monitoring.html#file-tag
For script you just have to put script name in backticks like: `/path/script.sh`

Regarding console from Tools menu - check "Access server console" user right.

try deleting libraries that were installed by older version, these are libnx* libnetxms* files in /usr/local/lib/netxms and /usr/local/lib
then make & make install again

Netxms updates on linux are available, only support for jessie was dropped, that's why it's stuck on 2.2.

Currently supported are Debian 9 (Stretch) and 10 (Buster) so you might need to upgrade the OS.

Upgrade of NetXMS most probably will happen automatically, but it's strongly recommended to do it first in testing environment and have DB backup/snapshot prior to upgrading.

1) The chosen operation is not enabled - how's the server is specified in agent config? Is it MasterServer, ControlServer or Server? Should be MasterServer to be able to edit config file remotely.
If this is not the reason, I suggest to upgrade to a current version - current one is 3.7. Could be that there were some issues with that on 2.2.

2) As for automatically including primary host name into config, all necessary functionality is available starting from v.3.6:

First of all, you need to use configuration policy for that. Configuration policy is configured in a template (right click on a template -> Agent policies).
Configuration policy allows to specify a part of agent config. These parts are uploaded to agent system and merged together on agent start.
Changes in configuration policies require agent restart to get applied (except for lines in [ENV] section of config - this is applied on the fly). You can collect agent parameter Agent.IsRestartPending to determine, if agent received new configuration policy and execute agent restart action from EPP.
In configuration policy there's checkbox "Expand macro". If it's set, the macros are expanded (see https://www.netxms.org/documentation/adminguide/event-processing.html?highlight=macros%20event%20processing#macros-for-event-processing)

MIB files only provide a more convenient way to work in MIB explorer.

SNMP driver is selected from a number of drivers present in the system. List of drivers is available in docs: https://www.netxms.org/documentation/adminguide/snmp.html?highlight=snmp%20driver
These drivers provide special handling for some devices that are not handled well by generic driver.

Hi!

1) as discussed in another thread, under linux logger utility could be helpful to generate syslog messages
2) A matched syslog line generates an event, so we have to do the logic in Event Processing Policy (EPP). There you have filtering script - if it's not empty, event will be processed further only if that script returns true. You can just take current time in that script and check it:
now = localtime();
return (now->hour >= 8);

3) I am not exactly sure how to use the repeatCount in syslog processing, but anyway reaction to syslog only happens when a new syslog message is received. Here we need something in another place that would be executed regularly, event if there will be no syslog messages from a given node. A possible approach could be:
- when you receive backup successful message, store current unixtime in custom attribute of the node. You can do this in filter script in EPP:
$node->setCustomAttribute("lastBackupTime", time());
- create a DCI with origin "Internal" and parameter "Dummy".
- in transformation script add the following:
return time() - $node->getCustomAttribute("lastBackupTime");
as the result this DCI will have time in seconds since last backup.
- add threshold so that an event will be generated when time since last backup is too big.

Quote from: NicovdWalt on January 04, 2021, 11:25:23 AM
Good day,
I also did the update to 3.7.95 today and it keeps failing to start.
Centos 7.9

Check /var/log/netxmsd for any errors (or run       netxmsd -D5     in this case it will put log messages right to the console).

For active discovery do you specify particular proxy in "Active Discovery Targets"?

Do you have ping.nsm subagent enabled in proxy's configuration file?

Try abort instead of return null:

if ($1 < -100) {
  abort;
} else {
  return $1;
}