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