NetXMS Support Forum

Hi!

Do you mean automatic agent installation on remote machine or just automatic addition of new machines with agents to monitoring database? Latter is possible with automatic discovery - you can turn on automatic discovery and set filter to only accept nodes with agent installed. Then you can use automatic binding scripts on containers to place those new nodes into object tree. You can also send notification when new node added by adding appropriate action for SYS_NODE_ADDED event.

Best regards,
Victor

Hi!

You can create internal type DCI (with source set to "Internal") and Dummy parameter - it will just generate 0. Then in transformation script you can use SNMPGetValue function to get actual value of required OID. This function will return null if OID does not exist, so you can check it and return some meaningful value in that case.

Best regards,
Victor

Hi!

I would suggest the following scheme:

Create events (of course you can name them any way you want):

TRAP_RAW (normal severity)
TRAP_INFO (normal severity)
TRAP_WARNING (warning severity)
TRAP_CRITICAL (critical severity)
TRAP_CLOSE (normal severity)

Create SNMP trap mapping for trap .1.3.6.1.4.1.23986.1.4.1 with the following varbind mapping:
#2 - .1.3.6.1.4.1.23986.1.2.3.1.9.200083
#3 - .1.3.6.1.4.1.23986.1.3.4.1.6.2368
#4 - .1.3.6.1.4.1.23986.1.3.4.1.8.2368  (this is needed if you want to pass message as parameter to event)

Create server action that will call the following NXSL script from library:


if ($event->parameters[2] == 2)
{
   switch($event->parameters[3])
   {
      case 3:
         evt = "TRAP_CRITICAL";
         break;
      case 2:
         evt = "TRAP_WARNING";
         break;
      default:
         evt = "TRAP_INFO";
         break;
   }
   PostEvent($node, evt, null, $event->parameters[4]);  // pass message as first parameter to generated event
}
else
{
   PostEvent($node, "TRAP_CLOSE");
}


Then create the following rules in event processing policy:

1.

event is TRAP_RAW

action: call script and stop processing

2.

event is TRAP_INFO, TRAP_WARNING, or TRAP_CRITICAL

action: create alarm with some key

3.

event is TRAP_CLOSE

action: terminate alarm with key used in rule #2

Please note that message extracted from trap will be available as %1 in message template for generated events and alarms.

Best regards,
Victor

Can you please compare MD5 hash of files netxms.mib on server and on client? Problem in 1.2.11 was caused by error during file transfer  -we have to check if now it is the same issue or not.

Best regards,
Victor

Hi!

I suppose you mean 1.2.13 - 1.2.12 already archived and not referenced directly on download page. I'll prepare 1.2.14 release in a next few days - it should fix crashes discovered in 1.2.12 and 1.2.13. Then 1.2.13 will be moved to archive.

Best regards,
Victor

Try to do configuration poll for the node with changed IP address - will it resolve primary host name to new IP?

Best regards,
Victor

Hard to suggest anything except trying to upgrade to latest Java 7 JRE or maybe try Java 6.

Best regards,
Victor

Quote from: VSS on April 14, 2014, 10:53:37 AM

Quote from: kozlov_ao on April 14, 2014, 10:35:27 AM
* 7-22 * * * */30 - дергает данные каждые 30 секунд с 7 до 22 часов каждый день.
* 9-19 * * * - дергает данные каждую минуту с 9 до 19 часов

Как ограничить праздничные дни - незнаю.. вернее предполагаю, но будет реально много записей.

Спасибо! "-" просто не было в доке, а в исходниках смотреть тяжеловато...

А по поводу праздников может что-то с помощью Transformation script ... придумать... ?

Можно, только не в transformation script, а в event processing policy - можно добавить скрипт в условие, чтобы он не давал срабатывать действиям по выходным например.

Скрипт, который не дает срабатывать правилу в воскресенье:


return localtime()->wday != 0;


Скрипт, кототый не дает срабатывать правилу 1-го января:


t = localtime();
return (t->mon != 0) || (t->mday != 1);


Hi!

Could you please describe your goal more specific? MPLS by itself will not give you ability to communicate with remote server, you'll need IP connectivity over MPLS network anyway.

Best regards,
Victor

Hi!

Please check log files located under web UI installation directory.

Best regards,
Victor

Пожалуй единственный вариант - это сделать Internal DCI с параметром Dummy и в transformation script вызывать AgentQueryParameter с нужным SQL запросом.

Похоже по какой-то причине агент тексты ошибок на русском получает.

Расшифровка кода такая:
0xC0000BB8 (PDH_CSTATUS_NO_OBJECT)   The specified object is not found on the system.

Непонятно только к какому объекту это относится. Больше в логе ничего нет?

Все что есть: https://www.netxms.org/documentation/adminguide/subagents.html#dbquery

А запрос определен в конфиге агента или прямо в DCI?

Замени еще src/server/core/nxslext.cpp на приложенный