help with NetXMS

[Filipp Sudanov]

1. Yes, you need to configure DCIs with relevant OIDs. This typically is done in a template, for modular things like PSUs instance discovery can be used to autodetect things. Feel free to ask for more details.

2. Since v 5.something we have out-of-the-box templates for traffic monitoring, see under Templates->Interface traffic. They are not applied by default (to avoid surprise on large installations with thousands of network devices), so you need to add custom attribute "Template.InterfaceTraffic" with value "YES", you can just do it on Infrastructure Services and put "Inheritable" checkbox.

[nichky]

Hi Filipp

1. Could you please elaborate further?

2. Understood. I need to create a new parameter in Templates → Interface Traffic and apply it to the routers where I want to create Data Collection Items.

[Filipp Sudanov]

1. will get back later
2. I was mentioning custom attribute, please consult the documentation: https://netxms.org/documentation/adminguide/object-management.html#custom-attributes

[nichky]

For the first one, I’m not completely sure if it’s correct, but this is what worked for me:

I created a new template called CPU, then under Data Collection I added the OID. Finally, I applied the template to all devices.

With the second one, I didn’t have any luck. I’ll need to look into it further.

[nichky]

Hi Filipp - let me know about the first one when u get a chance. thx

[nichky]

Filip

about Create Data Collection Items:
this is what im doing:

Navigate to Infrastructure Services in the object tree.
Right-click on Infrastructure Services and select Properties.
Go to the Custom Attributes tab.
ADD:
Name: Template.InterfaceTraffic
Value: YES
tick the “Inheritable” box.

Pull->configuration

is not working

can you pleas advice

[nichky]

Just a quick update on this. I’m currently using MikroTik devices, and I can see the physical interfaces in NetXMS without any issues.

Physical interfaces are working correctly; however, virtual interfaces such as VLANs, PPPoE interfaces, VPN interfaces, etc., are not appearing.

Could you please advise what might be causing this or what I should check to ensure these interfaces are discovered properly?

[victor]

Just to clarify - you mean you have created VPN or VLAN interface on Mikrotik device, and it is not visible in "Interfaces" view?
One note on newly added interfaces - they will appear in NetXMS after next configuration poll. You can manually force configuration poll by selecting Poll -> Configuration from node menu.
If new interface did not appear after configuration poll, please provide more specific details on interface type and how it is configured in Mikrotik so we could reproduce the issue.

[nichky]

1.Just to clarify - you mean you have created VPN or VLAN interface on Mikrotik device, and it is not visible in "Interfaces" view?

YES
The goal is to include all interfaces — such as VPN, VLAN, and PPPoE — in the data collections. I am currently using Template.InterfaceTraffic on the customer attribute, which allows me to see all physical interfaces in the data collections. However, I need a solution to also include virtual interfaces. Additionally, I would like an easy way to add monitoring for CPU, temperature, voltage, and other hardware metrics.

2. One note on newly added interfaces - they will appear in NetXMS after next configuration poll. You can manually force configuration poll by selecting Poll -> Configuration from node menu.
   If new interface did not appear after configuration poll, please provide more specific details on interface type and how it is configured in Mikrotik so we could reproduce the issue.

I'm aware of that.

[alk]

Hi,

Most likely the virtual interfaces are actually present as objects, and what's missing is only the DCIs for them - these are two separate mechanisms. Here's what's actually happening:

NetXMS builds the interface list from the standard ifTable and creates interface objects for everything the device reports - VLAN, PPPoE, bridges and tunnels included, there is no filtering by type at that stage. So after a configuration poll they all should be visible in the Interfaces view under the node - I do believe they are there on your system? If some are genuinely missing even after configuration poll, that would mean RouterOS is not exposing them over SNMP, but that would be unusual.

What filters them out is the Interface Traffic template itself. Its DCIs are created by instance discovery, and the filter script in the prototype DCIs only accepts interfaces with ifType 6, 7 or 22 (ethernet-like types). VLAN (ifType 135), PPP/PPPoE (23), tunnels (131), bridges (209) are all rejected by that check. The filter also skips loopbacks, interfaces whose expected state is not UP, and interfaces with speed at or below 20 Mbit/s.

You can see it happening: run Poll -> Instance discovery on the node and look at the poller output - there will be a "skipped - interface type" line for every virtual interface.

To include them, open the template under Templates -> Interface traffic, edit the instance discovery filter script in the prototype DCIs and extend the interfaceTypes array at the top with the types your virtual interfaces report:

interfaceTypes = [6, 7, 22, 23, 131, 135, 209];

Actual ifType of every interface is shown on the interface object's Overview tab, so check there which values you need. Note: with default server configuration (Server.ImportConfigurationOnStartup = 1) your edits to this template survive server upgrades - stock templates are not overwritten on import.

For CPU / temperature / voltage on MikroTik you don't need to hunt for OIDs manually:

• Health metrics - create DCI with origin "Network device driver". For MikroTik nodes the driver reads the RouterOS health gauge table and offers every gauge the particular model exposes (cpu-temperature, board-temperature, voltage, fan speeds, etc.) by name in the metric selection dialog. Values come exactly as the device reports them, so check the scale and add a transformation script if needed.
• CPU load - standard SNMP DCI on 1.3.6.1.2.1.25.3.3.1.2 (hrProcessorLoad from HOST-RESOURCES MIB, one row per core).

Put these DCIs into your own template and let it apply automatically to all RouterOS devices with auto-apply filter script:

return $node.driver == "MIKROTIK";

• same idea as the custom attribute you already use for interface traffic, just keyed on the driver instead.