Smokeping_probes_DismanPing(3) | SmokePing | Smokeping_probes_DismanPing(3) |
Smokeping::probes::DismanPing - DISMAN-PING-MIB Probe for SmokePing
*** Probes *** +DismanPing offset = 50% pings = 15 step = 300 # The following variables can be overridden in each target section ownerindex = smokeping packetsize = 56 pinghost = pinger@router.example.com # mandatory pingsrc = 192.0.2.9 # [...] *** Targets *** probe = DismanPing # if this should be the default probe # [...] + mytarget # probe = DismanPing # if the default probe is something else host = my.host ownerindex = smokeping packetsize = 56 pinghost = pinger@router.example.com # mandatory pingsrc = 192.0.2.9
Uses the DISMAN-PING-MIB to cause a remote system to send probes.
Supported probe-specific variables:
Example value: 50%
Example value: 15
Default value: 15
Example value: 300
Supported target-specific variables:
By default this will be set to
Example value: smokeping
Default value: 56
Example value: pinger@router.example.com
This setting is mandatory.
Example value: 192.0.2.9
Bill Fenner <fenner@research.att.com>, Tobi Oetiker <tobi@oetiker.ch>
This probe uses the menu name of a test as part of the unique index. If the menu name is longer than 32 characters, the last 32 characters are used for the index. Collisions are *not* detected and simply cause one test's results to be used for all colliding names.
This probe requires read/write access to the pingCtlTable. It also requires read-only access to the pingResultsTable and the pingHistoryTable. The DISMAN-PING-MIB is structured such that it is possible to restrict by pingCtlOwnerIndex. This probe uses a pingCtlOwnerIndex of "SP on hostname" as ownerindex by default; use ownerindex to configure this if needed.
This configuration permits the community "pinger" read-write access to the full DISMAN-PING-MIB, but only when sourced from the manager at 192.0.2.134.
snmp { view pingMIB { oid .1.3.6.1.2.1.80 include; } community pinger { view pingMIB; authorization read-write; clients { 192.0.2.134/32; } } }
This configuration allows the "pinger" community full access to the DISMAN-PING-MIB. There is information in the description of pingCtlOwnerIndex in RFC 4560 (<http://tools.ietf.org/html/rfc4560>) about using the vacmViewTreeFamilyTable to further restrict access. The author has not tried this method.
2022-10-15 | 2.7.3 |