NetXMS Support Forum

Hi!

Looks like broken build. I'll make sure that versions for 1.2.8 will match, so you'll be able to use it after upgrade.

Best regards,
Victor

Looks like server connects to loopback for some reason and so reads data from it's own agent. Can you please try to remove "wrong" duplicate nodes (with agent marked as presented) and see if they will reappear? Is it possible to determine if duplicates was created by 1.2.7 or previous server version?

Best regards,
Victor

Hi!

Looks like problem is with SNMP communications. Can you try to get something from the switch using nxsnmpwalk command line tool? Please send me the output of nxsnmpwalk of .1.3.6.1.2.1.1 MIB. Also, what SNMP version you are using? What authentication/encryption if SNMP v3?

Best regards,
Victor

Hi!

What is the configuration poll output for 2510? As you cannot get interface list, I suspect that it does not respond to SNMP requests from NetXMS server, and so topology cannot be built correctly.

Best regards,
Victor

Hi!

It makes perfect sense. I was thinking for some time about representing different entities as separate object classes. Main reason why this not implemented yet is lack of resources (time and/or staff).

System itself can be expanded this way quite easy, and creating new object classes is not a big issue. Also, we already have implemented APIs which allow creation of server modules and corresponding UI plugins to provide additional object classes, so it is even possible to have custom objects. Creating such extension, however, requires good understanding of server and GUI internals.

Another possible option is to allow user to configure custom objects. It can be some simple extension to container (or just allow containers to have DCIs) which allows data collection. Actual data for DCIs defined on such objects can be read from nodes using "proxy node" option in DCIs or transformation scripts.

Some workarounds also exists - for example, you can create additional "fake" nodes without IP address to represent components, and use same proxy node and/or transformation script technique to get data.

Best regards,
Victor

Hi!

This issue should be fixed in 1.2.8 release.

Best regards,
Victor

Hi!

Can you gather more information about these nodes? Also, could it be situation when node with agent has DHCP-assigned address which is reassigned to node without agent?

Best regards,
Victor

Hi!

SNMP tables not supported in 1.2.7. Coming 1.2.8 release will have support for this.

Best regards,
Victor

Надо ключ для терминирования аларма поменять на mypbx_trunk_down_%i_%3

Your problem is very strange indeed. When you install NetXMS, what installer you was using - full or minimal? If full, did you select to install DB client library?

Best regards,
Victor

Hi!

"Entire Network" tree always populates automatically - it's a representation of actual IP topology. If auto discovery is turned off, server will only add to it nodes you add to the system manually. For logical organization of nodes you should use "Infrastructure Services" tree. If you don't want that you users see "Entire Networks" tree, you can control it with access rights.

Best regards,
Victor

Hi!

we have some basic functionality already in place, and plan to extend it in the future. You have to configure business services and checks, then system will start collecting uptime data for them. There are short documentation on that topic: http://wiki.netxms.org/wiki/UM:Business_Services.

Best regards,
Victor

Не совсем так. Надо проверять на alarm_state = 3, term_by может быть равен 0 если аларм был закрыт пользователем admin или системой. last_change_time будет в этом случае содержать время закрытия, да.

Есть. Надо создать объект карты с типом "Custom" в поддереве Network Maps, после этого карту можно открыть и добавлять обьекты. Между обьектами можно делать соединения - для этого надо выбрать два обьекта (с CTRL+клик) и нажать Ctrl+L, или кнопку Link на тулбаре. У каждого соединения есть свойства, доступны по правому клику на соединении.

Вот такой SQL даст пользователей, которые делали acknowledge, resolve, и terminate:


select
    op.name,
    message,
    creation_time as begin,
    last_change_time as last_change,
    u1.name as user_ack_by,   
    u2.name as user_resolved_by,   
    u3.name as user_term_by   
from alarms
inner join object_properties op
    on source_object_id = object_id
left outer join users u1
    on u1.id=ALARMS.ack_by
left outer join users u2
    on u1.id=ALARMS.resolved_by
left outer join users u3
    on u1.id=ALARMS.term_by
order by creation_time desc


Отдельных timestamp'ов на это нет, при каждом изменении обновляется last_change_time.