NetXMS Support Forum

Helleo together,

it seems that there is a problom withn the legend in linecharts. The values within the "Curr" column seem to be wrong. For illustration screenshots attached from "Performance"-Tab and dedicated Linechart.

Best regards

Georg

I did the first request out of capture for full configuration poll and got following results:

nxsnmpget -v 3 -u xxxxx IP 1.3.6.1.2.1.1.2.0
1.3.6.1.2.1.1.2.0 [OBJECT IDENTIFIER]: 1.3.6.1.4.1.19536.10.1
// Value seems to be OK as the PDU comes from Panduit

nxsnmpget -v 3 -u xxxxx IP 1.3.6.1.2.1.1.1.0
1.3.6.1.2.1.1.1.0 [STRING]:  SN:PDU Metered PN:Device Model:P30D05M Rating:346-415V, 16A, 11.0kVA, 50/60Hz
// Value is OK

nxsnmpget -v 3 -u xxxxx IP 1.3.6.1.4.1.35160.1.1.0
1.3.6.1.4.1.35160.1.1.0 [NULL]:
// I don't know why this OID is requested it seems that it has nothing to do with Panduit

nxsnmpget -v 3 -u xxxxx IP 1.3.6.1.6.3.15.1.1.4.0
1.3.6.1.6.3.15.1.1.4.0 [NULL]:
// This is the OID from the report

it seems that the next calls to the device are done with global configured authtenticationparameters as they are encrypted. Within nodeconfiguration I have configured authentication parameters for that host.

nxsnmpget -v 3 -u xxxxx IP 1.3.6.1.2.1.1.3.0
1.3.6.1.2.1.1.3.0 [TIMETICKS]: 866125100
// Result for this request returned that is done as the last SNMP-Request in packet-capture

So it seems to be odd why the PDU is nor recognized as SNMP capable...

Best regards

Georg

I captured data for two situations:
1.) Configuration poll (full poll)
2.) nxsnmpget for special OID

Capturing a DCI-Poll (Forced Poll) gave me an empty file. I think the poll was  not done, because netxms was not able to detect SNMP capabilities at configuration poll.

@Filipp: I will send You a downloadlink as PM

Helle together,

it is even more than two month I got many of these logentries:

