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

#1
Thanks for the input - I will check on it asap and feedback here.
#2
General Support / Re: Bug or misuse?
June 26, 2025, 03:18:59 PM
Hi Filipp, 

the example with the brackets is here: 

https://www.netxms.org/documentation/adminguide/web-services-monitoring.html#examples 

You are right, I can see the DCI as "unsupported" when I go to edit mode. 

My use case: 

I am polling the Cisco Meraki API for some license informations. For the Licensed Devices, I receive a JSON.
I want to break down the json into a DCI table and therefore I created a Table DCI 
As soon as I change the Instance discovery method to Web Service, its unsupported. (and not viewable in the view mode as I learned). In the edit mode, I can see it.

KR Georg
#3
General Support / Re: Bug or misuse?
June 22, 2025, 06:10:53 PM
Update: this happens everytime I add a web service instance discovery, regardless of the request string
#4
Hi Filipp,

It happens as soon as the agent is available again, I do not trigger a config or full config .

KR
#5
General Support / Bug or misuse?
June 22, 2025, 06:02:31 PM
Hi community,

first of all, proms to the developers - I am implementing NetXMS now for around a month and the last Network Management system I loved that much was CA Spectrum. Thanks for the good work!

Now, I think I discovered a bug.

I am implementing a DCI with a Web Service and I am using the example here (from the bottom):
https://www.netxms.org/documentation/adminguide/web-services-monitoring.html

I try to enumerate with the Web Service method, but as soon as I enter the WebService Request 

WebService(certs/host1):[.[].friendlyName] 

and then click apply and close, the DCI is disappeared.
It really disappears, I tried to alter the view option (disabled, ...), but it is gon
when I create another DCI, also the ID counts up

KR Georg
#6
Hi all,

I noticed today that the CISCO-WLC driver does not recognize the modern Catalyst 9800 WLCs.
I tried setting CISCO-WLC as custom attribute "snmp.driver", but the driver used on the node stays CISCO-GENERIC, even after Polling a Full Configuration.

I assume that the driver does not recognize modern Controllers, but only the AireOS models.
Is there a chance to get the driver working with 9800s? I am aware that there have been essential changes in the way the controllers work as well as in the MIBs. If I can assist you in any way, I would love to do so.

KR Georg
#7
Hi all,

I noticed that the expected interface state is lost when a nodes snmp agent does not respond, because the interfaces get deleted and when the agent comes back on, they are newly created.

Is there a way to change this behaviour in the config?

Thank You,
KR