NetXMS Support Forum

Victor - this has been resolved.

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.

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.

It's either something is still missing in the configuration, or there is firewall or connectivity issue.
Can you share screenshot of your network discovery configuration?
Also, note that discovered nodes will appear in "Network" perspective with default configuration. To make them appear in "Infrastructure" perspective you have to create containers with auto-bind filters.

i have one more query.

I have a MikroTik device running OSPF, however it does not appear in the overview and is showing OSPF = No.

Additionally, I have a router running CAPsMAN, but it is showing Wireless Controller=No

@victor Also, the timestamp conversion will be a background task after netxms server/db upgrade?  If so, how will nxsl/rest api present the timestamps when not all timestamps have been converted?  Will we have a mix of seconds and millisecond timestamps or will netxms server convert seconds to milliseconds even if the db entry has not been updated by the background task yet?

When im adding node ive added user-name PS and SSH port.

what i want is access to the same note via SSH

too -> Connect -> SSH.

Once i put the user name im gettign the above

Сабж. Вводят в заблуждение - предлагаю убрать, оставив только квадратики пустые. Либо, что лучше, если возможно и позволит ширина квадратиков - заполнять автоматически giXX / %interface name%, как в всплывающем меню собственно.

This screenshot looks like an output of the OpenSSH client (https://www.openssh.org), started without parameters.

What have you configured and what are you trying to achieve?

Could you please update docs pages (NXSL and admin guide) for where unix timestamps are in milliseconds vs seconds.  It feels like this could get confusing if there is a mix of unit when unix timestamp is referred to.

I'm expecting that this (https://www.netxms.org/documentation/nxsl-latest/#class-datapoint) would be the only place that would have changed from seconds to milliseconds because this is the only place to get list of DCI datapoints including timestamp right?