mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-04-26 20:31:27 -07:00
Clarify which ping module to use (#34935)
* Clarify which ping module to use Ensure each of the ping modules link to each other ping - Requires Python on remote-node nxos_ping - Only on Cisco NXOS ios_ping - Only on Cisco IOS net_ping - For network devices win_ping - only for Windows
This commit is contained in:
parent
4ba7b005f5
commit
db61f8f967
5 changed files with 26 additions and 3 deletions
|
@ -21,11 +21,13 @@ short_description: Try to connect to host, verify a usable python and return C(p
|
|||
description:
|
||||
- A trivial test module, this module always returns C(pong) on successful
|
||||
contact. It does not make sense in playbooks, but it is useful from
|
||||
C(/usr/bin/ansible) to verify the ability to login and that a usable python is configured.
|
||||
- This is NOT ICMP ping, this is just a trivial test module.
|
||||
C(/usr/bin/ansible) to verify the ability to login and that a usable Python is configured.
|
||||
- This is NOT ICMP ping, this is just a trivial test module that requires Python on the remote-node.
|
||||
- For Windows targets, use the M(win_ping) module instead.
|
||||
- For Network targets, use the M(net_ping) module instead.
|
||||
notes:
|
||||
- For Windows targets, use the M(win_ping) module instead.
|
||||
- For Network targets, use the M(net_ping) module instead.
|
||||
options:
|
||||
data:
|
||||
description:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue