NetXMS Support Forum

When I use the Unattended installation of netxms5.1.1, after installation, 
start /wait "" "nxagent-5.1.1-x64.exe" /SILENT /SUPPRESSMSGBOXES /SERVER=serverip /CENTRALCONFIG /SUBAGENT=UPS
 /SUBAGENT=FILEMGR /SUBAGENT=LOGWATCH /SUBAGENT=PING /SUBAGENT=WMI /SUBAGENT=netsvc /SUBAGENT=winperf
 /LOGFILE=C:\NetXMS\log\netxms.log /FILESTORE=C:\NetXMS\var
it does not add nxuseragent.exe and nxsagent.exe to the startup folder of windows like directly using the installation file, although the services of both will be installed and executed normally,
but the Unattended installation is used because there is no automatic activation project in front,
As a result, "Take Screenshot" and "FileManager" cannot be used normally when using NXMC,
but the Edit Agent configuration on NXMC is normal

Of course, if I manually add a shortcut to nxuseragent.exe and nxsagent.exe in the Windows startup directory, it will all be back to normal again.

Is there some problem here?

Recently, I started to use wmi query seriously in my working environment USING NETXMS 5.1.0 .
I added a DCI tableB in node and used agent as the data source. 
When setting METRIC to WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product"), 
It was found that it had no effect. The DCI was blank and had no field name, 
but the DCI did not automatically DISABLE. However, 
when I changed the query command to the following 
SELECT * FROM Win32_OperatingSystem
SELECT * FROM Win32_Process
SELECT * FROM Win32_Service
SELECT * FROM Win32_BIOS
SELECT * FROM Win32_NetworkAdapterConfiguration
SELECT * FROM Win32_UserAccount
All values in table format are displayed normally.
I just want to change the built-in NODE function 「SOFTWARE INVENTORY 」of NETXMS
to be used on DCI TABLE, but I found that the built-in functions are all normal,
except that I cannot reproduce it on DCI.
Get-WmiObject -Class Win32_Product | Select-Object Name, Version, Vendor | Format-Table -AutoSize On the tested NODE, it is normal to use POWERSHELL to test.
What is the cause of this problem?
The following is what I excerpted from the DEBUG LOG. ERROR=500 RESULT =5 appears.


