paloaltonetworks.panos.panos_ipsec_tunnel module – Manage IPSec Tunnels on the firewall with subset of settings.
Note
This module is part of the paloaltonetworks.panos collection (version 2.21.2).
To install it, use: ansible-galaxy collection install paloaltonetworks.panos
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: paloaltonetworks.panos.panos_ipsec_tunnel
.
New in paloaltonetworks.panos 1.0.0
Synopsis
Use IPSec Tunnels to establish and manage IPSec VPN tunnels between firewalls. This is the Phase 2 portion of the
IKE/IPSec VPN setup.
Requirements
The below requirements are needed on the host that executes this module.
pan-python can be obtained from PyPI https://pypi.python.org/pypi/pan-python
pandevice can be obtained from PyPI https://pypi.python.org/pypi/pandevice
Parameters
Parameter |
Comments |
---|---|
Name of the existing IKE gateway (auto-key). Default: :ansible-option-default:`"default"` |
|
Name of the existing IPsec profile or use default (auto-key). Default: :ansible-option-default:`"default"` |
|
Enable anti-replay check on this tunnel. Choices: |
|
Deprecated Use provider to specify PAN-OS connectivity instead. The API key to use instead of generating it using username / password. |
|
Deprecated Please use paloaltonetworks.panos.panos_commit_firewall, paloaltonetworks.panos.panos_commit_panorama, paloaltonetworks.panos.panos_commit_push instead. Commit changes after creating object. If ip_address is a Panorama device, and device_group or template are also set, perform a commit to Panorama and a commit-all to the device group/template. Choices: |
|
Copy IPv6 flow label for 6in6 tunnel from inner packet to IPSec packet (not recommended) (7.0+). Choices: |
|
Copy IP TOS bits from inner packet to IPSec packet (not recommended). Choices: |
|
Disable the IPsec tunnel. Choices: |
|
Enable tunnel monitoring on this tunnel. Choices: |
|
When state=gathered. An advanced filtering option to filter results returned from PAN-OS. Refer to the guide discussing gathered_filter for more information. |
|
Profile for authenticating GlobalProtect gateway certificates (global-protect-satellite). |
|
Interface to communicate with portal (global-protect-satellite). |
|
Floating IPv4 IP address in HA Active-Active configuration (7.0+) (global-protect-satellite). |
|
Exact IPv4 IP address if interface has multiple IP addresses (global-protect-satellite). |
|
Floating IPv6 IP address in HA Active-Active configuration (8.0+) (global-protect-satellite). |
|
Exact IPv6 IP address if interface has multiple IP addresses (8.0+) (global-protect-satellite). |
|
GlobalProtect satellite certificate file name (global-protect-satellite). |
|
GlobalProtect portal address (global-protect-satellite). |
|
Prefer to register portal in IPv6 (8.0+) (global-protect-satellite). Choices: |
|
Enable publishing of connected and static routes (global-protect-satellite). Choices: |
|
Specify list of routes to publish to GlobalProtect gateway (global-protect-satellite). |
|
Deprecated Use provider to specify PAN-OS connectivity instead. The IP address or hostname of the PAN-OS device being configured. |
|
Use IPv6 for the IPsec tunnel (7.0+) Choices: |
|
Authentication key (manual-key). |
|
Authentication type for tunnel access (manual-key). Choices: |
|
Encryption algorithm for tunnel traffic (manual-key). Choices: |
|
Encryption key (manual-key). |
|
Interface to terminate tunnel (manual-key). |
|
Floating IP address in HA Active-Active configuration (manual-key). |
|
Exact IP address if interface has multiple IP addresses (manual-key). |
|
Outbound SPI in hex (manual-key). |
|
Protocol for traffic through the tunnel (manual-key). Choices: |
|
Tunnel peer IP address (manual-key). |
|
Inbound SPI in hex (manual-key). |
|
Name for the IPSec tunnel. |
|
Deprecated Use provider to specify PAN-OS connectivity instead. The password to use for authentication. This is ignored if api_key is specified. |
|
Deprecated Use provider to specify PAN-OS connectivity instead. The port number to connect to the PAN-OS device on. Default: :ansible-option-default:`443` |
|
A dict object containing connection details. |
|
The API key to use instead of generating it using username / password. |
|
The IP address or hostname of the PAN-OS device being configured. |
|
The password to use for authentication. This is ignored if api_key is specified. |
|
The port number to connect to the PAN-OS device on. Default: :ansible-option-default:`443` |
|
The serial number of a firewall to use for targeted commands. If ip_address is not a Panorama PAN-OS device, then this param is ignored. |
|
The username to use for authentication. This is ignored if api_key is specified. Default: :ansible-option-default:`"admin"` |
|
(Panorama only) The template this operation should target. Mutually exclusive with template_stack. |
|
(Panorama only) The template stack this operation should target. Mutually exclusive with template. |
|
Specify existing tunnel interface that will be used. Default: :ansible-option-default:`"tunnel.1"` |
|
Destination IP to send ICMP probe. |
|
Monitoring action. |
|
Which proxy-id (or proxy-id-v6) the monitoring traffic will use. |
|
Type of IPsec tunnel. Choices: |
|
Deprecated Use provider to specify PAN-OS connectivity instead. The username to use for authentication. This is ignored if api_key is specified. Default: :ansible-option-default:`"admin"` |
Notes
Note
Panorama is supported.
Check mode is supported.
PAN-OS connectivity should be specified using provider or the classic PAN-OS connectivity params (ip_address, username, password, api_key, and port). If both are present, then the classic params are ignored.
If the PAN-OS to be configured is Panorama, either template or template_stack must be specified.
Examples
- name: Add IPSec tunnel to IKE gateway profile
paloaltonetworks.panos.panos_ipsec_tunnel:
provider: '{{ provider }}'
name: 'IPSecTunnel-Ansible'
tunnel_interface: 'tunnel.2'
ak_ike_gateway: 'IKEGW-Ansible'
ak_ipsec_crypto_profile: 'IPSec-Ansible'