1Smokeping_probes_TelnetJunOSPing(3)SmokePingSmokeping_probes_TelnetJunOSPing(3)
2
6 Smokeping::probes::TelnetJunOSPing - Juniper JunOS Probe for SmokePing
7
9 *** Probes ***
10 +TelnetJunOSPing
12 forks = 5
14 offset = 50%
15 packetsize = 100
16 step = 300
17 timeout = 15
18 # The following variables can be overridden in each target section
20 junospass = password # mandatory
21 junosuser = user # mandatory
22 pings = 5
23 psource = 192.168.2.129
24 source = 192.168.2.1 # mandatory
25 # [...]
27 *** Targets ***
29 probe = TelnetJunOSPing # if this should be the default probe
31 # [...]
33 + mytarget
35 # probe = TelnetJunOSPing # if the default probe is something else
36 host = my.host
37 junospass = password # mandatory
38 junosuser = user # mandatory
39 pings = 5
40 psource = 192.168.2.129
41 source = 192.168.2.1 # mandatory
42
44 Integrates Juniper JunOS as a probe into smokeping. Uses the telnet
45 protocol to run a ping from an JunOS device (source) to another device
46 (host). This probe basically uses the "extended ping" of the Juniper
47 JunOS. You have the option to specify which interface the ping is
48 sourced from as well.
49
51 Supported probe-specific variables:
52 forks
54 Run this many concurrent processes at maximum
55 Example value: 5
57 Default value: 5
59 offset
61 If you run many probes concurrently you may want to prevent them
62 from hitting your network all at the same time. Using the probe-
63 specific offset parameter you can change the point in time when
64 each probe will be run. Offset is specified in % of total interval,
65 or alternatively as 'random', and the offset from the 'General'
66 section is used if nothing is specified here. Note that this does
67 NOT influence the rrds itself, it is just a matter of when data
68 acqusition is initiated. (This variable is only applicable if the
69 variable 'concurrentprobes' is set in the 'General' section.)
70 Example value: 50%
72 packetsize
74 The (optional) packetsize option lets you configure the packetsize
75 for the pings sent.
76 Default value: 100
78 step
80 Duration of the base interval that this probe should use, if
81 different from the one specified in the 'Database' section. Note
82 that the step in the RRD files is fixed when they are originally
83 generated, and if you change the step parameter afterwards, you'll
84 have to delete the old RRD files or somehow convert them. (This
85 variable is only applicable if the variable 'concurrentprobes' is
86 set in the 'General' section.)
87 Example value: 300
89 timeout
91 How long a single 'ping' takes at maximum
92 Example value: 15
94 Default value: 5
96 Supported target-specific variables:
98 junospass
100 The junospass option allows you to specify the password for the
101 username specified with the option junosuser.
102 Example value: password
104 This setting is mandatory.
106 junosuser
108 The junosuser option allows you to specify a username that has ping
109 capability on the JunOS Device.
110 Example value: user
112 This setting is mandatory.
114 pings
116 How many pings should be sent to each target, if different from the
117 global value specified in the Database section. Note that the
118 number of pings in the RRD files is fixed when they are originally
119 generated, and if you change this parameter afterwards, you'll have
120 to delete the old RRD files or somehow convert them.
121 Example value: 5
123 psource
125 The (optional) psource option specifies an alternate IP address or
126 Interface from which you wish to source your pings from. Routers
127 can have many many IP addresses, and interfaces. When you ping
128 from a router you have the ability to choose which interface and/or
129 which IP address the ping is sourced from. Specifying an
130 IP/interface does not necessarily specify the interface from which
131 the ping will leave, but will specify which address the packet(s)
132 appear to come from. If this option is left out the JunOS Device
133 will source the packet automatically based on routing and/or
134 metrics. If this doesn't make sense to you then just leave it out.
135 Example value: 192.168.2.129
137 source
139 The source option specifies the JunOS device to which we telnet.
140 This is an IP address of an JunOS Device that you/your server:
141 1) Have the ability to telnet to 2) Have a valid
142 username and password for
143 Example value: 192.168.2.1
145 This setting is mandatory.
147
149 S H A N <shanali@yahoo.com>
150 based HEAVILY on Smokeping::probes::TelnetIOSPing by
152 John A Jackson <geonjay@infoave.net>
154 based on Smokeping::probes::JunOSPing by
156 Paul J Murphy <paul@murph.org>
158 based on Smokeping::probes::FPing by
160 Tobias Oetiker <tobi@oetiker.ch>
162
164 JunOS configuration
165 The JunOS device should have a username/password configured, as well as
166 the ability to connect to the VTY(s).
167 Some JunOS devices have a maximum of 5 VTYs available, so be careful
169 not to hit a limit with the 'forks' variable.
170 Requirements
172 This module requires the Net::Telnet module for perl. This is usually
173 included on most newer OSs which include perl.
174 Debugging
176 There is some VERY rudimentary debugging code built into this module
177 (it's based on the debugging code written into Net::Telnet). It will
178 log information into three files "TIPreturn", "TIPoutlog", and
179 "TIPdump". These files will be written out into your current working
180 directory (CWD). You can change the names of these files to something
181 with more meaning to you.
182 Password authentication
184 You should be advised that the authentication method of telnet uses
185 clear text transmissions...meaning that without proper network security
186 measures someone could sniff your username and password off the
187 network. I may attempt to incorporate SSH in a future version of this
188 module, but it is very doubtful. Right now SSH adds a LOT of
189 processing overhead to a router, and isn't incredibly easy to implement
190 in perl.
191 Having said this, don't be too scared of telnet. Remember, the
193 original JunOSPing module used RSH, which is even more scary to use
194 from a security perspective.
195 Ping packet size
197 The FPing manpage has the following to say on the topic of ping packet
198 size:
199 Number of bytes of ping data to send. The minimum size (normally 12)
201 allows room for the data that fping needs to do its work (sequence
202 number, timestamp). The reported received data size includes the IP
203 header (normally 20 bytes) and ICMP header (8 bytes), so the minimum
204 total size is 40 bytes. Default is 56, as in ping. Maximum is the
205 theoretical maximum IP datagram size (64K), though most systems limit
206 this to a smaller, system-dependent number.
2072.7.2 2019-02-02Smokeping_probes_TelnetJunOSPing(3)