check_point.mgmt.cp_mgmt_vsx_provisioning_tool module – Run the VSX provisioning tool with the specified parameters.
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_vsx_provisioning_tool
.
New in check_point.mgmt 6.0.0
Synopsis
Run the VSX provisioning tool with the specified parameters. Note - An automatic session publish is part of all the operations in this API.
All operations are performed over Web Services API.
Parameters
Parameter |
Comments |
---|---|
Parameters for the operation to add a physical interface to a VSX gateway or VSX Cluster. |
|
Name of the interface. |
|
True if this interface is a VLAN trunk. Choices:
|
|
Name of the VSX Gateway or Cluster object. |
|
Parameters for the operation to add a route to a Virtual System or Virtual Router. |
|
Route destination. To specify the default route, use ‘default’ for IPv4 and ‘default6’ for IPv6. |
|
Virtual Router for this route<br/>This VD must have an existing connection to the VR. |
|
Subnet mask for this route. |
|
Next hop IP address. |
|
CIDR prefix for this route. |
|
Propagate this route to adjacent virtual devices. Choices:
|
|
Name of the Virtual System, Virtual Switch, or Virtual Router. |
|
Parameters for the operation to add a new interface to a Virtual Device. |
|
The anti-spoofing enforcement setting of this interface. Choices:
|
|
The anti-spoofing tracking setting of this interface. Choices:
|
|
IPv4 Address of this interface with optional CIDR prefix.<br/>Required if this interface belongs to a Virtual System or Virtual Router. |
|
IPv4 Subnet mask of this interface. |
|
IPv4 CIDR prefix of this interface. |
|
IPv6 Address of this interface<br/>Required if this interface belongs to a Virtual System or Virtual Router. |
|
IPv6 Subnet mask of this interface. |
|
IPv6 CIDR prefix of this interface. |
|
Virtual Switch or Virtual Router for this interface. |
|
MTU of this interface. |
|
Name of the interface. |
|
Propagate IPv4 route to adjacent virtual devices. Choices:
|
|
Propagate IPv6 route to adjacent virtual devices. Choices:
|
|
Specific group for interface topology.<br/>Only for use with topology option ‘internal_specific’. |
|
Topology of this interface.<br/>Automatic topology calculation based on routes must be disabled for this VS. Choices:
|
|
Name of the Virtual System, Virtual Switch, or Virtual Router. |
|
VTI settings for this interface. This Virtual System must have VPN blade enabled. |
|
The IPv4 address of the VPN tunnel on this Virtual System. |
|
The name of the remote peer object as defined in the VPN community. |
|
The IPv4 address of the VPN tunnel on the remote VPN peer. |
|
Optional unique Tunnel ID.<br/>Automatically assigned by the system if empty. |
|
Parameters for the operation to add a new Virtual Device (VS/VSB/VSW/VR). |
|
Calculate interface topology automatically based on routes.<br/>Relevant only for Virtual Systems.<br/>Do not use for virtual devices. Choices:
|
|
The list of interfaces for this new Virtual Device.<br/>Optional if this new VD is a Virtual Switch. |
|
The anti-spoofing enforcement setting of this interface. Choices:
|
|
The anti-spoofing tracking setting of this interface. Choices:
|
|
IPv4 Address of this interface with optional CIDR prefix.<br/>Required if this interface belongs to a Virtual System or Virtual Router. |
|
IPv4 Subnet mask of this interface. |
|
IPv4 CIDR prefix of this interface. |
|
IPv6 Address of this interface<br/>Required if this interface belongs to a Virtual System or Virtual Router. |
|
IPv6 Subnet mask of this interface. |
|
IPv6 CIDR prefix of this interface. |
|
Virtual Switch or Virtual Router for this interface. |
|
MTU of this interface. |
|
Name of the interface. |
|
Propagate IPv4 route to adjacent virtual devices. Choices:
|
|
Propagate IPv6 route to adjacent virtual devices. Choices:
|
|
Specific group for interface topology.<br/>Only for use with topology option ‘internal_specific’. |
|
Topology of this interface.<br/>Automatic topology calculation based on routes must be disabled for this VS. Choices:
|
|
Main IPv4 Address.<br/>Required if this device is a Virtual System.<br/>Do not use for other virtual devices. |
|
Number of IPv4 instances for the Virtual System.<br/>Must be greater or equal to 1.<br/>Only relevant for Virtual Systems and Virtual Systems in bridge mode. |
|
Main IPv6 Address.<br/>Required if this device is a Virtual System.<br/>Do not use for other virtual devices. |
|
Number of IPv6 instances for the Virtual System.<br/>Only relevant for Virtual Systems and Virtual Systems in bridge mode. |
|
The list of routes for this new Virtual Device (VS or VR only). |
|
Route destination. To specify the default route, use ‘default’ for IPv4 and ‘default6’ for IPv6. |
|
Virtual Router for this route<br/>This VD must have an existing connection to the VR. |
|
Subnet mask for this route. |
|
Next hop IP address. |
|
CIDR prefix for this route. |
|
Propagate this route to adjacent virtual devices. Choices:
|
|
Type of the Virtual Device <br><br>vs - Virtual Firewall<br>vr - Virtual Router<br>vsw - Virtual Switch<br>vsbm - Virtual Firewall in bridge mode. Choices:
|
|
Name of the Virtual System, Virtual Switch, or Virtual Router. |
|
MTU of the Virtual System.<br/>Only relevant for Virtual Systems in bridge mode.<br/>Do not use for other virtual devices. |
|
Name of the VSX Gateway or Cluster object. |
|
Parameters for the operation to add a new VSX Cluster. |
|
Cluster type for the VSX Cluster Object.<br/>Starting in R81.10, only VSLS can be configured during cluster creation.<br/>To use High Availability (‘ha’), first create the cluster as VSLS and then run vsx_util on the Management. Choices:
|
|
Main IPv4 Address of the VSX Gateway or Cluster object.<br/>Optional if main IPv6 Address is defined. |
|
Main IPv6 Address of the VSX Gateway or Cluster object.<br/>Optional if main IPv4 Address is defined. |
|
The list of cluster members for this new VSX Cluster. Minimum, 2. |
|
Main IPv4 Address of the VSX Cluster member.<br/>Mandatory if the VSX Cluster has an IPv4 Address. |
|
Main IPv6 Address of the VSX Cluster member.<br/>Mandatory if the VSX Cluster has an IPv6 Address. |
|
Name of the new VSX Cluster member. |
|
SIC one-time-password of the VSX Gateway or Cluster member.<br/>Password must be between 4-127 characters in length. |
|
Sync IP address for the VSX Cluster member. |
|
Add a default drop rule to the VSX Gateway or Cluster initial policy. Choices:
|
|
Add a rule to allow HTTPS traffic to the VSX Gateway or Cluster initial policy. Choices:
|
|
Add a rule to allow ping traffic to the VSX Gateway or Cluster initial policy. Choices:
|
|
Add a rule to allow ping6 traffic to the VSX Gateway or Cluster initial policy. Choices:
|
|
Add a rule to allow SNMP traffic to the VSX Gateway or Cluster initial policy. Choices:
|
|
Add a rule to allow SSH traffic to the VSX Gateway or Cluster initial policy. Choices:
|
|
Sync interface name for the VSX Cluster. |
|
Sync interface netmask for the VSX Cluster. |
|
Name of the VSX Gateway or Cluster object. |
|
Version of the VSX Gateway or Cluster object. |
|
Parameters for the operation to add a new VSX Gateway. |
|
Main IPv4 Address of the VSX Gateway or Cluster object.<br/>Optional if main IPv6 Address is defined. |
|
Main IPv6 Address of the VSX Gateway or Cluster object.<br/>Optional if main IPv4 Address is defined. |
|
Add a default drop rule to the VSX Gateway or Cluster initial policy. Choices:
|
|
Add a rule to allow HTTPS traffic to the VSX Gateway or Cluster initial policy. Choices:
|
|
Add a rule to allow ping traffic to the VSX Gateway or Cluster initial policy. Choices:
|
|
Add a rule to allow ping6 traffic to the VSX Gateway or Cluster initial policy. Choices:
|
|
Add a rule to allow SNMP traffic to the VSX Gateway or Cluster initial policy. Choices:
|
|
Add a rule to allow SSH traffic to the VSX Gateway or Cluster initial policy. Choices:
|
|
SIC one-time-password of the VSX Gateway or Cluster member.<br/>Password must be between 4-127 characters in length. |
|
Name of the VSX Gateway or Cluster object. |
|
Version of the VSX Gateway or Cluster object. |
|
Parameters for the operation to attach a new bridge interface to a Virtual System. |
|
Name of the first interface for the bridge. |
|
Name of the second interface for the bridge. |
|
Name of the Virtual System, Virtual Switch, or Virtual Router. |
|
Publish the current session if changes have been performed after task completes. Choices:
|
|
The name of the provisioning operation to run. Each operation has its own specific parameters.<br> The available operations are,<ul><li><i>add-vsx-gateway</i> - Adds a new VSX gateway</li><li><i>add-vsx-cluster</i> - Adds a new VSX cluster*</li><li><i>add-vsx-cluster-member</i> - Adds a new VSX cluster member*</li><li><i>add-vd</i> - Adds a new Virtual Device (VS/VSB/VSW/VR) to a VSX gateway or VSX cluster</li><li><i>add-vd-interface</i> - Adds a new virtual interface to a Virtual Device</li><li><i>add-physical-interface</i> - Adds a physical interface to a VSX gateway or VSX cluster</li><li><i>add-route</i> - Adds a route to a Virtual Device</li><li><i>attach-bridge</i> - Attaches a bridge interface to a Virtual System</li><li><i>remove-vsx</i> - Removes a VSX gateway or VSX cluster</li><li><i>remove-vd</i> - Removes a Virtual Device</li><li><i>remove-vd-interface</i> - Removes an interface from a Virtual Device</li><li><i>remove-physical-interface</i> - Removes a physical interface from a VSX gateway or VSX cluster</li><li><i>remove-route</i> - Removes a route from a Virtual Device</li><li><i>set-vd</i> - Modifies a Virtual Device</li><li><i>set-vd-interface</i> - Modifies an interface on a Virtual Device</li><li><i>set-physical-interface</i> - Modifies a physical interface on a VSX cluster or VSX gateway</li></ul><br> * When adding a VSX Cluster, you must also add at least 2 cluster members<br> * Adding cluster members is only allowed when adding a new VSX cluster<br> * To add members to an existing cluster, use vsx-run-operation. Choices:
|
|
Parameters for the operation to remove a physical interface from a VSX (Gateway or Cluster). |
|
Name of the interface. |
|
Name of the VSX Gateway or Cluster object. |
|
Parameters for the operation to remove a route from a Virtual System or Virtual Router. |
|
Route destination. To specify the default route, use ‘default’ for IPv4 and ‘default6’ for IPv6. |
|
Subnet mask for this route. |
|
CIDR prefix for this route. |
|
Name of the Virtual System, Virtual Switch, or Virtual Router. |
|
Parameters for the operation to remove a logical interface from a Virtual Device. |
|
Virtual Switch or Virtual Router for this interface. |
|
Name of the interface. |
|
Name of the Virtual System, Virtual Switch, or Virtual Router. |
|
Parameters for the operation to remove a Virtual Device. |
|
Name of the Virtual System, Virtual Switch, or Virtual Router. |
|
Parameters for the operation to remove a VSX Gateway or VSX Cluster. |
|
Name of the VSX Gateway or Cluster object. |
|
Parameters for the operation to change the configuration of a physical interface. |
|
Name of the interface. |
|
True if this interface is a VLAN trunk. Choices:
|
|
Name of the VSX Gateway or Cluster object. |
|
Parameters for the operation to change the configuration of a logical interface. |
|
The anti-spoofing enforcement setting of this interface. Choices:
|
|
The anti-spoofing tracking setting of this interface. Choices:
|
|
IPv4 Address of this interface with optional CIDR prefix.<br/>Required if this interface belongs to a Virtual System or Virtual Router. |
|
IPv6 Address of this interface<br/>Required if this interface belongs to a Virtual System or Virtual Router. |
|
Virtual Switch or Virtual Router for this interface. |
|
MTU of this interface. |
|
Name of the interface. |
|
New Virtual Switch or Virtual Router for this interface. |
|
Propagate IPv4 route to adjacent virtual devices. Choices:
|
|
Propagate IPv6 route to adjacent virtual devices. Choices:
|
|
Specific group for interface topology.<br/>Only for use with topology option ‘internal_specific’. |
|
Topology of this interface.<br/>Automatic topology calculation based on routes must be disabled for this VS. Choices:
|
|
Name of the Virtual System, Virtual Switch, or Virtual Router. |
|
Parameters for the operation to change the configuration of a Virtual Device. |
|
Calculate interface topology automatically based on routes.<br/>Relevant only for Virtual Systems.<br/>Do not use for virtual devices. Choices:
|
|
Main IPv4 Address.<br/>Relevant only if this device is a Virtual System.<br/>Do not use for other virtual devices. |
|
Number of IPv4 instances for the Virtual System.<br/>Must be greater or equal to 1.<br/>Only relevant for Virtual Systems and Virtual Systems in bridge mode. |
|
Main IPv6 Address.<br/>Relevant only if this device is a Virtual System.<br/>Do not use for other virtual devices. |
|
Number of IPv6 instances for the Virtual System.<br/>Only relevant for Virtual Systems and Virtual Systems in bridge mode. |
|
Name of the Virtual System, Virtual Switch, or Virtual Router. |
|
MTU of the Virtual System.<br/>Only relevant for Virtual Systems in bridge mode.<br/>Do not use for other virtual devices. |
|
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: vsx-provisioning-tool
cp_mgmt_vsx_provisioning_tool:
add_vsx_cluster_params:
cluster_type: vsls
ipv4_address: 10.1.1.15
members:
- ipv4_address: 10.1.1.1
name: VSX1
sic_otp: sicotp123
sync_ip: 192.168.1.1
- ipv4_address: 10.1.1.2
name: VSX2
sic_otp: sicotp123
sync_ip: 192.168.1.2
rule_drop: enable
rule_ping: enable
sync_if_name: eth3
sync_netmask: 255.255.255.0
vsx_version: R81.10
vsx_name: VSX_CLUSTER
operation: add-vsx-cluster
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The checkpoint vsx-provisioning-tool output. Returned: always. |