NetXMS Support Forum

Check configuration -> Event processing policy. 

The way NetXMS is built is that when something happenins (interface went down, threshold reached, etc...) it creates events (log of these can be seen in Event Log). Reaction to events is defined in Event processing policy (make sure you click "save" button when working with it).

This page: https://help.mikrotik.com/docs/display/ROS/Routing+Protocol+Overview says that "OSPF SNMP monitoring" is N/A, so looks that this is not yet implemented in Mikrotik.
I've seen mentions that OSPF can be monitored using Miktorik API - I've never tried that, but it should be possible to take some client for that and use it via NetXMS agent external metrics.
Or, if this information can be collected via ssh - collecting metrics via ssh is out-of-the-box in NetXMS

I'm only interested in major alerts such as node down and ifdown. I don't want the agent to report alerts such as package installation. What should I do

We are attempting to monitor our OSPF links with NetXMS, however NetXMS does not appear to be detecting OSPF on V6 or V7 routers? Is there a command or option I need to enable or turn on for this to work?

Why does netxms continually try snmp communities when the community is already known ?  I have a few different community strings and netxms will still try all others even though the correct string is already configured  in the node settings. This causes issues with switches that have security measures to block snmp if failed snmp attemps are reached. As well as causing bloated logs with auth failed attempts.

We just published patch release 5 for version 4.5. Changes since previous patch release:

- Fixed scheduled file upload
- Fixed policy apply on object selection change
- Fixed custom attribute conflict propagation and conflict removal
- Fixed agent crash on empty output from external table provider
- Fixed bug in pin/popup agent file view
- Updated OPC UA subagent dependencies
- New agent metrics System.CurrentTime.ISO8601.Local, System.CurrentTime.ISO8601.UTC, and System.TimeZoneOffset
- Bundled zlib updated to latest version
- Print exception trace replaced by error logging
- Disable walk action on root object in mib browser
- Business service polls can be disabled or will not be executed if object is unmanaged
- Added peer certificate verification for notification channels
- Fixed issues:
   - NX-2511 (In repeating events, you can specify no more than 5 characters, sometimes more is needed)
   - NX-2516 (CURLAUTH_NEGOTIATE in not available in libCURL 7.29.0)

Добрый день!


Подскажите!!  Автоматически не выстраивается map layer2(((((( На нодах включены snmp, lldp  и cdp. На ноде, от кого строится map собрана информация в interface. В map -> properties -> map options поставлена галка include end note. В чем может быть проблема?

Hello everyone,

I've searched the forum and although I've found a few posts I haven't been able to find a solution for sending notification emails using the Office365 servers.

Example of my configuration:
Server=smtp.office365.com
[email protected]
Password=##########
Port=587
TLSMode=STARTTLS
RetryCount=1
FromName=Account Name
[email protected]
MailEncoding=utf8
IsHTML=yes


How did you encrypt the password? There's some help in the manual, but I'm not sure what kind of encryption Office365 uses.

Are these the right settings or is something missing? When i try to send a email i get DRIVER ERROR

qtech-olt is an old driver module, now it is called qtech. So what happened is that server attempted to load driver module built for old version, which had now incorrect references to other libraries.
If you are building server from source, make sure that before doing "make install" (or copying binaries to target machine) you removed everything from <install_prefix>/lib/netxms (/usr/local/lib/netxms in your case).

Best regards,
Victor

I was able to get the sever back up and running by isolating the qtech-olt.ndd into its own directory so it would not be loaded