NetXMS Support Forum

Hi!

I found explanation for this problem: http://postgresql.1045698.n5.nabble.com/BUG-2305-quot-No-bufferspace-available-quot-error-on-large-insert-td2120136.html. Looks like the only way to fix it is to add check for this error in POstgreSQL driver on NetXMS side and do sleep and retry to allow DB server to process data it already have. I'll make a patch and post updated driver here.

Best regards,
Victor

Hi!

I see that snmptester uses SNMP version 1. Is it possible that device does not support SNMP version 2c? Can you try to run nxsnmpget  with -v1 option?

Best regards,
Victor

Don't have time to look into it in details yet. Hopefully will be able to work on it this week. I have similar report in Russian forum, so you are not alone with this problem

Best regards,
Victor

Hi!

It's a bug.

Best regards,
Victor

Hi!

Looks like broken database. Can you try to stop the server and run database check (with command nxdbmgr check)?

Best regards,
Victor

Hi!

NetXMS server has "network device drivers" which handles all vendor/device specifics. As there are no standard MIBs for reading physical port information, "Ports" tab is blank for devices without drivers. It also can affect VLAN info display. If you can point me to appropriate MIBs for AlliedTelesis switches, I can create a driver and include it into next release.

Best regards,
Victor

Hi!

Do you see SNMP in node capabilities? I see that your node using non-standard port - did you set it correctly in communication properties for the node? If you do configuration poll manually, what messages you get about SNMP support?

Best regards,
Victor

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