Pinging with large packet and monitoring router internal/external address

[Egert143]

Hello

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 ?

Egert

[Filipp Sudanov]

One way is to create a DCI on that node with Icmp.Ping(target, timeout, psize) metric. "psize" parameter defines packet size.
In "Source node" in DCI's properties you can select a node from which the ping will be actually sent.

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.
https://www.netxms.org/documentation/adminguide/icmp-ping.html#

[Egert143]

Got that part working, any good suggestions how to implement something like that:

example:
packet size 1500+ pings = good
less then 1500 pings but bigger packet not = bad
no response = external network down

sometimes network provider network wount pass packet size over for example 1000 and that kills vpn tunnel.

[Filipp Sudanov]

There are several approaches here

• 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
  GetDCIValue($node, FindDCIByName($node, "DCI_NAME"))
  and make decision. This script DCI can return e.g. 1 or 0 and have a trigger that creates event.

• You can have a script DCI that poll several agent parameters at once.
  $node->readAgentParameter("Icmp.Ping(8.8.8.8, 1000, 1500)")
  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.

For timeout Icmp.Ping returns value of 10000.