NetXMS Support Forum

U eventa severity zestko zadan. Esli est' neskol'ko thresholdov, to obichno delaetsja neskol'ko eventov i v zavisimost' ot thresholda generirujutsja raznie eventi.

It can be done already by creating additional DCI (you can use dummy DCI or one of the parameters you wish to sum up as the base) and sum all required values in transformation script.

Best regards,
Victor

Quote from: paul-k on December 09, 2010, 04:59:57 PM
несколько вопросов в основном про графики:

1) не могу понять, каким образом отображаются графики параметров на perfomance tab, наследуемых от System.Agent'a? в темплейте в DCI параметры не вынесены на вкладку perfomance, но, тем не менее - отображаются в соответствующих нодах (параметров пять, графика, что характерно - 4).

Eto hardcoded konfiguracija. Iznachal'no bila tol'ko ona, potom ja sdelal vozmoznost' dobavit' ljuboj DCI na performance tab. Teper' dumaju chto hardcoded parametri mozno i ubrat'.

Quote from: paul-k on December 09, 2010, 04:59:57 PM
2) можно ли изменить масштаб (scope) на perfomance tab?

Net. Ja planiruju eto sdelat', no skoree vsego uze tol'ko v novoj konsoli.

Quote from: paul-k on December 09, 2010, 04:59:57 PM
3) можно ли строить два (и больше) графика на одном - например совмещать network in/out или нагрузку по разным процам на одном графике?

Net. No toze v planah.

Quote from: paul-k on December 09, 2010, 04:59:57 PM
и вопрос не про графики:
не понял, где задается правило если SYS_IF_DOWN => SYS_NODE_CRITICAL. В Event Proc Policy вроде бы стоит (по умолчанию) - Severity: From Event... (хочется, чтобы по SYS_IF_DOWN статус узла становился Minor)

Status hosta opredeljaetsja kak most critical iz aktivnih alarmov i podchinennih ob'ektov (obichno interfejsov). Sootvetstvenno esli interfejs nedostupen, to ego status CRITICAL, i host stanovitsja CRITICAL. Eto mozno menjat', menjaja Status Calculation u hosta ili Status Propagation u interfejsa - naprimer mozno v Status Propagation interfejsa zadat', chto svoj status CRITICAL naverh on otdaet kak MINOR.

Hi!

Appearance of these graphs depends of availability of appropriate parameters on agent. As on Windows physical memory stats provided by core agent, and CPU and disk stats provided by winperf subagent, most likely you do not have winperf.nsm loaded on your node.

Best regards,
Victor

Hi!

There are no really working sample code like agent skeleton. I quickly trim code from one of our commercial modules - it can be used as starting point. I added comments on important parts of the code.

Best regards,
Victor

Yes, it must be named "Dummy". This is what I wrote in my previous message:

Quote from: Victor Kirhenshtein on December 07, 2010, 09:52:00 AM
You can create additional DCI with source "Internal" and name "Dummy" (of course description can be any).

You can change description of the DCI, but not the name. Description is a free form text intended to be read and understand by humans, but name is a parameter's identifier understandable by server and/or agents. "Internal" origin means that values for these parameters generated by NetXMS serer itself, without asking any external entities. One of supported internal parameters is named "Dummy", and it always returns 0 when polled for value. It was added specifically for providing "ticks" for calculated DCIs.

So it is not a "workaround", it's just correct system configuration

Best regards,
Victor

It's a value reported by SNMP agent on target node for standard SNMP OID .1.3.6.1.2.1.1.2.0 (sysObjectID), which is described as following:

The vendor's authoritative identification of the network management subsystem contained in the entity.  This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed.  For example, if  vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

Best regards,
Victor

Классическая последовательность действий такая:

1. Делаем новый event, например PROCESS_DOWN; Текст делаем таким:
Process %6 is not running

2. Делаем DCI для параметра агента "Process.Count(process.exe)"

3. В поле instance пишем "process.exe"

4. Добавляем threshold с условием "equals 0", в качестве события ставим PROCESS_DOWN;

5. В event processing policy добавляем обработку события PROCESS_DOWN (генерация аларма или отсылка уведомления).

Теперь если процессов под названием "process.exe" не будет, получим уведомление/аларм с текстом

Process process.exe is not running

Hi!

If you call GetVariableStr with only variable id argument, dynamically allocated string returned, and it is responsibility of the caller to deallocate it when it's no longer needed by calling "free".

Best regards,
Victor

Hi!

I've found a bug (or feature ). NetXMS expects that every node which have IP address is bound to at least one IP subnet. Usually this is done automatically during configuration poll. As you have configuration polls disabled, subnet bindings never occurs, and so on startup server considers these nodes as problematic (because they dos not have subnet binding) and fails to load them. I'll change this in next release. As a workaround for current version you can do manual configuration poll on each node once - this will create subnet object and bind nodes to subnet. Also, you can try to replace nxcore.dll and nxdbmgr.exe with attached patched version - this should allow server to load correctly even if nodes does not have subnet binding.

Best regards,
Victor

Could you please send me screenshots of your DCI configuration?

Best regards,
Victor

Hi!

Attached is modified portcheck.nsm, which uses same timeout value as for connect to wait for data available from server, so you can use ServiceCheck.SMTP parameter like following:

ServiceCheck.SMTP(host, mail@domain, 5000)

to use 5 seconds timeout on connect and waiting for data. Don't forget that NetXMS server by default waits obnly 2 seconds for results from agent, so if your check takes longer time, you need to increase value of server's configuration parameter AgentCommandTimeout.

Best regards,
Victor

Looks like database is damaged for unknown reason. If I understand correctly, you are running NetXMS server as a service, and database corruption occurs if you restart your PC. I suspect that during shutdown server process terminated before it completes database update, so database becomes inconsistent. To check it, could you please do the following:

1. Run nxdbmgr with debug level 6 (by adding -D 6 to netxmsd.exe command line)
2. Before restarting PC, stop NetXMS Core service manually
3. Restart PC and check database for correctness

If there will be same problem, send me debug log. If problem will disappear, try to restart PC as usual (without stopping NetXMS service), and if problem will appear, send me debug log.

Best regards,
Victor

Hi!

Unfortunately, there are no predefined checks for protocols other then you listed. You can either use "custom" check, which just checks connectivity to TCP port, or write external scripts and call them via external parameters for protocol checking.
For a long time I wish to rewrite port checker subagent as an engine which runs NXSL scripts doing protocol checks, so it can be easily extended, but still cannot find enough free time to do that

Best regards,
Victor

Hi!

Looks like a serious bug. Could you please run netxmsd with full debug on (by adding option -D 9) and send me debug log?

Best regards,
Victor