NetXMS Support Forum

Я подозреваю что это все-таки на уровне ОС проблема. NetXMS сервер сам по себе ничего не пересчитывает, только через API. Еще возможно что на сервере поправили environment variable TZ, а сам сервер не рестартили, тогда внутри netxmsd может быть старое значение TZ. А на Windows машинах какие настройки timezone сейчас?

Hi!

Group boxes can be selected and moved again. They also can be resized. There are still couple of small glitches related to decoration layer, hopefully I'll fix it in 1.2.5.

What do yo mean by "cannot add an image like a switch onto the map, only actual nodes"? You need to add just image, or object?

Best regards,
Victor

Hi!

Yes, it is known bug.

Best regards,
Victor

Hi!

Looks like this function was forgotten during migration to new console. I'll fix it. As a workaround, you can run legacy console and create vpn connector objects there.

Best regards,
Victor

Hi!

Just added resize possibility for boxes, and they can be moved again. This was caused by migration to Zest 2.0 (underlying graph drawing library). There are still couple of glitches with decoration elements, we will resolve those in 1.2.5. And I have added "snap to grid" function to 1.2.5 features list.

Best regards,
Victor

Hello!

This bug is fixed in upcoming 1.2.4 release.

Best regards,
Victor

Hi!

Due to various reasons there was a big pause in development. I hope to make a 1.2.4 release this week. Automatic maps already working

Best regards,
Victor

Т.е. получается, что nxsnmpwalk выдает правильные данные, а walk из консоли - с 00 вместо правильного последнего байта?

Hi!

Thank you, I've integrated them into source code. I'll create more message files to translate soon. In the meantime, you can translate error messages from NetXMS API:

      "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"

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

Best regards,
Victor

Hi!

Actually, this script will filter out time from 19:00 to 22:00, not from 18:00 - because even for 18:59 condition now->hour <= 18 will be true. You either should lost 1 minute, and use now->hour <= 17, or use condition like

(now->hour < 18 || now->hour >= 22 || (now->hour == 18 && now->min == 0))

If you need to add Saturday and Sunday, you can use script like this:


now = localtime();
if (now->wday == 0)
   return /* sunday-specific check */
if (now->wday == 6)
   return /* saturday-specific check */
return (now->hour < 18 || now->hour >= 22 || (now->hour == 18 && now->min == 0));


Best regards,
Victor

Hi!

For better understanding, this is how discovery works:

If active discovery is on, server uses ICMP ping to find new nodes. Each responded address goes to polling queue.
If passive discovery is on, server polls routing and ARP tables on already known devices. Each new IP address found goes to polling queue.

In parallel, server gets IP addresses from polling queue and checks them for SNMP and NetXMS agent. Then, if it passes discovery filter, new node is created in NetXMS.

So, if NetXMS already knows you routers (and has SNMP access to them), most likely it will soon discovers all computers in your network - just because they are very likely to be found in router's ARP cache. To prevent discovery of unwanted devices, you should set discovery filter. You can limit IP addresses to discover, and you can only add nodes with certain capabilities (like only add SNMP-enabled nodes).

Best regards,
Victor

А можно получить дамп пакетов с трапами? И как сконфигурен сам трап в NetXMS?

А если nxsnmpget с командной строки вызвать, тоже результат неправильный будет?
Про варбинды я что-то не понял до конца, в каком именно месте вылезает неправильное значение?

pohozhe chto da. A est' vozmozhnost' najti core file i poluchit' stack trace iz nego?

Hi!

You have to restart netxms server after changing this parameter.

Best regards,
Victor