NetXMS Support Forum

Are you sure that the other monitoring software is using exactly SNMP, not some proprietary protocol? Does it use standard SNMP port?
You can try capturing communication of that software to the router with Wireshark and compare what network packets it's actually sending.

also you can try getting some data via SNMP using snmpget package from netsnmp software https://sourceforge.net/projects/net-snmp/files/net-snmp%20binaries/5.5-binaries/net-snmp-5.5.0-2.x64.exe/download

Mapping tables might better just for the reason of not disclosing the addresses to 3-rd party and for reliability.

You can add this script to script library and then use macro %[name_of_script] to get mac address of that node's interface that has primary IP address.
mac = NULL;
for (i:$node->interfaces)
{
  if ($node->ipAddr == i->ipAddr) mac = i->macAddr;
}
return mac;

TCP connection to port 44818 happens on the next step of configuration poll - that's an attempt to connect via Ethernet/IP protocol. It's a protocol used in industrial devices. Your router is answering with RST - it says that this port is closed. This is normal.
The part related to SNMP is above. You can see that NetXMS is sending SNMP request that have three OIDs in it - 1.3.6.1.2.1.1.2.0 and so on. The is no reply, so the request is being repeated multiple time.

It could be that the router does not like that three OIDs are requested simultaneously. You can try turning on server configuration parameter SNMP.Discovery.SeparateProbeRequests, then only one OID will be requested at a time.

Note these lines in configuration poll:
[15.01.2021 12:10:10]    Checking SNMP...
[15.01.2021 12:10:24]    No response from SNMP agent
For some reasons netxms is not able to receive response from that router. There are two options:
- problems with network/firewall/etc so that packets are not getting to where they should
- this router does not understand the way how netxms created SNMP request and does not reply.

I would suggest capturing communication between netxms and this router using tcpdump or Wireshark. If you need help in doing that, please inform, if your netxms is running on linux or windows.

As per above screenshot - you are using parameter of origin "Internal". In this case, the parameter should be just "Icmp.PacketLoss" and it will return stats for pinging node's primary host name. Option for specifying IP address in brackets if for situation, when you set checkbox "Collect ICMP response statistics for this interface" in properties of an interface of a node.

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)