Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - mrtur

#1
Hello,

Since upgrading to recent versions of NetXMS, I no longer receive "SYS_NODE_DOWN" events when a device goes offline. Instead, I always receive "SYS_NODE_UNREACHABLE" events—even when the affected node is simply powered off and there are no other network devices between the NetXMS server and the node.

Previously, "SYS_NODE_DOWN" would be triggered in these cases, but now it seems NetXMS always classifies the situation as "UNREACHABLE," regardless of the actual network topology or the absence of intermediate devices.

Has anyone experienced this behavior? Are there specific configuration parameters or changes in recent versions that could explain this shift? Any advice on how to restore the previous event behavior would be appreciated.

Thank you!
#2
General Support / Mikrotik agent using container
October 18, 2023, 01:32:01 PM
Hi,

I'm trying to use the Mikrotik agent using containers using theses instructions: https://github.com/alkk/netxms-agent-mikrotik

I've managed to run the container by building the docker image manually (my mikrotik RB1100Hx4 were arm and not arm64), and I've setup DNAT for redirecting ports tcp 4700 and udp 161 from NetXMS server to the container.   Mikrotik IP address is 10.1.99.1/24 on management interface, 172.17.0.1/24 on container bridge, and container ip is 172.17.0.2/24. I want to use agent as remote proxy node for monitoring of 10.1.99.0/24 nodes behind the mikrotik router (container can ping these devices).

Agent is seen in NetXMS and snmp is working, but I cannot use it as a proxy agent. I've tried to create a new zone, placed the mikrotik agent node in it, and define it as the proxy node for this zone. Then I've added the 10.1.99.0/24 subnet in active discovery settings, select the new zone and define my mikrotik agent as proxy node, but the scan doesn't discover any devices.

Am I doing something wrong? 
#3
General Support / Issues with zoning
October 17, 2023, 06:40:47 PM
Hi,

I'm new to NetXMS and I'm try to monitor ~20-30 remote sites with network devices (router, switches, access points) mainly from Mikrotik and Unifi (with SNMP enabled).

Each site is connected to Internet and linked to an OpenVPN server for monitoring and remote config. On each site there's a management network with a unique 10.1.X.0/24 subnet, containing networking devices. Users (wired or wireless) are placed in a VLAN using the same private subnet (172.16.0.0/22) on each site. I've attached a schema. 

In NetXMS I've created a container (in infrastructure tab) and a zone for each remote site. Then I add each 10.1.X.0/24 subnet in the network discovery settings (passive + active). Discovery works only if I don't specify a zone for the subnet, but doing so all the devices show up in the same Default zone. So I wrote a nxshell script to move all my device in the right zone after discovery ended.

It works, but I see lots of duplicates devices showing up constantly in netxms (I've already setup the server parameter to merge duplicates and restarted netxms), and I can't do some polls like full configuration polls after a device have been placed in a zone.

In the documentation, it seems like the right way to use zoning is by defining a proxy node in each zone, but in my case I cannot use the mikrotik routers as proxy nodes, because I cannot install the netxms agent on it. I've tried using containers, but it requires a physical opertion on each site, so its not an option right now.

What is the correct configuration to have all of my remote sites in netxms with zoning (or other solution)?

Thanks
#4
General Support / SMTP + STARTTLS notification error
October 09, 2023, 03:32:12 PM
Hi, 


I'm new to NetXMS, and I was trying to setup some notifications channels: it works well for Slack, but I struggle with SMTP which is always in error (ends up with status "Failure"  and error message "Driver error").

I've set the ncd.smtp debug level to 6, and I can see the following messages:
Sending mail with url="smtp://pro1.mail.ovh.net:587", to="[email protected]", subject="test", login="[email protected]"
2023.10.09 12:15:18.234 *D* [ncd.smtp           ] Call to curl_easy_perform("smtp://pro1.mail.ovh.net:587") failed (56: Failure when receiving data from the peer)


There is my SMTP notification channel configuration:

[email protected]
FromName=NetXMS
IsHTML=no
[email protected]
Password=my_smtp_password
Port=587
Server=pro1.mail.ovh.net
TLSMode=STARTTLS

My mail provider (OVH) needs a secure SMTP connection on port 587 with STARTTLS and authentication is required using my email/password.
There is the ';' caracter at the end of my password, so I thought the problem might be here, but even when I encode the password with the "nxencpassd" utility, SMTP notification are still in error.

How could I solve this issue?

Thanks