paloaltonetworks.panos.panos_tunnel module – Manage tunnel interfaces
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_tunnel
.
New in paloaltonetworks.panos 1.0.0
Synopsis
Manage tunnel interfaces on PanOS
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 |
---|---|
Deprecated Use provider to specify PAN-OS connectivity instead. The API key to use instead of generating it using username / password. |
|
Interface comment. |
|
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: |
|
When state=gathered. An advanced filtering option to filter results returned from PAN-OS. Refer to the guide discussing gathered_filter for more information. |
|
Name of the interface to configure. |
|
List of static IP addresses. |
|
Deprecated Use provider to specify PAN-OS connectivity instead. The IP address or hostname of the PAN-OS device being configured. |
|
Interface management profile name; it must already exist. |
|
MTU for tunnel interface. |
|
Netflow profile for tunnel interface. |
|
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. This param is required if the PAN-OS device is Panorama. |
|
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"` |
|
Name of the virtual router; it must already exist. |
|
The vsys this object should be imported into. Objects that are imported include interfaces, virtual routers, virtual wires, and VLANs. Interfaces are typically imported into vsys1 if no vsys is specified. |
|
Deprecated Use vsys to specify the vsys instead. Name of the vsys (if firewall) or device group (if panorama) to put this object. |
|
Name of the zone for the interface. If the zone does not exist it is created but if the zone exists and it is not of the correct mode the operation will fail. |
Notes
Note
Checkmode is supported.
Panorama 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.
Examples
# Create tunnel.1
- name: create tunnel.1
paloaltonetworks.panos.panos_tunnel:
provider: '{{ provider }}'
if_name: "tunnel.1"
ip: ["10.1.1.1/32"]
# Update tunnel comment.
- name: update tunnel.1 comment
paloaltonetworks.panos.panos_tunnel:
provider: '{{ provider }}'
if_name: "tunnel.1"
ip: ["10.1.1.1/32"]
comment: "tunnel interface"