NetXMS Support Forum

Quote from: nichky on August 01, 2025, 03:26:06 PMyes the one that i'm using is
/netxms-agent-mikrotik , so i need to install WebUI and acces :expose :8080/:8443.

are we on the same page?

you need to install server + web somewhere.
then you can add mikrotok to the system and collect data over SNMP.
agnet on the mikrotik is required only if you want to install it on the customer's firewall, for example (so you can get access to the NATed network)

Quote from: nichky on August 01, 2025, 03:06:27 PMThansk Alex

so this is i'm expecting.
Since the container is running i should be able to log in to netxms (similar to how i'm doing on windows) via web using ip:8080 , ip:4700 or ip:4701

You are mixing up monitoring server, web, and agent.

Monitoring server (netxmsd, "NetXMS Core" service) listens on port 4701, you connect there using desktop client.
Server do all the scheduling, data collection, and processing. Collection can be done via multiple procorols - SNMP, native agent, SSH, etc.

WebUI - expose :8080/:8443, you connect there with the browser. WebUI transparently connects to the monitoring server.

Agents listen on port 4700 (they can go in reverse as well). Server connects to the agents to collect data / perform tasks.



So no, you do not connect to the agent with the browser. You could register it in the monitoring instead, and configure metrics you want to monitor.

what do you mean "can't login"? it's an agent, not a server.

Quote from: nichky on August 01, 2025, 01:09:40 PMpls, how to fix the the accessing to ssh from NetXMS?

check that:
1) you saved and applied properties before test
2) you are running latest version of the system.

I've just checked, and custom port works just fine.

Quote from: nichky on August 01, 2025, 08:46:24 AMbut we have options that we can run netxms on MikroTik container?

yes, you can run agent on the mikrotiks. normally, it's enough to collect information via SNMP. Agent is mostly used for running zone proxies (e.g. with network behind NATs). Full instructions are on the GitHub page.

Quote from: nichky on August 01, 2025, 12:52:40 AMthis is what im gettign

C:\NetXMS\bin>nxsnmpwalk IP 1.3.6.1.2.1.2.2.1.2
Unable to create UDP transport: Invalid hostname or IP address

Replace "IP" with actual IP of the router in question.

That's the whole command. Replace "IP" with actual IP of the router in question.

C:\NetXMS\bin\nxsnmpwalk IP 1.3.6.1.2.1.2.2.1.2


.1.3.6.1.2.1.2 is a base OID for IF-MIB.

something like "nxsnmpwalk IP 1.3.6.1.2.1.2.2.1.2" should fetch list of interfaces.

what you mean by "getting a graph on some of the interfaces"?

can you query .1.3.6.1.2.1.2 on the routers where interfaces are not reported?

Increase sever debug to level 6 (either globally or for tag ncd.smtp), then check server logs for errors. SMTP driver logs with tag "ncd.smtp".

Do you install from packages or build from source?

Looks like webapi module was not packaged in 5.1. I recommend you to upgrade to latest (5.2.4 at the moment) version.

what's in the logs? Also ",Y" is not required anymore, it's default now.
Which version of the server you are using?

In next patch release

If I understand your correctly, this should be enough:

InetAddress("10.5.3.0", 24).contains($node.ipAddress)

This autobind script will collect all 10.5.3.0/24 nodes into container.
$node.ipAddress is detected management address, if you want to do it based on the interfaces:

for (i : $node.interfaces) {
  for (addr : i.ipAddressList) {
    if (InetAddress("10.5.3.0", 24).contains(addr)) {
      return true;
    }
  }
}
return false;