One more comment regarding this issue:
As I wrote the problematic nodes works properly but after all I found that in case of nodes with question mark the trap processing based event generation does not work. Only the threshold based DCI alarms works.

BR,
Zsolt

This is the requested log detail:

Information 2/28/2019 5:40:02 PM NetXMSCore 179 None [poll.conf          ] ConfPoll(Bacsalmas_SME_Controller_Kossuth): selected device driver GENERIC
Information 2/28/2019 5:40:02 PM NetXMSCore 65 None FindDriverForNode(Bacsalmas_SME_Controller_Kossuth): found potential device driver PING3 with priority 63
Information 2/28/2019 5:40:02 PM NetXMSCore 179 None [poll.conf          ] ConfPoll(Bacsalmas_SME_Controller_Kossuth): SNMP agent detected (version 2c)
Information 2/28/2019 5:40:02 PM NetXMSCore 179 None [client.session.4  ] Sending message CMD_POLLING_INFO (120 bytes)
Information 2/28/2019 5:40:01 PM NetXMSCore 179 None [poll.conf          ] ConfPoll(Bacsalmas_SME_Controller_Kossuth): calling SnmpCheckCommSettings()
Information 2/28/2019 5:40:01 PM NetXMSCore 179 None [client.session.4  ] Sending message CMD_POLLING_INFO (88 bytes)
Information 2/28/2019 5:40:01 PM NetXMSCore 179 None [poll.conf          ] ConfPoll(Bacsalmas_SME_Controller_Kossuth): checking for NetXMS agent - finished
Information 2/28/2019 5:40:01 PM NetXMSCore 179 None [agent.conn.62507  ] Disconnect completed
Information 2/28/2019 5:40:01 PM NetXMSCore 179 None [agent.conn.62507  ] disconnect() called
Information 2/28/2019 5:40:01 PM NetXMSCore 179 None [poll.conf          ] ConfPoll(Bacsalmas_SME_Controller_Kossuth): checking for NetXMS agent - failed to connect (error 910)
Information 2/28/2019 5:40:01 PM NetXMSCore 179 None [agent.conn.62507  ] Cannot create communication channel
Information 2/28/2019 5:40:01 PM NetXMSCore 179 None [agent.conn.62507  ] Cannot establish connection with agent at 172.17.51.184:4700

I hope this will be good for debugging.

BR,
Zsolt

Best regards,
Victor

I have checked the ifMIB walk and I found that this feature does not implemented in this type of device.
Besides this I installed an older version (v2.2.2) NetXMS test server to verify the previous display mode.

Please find in the attachement two screenshoots about the two different NXMC versions.
So, in case of older versions the nodes without ifMIB feature were displayed with "unknown" named interface element without question mark.
I think that the older indication mode was a little more logical.
 
BR,
Zsolt

Best regards,
Victor

Please see the requested results:

[2019.02.20 13:57:19] **** Poll request sent to server ****
[2019.02.20 13:57:19] Poll request accepted
[2019.02.20 13:57:19] Starting configuration poll for node Aggtelek_SME_Controller_Kossuth
[2019.02.20 13:57:19] Checking node's capabilities...
[2019.02.20 13:57:19]    Checking NetXMS agent...
[2019.02.20 13:57:20]    Checking SNMP...
[2019.02.20 13:57:20]    SNMP agent is active (version 2c)
[2019.02.20 13:57:22] Capability check finished
[2019.02.20 13:57:22] Checking interface configuration...
[2019.02.20 13:57:28] Interface configuration check finished
[2019.02.20 13:57:28] Checking node name
[2019.02.20 13:57:28] Node name is OK
[2019.02.20 13:57:28] Finished configuration poll for node Aggtelek_SME_Controller_Kossuth
[2019.02.20 13:57:28] Node configuration was not changed after poll
[2019.02.20 13:57:28] **** Poll completed successfully ****

[2019.02.20 13:58:15] **** Poll request sent to server ****
[2019.02.20 13:58:15] Poll request accepted
[2019.02.20 13:58:15] Starting status poll for node Aggtelek_SME_Controller_Kossuth
[2019.02.20 13:58:15] Checking SNMP agent connectivity
[2019.02.20 13:58:15] Node is connected
[2019.02.20 13:58:15] Finished status poll for node Aggtelek_SME_Controller_Kossuth
[2019.02.20 13:58:15] Node status after poll is UNKNOWN
[2019.02.20 13:58:15] **** Poll completed successfully ****

BR,
Zsolt

please provide output of configuration and status poll for such node.

Best regards,
Victor