NetXMS Support Forum

Update worked fine on Linux 64bit (compiled from sources). Thanks a lot!

thanks. I hope the Cisco SMB driver also made it in this release

thanks Victor, Do you already have a release date for 1.2.13?

Hi Victor

Have you reproduced this behaviour?

Thanks
Dani

thanks Victor. So you name the events after the source of the event.
Has anybody a good system for naming the DCI descriptions?
At the moment I handle it as good as possible hirachical from left to right like this:
- Windows DNS Queries Total/sec
- Windows DNS Queries PTR/sec
- Synology Disk Volume5 Size Used
- Cisco WAN Interface In
- Windows Service State: Task Scheduler

Is there an 'official' naming convention in NetXMS or maybe a good suggestion for naming objects like:
- DCI
- Event (I see 'DC_', 'SNMP_', 'SYS_', what is the definition behind this 3?)
- EventProcessingPolicies
- Actions

A good system/convention in DCIs and Events would be the most important part.
How do others handle this?

now the penny has dropped ;-) thanks!

Thanks. I saw that in the documentation. But you gave me this:
Icmp.Ping(" . $1 . ")

I don't understand " . $1 . ".
'$1' is the result of the SNMPget, thats clear, but why these points?
I had expected something like Icmp.Ping("$1")

sorry last post was too early :-)
I changed the Data Type of the DCI to integer and now it's ok. I thought the Data Type must be the type of the SNMP value. But it looks like Data Type is the type of the DCI-result after the transformation script.
So only the question about the icmp.ping syntax is open.

another 'problem' is: now the result of the DCI is the latency of the ping (=ok) but it's a string, not an integer. Maybe because the SNMP Data Type is string (it's an IP address) but the result of the transformation script should be an integer.

Hi Victor

Many thanks for the very fast solution. It works

The following line is the solution:
return AgentReadParameter(server, "Icmp.Ping(" . $1 . ")"); [I didn't know that]

But can you explain me the syntax you used 'icmp.ping(" . $1 . ")?
From SubAgent documentation I have this syntax 'Icmp.Ping(target,*timeout*,*psize*)'

thanks a lot!

Dani

Hi Victor

But in your suggestion, I have first get 'ip' (as you called it in your post) from a SNMPGetValue on node GATEWAY1. Can I use a script in the 'parameter' field of the DCI for this?

thanks
Dani

yes but its not the WAN IP address (which I could get from resolved DDNS name), it's the default gateway address of the WAN subnet. I can get the default gateway IP address from the local routing table by SNMP, thats not the problem. But than I have to 'ping' this IP from the NetXMS server.

I have the following situation:
some firewalls (call it GATEWAY1) with dynamic WAN-IP addresses. There I have to ping the default gateway of the WAN interface from the NetXMS server and the result should be shown on the node GATEWAY1.

I see two possibilities but can't find a working solution:
1.
On GATEWAY1 a DCI: Origin = Internal, Parameter = Dummy, Proxy-node = NetXMS-server. Than in transformation script SNMPGetValue (is functional) and a call of a subagnet icmp.ping. But I could't find a possibility to call a subagent from the script.
2.
put the SNMPGetValue in a script in the script library
On GATEWAY1 a DCI: Origin = NetXMS Agent, Parameter = something like 'icmp.ping(script:getip)', no proxy node

Does anybody have a hint or better a solution? I hope I described the situation accurate

found, thanks!