Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Kiwi CatTools > Kiwi CatTools 3.11 Administrator Guide > Activities > Activities list > Device.InterDevice.Ping > When to use the Device.InterDevice.Ping

When to use the Device.InterDevice.Ping

Table of contents
No headers
Created by Caroline Juszczak, last modified by Caroline Juszczak on Jun 28, 2016

Views: 2 Votes: 0 Revisions: 1

 

The Device.InterDevice.Ping activity is a useful network management tool because it allows you to perform and report on multi-directional testing across your whole network.

 

In many router networks, pinging the routers is not a sufficient test to provide a high level of confidence in the proper working of the network, because the router is closer to you than the devices that actually need to use the network.

 

It is reasonably common, for example, for pings to remote routers to use the WAN interface IP Address. So as long as the WAN and Router are functional the ping request will succeed, but this does not tell you that the LAN on the far side of the Router is operating as you intend. It also only tests your ability to Ping the Router from a particular point in your network: it does not test from other points, nor does it test the ability of Devices on the far side to successfully use your network.

 

If you have a Linux Device on each remote LAN segment (or at least "behind" each remote router) you can access each of those Devices from CatTools in turn, and use it to Ping all other significant parts of your network. This provides better evidence that the network is operating properly than simply pinging the routers WAN interface from a single central point.

 

Also, by default the Activity appends reporting information to the same file:

...\Reports\Device.InterDevice.Ping.txt

 

This file could be very useful for providing forensic data in the event of a service provider outage or other event that affects your network.

If you Schedule this Activity on a regular basis, say every 5 minutes (unless you have a quite large number of Devices in your network this would not be a significant loading), then you should be able to use the time-stamped record of ping failures to connect the two events. Although that might not prove the source of the failure, it should provide helpful evidence.

 

Checking availability of a central device

 

This test will allow you to test branch office connectivity back to the central office server. Simply select all the branch office routers (or a Linux machine sitting in the branch office) and have them ping the server back in central office. This will ensure that all of your customers can access the central server.

 

Last modified
07:19, 28 Jun 2016

Tags

Classifications

Public