2024.11.16 23:12:57.099 *D* [dc.agent          ] Node(YMXXXX)->getTableFromAgent(WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")): error=500 result=5
2024.11.16 23:12:57.099 *D* [client.session.0  ] Sending message CMD_NOTIFY (48 bytes)
2024.11.16 23:12:57.099 *D* [client.session.0  ] Message dump:
  ** 000000 | 00 12 50 00 00 00 00 30 00 00 00 00 00 00 00 02 | ..P....0........
  ** 000010 | 00 00 00 17 00 00 00 00 00 00 00 22 00 00 00 00 | ..........."....
  ** 000020 | 00 00 00 5C 00 00 00 00 00 01 1E 68 00 00 00 00 | ...\.......h....
  ** code=0x0012 (CMD_NOTIFY) version=5 flags=0x0000 id=0 size=48 numFields=2
  ** 000000: [    23] INT32      34
  ** 000010: [    92] INT32      73320

2024.11.16 23:12:57.099 *D* [client.session.0  ] Sending message CMD_NOTIFY (48 bytes)
2024.11.16 23:12:57.099 *D* [client.session.0  ] Message dump:
  ** 000000 | 00 12 50 00 00 00 00 30 00 00 00 00 00 00 00 02 | ..P....0........
  ** 000010 | 00 00 00 17 00 00 00 00 00 00 00 22 00 00 00 00 | ..........."....
  ** 000020 | 00 00 00 5C 00 00 00 00 00 01 1E 68 00 00 00 00 | ...\.......h....
  ** code=0x0012 (CMD_NOTIFY) version=5 flags=0x0000 id=0 size=48 numFields=2
  ** 000000: [    23] INT32      34
  ** 000010: [    92] INT32      73320
2024.11.16 23:27:01.926 *D* [obj.dc.queue      ] DataCollectionTarget(YMXXXX)->QueueItemsForPolling(): item 143083 "WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")" added to queue
2024.11.16 23:27:01.926 *D* [dc.collector      ] DataCollector(): processing DC object 143083 "WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")" owner=73320 sourceNode=0
2024.11.16 23:27:05.928 *D* [dc.agent          ] Node(YMXXXX)->getTableFromAgent(WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")): error=500 result=5

A while ago, in order to get the name of the interface from snmp,
 because the name encoding uses UTF-8, I set UTF-8 in the setting option of SNMP.Codepage, 
and found that it had no effect.SNMP.Codepage


Later, it wasn't until I thought of changing UTF-8 to utf-8 that it started to work normally. 
Should this input be changed to mainly uppercase, 
or should it be made directly case-insensitive?

New NXMC already has mib file upload feature ,
There is no need to pull the mib file from the server side

another The jar file used in the report server also needs to be added to the server.
If it can be uploaded directly to the server through nxmc on the client, it will become very convenient to maintain or update.

When performing network topology on the switch, the results of lldp and fdb are obtained at the same time, resulting in a conflict and failure to establish the peernode.

In the following log record, I found that two record is

2024.10.16 23:13:55.965 *D* [topology.link      ] LinkLayerNeighbors::isDuplicate: inconsistent data: FDB(ifLocal=2 remote=76050/5) FDB(ifLocal=41 remote=76040/5)
2024.10.16 23:13:55.965 *D* [topology.link      ] LinkLayerNeighbors::isDuplicate: inconsistent data: FDB(ifLocal=2 remote=76050/5) FDB(ifLocal=42 remote=76048/5)

As a result, I was supposed to find 5 but then I only found 2.

The netxms I use is 5.0.8 and the switch is dlink dgs-1510-52
Other switches of the same type Also having the same issue. The switches are connected to computers and operating systems with the same hardware specifications.
I would like to ask what is the reason for this result, which makes me very confused. I've found that this issue may not be limited to a certain type of network switch.


2024.10.16 23:13:51.088 *D* [topology.fdb      ] GetSwitchForwardingDatabase(sw-203-dlink [47278]): 165 entries read from dot1qTpFdbTable
2024.10.16 23:13:51.177 *D* [topology.fdb      ] GetSwitchForwardingDatabase(sw-203-dlink [47278]): 0 entries read from dot1dTpFdbTable
2024.10.16 23:13:51.177 *D* [poll.topology      ] Switch forwarding database retrieved for node sw-203-dlink [47278]
2024.10.16 23:13:51.177 *D* [topology.link      ] BuildLinkLayerNeighborList(sw-203-dlink [47278]): building link level topology
2024.10.16 23:13:51.177 *D* [topology.driver    ] Collecting topology information from driver DLINK for node sw-203-dlink [47278]
2024.10.16 23:13:51.177 *D* [topology.driver    ] Driver for node sw-203-dlink [47278] cannot provide link layer topology information
2024.10.16 23:13:51.177 *D* [topology.lldp      ] Collecting LLDP topology information for node sw-203-dlink [47278]
2024.10.16 23:13:55.690 *D* [topology.lldp      ] 5 entries in LLDP-MIB connection database for node sw-203-dlink [47278]
2024.10.16 23:13:55.690 *D* [topology.lldp      ] Finished collecting LLDP topology information for node sw-203-dlink [47278]
2024.10.16 23:13:55.965 *D* [poll.topology      ] Node::addHostConnections(sw-203-dlink [47278]): FDB retrieved
2024.10.16 23:13:55.965 *D* [poll.topology      ] Node::addHostConnections(sw-203-dlink [47278]): found single MAC A0:36:BC:5B:19:A7 on interface eth1/0/2
2024.10.16 23:13:55.965 *D* [poll.topology      ] Node::addHostConnections(sw-203-dlink [47278]): found remote interface ethernet 2 [76051]
2024.10.16 23:13:55.965 *D* [poll.topology      ] Node::addHostConnections(sw-203-dlink [47278]): found single MAC A0:36:BC:5B:18:1C on interface eth1/0/3
2024.10.16 23:13:55.965 *D* [poll.topology      ] Node::addHostConnections(sw-203-dlink [47278]): found remote interface ethernet [75986]
2024.10.16 23:13:55.965 *D* [poll.topology      ] Node::addHostConnections(sw-203-dlink [47278]): found single MAC A0:36:BC:5B:18:D9 on interface eth1/0/41
2024.10.16 23:13:55.965 *D* [poll.topology      ] Node::addHostConnections(sw-203-dlink [47278]): found remote interface ethernet 2 [76041]
2024.10.16 23:13:55.965 *D* [topology.link      ] LinkLayerNeighbors::isDuplicate: inconsistent data: FDB(ifLocal=2 remote=76050/5) FDB(ifLocal=41 remote=76040/5)
2024.10.16 23:13:55.965 *D* [poll.topology      ] Node::addHostConnections(sw-203-dlink [47278]): found single MAC A0:36:BC:5B:1A:E0 on interface eth1/0/42
2024.10.16 23:13:55.965 *D* [poll.topology      ] Node::addHostConnections(sw-203-dlink [47278]): found remote interface ethernet 2 [76049]
2024.10.16 23:13:55.965 *D* [topology.link      ] LinkLayerNeighbors::isDuplicate: inconsistent data: FDB(ifLocal=2 remote=76050/5) FDB(ifLocal=42 remote=76048/5)
2024.10.16 23:13:55.965 *D* [topology.link      ] BuildLinkLayerNeighborList(sw-203-dlink [47278]): 2 connections found

i use netxms server 4.4.2
after hook::CreateInterface add below script ,interface name and descript become unknown. why? 

if ($1->name ~= "(?i).*Teredo.*|.*isatap.*|.*Loopback.*|.*Bluetooth.*|Local Area Connection\* 12|Local Area Connection\* 11|Local Area Connection\* 9|Local Area Connection\* 8|Local Area Connection\* 2|6TO4 Adapter|sit0") {
  return false;
} else {
  return true;
}

I use the latest windows X64 version of netxms 2.2.17 with the Microsoft sql server database.
I found that when using a string mixed with one-byte word and two-byte word to store the database,
the calculation length error will occur, causing the string to be Truncated.
I suspect that it may be that ms sql calculates the character length for varchar in a different way than other databases.
Nvarchar will treat both one-byte word and the two-byte word as one character, but the varchar data type will treat the ASCII word of one-byte  as a character, but the two-character word will be treated as two characters.

Is there any possibility to solve this problem?

Attached below is the SQL query I fetched using SQL PROFILER, select @p1 actully is stored = 'Sw-209-dlink總務' not 'Sw-209-dlink總務處',because the p1 is varchar(16)

declare @p1 int
set @p1=6981
exec sp_prepexec @p1 output,N'@P1 varchar(16),@P2 int,@P3 int,@P4 int,@P5 int,@P6 int,@P7 int,@P8 int,@P9 int,@P10 varchar(9),@P11 int,@P12 varchar(9),@P13 varchar(1),@P14 int,@P15 int,@P16 varchar(9),@P17 varchar(9),@P18 int,@P19 int,@P20 varchar(37),@P21 varchar(37),@P22 int,@P23 varchar(1),@P24 varchar(1),@P25 varchar(1),@P26 varchar(1),@P27 bigint,@P28 int,@P29 int',N'UPDATE object_properties SET name=@P1,status=@P2,is_deleted=@P3,inherit_access_rights=@P4,last_modified=@P5,status_calc_alg=@P6,status_prop_alg=@P7,status_fixed_val=@P8,status_shift=@P9,status_translation=@P10,status_single_threshold=@P11,status_thresholds=@P12,comments=@P13,is_system=@P14,location_type=@P15,latitude=@P16,longitude=@P17,location_accuracy=@P18,location_timestamp=@P19,guid=@P20,image=@P21,submap_id=@P22,country=@P23,city=@P24,street_address=@P25,postcode=@P26,maint_event_id=@P27,state_before_maint=@P28 WHERE object_id=@P29','Sw-209-dlink總務處',2,0,1,1566991628,0,0,1,0,'01020304',75,'503C2814','',0,0,'0.000000','0.000000',0,0,'d025b358-fd3d-1d4d-9b5e-6337e2fd9fc1','00000000-0000-0000-0000-000000000000',0,'','','','',0,0,713
select @p1

I USE NODE TOPOLOGY->SWITCH FORWARDING TABLE (MAC ADDRESS TABLE) FOR HP ARUBA SWITCH S2500 & S3500,

NetXMS:
Version: 2.2.16
Platform: Windows, 64-bit
Database: PostgreSQL

ALL ARUBA S2500 & S3500 SWITCH  is detected as GENERIC driver by NetXMS.

Problem:
Switchports that are in access mode in vlan 1, and ports that are in trunk mode and include vlan 1 in trunk vlans list are identified properly.
However, ports that do not include vlan 1 are shown as interface name "[ 0 ]" in the "Topology -> Switch forwarding database (MAC address table)" screen.
so i can't to know what peer node,problem screen is below


.1.3.6.1.2.1.17.1.4.1.2

.1.3.6.1.2.1.2.1.0

.1.3.6.1.2.1.2.2.1.1

.1.3.6.1.2.1.31.1.1.1.1

.1.3.6.1.2.1.2.2.1.2