2025.11.01 00:02:22.882 *E* [db.drv             ] SQL query failed (Query = "INSERT INTO nodes (primary_ip,primary_name,snmp_port,capabilities,snmp_version,community,agent_port,secret,snmp_oid,uname,agent_version,platform_name,poller_node_id,zone_guid,proxy_node,snmp_proxy,icmp_proxy,required_polls,use_ifxtable,usm_auth_password,usm_priv_password,usm_methods,snmp_sys_name,bridge_base_addr,down_since,driver_name,rack_image_front,rack_position,rack_height,physical_container_id,boot_time,agent_cache_mode,snmp_sys_contact,snmp_sys_location,last_agent_comm_time,syslog_msg_count,snmp_trap_count,node_type,node_subtype,ssh_login,ssh_password,ssh_key_id,ssh_port,ssh_proxy,port_rows,port_numbering_scheme,agent_comp_mode,tunnel_id,lldp_id,fail_time_snmp,fail_time_agent,fail_time_ssh,rack_orientation,rack_image_rear,agent_id,agent_cert_subject,hypervisor_type,hypervisor_info,icmp_poll_mode,chassis_placement_config,vendor,product_code,product_name,product_version,serial_number,cip_device_type,cip_status,cip_state,eip_proxy,eip_port,hardware_id,cip_vendor_code,agent_cert_mapping_method,agent_cert_mapping_data,snmp_engine_id,snmp_context_engine_id,syslog_codepage,snmp_codepage,ospf_router_id,mqtt_proxy,modbus_proxy,modbus_tcp_port,modbus_unit_id,vnc_password,vnc_port,vnc_proxy,path_check_reason,path_check_node_id,path_check_iface_id,expected_capabilities,id) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) ON DUPLICATE KEY UPDATE primary_ip=VALUES(primary_ip),primary_name=VALUES(primary_name),snmp_port=VALUES(snmp_port),capabilities=VALUES(capabilities),snmp_version=VALUES(snmp_version),community=VALUES(community),agent_port=VALUES(agent_port),secret=VALUES(secret),snmp_oid=VALUES(snmp_oid),uname=VALUES(uname),agent_version=VALUES(agent_version),platform_name=VALUES(platform_name),poller_node_id=VALUES(poller_node_id),zone_guid=VALUES(zone_guid),proxy_node=VALUES(proxy_node),snmp_proxy=VALUES(snmp_proxy),icmp_proxy=VALUES(icmp_proxy),required_polls=VALUES(required_polls),use_ifxtable=VALUES(use_ifxtable),usm_auth_password=VALUES(usm_auth_password),usm_priv_password=VALUES(usm_priv_password),usm_methods=VALUES(usm_methods),snmp_sys_name=VALUES(snmp_sys_name),bridge_base_addr=VALUES(bridge_base_addr),down_since=VALUES(down_since),driver_name=VALUES(driver_name),rack_image_front=VALUES(rack_image_front),rack_position=VALUES(rack_position),rack_height=VALUES(rack_height),physical_container_id=VALUES(physical_container_id),boot_time=VALUES(boot_time),agent_cache_mode=VALUES(
agent_cache_mode),snmp_sys_contact=VALUES(snmp_sys_contact),snmp_sys_location=VALUES(snmp_sys_location),last_agent_comm_time=VALUES(last_agent_comm_time),syslog_msg_count=VALUES(syslog_msg_count),snmp_trap_count=VALUES(snmp_trap_count),node_type=VALUES(node_type),node_subtype=VALUES(node_subtype),ssh_login=VALUES(ssh_login),ssh_password=VALUES(ssh_password),ssh_key_id=VALUES(ssh_key_id),ssh_port=VALUES(ssh_port),ssh_proxy=VALUES(ssh_proxy),port_rows=VALUES(port_rows),port_numbering_scheme=VALUES(port_numbering_scheme),agent_comp_mode=VALUES(agent_comp_mode),tunnel_id=VALUES(tunnel_id),lldp_id=VALUES(lldp_id),fail_time_snmp=VALUES(fail_time_snmp),fail_time_agent=VALUES(fail_time_agent),fail_time_ssh=VALUES(fail_time_ssh),rack_orientation=VALUES(rack_orientation),rack_image_rear=VALUES(rack_image_rear),agent_id=VALUES(agent_id),agent_cert_subject=VALUES(agent_cert_subject),hypervisor_type=VALUES(hypervisor_type),hypervisor_info=VALUES(hypervisor_info),icmp_poll_mode=VALUES(icmp_poll_mode),chassis_placement_config=VALUES(chassis_placement_config),vendor=VALUES(vendor),product_code=VALUES(product_code),product_name=VALUES(product_name),product_version=VALUES(product_version),serial_number=VALUES(serial_number),cip_device_type=VALUES(cip_device_type),cip_status=VALUES(cip_status),cip_state=VALUES(cip_state),eip_proxy=VALUES(eip_proxy),eip_port=VALUES(eip_port),hardware_id=
VALUES(hardware_id),cip_vendor_code=VALUES(cip_vendor_code),agent_cert_mapping_method=VALUES(agent_cert_mapping_method),agent_cert_mapping_data=VALUES(agent_cert_mapping_data),snmp_engine_id=VALUES(snmp_engine_id),snmp_context_engine_id=VALUES(snmp_context_engine_id),syslog_codepage=VALUES(syslog_codepage),snmp_codepage=VALUES(snmp_codepage),ospf_router_id=VALUES(ospf_router_id),mqtt_proxy=VALUES(mqtt_proxy),modbus_proxy=VALUES(modbus_proxy),modbus_tcp_port=VALUES(modbus_tcp_port),modbus_unit_id=VALUES(modbus_unit_id),vnc_password=VALUES(vnc_password),vnc_port=VALUES(vnc_port),vnc_proxy=VALUES(vnc_proxy),path_check_reason=VALUES(path_check_reason),path_check_node_id=VALUES(path_check_node_id),path_check_iface_id=VALUES(path_check_iface_id),expected_capabilities=VALUES(expected_capabilities),id=VALUES(id)"): Data too long for column 'lldp_id' at row 1

Checking the database with nxdbmgr does not report any errors.

Using version 5.2.8 with mariadb on debian

Best regards

Georg

Hello together,

my current version of netxms is 5.2.8 on debian, I'm currently migrating my monitoring to.

