Netwatch monitors state of hosts on the network. It does so by sending ICMP pings to the list of specified IP addresses. For each entry in netwatch table you can specify IP address, ping interval and console scripts. The main advantage of netwatch is it's ability to issue arbitrary console commands on host state changes.
Netwatch monitors state of hosts on the network. It does so by sending ICMP pings to the list of specified IP addresses. For each entry in netwatch table you can specify IP address, ping interval and console scripts. The main advantage of netwatch is it's ability to issue arbitrary console commands on host state changes.
<td>The time between pings. Lowering this will make state changes more responsive, but can create unnecessary traffic and consume system resources.</td>
|type=IP
</tr>
|default=0.0.0.0
<tr>
|desc=IP address of the host that should be monitored
<td>Console script that is executed once when state of a host changes to <b>up</b></td>
</tr>
{{Mr-arg-table
</table>
|arg=interval
|type=time
|default=1m
|desc=Time interval between pings. Lowering this will make state changes more responsive, but can create unnecessary traffic and consume system resources.
}}
{{Mr-arg-table
|arg=timeout
|type=time
|default=1s
|desc=Timeout in seconds after which host is considered down
}}
{{Mr-arg-table-end
|arg=up-script
|type=string
|default=
|desc=Console script that is executed once when state of a host changes to '''up'''
}}
==Status==
==Status==
<p>
Command <code>/ip dhcp-client print</code> will show current status of netwatch and <b>read-only</b> properties listed in table below:
Command <code>/ip dhcp-client print</code> will show current status of netwatch and <b>read-only</b> properties listed in table below:
<table class="styled_table">
<tr>
<th width="40%">Property</th>
<th >Description</th>
</tr>
<tr>
<td><var><b>since</b></var> (<em>time</em>)</td>
<td>Indicates when state of the host changed last time</td>
</tr>
<tr>
<td><var><b>status</b></var> (<em>up | down | unknown</em>)</td>
<td>Shows the current status of the host</td>
</tr>
</table>
</p>
{{Mr-arg-table-h
|prop=Property
|desc=Description
}}
{{Mr-arg-ro-table
|arg=since
|type=time
|desc=Indicates when state of the host changed last time
}}
{{Mr-arg-ro-table-end
|arg=status
|type=up {{!}} down {{!}} unknown
|desc=Shows the current status of the host
}}
==Basic examples==
==Basic examples==
<p>
This example will run the scripts gw_1 or gw_2 which change the default gateway depending on the status of one of the gateways:
This example will run the scripts gw_1 or gw_2 which change the default gateway depending on the status of one of the gateways:
<pre>
<pre>
Line 79:
Line 98:
[admin@MikroTik] tool netwatch>
[admin@MikroTik] tool netwatch>
</pre>
</pre>
</p>
<p>
Without scripts, netwatch can be used just as an information tool to see which links are up, or which specific hosts are running at the moment.
Without scripts, netwatch can be used just as an information tool to see which links are up, or which specific hosts are running at the moment.
</p>
<p>
Let's look at the example above - it changes default route if gateway becomes unreachable. How it's done? There are two scripts. The script "gw_2" is executed once when status of host changes to up. In our case, it's equivalent to entering this console command:
Let's look at the example above - it changes default route if gateway becomes unreachable. How it's done? There are two scripts. The script "gw_2" is executed once when status of host changes to up. In our case, it's equivalent to entering this console command:
<pre>
<pre>
Line 89:
Line 107:
</pre>
</pre>
The /ip route find dst 0.0.0.0 command returns list of all routes whose dst-address value is 0.0.0.0. Usually, that is the default route. It is substituted as first argument to /ip route set command, which changes gateway of this route to 10.0.0.217
The /ip route find dst 0.0.0.0 command returns list of all routes whose dst-address value is 0.0.0.0. Usually, that is the default route. It is substituted as first argument to /ip route set command, which changes gateway of this route to 10.0.0.217
</p>
<p>
The script "gw_1" is executed once when status of host becomes down. It does the following:
The script "gw_1" is executed once when status of host becomes down. It does the following:
<pre>
<pre>
Line 96:
Line 114:
</pre>
</pre>
It changes the default gateway if 10.0.0.217 address has become unreachable.
It changes the default gateway if 10.0.0.217 address has become unreachable.
</p>
<p>
Here is another example, that sends e-mail notification whenever the 10.0.0.215 host goes down:
Here is another example, that sends e-mail notification whenever the 10.0.0.215 host goes down:
Netwatch monitors state of hosts on the network. It does so by sending ICMP pings to the list of specified IP addresses. For each entry in netwatch table you can specify IP address, ping interval and console scripts. The main advantage of netwatch is it's ability to issue arbitrary console commands on host state changes.
Properties
Sub-menu:/tool netwatch
Property
Description
down-script (string; Default: )
Console script that is executed once when state of a host changes to down
host (IP; Default: 0.0.0.0)
IP address of the host that should be monitored
interval (time; Default: 1m)
Time interval between pings. Lowering this will make state changes more responsive, but can create unnecessary traffic and consume system resources.
timeout (time; Default: 1s)
Timeout in seconds after which host is considered down
up-script (string; Default: )
Console script that is executed once when state of a host changes to up
Status
Command /ip dhcp-client print will show current status of netwatch and read-only properties listed in table below:
Property
Description
since (time)
Indicates when state of the host changed last time
status (up | down | unknown)
Shows the current status of the host
Basic examples
This example will run the scripts gw_1 or gw_2 which change the default gateway depending on the status of one of the gateways:
[admin@MikroTik] system script> add name=gw_1 source={/ip route set
{... [/ip route find dst 0.0.0.0] gateway 10.0.0.1}
[admin@MikroTik] system script> add name=gw_2 source={/ip route set
{.. [/ip route find dst 0.0.0.0] gateway 10.0.0.217}
[admin@MikroTik] system script> /tool netwatch
[admin@MikroTik] tool netwatch> add host=10.0.0.217 interval=10s timeout=998ms \
\... up-script=gw_2 down-script=gw_1
[admin@MikroTik] tool netwatch> print
Flags: X - disabled
# HOST TIMEOUT INTERVAL STATUS
0 10.0.0.217 997ms 10s up
[admin@MikroTik] tool netwatch> print detail
Flags: X - disabled
0 host=10.0.0.217 timeout=997ms interval=10s since=feb/27/2003 14:01:03
status=up up-script=gw_2 down-script=gw_1
[admin@MikroTik] tool netwatch>
Without scripts, netwatch can be used just as an information tool to see which links are up, or which specific hosts are running at the moment.
Let's look at the example above - it changes default route if gateway becomes unreachable. How it's done? There are two scripts. The script "gw_2" is executed once when status of host changes to up. In our case, it's equivalent to entering this console command:
The /ip route find dst 0.0.0.0 command returns list of all routes whose dst-address value is 0.0.0.0. Usually, that is the default route. It is substituted as first argument to /ip route set command, which changes gateway of this route to 10.0.0.217
The script "gw_1" is executed once when status of host becomes down. It does the following:
