1Smokeping_probes_DismanPing(3) SmokePing Smokeping_probes_DismanPing(3)
2
6 Smokeping::probes::DismanPing - DISMAN-PING-MIB Probe for SmokePing
7
9 *** Probes ***
10 +DismanPing
12 offset = 50%
14 pings = 15
15 step = 300
16 # The following variables can be overridden in each target section
18 ownerindex = smokeping
19 packetsize = 56
20 pinghost = pinger@router.example.com # mandatory
21 pingsrc = 192.0.2.9
22 # [...]
24 *** Targets ***
26 probe = DismanPing # if this should be the default probe
28 # [...]
30 + mytarget
32 # probe = DismanPing # if the default probe is something else
33 host = my.host
34 ownerindex = smokeping
35 packetsize = 56
36 pinghost = pinger@router.example.com # mandatory
37 pingsrc = 192.0.2.9
38
40 Uses the DISMAN-PING-MIB to cause a remote system to send probes.
41
43 Supported probe-specific variables:
44 offset
46 If you run many probes concurrently you may want to prevent them
47 from hitting your network all at the same time. Using the probe-
48 specific offset parameter you can change the point in time when
49 each probe will be run. Offset is specified in % of total interval,
50 or alternatively as 'random', and the offset from the 'General'
51 section is used if nothing is specified here. Note that this does
52 NOT influence the rrds itself, it is just a matter of when data
53 acqusition is initiated. (This variable is only applicable if the
54 variable 'concurrentprobes' is set in the 'General' section.)
55 Example value: 50%
57 pings
59 How many pings should be sent to each target. Note that the maximum
60 value for DismanPing MIP is 15, which is less than the SmokePing
61 default, so this class has its own default value. If your Database
62 section specifies a value less than 15, you must also set it for
63 this probe. Note that the number of pings in the RRD files is
64 fixed when they are originally generated, and if you change this
65 parameter afterwards, you'll have to delete the old RRD files or
66 somehow convert them.
67 Example value: 15
69 Default value: 15
71 step
73 Duration of the base interval that this probe should use, if
74 different from the one specified in the 'Database' section. Note
75 that the step in the RRD files is fixed when they are originally
76 generated, and if you change the step parameter afterwards, you'll
77 have to delete the old RRD files or somehow convert them. (This
78 variable is only applicable if the variable 'concurrentprobes' is
79 set in the 'General' section.)
80 Example value: 300
82 Supported target-specific variables:
84 ownerindex
86 The SNMP OwnerIndex to use when setting up the test. When using
87 VACM, can map to a Security Name or Group Name of the entity
88 running the test.
89 By default this will be set to
91 Example value: smokeping
93 packetsize
95 The packetsize parameter lets you configure the packet size for the
96 pings sent. The minimum is 8, the maximum 65507. Use the same
97 number as with fping if you want the same packet sizes being used
98 on the network.
99 Default value: 56
101 pinghost
103 The (mandatory) pinghost parameter specifies the remote system
104 which will execute the pings, as well as the SNMP community string
105 on the device.
106 Example value: pinger@router.example.com
108 This setting is mandatory.
110 pingsrc
112 The (optional) pingsrc parameter specifies the source address to be
113 used for pings. If specified, this parameter must identify an IP
114 address assigned to pinghost.
115 Example value: 192.0.2.9
117
119 Bill Fenner <fenner@research.att.com>, Tobi Oetiker <tobi@oetiker.ch>
120
122 MENU NAMES
123 This probe uses the menu name of a test as part of the unique index.
124 If the menu name is longer than 32 characters, the last 32 characters
125 are used for the index. Collisions are *not* detected and simply cause
126 one test's results to be used for all colliding names.
127 CONFIGURATION
129 This probe requires read/write access to the pingCtlTable. It also
130 requires read-only access to the pingResultsTable and the
131 pingHistoryTable. The DISMAN-PING-MIB is structured such that it is
132 possible to restrict by pingCtlOwnerIndex. This probe uses a
133 pingCtlOwnerIndex of "SP on hostname" as ownerindex by default; use
134 ownerindex to configure this if needed.
135 SAMPLE JUNOS CONFIGURATION
137 This configuration permits the community "pinger" read-write access to
138 the full DISMAN-PING-MIB, but only when sourced from the manager at
139 192.0.2.134.
140 snmp {
142 view pingMIB {
143 oid .1.3.6.1.2.1.80 include;
144 }
145 community pinger {
146 view pingMIB;
147 authorization read-write;
148 clients {
149 192.0.2.134/32;
150 }
151 }
152 }
153 SAMPLE CONFIGURATIONS NOTE
155 This configuration allows the "pinger" community full access to the
156 DISMAN-PING-MIB. There is information in the description of
157 pingCtlOwnerIndex in RFC 4560 (<http://tools.ietf.org/html/rfc4560>)
158 about using the vacmViewTreeFamilyTable to further restrict access.
159 The author has not tried this method.
1602.7.2 2018-07-15 Smokeping_probes_DismanPing(3)