NetXMS Support Forum

Hi,

tcp/4700: server -> agent
tcp/4701: client (gui or integration tools) -> server
tcp/4747: mobile agent -> server

Best regards,
Victor

Can you communicate with the library using command line tool (nxsnmpwalk or nxsnmpget)? For example

nxsnmpwalk -v2c -c your_community ip_address .1.3.6.1.2.1.1

also try community "public".

Best regards,
Victor

Did configuration poll detect MSL node as SNMP node? If yes, it could be some other server trying to communicate with MSL over SNMP, and MSL just sending SNMP authentication failure traps to NetXMS server (because it is configured so).

Best regards,
Victor

Добавил feature request про SAPI в новой консоли: https://dev.raden.solutions/issues/1271 (чтобы не забылось).

One (or two) issues here. First of all, ensure that you are using "SNMP walk - OIDs" as discovery method (because you want instance to be interface index). Alternatively, you can change base OID to return interfaces indexes as values.
And most important, you replace original instance value with interface operational state:


return %(true, oper, dec . " - " . nam);


effectively reducing all instances into few. Correct will be to keep interface index as instance:\


return %(true, $1, dec . " - " . nam);


Best regards,
Victor

Hi,

it's definitely a network issue. One possible cause could be MTU mismatch and/or disabled fragmentation somewhere along the route. This could explain why small packets (connection setup and ack) pass through while larger packets with data cannot.

Best regards,
Victor

Hi,

please increase debug level to 6 and check server log for messages with XMPP prefix - maybe there will be some hints.

Best regards,
Victor

What is in the netxmsd log when you try to connect after OS restart?

Best regards,
Victor

Hi,

seems to be a bug. Most likely you have agent cache on, and server do not send reconfiguration command when you change DCI on another node. I'll fix that.

Best regards,
Victor

Hi,

currently it's not possible. Actually table thresholds need major rework, I'll try to do at least some improvements in 2.1.

Best regards,
Victor

Hi,

you are using undefined variable "transport" here:


adm = SNMPGet(transport, ".1.3.6.1.2.1.2.2.1.7." . $1);


Best regards,
Victor

Hi,

please show output of configuration and status poll for camera node.

Best regards,
Victor

Hi,

seems that configuration still mismatch. Double check community on device and in node properties in NetXMS. Also make sure that NetXMS server IP address is listed as allowed in device SNMP configuration.

Best regards,
Victor

Hi,

this is not an error, just message dump with system event configuration being transmitted to client. If you have SMTP issues, you should look for lines with word SMTP.

Best regards,
Victor

Hi,

your initial configuration is correct, seems to be a bug in a server. What version you are using?

As for alarms auto-resolve, you should set alarm key when create alarm, and use "resolve alarm" or "terminate alarm" action when processing recovery event with matching key. You can use default rules for node down/node up as an example.

Best regards,
Victor