NetXMS Support Forum

Hi,

very interesting observation. Looks like something got broken when large number of sockets can be open in parallel. I'll look in this direction.

Best regards,
Victor

Да, так и не сделал. Зарегистрировал баг, чтобы не забыть: https://www.radensolutions.com/chiliproject/issues/286.

На самом деле все не совсем так страшно. Если консоль при подключении не выдает сообщения о несовместимой версии протокола, то более новой консолью можно управлять более старым сервером. Какой-то функционал может не работать естественно, как правило в этом случае будет ошибка "command not implemented".

You mention that some pollers seems to be stuck. Please send me list of these pollers and information about nodes they trying to process.

Best regards,
Victor

Hi!

Due to changes in 1.2.7, you can occasionally get "syncer thread not responding" message. That's ok, and you can safely ignore it, unless it's stuck in not responding state forever. Can you double check that syncer thread really never come back from not responding state?

Best regards,
Victor

Quote from: Athesis on May 27, 2013, 05:09:31 PM
Hi,

I would also support an Display like that, it would be enoumous advantage for traffic monitoring and clarity what where is. At least to say witch port is connected to what device etc.

Just one comments regarding which port is connected to what device - it's already possible. You can either do this manually (just link objects on the map and put appropriate labels on link), or automatically (create new map of type "layer 2 topology", put some network device as a seed, and NetXMS will build and update it automatically with known layer 2 connectivity information).

There are also minor move toward active network maps: you already can show values of selected DCIs in object's tooltips. Just check "show in object tooltips" checkbox in DCI properties, and value of this DCI will be displayed when you hover mouse over node object on map.

I'll try to add options for displaying DCI data over map links in 1.2.8 or 1.2.9, depending on how well it will go.

Best regards,
Victor

So, version 1.0.7 was working? That means some bug in NetXMS SNMP library. Is it possible to send me captured packets sent between NetXMS and ethernetbox? Also, is it possible that ethernetbox responds from IP address different then IP address used for request?

Best regards,
Victor

Hi!

No, it's not possible. Actually, idea is good and very easy to implement. I'll do this for 1.2.8 release.

Best regards,
Victor

Hi!

Yes, it's possible. You can define "proxy node" for any DCI. If proxy node is defined, real data collection will happen on proxy node, not n the node where DCI is configured. You have to add node where you create proxied DCI to proxy node's "trusted nodes" list, or turn off trusted nodes checking by setting server configuration variable CheckTrustedNodes to 0. A bit more detailed explanation of trusted nodes concept is here: http://wiki.netxms.org/wiki/SG:Security_Issues.

Best regards,
Victor

Hi!

isSNMP attribute set automatically when server is able to communicate with the node over SNMP. Check that device responds to SNMP. You can use nxsnmpget/nxsnmpwalk command line tools for diagnostic. Check that correct SNMP community is set in node's communication properties.

Best regards,
Victor

Hi!

Export file is in fact SQLite database, and file dbschema_sqlite.sql used to create empty export file. Looks like installer contains wrong version of this file. Find schema files and replace them with attached, then export should work.

Best regards,
Victor

Hi!

It should be placed there automatically. Can you please do forced configuration poll from console? Also, please check if interface object has IP address.

P.S. Можно и по русски, отвечают везде

Do you have web console deployed? Will be great to check if web console has same issue. I cannot reproduce this issue, but I run console on Windows 7. I'll try to check it on XP later today.

Also, on what OS server is installed?

Best regards,
Victor

Hi!

It should not be related to encryption. I've found an error in Makefile for nxencpasswd - there are no reference to libtre library. Can you check on machine where upgrade was successful value of "Use internal libtre" in upgrade log?

Best regards,
Victor

So this seems to be a management console problem. Can you try to connect with different console? Also, sometimes it could be a problem if you unpack new version of management console over previous version. If this is he case, try to unpack console into empty directory.

Best regards,
Victor