Спасибо. Работает.

Slow, but implemented finally However, it's not complete implementation yet - there are some limitations: All agents must support same SNMP version; All agents must use same community string or USM credentials; Agents on ports other than node's default not checked for availability during status polls (you can however detect DCI collection errors). I plan to add full per-agent configuration (version, credentials, etc.) in future versions. Best regards, Victor

Хотелось бы кнопочку "Отметить все"

Dear Team, Please provide support for CIMD Computer Interface to Message Distribution Promoted by Nokia with openly available specifications and widely used. SMPP http://en.wikipedia.org/wiki/SMPP There is huge, matured and widespread acceptability of SMPP standard across telecom industry. SMPP approved by ITU (International Telecom Union) for SMS. URL http://opensmpp.logica.com/introhtml/menu.htm contains specification of SMPPv3.4 and library, simulator, and test-program from Logica promoter company. URL http://smppapi.sourceforge.net/ is another good library to be used. I donot recommend because it is too lengthy where Logica library is very much abstract to developers Current implementation requires a compatible modem on serial-port which may not be choice for many of network admin. I can understand that if there is network outage then no SMS alert will be received by admin but then it is good to have alert for other outages

 In the node 'move to another container' operation the view is a flat list of all the containers, it would be useful if instead of a list the view showed the same hierarchical structer that can be seen in the object browser. Regards, David

I would second that. The ability to segment the network tree and the unique IP address rules being moved to the 'customer' segment would great functionality, maybe this is the zoning feature Victor refers to. David

Hi, We are, at the moment, using two installations to monitor two different locations. The largest installation contains about 1000 nodes and the smaller one about 200 - 300. We are planning to add about 1 - 2 more locations in the near future and gather all the alams in a central server for easier management.

Victor, thank you for your quick reply and willingness to improve the NXSL flexibility. @victor said in NXSL improvements: @borislavl said in NXSL improvements: Actions to be able to return a value(response from the command) to a specified DCI. How this is different from DCI with external parameter as a source? The differences are that the External Parameter can be attached to a DCI (collected on a period), but not to the event processing policy. If trying to create management workflow in NXSL - it is needed on some events to execute action, which result to trigger a second event and action on the local server. On the Linux servers this can be done with 2 nested nxpush executions (the result from the first nxpush is being pushed back to the local server from the second nxpush), but on the Windows servers this become complicated, because of the restrictions of the Win cmd shell. @victor said in NXSL improvements: @borislavl said in NXSL improvements: Or to call action from NXSL and receive/not receive value as response I'm not sure that this is needed in DCI transformation and event filtering scripts. Main concern here is performance - for example, if event filtering script calls external action and waits for it's completion, it potentially could block event processing for significant amount of time. I understand your concerns here, I was looking for such functionality in the scripts library, so when one action with parameter %[script] is executed - to be possible to execute another action before it and pass the result to the main action. Or based on the logic in the script to execute one or more actions. At the moment if the logic is straight forward - this can be done with multiple lines in the Event Processing Policy, different scripts which return 1 or 0 (execute/not execute) and different action on each line. Or one action which calls a script in the OS shell and there nxget and nxpush to be used as communication with the variables (DCI). @victor said in NXSL improvements: @borislavl said in NXSL improvements: From NXSL to be possible to set DCI values (activating their Thresholds as configured) Could be implemented, but probably for "push" DCIs only (I mean allow to set value only for push DCIs). This would be great. Even in "push" DCIs - it will be useful. At the moment the alternative is to do actions which are calling the shell command nxpush, but if this can be done direct from the script - it will be much easier.

Hi! @jdl said in Some new things: When creating a node, reverse lookup would be interesting. Sometimes one knows the IP but not the FQDN. If you enter an IP @ and push "resolve" you get IP @ of localhost (the one running the console) and no name. Currently, you can enter IP address as node name, press "Resolve" to fill IP address field with same value. If node has IP address as it's name, it will be resolved via DNS or agent at first configuration poll. But yes, reverse lookup in dialog could be useful. @jdl said in Some new things: when defining a new event processing rule, we hav eto close the window to get asked if we want to save the story. Would be nice to have a drop down menu with options (like duplicate rule, etc...) among which "save" to save the current config if relevant (if no change then greyed out You can use main menu Policy -> Save policy or just press Ctrl+S. Best regards, Victor

