<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Pinging with large packet and monitoring router internal/external address]]></title><description><![CDATA[<p dir="auto">Hello</p>
<p dir="auto">Question when i am monitoring router with local network address, is it possible to monitor external address also within same node or do i need to create seperate node ? Also how can i check if large packet ping is working ?</p>
<p dir="auto">Egert</p>
]]></description><link>https://forum.netxms.org/topic/7134/pinging-with-large-packet-and-monitoring-router-internal-external-address</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 20:31:33 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7134.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 17 Aug 2021 10:15:43 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Pinging with large packet and monitoring router internal/external address on Fri, 20 Aug 2021 08:59:52 GMT]]></title><description><![CDATA[<p dir="auto">There are several approaches here</p>
<ul>
<li>
<p dir="auto">you can create two DCIs - one for pinging with short packets, another for big packets. In a third, script, DCI you can read last collected values of these pinging DCIs<br />
GetDCIValue($node, FindDCIByName($node, "DCI_NAME"))<br />
and make decision. This script DCI can return e.g. 1 or 0 and have a trigger that creates event.</p>
</li>
<li>
<p dir="auto">You can have a script DCI that poll several agent parameters at once.<br />
$node-&gt;readAgentParameter("Icmp.Ping(8.8.8.8, 1000, 1500)")<br />
It's not recommended for such script DCI to run for very long (longer then 3-5 seconds) as having many such script DCIs may occupy data collection pollers for too long and cause problems with data collection.</p>
</li>
</ul>
<p dir="auto">For timeout Icmp.Ping returns value of 10000.</p>
]]></description><link>https://forum.netxms.org/post/30364</link><guid isPermaLink="true">https://forum.netxms.org/post/30364</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Fri, 20 Aug 2021 08:59:52 GMT</pubDate></item><item><title><![CDATA[Reply to Pinging with large packet and monitoring router internal/external address on Wed, 18 Aug 2021 05:59:14 GMT]]></title><description><![CDATA[<p dir="auto">Got that part working, any good suggestions how to implement something like that:</p>
<p dir="auto">example:<br />
packet size 1500+ pings = good<br />
less then 1500 pings but bigger packet not = bad<br />
no response = external network down</p>
<p dir="auto">sometimes network provider network wount pass packet size over for example 1000 and that kills vpn tunnel.</p>
]]></description><link>https://forum.netxms.org/post/30360</link><guid isPermaLink="true">https://forum.netxms.org/post/30360</guid><dc:creator><![CDATA[Egert143]]></dc:creator><pubDate>Wed, 18 Aug 2021 05:59:14 GMT</pubDate></item><item><title><![CDATA[Reply to Pinging with large packet and monitoring router internal/external address on Tue, 17 Aug 2021 22:21:33 GMT]]></title><description><![CDATA[<p dir="auto">One way is to create a DCI on that node with Icmp.Ping(target, timeout, psize) metric. "psize" parameter defines packet size.<br />
In "Source node" in DCI's properties you can select a node from which the ping will be actually sent.</p>
<p dir="auto">Second way - you can manually add an interface with the external IP and then use ICMP statistic collection on that interface. But in this case it's not possible to set packet size.<br />
<a href="https://www.netxms.org/documentation/adminguide/icmp-ping.html#" rel="nofollow ugc">https://www.netxms.org/documentation/adminguide/icmp-ping.html#</a></p>
]]></description><link>https://forum.netxms.org/post/30359</link><guid isPermaLink="true">https://forum.netxms.org/post/30359</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Tue, 17 Aug 2021 22:21:33 GMT</pubDate></item></channel></rss>