NetXMS Support Forum

Hello friends,
https://www.youtube.com/watch?v=TPgvtBPODEc
https://lasiszm.wordpress.com/2018/05/31/netxms-and-mikrotik-registration-table/
Best regards

Hello Sir,

Current:
If I execute tool with output on 3 nodes it will open 3 windows with tool output.
Concept:
Execution of tool on 3 nodes and live output in one window, and some ability to control that behavior with one click just before choosing tool.

Is there any chance to implement that in future releases?

Best regards.

Hello all,
https://www.youtube.com/watch?v=pNa1Pc8OT78

Hello all,
https://www.youtube.com/watch?v=jBfJSFajKq4
https://lasiszm.wordpress.com/2018/04/15/monitoring-gpon-cable-down-events-with-netxms/

Current version(2.2.4).

Hello friends,
how to deal with overlapping text's in chart legend?
I've tried to change display format, but clearly missed something(can't force only one digit after dot).
Screenshot is in attachments.
Thanks in advance.

Hello All,
https://youtu.be/WXl9mDfTDAs
https://lasiszm.wordpress.com/2018/03/19/netxms-monitoring-of-gpon-onus/

Hello All,

It's hard to call that tutorial, this time slides and demo only(some time related issues).

https://lasiszm.wordpress.com/2018/03/04/netxms-syslog-parsing/
https://youtu.be/p32z-h1rd_s

Have a good day

Hello,
I want to share process of creation  MikroTik template.
Description:
-auto apply rules(RB750, RB2011, CCR's, CRS's)
-interface IN/OUT BPS/PPS(only ethernet) DCI's
-spike(due to reset of counters/reboot etc.) filtering
-using 64 bit OIDS
https://lasiszm.wordpress.com/2017/10/22/netxms-template-for-monitoring-mikrotik-interfaces/
https://youtu.be/Q_7LOUh66vM
Best regards

Hi, improved MT template with dci summary table and my definition of ping tool.
Please view code before import(Im still learning NetXMS)
I will also improve my upgrade tools from other topic(soon).
Best regards

When Ive upgraded to 2.07 and I saw couple of hosts on L2 map(map Ive created before) without changing anything in their config. All hosts have similiar configuration, and software version. Yesterday Ive upgraded NetXMS to newest BETA and all host dissapeared from map.
This post is only info(version 2.07 started to discover network). Im waiting for LLDP in MT(now in release candidate).
When Ive tried to pull L2 from Nexus Ive got info about problem retrieving FDB. My Nexus was discovered with driver Generic.

Thak You Sir.
It is working. Before answer Ive resolved problem other way(file without 001 ending i attachments).
Ive attached my MikroTik templates(file with 001 is corrected as Mr Victor suggested to deal with that voltage OID) for everyone.

Template's DCI's:
-CPU usage
-MEM Usage
-Voltage
-Count of Wireless Clients
-Speed/Packets of all interfaces(interfaces with "vl" and "br" in names are not included)
-RouterOS and Firmware version
-Board Name
-Ping

New post only for refresh purpose.
Ive tried instance discovery with following code:
transport = CreateSNMPTransport($node);
if (transport == null)
{
    return false;
}

value = SNMPGetValue(transport, ".1.3.6.1.4.1.14988.1.1.3.8.0");
if (value == null)
{
    return false;
}
else
{
   return true;
}

Type : Script
Parameter: .1.3.6.1.4.1.14988.1.1.3.8

No results

Hello, I'm sorry for asking simple question again.
Ive done MikroTik template(in attachment) with following apply rule:
return $node->driver  == "MIKROTIK";

Almost everything working. But when template was applied on rb without voltage sensor(OID: .1.3.6.1.4.1.14988.1.1.3.8.0) NetXMS generate alarm. Ive tried to use instance discovery in template and script, but Im doing something wrong and cant skip applying this particular DCI for host without sensor.

SNMP Out for hosts with and witout sensor:
snmpwalk -v2c -c maincommunity 192.168.x.x .1.3.6.1.4.1.14988.1.1.3.8
iso.3.6.1.4.1.14988.1.1.3.8.0 = INTEGER: 257

snmpwalk -v2c -c maincommunity 192.168.x.x .1.3.6.1.4.1.14988.1.1.3.8
iso.3.6.1.4.1.14988.1.1.3.8 = No Such Object available on this agent at this OID

I know that isn't NetXMS, but main lack of knowlege about NXSL. I ask that you kindly provide a single example of filter that stops of creating DCI on node without voltage sensor.

Second problem is about MT's oid for number of wireless client's conected( .1.3.6.1.4.1.14988.1.1.1.4). When I do MIB walk value is correct, but when I create DCI(in template or direct on host) is always "UNSUPPORTED".

Than You in advance.

Yes workaround is bad idea.
On all Cisco devices all of mentioned disabled on Mikrotik's /ip neig disc disabled on all devices, on UBNT CDP off.
I thought that FDB is enough to populate topology.
If MT would have LLDP ability someday....
All Cisco's are "surrounded" by MT or p2p equipment with limited snmp support.