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 - cserzs

#31
General Support / Re: Request time out issue
July 22, 2017, 03:03:48 PM
HI,

Thank you for your support. I have checked the web managemenet console and unfortunately the result is the same (timeout issue) in this case as well. My experience is that this issue is obviusly related with the table type DCI elements because when I request any simple DCI time series (e.g. Polling interval: 180s
Retention time: 365days) for a 1years period (175200 samples) the chart processing time is less than 10-20 seconds. The timeout issue is occure only in case of table type DCI.

Do you have any ideas?

BR,
Zsolt
#32
Hi Victor,

Sorry for my less detailed question. I have integrated in my NetXMS configuration few hundred SNMP device and I would like to configure a new workstation with a Nxnc client what only displays a part of all devices. Meanwhile I found that this is probably possible to resolve with a dedicates user definition and with a corresponding access controll configuration. Is it correct or is it exist any other solultion for it?

Thanks in advance,
Zsolt
#33
General Support / Request time out issue
July 10, 2017, 03:26:50 PM
Hi,

I configured some table type DCI in our NetXMS system (v2.0.7).
The table settings are the following:

Polling interval: 180s
Retention time: 365days
Number of columns: 11

When I try to request a more than 4h length line chart from any element of this table I get always the "Request timeout" error message.


Do you have any solution for this issue?

Thank you in advance.
BR, Zsolt
#34
Hi,

Is it possible to configure a NetXMS client workstation with arbitrarily selected container and node content?

If, Yes. How is possible to configure it?

Thank you in advance.
Best regards,
Zsolt
#35
General Support / Re: v2.1-M1 upgrade problem
December 17, 2016, 06:12:13 PM
Hi,

I have installed the v2.0.7 sw successfully.
In this also is included the bugfix what is important for me.

Thank you very much.
BR,
Zsolt
#36
General Support / Re: v2.1-M1 upgrade problem
November 22, 2016, 12:13:53 AM
Hi,

Thank you in advance for your support. I have tried again the upgrade process from v2.0.6 to v2.0-M1. The exact problem is the following:
The upgrading process completed without any error messages. Despite this I couldn't start the v2.1-M1 NetXMS core service (it's always stopped).  After this, I ran again the "nxdbmgr upgrade" command with -t option. The screenshots about it please find in the attachment. My database version is MS SQL 2012(SP1) 11.0.300.0(x64) server.

BR,
Zsolt
#37
General Support / v2.1-M1 upgrade problem
November 17, 2016, 12:21:38 AM
Hi,

I have tried to upgrade my v1.06 NetXMS system to v2.1-M1 but I got a critical error about the version problem of database.
Then I tried  to use the "nxdbmgr upgrade" command without any success. The result of this command please find in the attachment.
Is there any solution to this issue?
#38
Hi Victor,

Thank you very much for your support.
I am waiting for the new release.

BR, Zsolt
#39
Is there any solution?
#40
Hi,

Thank you very much for your reply. I already tested your suggested configuration but my experience is that the number of samples parameter in case of diff function doesn't affect anything. So, in each cases the alarm event come up after the second identical result independetly from the value of sample number parameter. My NetXMS version is v2.03.

BR
#41
Hi,

Sorry but I don't understand exactly your suggestion.
In my previous example the SNMP GET 1., SNMP GET 2. etc. values are the results of a normal DCI scheduled polling. I would like to detect the presence of a specific number of same values between the successive DCI results.

BR.
#42
Hi,

I would like to generate an alarm event when the string type results of an SNMP get polling process is become to a uniform series.

e.g.

alarm generation after 5 same results:
SNMP GET 1. ,,sdffg" (alarm off)
SNMP GET 2. ,,dfgghf" (alarm off)
SNMP GET 3. ,,abab" (alarm off)
SNMP GET 3. ,,abab" (alarm off)
SNMP GET 4. ,,hujjklll" (alarm off)
SNMP GET 5. ,,wq" (alarm off)
SNMP GET 6. ,,wq" (alarm off)
SNMP GET 7. ,,wq" (alarm off)
SNMP GET 8. ,,wq" (alarm off)
SNMP GET 9. ,,wq" (alarm on)
SNMP GET 10. ,,wq" (alarm on)
SNMP GET 11. ,,wq" (alarm on)
SNMP GET 12. ,,wqq" (alarm off)
SNMP GET 13. ,,wqq" (alarm off)
...

How is possible to set a such alarm behaviour?

Thank you in advance and best regards.
#43
General Support / Re: 32 bit INT OID issue
April 08, 2016, 11:05:50 PM
Hello Victor,

Thank you very much for your support.
I will wait for the official fixed version.

BR, Zsolt
#44
General Support / Re: 32 bit INT OID issue
April 04, 2016, 05:36:19 PM
Hi,

Thank you for your feedback.
I have upgraded my NetXMS system to v2.0.3 but despite this the 32 bit INT OID issue still inadequate (remain the negative sign).
#45
General Support / 32 bit INT OID issue
March 31, 2016, 11:27:49 AM
Hi,

I have installed the v2.0-RC2 NetXMS system and I tried to integrate an SNMP device what uses 32 bit INT OIDs. I carried out the compilation process of corresponding MIB  files successfully but in DCI configuration/ Select MIB Object window when I tried to run an SNMP Walk process I found that the 32 bit INT OID components are not displayed properly (with negative sign). Please see the attached screenshot of this MIB Walk Results Window.