fortinet.fortimanager.fmgr_wanopt_profile module – Configure WAN optimization profiles.
Note
This module is part of the fortinet.fortimanager collection (version 2.3.0).
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 fortinet.fortimanager
.
To use it in a playbook, specify: fortinet.fortimanager.fmgr_wanopt_profile
.
New in fortinet.fortimanager 1.0.0
Synopsis
This module is able to configure a FortiManager device.
Examples include all parameters and values which need to be adjusted to data sources before usage.
Parameters
Parameter |
Comments |
---|---|
The token to access FortiManager without using username and password. |
|
the parameter (adom) in requested url |
|
Only set to True when module schema diffs with FortiManager API structure, module continues to execute without validating parameters. Choices:
|
|
Enable/Disable logging for task. Choices:
|
|
Authenticate Ansible client with forticloud API access token. |
|
The overridden method for the underlying Json RPC request. Choices:
|
|
The rc codes list with which the conditions to fail will be overriden. |
|
The rc codes list with which the conditions to succeed will be overriden. |
|
The directive to create, update or delete an object. Choices:
|
|
the top level parameters set |
|
Optionally add an authentication group to restrict access to the WAN Optimization tunnel to peers in the authentication group. |
|
no description |
|
Enable/disable byte-caching. Choices:
|
|
Enable/disable logging. Choices:
|
|
(list) no description |
|
Select dynamic or fixed-size data chunking for WAN Optimization. Choices:
|
|
Select Protocol specific optimitation or generic TCP optimization. Choices:
|
|
Enable/disable securing the WAN Opt tunnel using SSL. Choices:
|
|
Enable/disable WAN Optimization. Choices:
|
|
Tunnel sharing mode for aggressive/non-aggressive and/or interactive/non-interactive protocols. Choices:
|
|
Comment. |
|
no description |
|
Enable/disable byte-caching. Choices:
|
|
Enable/disable logging. Choices:
|
|
(list) no description |
|
Select dynamic or fixed-size data chunking for WAN Optimization. Choices:
|
|
Select Protocol specific optimitation or generic TCP optimization. Choices:
|
|
Enable/disable securing the WAN Opt tunnel using SSL. Choices:
|
|
Enable/disable SSL/TLS offloading Choices:
|
|
Enable/disable WAN Optimization. Choices:
|
|
Tunnel sharing mode for aggressive/non-aggressive and/or interactive/non-interactive protocols. Choices:
|
|
no description |
|
Enable/disable byte-caching. Choices:
|
|
Enable/disable logging. Choices:
|
|
(list) no description |
|
Select dynamic or fixed-size data chunking for WAN Optimization. Choices:
|
|
Select Protocol specific optimitation or generic TCP optimization. Choices:
|
|
Enable/disable securing the WAN Opt tunnel using SSL. Choices:
|
|
Enable/disable SSL/TLS offloading Choices:
|
|
(list) no description |
|
Enable/disable WAN Optimization. Choices:
|
|
Configure how to process non-HTTP traffic when a profile configured for HTTP traffic accepts a non-HTTP session. Choices:
|
|
Tunnel sharing mode for aggressive/non-aggressive and/or interactive/non-interactive protocols. Choices:
|
|
How to handle HTTP sessions that do not comply with HTTP 0. Choices:
|
|
no description |
|
Enable/disable byte-caching. Choices:
|
|
Enable/disable logging. Choices:
|
|
(list) no description |
|
Enable/disable securing the WAN Opt tunnel using SSL. Choices:
|
|
Enable/disable WAN Optimization. Choices:
|
|
Tunnel sharing mode for aggressive/non-aggressive and/or interactive/non-interactive protocols. Choices:
|
|
Profile name. |
|
no description |
|
Enable/disable byte-caching. Choices:
|
|
Select whether TCP byte-caching uses system memory only or both memory and disk space. Choices:
|
|
Enable/disable logging. Choices:
|
|
Port numbers or port number ranges for TCP. |
|
Enable/disable securing the WAN Opt tunnel using SSL. Choices:
|
|
Enable/disable SSL/TLS offloading Choices:
|
|
(list) Port numbers or port number ranges on which to expect HTTPS traffic for SSL/TLS offloading. |
|
Enable/disable WAN Optimization. Choices:
|
|
Tunnel sharing mode for aggressive/non-aggressive and/or interactive/non-interactive protocols. Choices:
|
|
Enable/disable transparent mode. Choices:
|
|
The adom to lock for FortiManager running in workspace mode, the value can be global and others including root. |
|
The maximum time in seconds to wait for other user to release the workspace lock. Default: |
Notes
Note
Running in workspace locking mode is supported in this FortiManager module, the top level parameters workspace_locking_adom and workspace_locking_timeout help do the work.
To create or update an object, use state present directive.
To delete an object, use state absent directive.
Normally, running one module can fail when a non-zero rc is returned. you can also override the conditions to fail or succeed with parameters rc_failed and rc_succeeded
Examples
- hosts: fortimanager-inventory
collections:
- fortinet.fortimanager
connection: httpapi
vars:
ansible_httpapi_use_ssl: True
ansible_httpapi_validate_certs: False
ansible_httpapi_port: 443
tasks:
- name: Configure WAN optimization profiles.
fmgr_wanopt_profile:
bypass_validation: False
workspace_locking_adom: <value in [global, custom adom including root]>
workspace_locking_timeout: 300
rc_succeeded: [0, -2, -3, ...]
rc_failed: [-2, -3, ...]
adom: <your own value>
state: <value in [present, absent]>
wanopt_profile:
auth-group: <string>
comments: <string>
name: <string>
transparent: <value in [disable, enable]>
cifs:
byte-caching: <value in [disable, enable]>
log-traffic: <value in [disable, enable]>
prefer-chunking: <value in [dynamic, fix]>
protocol-opt: <value in [protocol, tcp]>
secure-tunnel: <value in [disable, enable]>
status: <value in [disable, enable]>
tunnel-sharing: <value in [private, shared, express-shared]>
port: <list or integer>
ftp:
byte-caching: <value in [disable, enable]>
log-traffic: <value in [disable, enable]>
prefer-chunking: <value in [dynamic, fix]>
protocol-opt: <value in [protocol, tcp]>
secure-tunnel: <value in [disable, enable]>
ssl: <value in [disable, enable]>
status: <value in [disable, enable]>
tunnel-sharing: <value in [private, shared, express-shared]>
port: <list or integer>
http:
byte-caching: <value in [disable, enable]>
log-traffic: <value in [disable, enable]>
prefer-chunking: <value in [dynamic, fix]>
protocol-opt: <value in [protocol, tcp]>
secure-tunnel: <value in [disable, enable]>
ssl: <value in [disable, enable]>
status: <value in [disable, enable]>
tunnel-sharing: <value in [private, shared, express-shared]>
tunnel-non-http: <value in [disable, enable]>
unknown-http-version: <value in [best-effort, reject, tunnel]>
port: <list or integer>
ssl-port: <list or integer>
mapi:
byte-caching: <value in [disable, enable]>
log-traffic: <value in [disable, enable]>
secure-tunnel: <value in [disable, enable]>
status: <value in [disable, enable]>
tunnel-sharing: <value in [private, shared, express-shared]>
port: <list or integer>
tcp:
byte-caching: <value in [disable, enable]>
byte-caching-opt: <value in [mem-only, mem-disk]>
log-traffic: <value in [disable, enable]>
port: <string>
secure-tunnel: <value in [disable, enable]>
ssl: <value in [disable, enable]>
ssl-port: <list or integer>
status: <value in [disable, enable]>
tunnel-sharing: <value in [private, shared, express-shared]>
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The result of the request. Returned: always |
|
The full url requested. Returned: always Sample: |
|
The status of api request. Returned: always Sample: |
|
The api response. Returned: always |
|
The descriptive message of the api response. Returned: always Sample: |
|
The information of the target system. Returned: always |
|
The status the request. Returned: always Sample: |
|
Warning if the parameters used in the playbook are not supported by the current FortiManager version. Returned: complex |