NetXMS Support Forum

Quote from: isherim on August 27, 2008, 12:20:44 PM
Созданные для контейнеров карты не удаляются (где-то уже писалось об этом) и не отрисовывается автоматом топология. Не должна?

Topologija risujetsja tol'ko dlja kart s root object Entire Network. Esli root object - container, to risovat' vse nado rukami.

Quote from: isherim on August 27, 2008, 12:20:44 PM
После обновления до 0.2.22 с 0.2.20 и выбора параметра 3 для алиасов интерфейсов, в именах интерфейсов отображаются только первые 2 символа ( Tunnel - Tu, loop - Lo и т.п.). Так задумано?

a mozno screenshot object browser'a?

Pro deployment: est' takoj bug, kotorij mozet pojavljatsja na nekotorih sistemah. Dlja ego ustranenija neobhodimo zamenit' libnetxms.dll na servere na prilozennij.

You cannot create different events from same trap based on varbinds. However, you can process events differently based on event parameters. For example, if you wish to process differently events related to port 1, you can do the following:

1. set varbind .1.3.6.1.4.1.4111.1.2.2.1.1.1.0 as event parameter (let assume that it will be parameter #2)
2. in event processing policy, set appropriate event in event column, and in script column, create filtering script like this:


$2 == 'PortID:1'


This rule will match only events where parameter #2 is equal to string 'PortID:1'.

Best regards,
Victor

Quote from: corkies on August 27, 2008, 06:34:20 AM
I have an agent on 10.x.x.x  that needs to test telnet port on host 123.1.x.x

You should go like this:

1. Ensure that portCheck.nsm (or libnsm_portCheck on UNIX) is loaded at 10.x.x.x
2. Create node object for 123.1.x.x
3. Create network service object under node 123.1.x.x, set it's port to 23
4. For that service object, set poller node to 10.x.x.x

This will cause server to monitor telnet port on node 123.1.x.x from node 10.x.x.x. If something goes wrong, service object will change it's status to CRITICAL.

Alternative way, if you wish to use DCIs:

1. Ensure that portCheck.nsm (or libnsm_portCheck on UNIX) is loaded at 10.x.x.x
2. Create new DCI on 10.x.x.x for agent's parameter ServiceCheck.Custom(123.1.x.x,23)

This will create DCI which will check port 23 on host 123.1.x.x when polled. Values can be following:

0 = service ok
1 = bad arguments
2 = connect failed
3 = protocol handshake failed

Best regards,
Victor

Yes, it's possible.

You can do it in a two ways:

1. Just add device you wish to poll as a node. If node doesn't have neither NetXMS agent nor SNMP agent, NetXMS server will use ICMP ping to determine is it responding or not and change status accordingly.

2. Load PING subagent on any managed node, and use any of ICMP.xxx parameters to send ICMP pings. In this case, you can monitor not only reachable/unreachable status, but also ping response times. You can find additional information about PING subagent here: https://www.netxms.org/documentation/ping_subagent.shtml.

Best regards,
Victor

Hello all!

NetXMS version 0.2.22 is released.

Changes from previous release:

- Scripts now can be used to form event's message (via %[..] macro)
- Scripts in event processing policy now has access to node properties
  via $node variable and to event properties via $event variable
- Implemented XML encoding for NXCP messages
- Added support of custom object attributes
- Minor map improvements
- Fixed issues: #196, #201, #216, #220, #221, #222, #225, #226, #230, #231

Best regards,
Victor

Yes, it's possible. You should have NetXMS agent on monitored host, and have portCheck subagent loaded. Then in properties of network service you wish to check set poller node to monitored host with portCheck subagent.

Hi!

Seems like a bug in a map. I'll check this out. Currently, you can do all configuration from object browser.

Best regards,
Victor

No, it shouldn't be in a domain. All information gathered via NetXMS agent, which by default is running under Local SYstem acount and usually has all necessary rights. Problem is that for MS SQL Server service name is MSSQLSERVER, so correct parameter should be

System.ServiceState(MSSQLSERVER)

Best regards,
Victor

Выложил 0.2.22 - Windows installer и исходники:
https://www.netxms.org/download/netxms-0.2.22.exe
https://www.netxms.org/download/netxms-0.2.22.tar.gz

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

Alex: попробуйте поставить последний вариант сервера и запустить с параметром --debug 7 - я  добавил дополнительный отладочный вывод, поскольку теоретически не могу понять, чем могла быть вызвана проблема с пропадающими хостами при переходе на 0.2.22. Потом или пришлите мне лог целиком, или расскажите, что он пишет про проблемные ноды в строчках, содержащих текст StatusPoll.

Quote from: Sympology on August 19, 2008, 02:46:18 PM
I'm setting up a Data Collection for NetXMS Agents

I select ServiceCheck.Custom(SQLSERVER) Data type Integer. (I Have tried other services)

ServiceCheck.Custom intended to check TCP connectivity. If you wish to check state of Windows service, you should use parameter System.ServiceState, like below:


System.ServiceState(SQLSERVER)


Best regards,
Victor

Eto zaplanirovano sdelat', i budet realizovano.

U menja skompililsja bez problem... 

Ja dumaju chto nado budet poprobovat' MIB kompiler iz 0.2.22

Ja v WMI voobschem-to slablo razbirajus' Esli kto-nibud' napishet hotja-bi chernovik specifikacii - chto dolzno bit' na agente, chto v klientskoj chasti, kak konfiguracija dolzna vigljadet' - mozno budet poprobovat' realizovat'.