NetXMS Support Forum

Followup: just fixed it. Agent version 1.2.7 will pass 8 and 16 to log parser as level values for audit success and audit failure events.

Best regards,
Victor

Hi!

In Windows Vista/2008 event log API was changed significantly, and all security events now have priority Informational. This is why your filter doesn't work. I just found an article that describe these changes: http://www.eventlogblog.com/mt/mt-search.cgi?tag=Vista%20Event%20Log%20Changes&blog_id=1. As a workaround, you can remove "level" filter. For future releases I'll implement simulation of old behavior.

Best regards,
Victor

Do you have SNMP settings set correctly on the node? Does node has "isSNMP" set to yes in capabilities?

Best regards,
Victor

I agree that current model is too simple. I see two possible options to represent network interfaces in more details.

1. Separate physical and logical interfaces completely. Then object tree could look like this:

Node
  +-- Physical interface 1 (MAC address)
  +-- Physical interface 2 (MAC address)
  +-- IP interface 1 (IP address) (reference to physical interface)
  +-- IPv6 interface 1 (IPv6 address) (reference to physical interface)

and so on.

2. Try to build a logical-to-physical hierarchy, like this:

Node
  +-- IP interface 1 (IP address)
     +-- Physical Interface 1 (MAC address)
  +-- IP interface 2 (IP address)
     +-- Physical Interface 1 (MAC address)
  +-- IPv6 interface 1 (IPv6 address)
     +-- Physical Interface 1 (MAC address)
  +-- IP interface 3 (IP address)
     +-- Team 1
        +-- Physical Interface 2 (MAC address)
        +-- Physical Interface 3 (MAC address)

What do you think?

Best regards,
Victor

name в исходниках это собственно и есть OID. Поэтому именно в месте указанном стрелочкой {instance} можно ставить. Вечером напишу в wiki маленький tutorial по использованию instance discovery.

Консоль при старте выделяет тот обьект в дереве, который был выделен в момент закрытия. Проблема только с правильным выбором поддерева. Постараюсь исправить к 1.2.7, если не получится, то сделаю возможность отключения этой функции.

Hi!

Crash dump could be very helpful.

Best regards,
Victor

Hi!

Yes, we can provide you with technical support. Please contact me directly for discussing details.

Best regards,
Victor

Я добавлю дополнительный дебаг и выложу новые исходники. Пока-что посмортите правильно ли VLAN'ы собрались с этого коммутатора.

Hi!

NetXMS uses the following ports:

server: 4701 (client connections), 4702 (inter-server communications), 4747 (mobile agent connections)
agent: 4700 (server connections)

Best regards,
Victor

Hi!

All %number macros refers to event-specific event's parameters. They can have different meaning for different events. For example, for threshold violation events %6 refers to "instance" attribute, and for event created from SNMP trap it will be varbind mapping #6. For well-known events you can see exact parameter meaning in event description.

Best regards,
Victor

Hi!

You don't need any programming experience to configure NetXMS. It is advised however to have at least basic knowledge about SNMP and networking. You can configure NetXMS to collect data from your network devices via SNMP. Chater on data collection in manual may help you: http://wiki.netxms.org/wiki/UM:Data_Collection.

As for your specific question about line chart not showing data, please provide screenshots of your DCI configuration.

Best regards,
Victor

Hi!

What do you mean by "changing some menu"? Changing console source code or defining new object tools?

Best regards,
Victor

That's very strange. If you currently have such node, can you run configuration poll manually and send me it's output? Also, can you please try to get something from such node using nxget? Like

nxget <primary_ip> Agent.Version

Best regards,
Victor

FDB таблица из Object Tools - это конкретный SNMP OID. Здесь ничего не изменилось. Но есть FDB, которую знает сам сервер (она используется для построения топологии 2-го уровня) - там должна быть полная информация. Попробуйте функцию "Find switch port" для хостов в разных VLAN-ах - она должна работать корректно.
Й в следующем релизе заменю FDB из Object Tools на показ той таблицы, которую знает сервер.