NetXMS Support Forum

Sorry, I misunderstood the situation. Then you can use the following DCI:

Origin = SNMP, Parameter = OID you are using to get IP address

with the following transformation script:


server = FindNodeObject($node, "netxms-server-name");
return AgentReadParameter(server, "Icmp.Ping(" . $1 . ")");


Best regards,
Victor

Quote from: andrey--k on March 05, 2014, 04:34:01 PM
Приведите пожалуйста пример создания Transformatin script для SNMP-table.

Вот пример скрипта для таблицы - списка процессов на Cisco рутере. Колонку TIME из микросекунд переводим в проценты. В аттаче шаблон с етой таблицей, чтобы можно было посмотреть всю конфигурацию целиком.


ciTime = $1->getColumnIndex("TIME");
for(row = 0; row < $1->rowCount; row++)
{
value = $1->get(row, ciTime);
$1->set(row, ciTime, value * 100 / 1000000);
}


Quote from: andrey--k on March 05, 2014, 12:08:26 PM

Quote from: andrey--k on March 04, 2014, 11:09:53 PM
Решил задачу через динамические DCI. Там пишет raw (hex) в БД.

Спасибо.

Решение оказалось неудачным.
Сервер начал потреблять очень много ОЗУ.
Буду пробовать реализовать поддержку CP1251.

Подскажите пожалуйста, deb пакеты в последней версии (1.2.12), для Debian Wheezy, скомпилированы с  --enable-UNICODE ?

Да, с UNICODE.

Hi!

Solution #1 seems correct. You can get value from remote agent with AgentReadParameter function. However, easier would be to use proxy node directly:

On GATEWAY1 a DCI: Origin = Agent, Parameter = Icmp.Ping(ip), Proxy-node = NetXMS-server

No transformation script needed in this case.

Best regards,
Victor

Hi!

In general, all those values should be kept around zero, or on some stable level. It is normal to have occasional spikes on any of them, but average for 10-15 minutes should be low and not growing over time. Long time high or growing values for those DCIs could indicate:

"Configuration poller queue for last minute" - there are not enough configuration pollers or configuration polls take unusually long time. One of the common reason is timeouts because some communications are blocked by firewalls. It is recommended to disable agent and/or SNMP polling for nodes where they are not needed. Since 1.2.13 it is also possible to disable Check Point SNMP agent check globally - this could speed up configuration polling.

"Status poller queue for last minute" - there are not enough status pollers, or status polling interval should be increased.

"Average time to queue DCI for polling for last minute" - usually caused by excessive waits on different internal locks. Sometimes this is a sign of a bug in a server.

"Database writer's request queue for last minute" (all 3 variants) - indicates that there are more outstanding SQL INSERT or UPDATE requests then database can handle. When database by itself can handle more load but database connection is a bottleneck increasing number of database writers will help.

"Data collection poller's request queue for last minute" - server cannot collect data fast enough. This may happen when monitored nodes responds too slowly, or data collection interval set for too low.

Best regards,
Victor

Quote from: andrey--k on March 05, 2014, 11:25:51 AM
Удалил 75000 DCI.
Потребление памяти после запуска уменьшилось с 960 MB до 215 MB.
Нагрузка на ЦПУ упала с 50-60% до 0,5-2%.

What type those DCIs was - SNMP or agent? What was collection interval?

Best regards,
Victor

Quote from: Rabid on February 28, 2014, 10:31:21 PM
Will this version allow me to do what is in the following post and if so, how do I set it up?

https://www.netxms.org/forum/general-support/dci-thresold-on-string/

Sorry, I forgot to do this in 1.2.12. I've added service list and service table to Windows agent in upcoming 1.2.13 release.

Best regards,
Victor

Hi!

Try to add --disable-xmpp just in case.

Best regards,
Victor

Don't have CentOS 6.5 for testing at the moment, will try it tomorrow. How did you build agent (with what configure options)?

Best regards,
Victor

I suspect that when there is two adapters in same subnet ESXi choose one to reply from, and so response packet comes from different IP address and ignored by request sender. Capturing SNMP packets with tcpdump can prove or deny this assumption.

Best regards,
Victor

Да, действительно, в MIB'е есть описание конвертации:

DateAndTime ::= TEXTUAL-CONVENTION
    DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d"

кто бы мог подумать Сейчас наш MIB компилятор поле DISPLAY-HINT игнорирует, я добавлю feature request на это.

Looks like it's crashed even before agent completes initialization. Can you try to set log file to a file instead of syslog? Also, on what system you are running it?

Best regards,
Victor

It will be published on web site and announced on forum as usual.

Best regards,
Victor

А как показывает даты из .1.3.6.1.2.1.25.6.3.1 snmpwalk?

Hi!

Could you also get tcpdump from NetXMS server node and other node? Also, is there any difference between NetXMS and other node in network connectivity? Could be also issue with LACP (or related somehow) which causes packet duplication and/or loss. Did you try it with one uplink disconnected?

Best regards,
Victor