69
5.2. Ping and Scan Methods
ePowerSwitch 8M+
R2
has two methods to check whether an IP equipment (PC, server, router, Webcam...)
is still alive:
Address Pinging:
The first method uses the well-known Ping command whereby a request is sent to a specific IP address.
The Ping command, which is an echo request, enables you to determine through an ICMP protocol
(Internet Control Message Protocol) if an IP device is available on the network. If the system reacts to this
request, ePowerSwitch 8M+
R2
knows that the TCP/IP connection is established. If the system does not
react to one or several requests, ePowerSwitch 8M+
R2
can automatically switch the device off and after a
specified delay switch it again on (Reboot function).
Port Scanning:
The second method uses the Port Scan command to test a specific TCP/IP port. In other words, this
command allows you to find out if a specific protocol is available on a server (for example HTTP, FTP,
Telnet, POP...). ePowerSwitch 8M+
R2
simply tries to connect to a specific server port. If the connection is
possible, ePowerSwitch 8M+
R2
knows that a server program is running there. If the connection is not
possible, ePowerSwitch 8M+
R2
can automatically switch the device off and after a specified delay switch it
again on (Reboot function).
- The Supervision function works only if the ePowerSwitch 8M+
R2
is connected to the LAN.
- The Ping and Scan functions can be used separately or together.
- The network route between ePowerSwitch 8M+
R2
and the IP device you wish to supervise should
be as direct as possible, so do not use unnecessary routers and complex wiring between them.
A problem on a router or the wiring could reboot the IP device to supervise.
- Execute several Pings and/or Scans before running the Reboot function. It could be possible
that the IP device doesn't respond although it is still working.
- Choose a realistic supervision cycle. One second is possible, however it's not necessary to
overload the network with Ping and Scan requests.
Recommended values:
- Interval between Requests: 10 sec or more
- Number of unsuccessful Requests before Reboot: 3 or more
- Delay before Reboot: 10 sec or more
- Delay before restarting monitoring after Reboot: 120 sec or more
To Next Page
Loading...
General