Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#691
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
#692
Announcements / Q&A session at March 4th
February 24, 2021, 07:25:06 PM
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.
#693
А в логе самого netxmsd что-то есть?
#694
General Support / Re: DCI from table element
February 24, 2021, 03:23:22 PM
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
#695
General Support / Re: 3.8.166 Windows oddities
February 24, 2021, 03:17:40 PM
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
#696
General Support / Re: 3.8.166 Windows oddities
February 24, 2021, 02:43:57 PM
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
#697
General / Re: Issues with clearing alarms
February 24, 2021, 01:39:22 PM
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
#698
Announcements / NetXMS 3.8 version 3.8.166
February 23, 2021, 10:41:10 PM
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
#699
Спасибо за предоставленные устройства! Пока что частичный успех :)

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

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

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

Best regards,
Victor
#701
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
#702
Quote from: Denis on February 18, 2021, 11:52:25 AM
Виктор, спасибо. Было бы не плохо сделать специальный аттрибут, поскольку как я понимаю коммутаторов с такой проблемой не много (может они старые, а в современных все соответствует спецификации).
Quoteно это надо еще проверять, сделать больше VLAN'ов в разной конфигурации.
По поводу проверки, надо как-то специально настроить или просто назначить штук 10 vlan на разные порты?
да, именно так.
#703
Feature Requests / Re: Object Tool on Switch Port?
February 18, 2021, 10:15:15 AM
Currently it's not possible, but we will consider it for implementation.

Best regards,
Victor
#704
Hi,

I've added feature request for option to display ICMP stats on map - https://track.radensolutions.com/issue/NX-2007.

For placing data on the link you can right-click on link, go to properties, data sources, and add one or more DCIs whose value should be displayed on the link.

Best regards,
Victor
#705
Посмотрел один из предоставленных коммутаторов. Там действительно некорректные данные отдаются в dot1qVlanStaticEgressPorts. Спецификация говорит нам так:

Each octet within this value specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port.  Thus, each port of the bridge is represented by a single bit within the value of this object.  If that bit has a value of '1', then that port is included in the set of ports; the port is not included if its bit has a value of '0'.

Например, у нас порт 7 добавлен в VLAN. Тогда первый байт должен быть в двоичном виде равен 00000010, или 0x02. 4210 на котором я тестировал отдает 00000100 - похоже что каждый полубайт перевернут - но это надо еще проверять, сделать больше VLAN'ов в разной конфигурации.

Главная проблема - как отличить неправильные данные от правильных. У меня в офисе есть 4510, и он уже отдает все корректно. Каких-то различий в MIBах кроме модели и версии софта я не нашел. Один вариант - сделать специальный custom attribute, который будет включать переворачивание битов в маске VLAN'ов. На проблемных коммутаторах можно будет его вручную добавить.