NetXMS Support Forum

Hi

It's already renewed and uploaded a while ago.

I highly recommend to use netxms-release package, which update keys automatically.

Key locations:
https://packages.netxms.org/netxms-keyring.gpg -- binary keyring
https://packages.netxms.org/netxms.gpg -- armoured key

Also it's available from key servers.

Make sure that key is not imported into trusted keys (e.g. using apt-key), but is stored in separate key store, as recommended in recent Debian/Ubuntu.

Hi,

Time to renew this?

After upgrade i noticed that infrastructer object browser doesent auto refresh anymore, for example container binding or renaming. user has to press manual refresh.

Thank you Filipp. 

Ahh makes sense thanks for the reply

This feature might not have been transferred from the old client to the new one. Will be fixed.

Hi everyone,

Please, anyone knows if is it possible to configure color on the alarm list using the Management Client Version 4.5.6? That feature was available in previous version, but after upgrade to 4.5.6 I can´t found that option to set up.

PS: This problem is not present when accessing by webbrowser.

Thanks in advance.

You can check raw values in history of a DCI and do the calculation manually, but I am afraid that's just the data that this switch provides.

More experienced people might correct me, but as long as I remember, reading status of link duplex was pretty non-standard thing that differed accross device make and models. For your specific devices you can create SNMP DCIs. If you need to check across peer devices, it's possible in nxsl as interface class has peerInterface attribute.

It would be nice to be able to have checks that would show or alert on duplex mismatches on links between devices. Like wise it would also be beneficial to have indicators on the map the shows differences between interfaces that are 10-100M or 1-10GB etc  or a difference in line width if the links are 100m vs 10GB