I had implemented SNMP-requests to panduit G5 PDUs some time ago in a netxms-version 4.x and it worked fine even with some updates of netxms to current version.
Currently I did a firewareupdate on that PDU and afterwards a full configuration poll for the corresponding node. Within that poll netxms was not able checking running SNMP agent and doing a capability-update. (Testing it with a PDU that had an other firmwareversion same thing happend.) From that time on it got more strange:
- Using instance-poll with a DCI worked fine and all instances are created
- Created DCIs got an error while polling values
- Making a nxsnmpget request from server with needed SNMP-parameters with OID from one of the created DCIs worked fine and I got back the value for that OID

This bahavor is the same for SNMP v2c and v3. To simplyfy the problem I deactivated all encryption staff from v3.

As I have an old installation from netxms (Version 2.0.5) I added a node there and it all worked fine! (detection of node capabilities and DCI-Requests)

I do not know how to get it working on version 5.2.8 I'm currently migrating to.

Best regards

Georg

Hello everyone,

I have a question:

Has anyone done some integration/synchronisation of data between NetBox and NetXMS?
Till now I only have found some integrations of NetBox only with some other monitoring-systems.

Best regards

Georg

At my installation I have two folders .nxmc and .nxmc4 on Windows10
There is a very old client installed (Netxms 2.0.5) where it seemes that it is using .nxmc and a newer client beginning with 4.x that was upgraded to 5.0x as next version of monitoring server which uses folder .nxmc4. Deleting .nxmc4 helped me solving same problem redlam had.

Does this mean, that using OIDs in SNMP-requests as functionparameter also have to be done without leading "."?

What is the behavior if result of a SNMP-request is an OID itsself? Is this value returned without leading "."?

At my installation I'm using a networkmap for every floor with a jpg or png image as background and some other informations. These images are of different sizes. Til now it worked fine getting the image from image-library and it was displayed perfectly.
With version 5.0.1 mapsize within map properties has to be changed from width=0 and height=0 to a value that fits imagesize to be displayed correctly.
Is this a bug or intended behavior?
If this is intended behavior I have to change the values for many, many maps....

It is possible configuring rights for editing Maintenancejournal from within objectproperties of "Infrastructure Services".
Is there a possibility editing these rights from within user and group definitions at "User and groups"?

Hello together,

configuring different community-strings for read and write access is a common solution on SNMP-servers.
What is the way to implement the usage of a seperate community-string for SNMP-set-access to networkcomponents from within NetXMS.

Best regards

Georg

Passiv PDUs that are mounted at front or back of the rack can be documented within "Passive Elements". PDUs that are 19"-mountable and active managed can be placed at the HE as mounted.

Many larger PDUs are mounted vertically within rack (managed or unmanaged). Would it be possible to expand the logic for rack-definitions the way that these PDUs are documentable for a rack?

Thanks for the info. That helps me very much, concerning data I want to access within action message text!

But I got an other problem that I don't what goes wrong.

In message text I am calling a function this way %[NMSRV::test/testfkt1("p1","p2","p3","p4")] for test this is a very simple function with this definition in NMSRV::test :

function testfkt1(pm1,pm2,pm3,pm4)
 { retval = "Param1: "..pm1.." Param2:"..pm2.." Param3:"..pm3.." Param4:"..pm4;
  return (retval);
 }

The resulting message differs from expected result. Generated value from this function is:

Param1:  Param2:p1 Param3:p2 Param4:p3

It seems, that there is a shift of parameters when script is called from message text. I tested it with two different installations of NetXMS Version 4.4.3.

Best regards

Georg

Within action messsage text it is possible to use the %[name] macro for generating output to message-text. The called funktion can have parameters. That works fine.

The problem I want to solve is:
Who to use the values of other macros as parameter for the function. E.g. %[script/myfunct(%z,%a,%c)] with the values of %z, %a and %c. The first tests I did are resulting in the strings "%z", %a" and "%c" that are passed to called function.

Who can I achieve that values of macros are passed to the function?

Best regards

Goerg

Having an environmental Control unit where it is not possible to change sensornames via webgui I want to create a form from within netxms-gui where all connected sensors are listed with theire type (temperature, humidity, leakage). Within this form user should have the possibility to name the sensors and the data should be written via SNMP-set to the unit.
For user-convinience this should be done to for all used controller-units, even if there is possibility to change these data via web.
It would bee interesting applying some other data to the sensors like warning temperatur-settings individually per sensor with the same procedure.
Best regards
Georg