check_point.mgmt.cp_mgmt_network_probe module – Manages network-probe objects on Checkpoint over Web Services API
Note
This module is part of the check_point.mgmt collection (version 6.2.1).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install check_point.mgmt
.
To use it in a playbook, specify: check_point.mgmt.cp_mgmt_network_probe
.
New in check_point.mgmt 6.0.0
Synopsis
Manages network-probe objects on Checkpoint devices including creating, updating and removing objects.
All operations are performed over Web Services API.
Parameters
Parameter |
Comments |
---|---|
Publish the current session if changes have been performed after task completes. Choices:
|
|
Color of the object. Should be one of existing colors. Choices:
|
|
Comments string. |
|
The level of detail for some of the fields in the response can vary from showing only the UID value of the object to a fully detailed representation of the object. Choices:
|
|
Indicates which domains to process the commands on. It cannot be used with the details-level full, must be run from the System Domain only and with ignore-warnings true. Valid values are, CURRENT_DOMAIN, ALL_DOMAINS_ON_THIS_SERVER. |
|
Additional options when [protocol] is set to “http”. |
|
The destination URL. |
|
Additional options when [protocol] is set to “icmp”. |
|
One of these,<br>- Name or UID of an existing object with a unicast IPv4 address (Host, Security Gateway, and so on).<br>- A unicast IPv4 address string (if you do not want to create such an object). |
|
One of these,<br>- The string “main-ip” (the probe uses the main IPv4 address of the Security Gateway objects you specified in the parameter [install-on]).<br>- Name or UID of an existing object of type ‘Host’ with a unicast IPv4 address.<br>- A unicast IPv4 address string (if you do not want to create such an object). |
|
Apply changes ignoring errors. You won’t be able to publish such a changes. If ignore-warnings flag was omitted - warnings will also be ignored. Choices:
|
|
Apply changes ignoring warnings. Choices:
|
|
Collection of Check Point Security Gateways that generate the probe, identified by name or UID. |
|
The time interval in the range of 5-300 (seconds) between each probe request. Best Practice - The interval value should be lower than the timeout value. |
|
Object name. |
|
The probing protocol to use. Choices:
|
|
State of the access rule (present or absent). Choices:
|
|
Collection of tag identifiers. |
|
The probe expiration timeout in the range of 5-300 (seconds). If there is not a single reply within this time, the status of the probe changes to “Down”. |
|
Version of checkpoint. If not given one, the latest version taken. |
|
Wait for the task to end. Such as publish task. Choices:
|
|
How many minutes to wait until throwing a timeout error. Default: |
Examples
- name: add-network-probe
cp_mgmt_network_probe:
icmp_options:
destination: HOST_20.20.20.20
source: Host_10.10.10.10
install_on: GW_1
name: probe_GW1
state: present
- name: set-network-probe
cp_mgmt_network_probe:
icmp_options:
destination: 2.2.2.2
source: 1.1.1.1
name: probe_GW1
state: present
- name: delete-network-probe
cp_mgmt_network_probe:
name: probe_GW1
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The checkpoint object created or updated. Returned: always, except when deleting the object. |