Hi there, Some suggestions... I noticed that when an event (normal) clears out an alarm (critical) and you request an email to be sent with a message built up using macros, well the email is nearly empty as the macros are returning empty strings (%M, %A... only severity and time/date are given). Email subject is: [%S] %A - only severity returned Body content is: Alarm: [%S] %A\nNode: %n [%a]\nTime: %t - %A is not returned! Using %m is not always convenient! All this because the cleaning event is not creating any alarm. The only flexibility is about the message key for cleaning related events. It would be nice to still be able to define a message text available for action such as sendmail. You will most probably suggest to use %M or %[name] but for some scenarios no script is used. So it is quite cumbersome to have to define a script just for the sake of having a text message available. Suggestion: get events configured as for alarms and give the option to display event in alarm list or not. Then message text still exists and is available for actions. Further extension: active event list, history event list, archives. Created events are displayed in alarm list. When ack'ed or terminated, then instead of trashing them from the alarm list, park them in a history event list (new window) for a while (configurable) then trash it... or preferably archive it in a text file. Best regards, Jdamien

Hi Victor, Could you please update the NetXMS - so when there is a "data collection error" - this value to be recorded to the DCI where the error happens? At the moment if i.e. checking connection on specific interval and the last value was that there was connection, but after that there is data collection error - the DCI remains the same old value - that there is connection and just stop updating. If you are using the NXSL for checking this DCI it will continue accepting the old value before the error (like everything is ok).   Thank you, Boris

Just a note: Running XMS server on a Hyper-V Windows 2008 x64 machine and it works 100% ;D Already monitoring over 100 devices and servers

AS a part of this feature, it could be nice for windows copy-paste functionality in object browser. Such way brief info about monitoring settings could be pasted from single node And if only copy paste could work in data collection configuration... mmm!

Also, feel free to move this topic to general support tree - to keep forum clean

Здравствуйте, В Event Processing Policy Editor в строке Source можно указывать контейнеры или устройства и хорошо было бы, если бы можно было также указать устройства которые не должны обрабатываться при создании Policy. Как в access-list'ах: выбираю использовать в качестве Source такой-то контейнер (permit), но исключаю из этого контейнера несколько устройств (deny). Либо если есть устройства пересекающиеся в разных контейнерах, тогда ставлю deny на один контейнер и permit на другой. На мой взгляд это добавило бы гибкости.

Всем привет! Хотелось бы чтобы alarm viewer вместе с alarm notifier или без него должным образом сигнализировали о появлении алярмов. Звуковое оповещение вроде как есть, всплывающий popup в notifier'е есть, но мне кажется можно было бы добавить еще опцию, чтобы само окно alarm viewer'а всплывало на верх. Спасибо!

Hi,     I coonfigured NETXMS in my Office for monitoring 400 Production Machines, I want to send Alarms for Load, Disk, memory how to add the event and Description to Event Editor and need to Send Email Escalation .Please help me in this Thanks in Advance, Subbu

Здравствуйте. Возможно ли будет реализовать функцию информирования о статусе Netxms сервера по почте, с выбором нескольких почтовых адресов доставки и периодичность отправления. На мой взгляд в сообщении необходимо указывать число активных и неактивных нодов, список не активных нодов, ошибки зарегистрированные сервером и не отмеченные как решённые, возможно информацию с заданных DCI.

Hello! I don't know if this is already available, I tried to search buth without success. It could be an interesting feature the possibility to calculate the 95th percentile, as it used as a common way to estimate the bandwidth consumption. Marco.

Было бы неплохо заменить скрипт запуска для FreeBSD. тот который есть сейчас не дает запустить агента с какими либо ключами. #!/bin/sh # PROVIDE: nxagentd # REQUIRE: DAEMON # BEFORE: LOGIN # KEYWORD: shutdown nxagentd_enable=${nxagentd_enable-"NO"} nxagentd_flags=${nxagentd_flags-"-c /usr/local/etc/nxagentd.conf -d"} . /etc/rc.subr name="nxagentd" rcvar=`set_rcvar` command="/usr/local/bin/nxagentd" load_rc_config $name start_cmd="echo \"Starting ${name}.\"; ${command} ${nxagentd_flags}" run_rc_command "$1" Вот с таким скриптом все прекрасно работает. В /etc/rc.conf можно использовать различные флаги: nxagentd_enable="yes" nxagentd_flags="-M 10.1.10.18 -d"