NetXMS Support Forum

I schedule it for 1.2.10 release (https://www.radensolutions.com/chiliproject/issues/416).

Best regards,
Victor

It has to be changed in the code. I'll add this as an issue to our bug tracker.

Best regards,
Victor

Hi!

Looks like some plugins was not loaded. Is there any errors in Tomcat logs?

Best regards,
Victor

You have to get all bindings from trap into event, then you can use macros %2, %3, and so on to insert values of those varbinds into script command line. You can check interface up/down traps to see how varbinds are mapped to event parameters.

Best regards,
Victor

I suspect that your setup is not entirely correct. First of all, it is not recommended to use system events in data collection thresholds - better create your own event. And second, event generation does not automatically cause alarm - you have to create alarm from event in event processing policy.

Best regards,
Victor

Hi!

60-90 seconds interval looks suspiciously close to status polling intervals. Could it be that this device drops connection when it receives few ICMP pings and TCP connection requests? If device is registered in NetXMS as a node, try to turn off status polling for it (in properties on "Polling" page) and see if it helps. Also, try to turn off network discovery if it is on.

Best regards,
Victor

Hi!

That's good to hear that problem source is found - problem seemed very weird.

Best regards,
Victor

Вот сижу, занимаюсь подготовкой. Для затравки можете перевести сообщения он ошибках из клиентской библиотеки:

      "Request completed successfully",
      "Component locked",
      "Access denied",
      "Invalid request",
      "Request timed out",
      "Request is out of state",
      "Database failure",
      "Invalid object ID",
      "Object already exist",
      "Communication failure",
      "System failure",
      "Invalid user ID",
      "Invalid argument",
      "Duplicate DCI",
      "Invalid DCI ID",
      "Out of memory",
      "Input/Output error",
      "Incompatible operation",
      "Object creation failed",
      "Loop in object relationship detected",
      "Invalid object name",
      "Invalid alarm ID",
      "Invalid action ID",
      "Operation in progress",
      "Copy operation failed for one or more DCI(s)",
      "Invalid or unknown event code",
      "No interfaces suitable for sending magic packet",
      "No MAC address on interface",
      "Command not implemented",
      "Invalid trap configuration record ID",
      "Requested data collection item is not supported by agent",
      "Client and server versions mismatch",
      "Error parsing package information file",
      "Package with specified properties already installed on server",
      "Package file already exist on server",
      "Server resource busy",
      "Invalid package ID",
      "Invalid IP address",
      "Action is used in event processing policy",
      "Variable not found",
      "Server uses incompatible version of communication protocol",
      "Address already in use",
      "Unable to select cipher",
      "Invalid public key",
      "Invalid session key",
      "Encryption is not supported by peer",
      "Server internal error",
      "Execution of external command failed",
      "Invalid object tool ID",
      "SNMP protocol error",
      "Incorrect regular expression",
      "Parameter is not supported by agent",
      "File I/O operation failed",
      "MIB file is corrupted",
      "File transfer operation already in progress",
      "Invalid job ID",
      "Invalid script ID",
      "Invalid script name",
      "Unknown map name",
      "Invalid map ID",
      "Account disabled",
      "No more grace logins",
      "Server connection broken",
      "Invalid agent configuration ID",
      "Server has lost connection with backend database",
      "Alarm is still open in helpdesk system",
      "Alarm is not in \"outstanding\" state",
      "DCI data source is not a push agent",
      "Error parsing configuration import file",
      "Configuration cannot be imported because of validation errors",
      "Invalid graph ID",
      "Local cryptographic provider failure",
      "Unsupported authentication type",
      "Bad certificate",
      "Invalid certificate ID",
      "SNMP failure",
      "Node has no support for layer 2 topology discovery",
      "Invalid situation ID",
      "Named instance not found",
      "Invalid event ID",
      "Operation cannot be completed due to agent error",
      "Unknown variable",
      "Requested resource not available",
      "Job cannot be cancelled",
      "Invalid policy ID",
      "Unknown log name",
      "Invalid log handle",
      "New password is too weak",
      "Password was used before",
      "Invalid session handle",
      "Node already is a member of a cluster",
      "Job cannot be put on hold",
      "Job on hold cannot be resumed",
      "Zone ID is already in use",
      "Invalid zone ID",
      "Cannot delete non-empty zone object",
      "No physical component data",
      "Invalid alarm note ID",
      "Encryption error",
      "Invalid mapping table ID",
      "No software package data",
      "Invalid DCI summary table ID",
      "User is logged in",
      "XML parse error",
      "High query cost",
      "License violation",
      "Number of available client licenses exceeded"

      "Bad MIB file header",
      "Bad MIB file data"

Hi!

I suggest to run server with debug level 4 or higher and check server log. Maybe there are errors at command execution, or it is not executed at all. You can change debug level in run time by opening server debug console (from Tools->Server Console menu) and entering command debug 5 (or whatever debug level you need).

Best regards,
Victor

Hi!

Looks like a bug - maybe error threshold is broken somehow. I'll try to reproduce this on my test system.
Also, you should get SYS_SNMP_DOWN event at next configuration poll if SNMP agent is not responding - do you get those events?

Best regards,
Victor

Ну да, проблема в том, что устройство о своем интерфейсе не сообщает через стандартный MIB. При прямом подключении сервер из других мест может взять информацию (ARP кеш, таблицы MAC адресов на свитчах), а через прокси это не работает. Проще всего будет написать драйвер. Что это за устройство, и какие у него значения в ветке .1.3.6.1.2.1.1?

Hi!

Can you provide me latest vendor MIBs and full SNMP walk of a device (or ideally access to real device via SNMP)?

Best regards,
Victor

Hi!

You can add transformation script like this:


if ($1 > 100)
   return 100;
return $1;


(replace 100 with your maximal meaningful value).

Best regards,
Victor

Currently not.

Best regards,
Victor

You can set config variable LogAllSNMPTraps to 1 - then server will log traps from unknown devices, but you cannot get automated alarm from that log. There are also feature request for device discovery based on SNMP traps: https://www.radensolutions.com/chiliproject/issues/307. We plan to implement it in one of next versions.

Best regards,
Victor