NetXMS Support Forum

You should pass device number you have specified in Device= parameter. For exasmple, if you have

Device = 0:ANY:USB

in your config, then you should use for example UPS.SerialNumber(0).
Could you please post your agent's config? Also, try to tun agent in debug mode (with -D switch) and see if there area additional UPS-related messages.

Best regards,
Victor

Hello!

How do you run ./configure? odbcsapi.cpp is a part of odbcquery subagent, which compiles only if --enable-unstable is set. Try to run configure without that switch.

Best regards,
Victor

No, the only requirement is that agent should be reachable by IP. Try to run remote agent in debug mode (nxagentd -D) to see if connections comes to agent. Don't forget that if NetXMS server is multihomed or there are NAT between server and agent, you may need to specify different IP address under MasterServers in agent's configuration file.

Best regards,
Victor

Yes, it's libnxsms_nxagent.so on Linux and nxagent.sms on Windows.

Best regards,
Victor

1. Только при помощи дополнительных внешних скриптов.
2. нет
3. нет
4. это возможно - выбираем шаблон, делаем unbind, выбираем ноду, которую хотим убрать. После этого система спросит, что делать с DCI, созданными через шаблон - удалить или отвязать от шаблона.

При следующем зависании сервиса, попробуйте пожалуйста подключится к сервису командой nxadm -i, дайте команду dump, и пришлите получившийся дамп на [email protected] - попробуем разобраться.

Так вообще-то не должно быть. А какой тип данных стоит у DCI? Должен быть unsigned integer - тогда он будет правильно обрабатывать значения, боль шие чем 2 в степени 31, и переходы счетчика через 0.

Hi!

Because your application written in Java, in process list you will see only a bunch of Java VM processes. If you don't have some API to determine if your application is still running, I see the only way is to determine full command line for each of your applications, and if they are differs, then you are lucky and can monitor if each application is running by using Process.CountEx parameters.

Best regards,
Victor

Hello!

You should configure nxagent.sms as your SMS driver on server, and as SMSDrvConfig, set IP address of NetXMS agent where phone is attached.
On agent, you should load sms.nsm subagent, and set port for phone communication via Device parameter in SMS section. For example, for phone connected on COM1:


# main section here
SubAgent = sms.nsm

*SMS
Device = COM1:


Best regards,
Victor

Yes, but only on Windows. To add USB UPS, use the following syntax:

Device = 1:ANY:USB

if you have only one USB UPS attached, and

Device = 1:<UPS serial number here>:USB

if you have multiple USB devices.

Best regards,
Victor

You have to edit conf files if you wish to execute commands remotely via NetXMS agent. In that case you should add appropriate Action entries in agent configuration files.

Best regards,
Victor

Hello!

To run command on management server itself, you don't need to change server's configuration file. You just need to specify your executable under "Command". If you wish to run .bat or .cmd file, you may need to use form of

cmd.exe /C <your_cmd>

Executable can be located anywhere, but if it is not in system PATH, you should add full path to it when defining action.

Best regards,
Victor

Hi!

Your setup is very impressive It was a pleasure to read your post

Quote from: borislavl on January 29, 2010, 08:38:35 PM
The idea of pushing events between the servers is very good and helpful. Is there a other way to transfer values?

Not yet (except action + push mechanism you already using). I plan to add support for full-scale distributed monitoring, event forwarding is a first step in this direction.

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Is the Event processing the only way of setting the Situation attributes?

Yes.

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Can we for example do something like: s->status = "updated" (s - situation)?

Not yet. But it's very easy to implement, so I'll add it until next release.

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Can we see the current Situation attribute state in NetXMS console?

Yes, via View -> Situation. You should see situations - instances - attributes tree.

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Is there a way to change Custom Atributes?

Only manually via console, or by writing your own tool via C or Java API.

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Can we send parameters to the actions?

Yes (I suppose you mean actions on agents). In action definition you can use placeholders $1, $2, etc. - they will be replaced by appropriate parameter. Parameters should be separated by space - like for calling external command. For example, you can define on agent:

Action = Test:echo $1

and on server define remote action like

Test "%n"

Of course, if security is not a concern, you can define "universal" action like this:

Action = Execute:$1 $2 $3 $4 $5 $6 $7 $8 $9

and then just use any command you want without defining additional actions, like

Execute /my_script "%n" "%m"

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Can we write DCI value to a file (using actions)?

Yes. You can call action with a parameter with macro expansion using NXSL, and access DCI data for current node as usual.

Best regards,
Victor

See https://www.netxms.org/forum/index.php/topic,832.0.html

Hello!

Unfortunatelly, answers to all questions is "no". However, they all looks useful, so I will add them to feature request list.

Best regards,
Victor

Hi!

For example, we want to send email for every critical event in Windows "Application" event log. To achieve that, we should:

1. Create new event in NetXMS (via Control Panel -> Events). Remember ID assigned to new event. For example, let's call our new event EVENTLOG_ERROR and assume that ID 100001 was assigned to it. Set message template to

ERROR: %1

2. Create parser configuration file. To generate event with code 100001 on each error message it will looks like following:

<parser>
  <file>*Application</file>
  <rules>
    <rule>
      <severity>1</severity>
      <match>(.*)</match>
      <event params="1">100001</event>
    </rule>
  </rules>
</parser>

3. Configure LogWatch subagent:

in main section of nxagentd.conf:
SubAgent = logwatch.nsm

in LogWatch section:
*LogWatch
Parser = our_parser_file.xml

4. Restart agent

5. Add appropriate rule to event processing policy (send e-mail for each EVENTLOG_ERROR event)

That's all - now server should send e-mails for every error message written to application event log.

Best regards,
Victor