Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#2986
Hi,

do you mean tooltips on network map?

Best regards,
Victor
#2987
Just few clarifications:

1. load will not exceed size, bt it can exceed max size, as thread pool will not grow beyound max size.

2. Note that parameter name for load monitoring is "LoadAverage", not "Load", as it represents moving average of request queue for period (same as UNIX/Linux load average), while "Load" represents current thread pool load as % of threads processing request to current size of thread pool.

Also, I've updated internal DCI selector in UI - now it shows correct set of parameters.

Best regards,
Victor
#2988
I'll implemented it in 2.0-RC1 - change should be quite easy.

Best regards,
Victor
#2989
Hi,

seems to be a bug in NetXMS. Could you please show how interfaces on your nodes looks like (Interfaces tab in node details)?

Best regards,
Victor
#2990
Hi,

that's likely a problem. Currently NetXMS can only build topology if both peers provide LLDP information via SNMP. In this particular case ap1 reports that it identify itself using MAC address (.1.0.8802.1.1.2.1.4.1.1.4.0.57.2 = 4), but because it does not provide own LLDP ID via SNMP NetXMS cannot find node with this LLDP ID. I can add a fallback search using remote system name (.1.0.8802.1.1.2.1.4.1.1.9) - it may cause inconsistent results though if for example few nodes have identical system names.

Best regards,
Victor
#2991
Hi,

seems to be a bug in dashboard implementation. We will check.

Best regards,
Victor
#2992
Hi,

actually, LLDP is quite flexible in what is used to identify node - every peer sends it's identification along with ID type. It can be MAC address, host name, interface name, etc.). Can you please share results of SNMP walk on OID .1.0.8802.1.1.2.1.4.1.1 on switch1 as well as .1.0.8802.1.1.2.1.3 for ap1?

Best regards,
Victor
#2993
General Support / Re: v2.0-M5 & PostgreSQL
July 21, 2015, 04:23:28 PM
Hi,

it seems that at some point you forgot to specify prefix to configure and it installs binaries and libraries into default location (/usr/local). You can safely delete all netxms libraries from /usr/local/lib - then 2.0-M5 should work without problems.

Best regards,
Victor
#2994
Hi,

did you install it from sources or from binary package?

Best regards,
Victor
#2995
Hi,

I recommend to try 2.0-M5 - some memory leaks was fixed in that release.

Best regards,
Victor
#2996
Hi,

it seems that you still have older server version then your nxdbmgr. Try to download source package again and compile everything again.

Best regards,
Victor
#2997
I mean a bit different thing. Try to do the following:

1. Create script in script library that will calculate status as you need it.
2. Create script source DCI, select your script as source, check "use for status calculation" option.
3. Don't forget to remove "use for status calculation" option from internal status DCI.

Best regards,
Victor

P.S. also, you should use address 0.0.0.0 to create node without IP address.
#2998
Hi,

both are implemented and will be included in 2.0-RC1 release.

Best regards,
Victor
#2999
Hi,

condition object is limited to have only two possible statuses. However, you can create node object without IP address, then create script DCI on it that will return status as a number from 0 (normal) to 4 (critical) and mark this DCI as "status DCI". You'll have node with status based only on value provided by your script.

Best regards,
Victor
#3000
General Support / Re: v2.0-M5 & PostgreSQL
July 14, 2015, 09:10:01 PM
Hi,

if you delete /opt/netxms completely then it should not be an issue. Still it looks like older library somewhere. Can you please check if there are libnetxms.so.1 left somewhere?

Best regards,
Victor