NetXMS Support Forum

Hi,

if you got emails that means that somewhere you have rule that catches this event and sends an email. Maybe something  generic, like all events from certain devices or with certain severity. Easiest way to turn off processing for this event is to add as first rule in EPP with condition set to just that event and action set to "stop processing".

Best regards,
Victor

Hi,

currently the only way is to setup event processing action for desired events that will execute external script that will use snmptrap command to send trap to upper level NMS. We plan to have SNMP trap sending as separate action type for some time already, it will be implemented eventually. 

Best regards,
Victor

Hi,

what server version do you have and on what OS? If Linux, was it installed from packages or built from source?

Best regards,
Victor

Save the date – March 4, 2021 at 4pm CET.

We will organize online Q&A session with NetXMS developers. Please contact @moshenska in our Telegram support channel or at [email protected] to sign up.

P.S. If you have any complex questions, let us know in advance.

А в логе самого netxmsd что-то есть?

Hi,

you can use script DCI that will read table value either directly from agent or from table DCI and extract version of product of interest. For example, this script accepts package name as argument and return it's version, directly reading table from agent:

packages = $node->readAgentTable("System.InstalledProducts");
if (packages == null)
   return null;
for(p : packages->rows)
{
   name = p->get(0);
   if (name == $ARGS[1])
      return p->get(1);
}
return null;


Best regards,
Victor

We have switched bundled JRE to OpenJDK (AdoptOpenJDK build), that could be the reason. Try to uninstall old version first, then install 3.8.166 from scratch.

Regarding agent packages, you mean that it disappears from package list after server restart?

Best regards,
Victor

Hi,

you mean web UI installer for Windows? I just tested it, and it works as expected. Did you choose to install bundled JRE? If no, what Java version you have installed?

Best regards,
Victor

Two ways here:

1. Set alarm timeout and what event will be generated, and then create another rule to terminate alarm on timeout event. Note that timeout event will be generated only if alarm will still be in outstanding state.

2. Execute script action with required delay in same rule, and terminate alarm from that script.

Best regards,
Victor

Hi all!

New patch release for version 3.8 is just published (version 3.8.166). Changes since previous release:

- Improved driver for H3C (now HPE) switches
- Fixed intermittent problems with SNMP communications via proxy agents
- Fixed multiple file download in file manager in web UI
- Fixed excessive server memory consumption when transferring file from client to agent over slow link
- Fixed occasional high CPU usage by server process
- Deleted unused job_history table
- Fixed graph refresh
- Fixed object synchronization issue in web UI
- Fixed memory leak in server
- Fixed incorrect sorting by "Source" column in user management view
- Fixed intermittent client disconnects
- Fixed interface synchronization for network map element on dasbhboad
- Fixed issues:
        NX-1989 (Compile NXSL in dci instance discovery filter and container autobind filter)
        NX-1990 (Add filter in Script Library)
        NX-1996 (Retriggered event when node comes out of maintenance is missing value for currentValue (%4) parameter)
        NX-2005 (Add ability to have formatting in Telegram notifications)
        NX-2011 (NXSL inList function returns int32 instead of boolean)

Best regards,
Victor

Спасибо за предоставленные устройства! Пока что частичный успех

4210 с софтом версии 3.10 сейчас работает корректно. Новая версия драйвера войдет в сегодняшний релиз.

S3100 с софтом тоже версии 3.10 пока не работает. Несмотря на то, что версию он сообщает такую же, как и 4210, набор MIBов у него другой (Huawei, а не 3Com). Надо будет делать отдельный драйвер. К сегодняшнему релизу не успел, но думаю к следующему патч релизу в ветке 3.8 сделаю.

Hi,

we will test that. So far looks like a bug.

Best regards,
Victor

Hi,

change localhost to 127.0.0.1 as reporting server address. This is known issue - localhost resolved to IPv6 loopback, but reporting server process listens on IPv4 only.

Best regards,
Victor

Quote from: Denis on February 18, 2021, 11:52:25 AM
Виктор, спасибо. Было бы не плохо сделать специальный аттрибут, поскольку как я понимаю коммутаторов с такой проблемой не много (может они старые, а в современных все соответствует спецификации).

Quoteно это надо еще проверять, сделать больше VLAN'ов в разной конфигурации.

По поводу проверки, надо как-то специально настроить или просто назначить штук 10 vlan на разные порты?

да, именно так.

Currently it's not possible, but we will consider it for implementation.

Best regards,
Victor