<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Smokeping/probes/TelnetIOSPing</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>
<body style="background-color: white">
<p><a name="__index__"></a></p>
<!-- INDEX BEGIN -->
<!--
<ul>
<li><a href="#name">NAME</a></li>
<li><a href="#synopsis">SYNOPSIS</a></li>
<li><a href="#description">DESCRIPTION</a></li>
<li><a href="#variables">VARIABLES</a></li>
<li><a href="#authors">AUTHORS</a></li>
<li><a href="#notes">NOTES</a></li>
<ul>
<li><a href="#ios_configuration">IOS configuration</a></li>
<li><a href="#requirements">Requirements</a></li>
<li><a href="#debugging">Debugging</a></li>
<li><a href="#password_authentication">Password authentication</a></li>
<li><a href="#ping_packet_size">Ping packet size</a></li>
</ul>
</ul>
-->
<!-- INDEX END -->
<p>
</p>
<h1><a name="name">NAME</a></h1>
<p>Smokeping::probes::TelnetIOSPing - Cisco IOS Probe for SmokePing</p>
<p>
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
<pre>
*** Probes ***</pre>
<pre>
+TelnetIOSPing</pre>
<pre>
forks = 5
offset = 50%
packetsize = 56
step = 300
timeout = 15</pre>
<pre>
# The following variables can be overridden in each target section
iospass = password # mandatory
iosuser = user # mandatory
pings = 5
psource = 192.168.2.129
source = 192.168.2.1 # mandatory</pre>
<pre>
# [...]</pre>
<pre>
*** Targets ***</pre>
<pre>
probe = TelnetIOSPing # if this should be the default probe</pre>
<pre>
# [...]</pre>
<pre>
+ mytarget
# probe = TelnetIOSPing # if the default probe is something else
host = my.host
iospass = password # mandatory
iosuser = user # mandatory
pings = 5
psource = 192.168.2.129
source = 192.168.2.1 # mandatory</pre>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
<p>Integrates Cisco IOS as a probe into smokeping. Uses the telnet protocol
to run a ping from an IOS device (source) to another device (host).
This probe basically uses the ``extended ping'' of the Cisco IOS. You have
the option to specify which interface the ping is sourced from as well.</p>
<p>
</p>
<hr />
<h1><a name="variables">VARIABLES</a></h1>
<p>Supported probe-specific variables:</p>
<dl>
<dt><strong><a name="item_forks">forks</a></strong>
</dt><dd>
<p>Run this many concurrent processes at maximum</p>
<p>Example value: 5</p>
<p>Default value: 5</p>
</dd><dt><strong><a name="item_offset">offset</a></strong>
</dt><dd>
<p>If you run many probes concurrently you may want to prevent them from
hitting your network all at the same time. Using the probe-specific
offset parameter you can change the point in time when each probe will
be run. Offset is specified in % of total interval, or alternatively as
'random', and the offset from the 'General' section is used if nothing
is specified here. Note that this does NOT influence the rrds itself,
it is just a matter of when data acqusition is initiated.
(This variable is only applicable if the variable 'concurrentprobes' is set
in the 'General' section.)</p>
<p>Example value: 50%</p>
</dd><dt><strong><a name="item_packetsize">packetsize</a></strong>
</dt><dd>
<p>The (optional) packetsize option lets you configure the packetsize for
the pings sent.</p>
<p>Default value: 56</p>
</dd><dt><strong><a name="item_step">step</a></strong>
</dt><dd>
<p>Duration of the base interval that this probe should use, if different
from the one specified in the 'Database' section. Note that the step in
the RRD files is fixed when they are originally generated, and if you
change the step parameter afterwards, you'll have to delete the old RRD
files or somehow convert them. (This variable is only applicable if
the variable 'concurrentprobes' is set in the 'General' section.)</p>
<p>Example value: 300</p>
</dd><dt><strong><a name="item_timeout">timeout</a></strong>
</dt><dd>
<p>How long a single 'ping' takes at maximum</p>
<p>Example value: 15</p>
<p>Default value: 5</p>
</dd></dl>
<p>Supported target-specific variables:</p>
<dl>
<dt><strong><a name="item_iospass">iospass</a></strong>
</dt><dd>
<p>The iospass option allows you to specify the password for the username
specified with the option iosuser.</p>
<p>Example value: password</p>
<p>This setting is mandatory.</p>
</dd><dt><strong><a name="item_iosuser">iosuser</a></strong>
</dt><dd>
<p>The iosuser option allows you to specify a username that has ping
capability on the IOS Device.</p>
<p>Example value: user</p>
<p>This setting is mandatory.</p>
</dd><dt><strong><a name="item_pings">pings</a></strong>
</dt><dd>
<p>How many pings should be sent to each target, if different from the global
value specified in the Database section. Note that the number of pings in
the RRD files is fixed when they are originally generated, and if you
change this parameter afterwards, you'll have to delete the old RRD
files or somehow convert them.</p>
<p>Example value: 5</p>
</dd><dt><strong><a name="item_psource">psource</a></strong>
</dt><dd>
<p>The (optional) psource option specifies an alternate IP address or
Interface from which you wish to source your pings from. Routers
can have many many IP addresses, and interfaces. When you ping from a
router you have the ability to choose which interface and/or which IP
address the ping is sourced from. Specifying an IP/interface does not
necessarily specify the interface from which the ping will leave, but
will specify which address the <code>packet(s)</code> appear to come from. If this
option is left out the IOS Device will source the packet automatically
based on routing and/or metrics. If this doesn't make sense to you
then just leave it out.</p>
<p>Example value: 192.168.2.129</p>
</dd><dt><strong><a name="item_source">source</a></strong>
</dt><dd>
<p>The source option specifies the IOS device to which we telnet. This
is an IP address of an IOS Device that you/your server:
1) Have the ability to telnet to
2) Have a valid username and password for</p>
<p>Example value: 192.168.2.1</p>
<p>This setting is mandatory.</p>
</dd></dl>
<p>
</p>
<hr />
<h1><a name="authors">AUTHORS</a></h1>
<p>John A Jackson <<a href="mailto:geonjay@infoave.net">geonjay@infoave.net</a>></p>
<p>based HEAVILY on Smokeping::probes::IOSPing by</p>
<p>Paul J Murphy <<a href="mailto:paul@murph.org">paul@murph.org</a>></p>
<p>based on Smokeping::probes::FPing by</p>
<p>Tobias Oetiker <<a href="mailto:tobi@oetiker.ch">tobi@oetiker.ch</a>></p>
<p>
</p>
<hr />
<h1><a name="notes">NOTES</a></h1>
<p>
</p>
<h2><a name="ios_configuration">IOS configuration</a></h2>
<p>The IOS device should have a username/password configured, as well as
the ability to connect to the VTY(s).
eg:</p>
<pre>
!
username smokeping privilege 5 password 0 SmokepingPassword
!
line vty 0 4
login local
transport input telnet
!</pre>
<p>Some IOS devices have a maximum of 5 VTYs available, so be careful not
to hit a limit with the 'forks' variable.</p>
<p>
</p>
<h2><a name="requirements">Requirements</a></h2>
<p>This module requires the Net::Telnet module for perl. This is usually
included on most newer OSs which include perl.</p>
<p>
</p>
<h2><a name="debugging">Debugging</a></h2>
<p>There is some VERY rudimentary debugging code built into this module (it's
based on the debugging code written into Net::Telnet). It will log
information into three files ``TIPreturn'', ``TIPoutlog'', and ``TIPdump''.
These files will be written out into your current working directory (CWD).
You can change the names of these files to something with more meaning to
you.</p>
<p>
</p>
<h2><a name="password_authentication">Password authentication</a></h2>
<p>You should be advised that the authentication method of telnet uses
clear text transmissions...meaning that without proper network security
measures someone could sniff your username and password off the network.
I may attempt to incorporate SSH in a future version of this module, but
it is very doubtful. Right now SSH adds a LOT of processing overhead to
a router, and isn't incredibly easy to implement in perl.</p>
<p>Having said this, don't be too scared of telnet. Remember, the
original IOSPing module used RSH, which is even more scary to use from
a security perspective.</p>
<p>
</p>
<h2><a name="ping_packet_size">Ping packet size</a></h2>
<p>The FPing manpage has the following to say on the topic of ping packet
size:</p>
<p>Number of bytes of ping data to send. The minimum size (normally 12)
allows room for the data that fping needs to do its work (sequence
number, timestamp). The reported received data size includes the IP
header (normally 20 bytes) and ICMP header (8 bytes), so the minimum
total size is 40 bytes. Default is 56, as in ping. Maximum is the
theoretical maximum IP datagram size (64K), though most systems limit
this to a smaller, system-dependent number.</p>
</body>
</html>
distrib
>
Mandriva
>
2010.0
>
i586
>
media
>
contrib-release
>
by-pkgid
>
d97b4c58d8763adc61a7b020afdfd868
>
files
>
145
