fortinet.fortimanager.fmgr_pkg_firewall_shapingpolicy module – Configure shaping policies.
Note
This module is part of the fortinet.fortimanager collection (version 2.1.5).
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_pkg_firewall_shapingpolicy
.
New in version 2.10: of fortinet.fortimanager
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 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:
|
|
the parameter (pkg) in requested url |
|
the top level parameters set |
|
IDs of one or more application categories that this shaper applies application control traffic shaping to. |
|
One or more application group names. |
|
IDs of one or more applications that this shaper applies application control traffic shaping to. |
|
Traffic class ID. |
|
Comments. |
|
Enable to change packets DiffServ values to the specified diffservcode-forward value. Choices:
|
|
Enable to change packets reverse (reply) DiffServ values to the specified diffservcode-rev value. Choices:
|
|
Change packets DiffServ to this value. |
|
Change packets reverse (reply) DiffServ to this value. |
|
IPv4 destination address and address group names. |
|
IPv6 destination address and address group names. |
|
One or more outgoing (egress) interfaces. |
|
Apply this traffic shaping policy to user groups that have authenticated with the FortiGate. |
|
Shaping policy ID. |
|
Enable/disable use of Internet Services for this policy. If enabled, destination address and service are not used. Choices:
|
|
Custom Internet Service name. |
|
Custom Internet Service group name. |
|
Internet Service group name. |
|
Internet Service ID. |
|
Internet Service ID. |
|
Enable/disable use of Internet Services in source for this policy. If enabled, source address is not used. Choices:
|
|
Custom Internet Service source name. |
|
Custom Internet Service source group name. |
|
Internet Service source group name. |
|
Internet Service source ID. |
|
Internet Service source name. |
|
Apply this traffic shaping policy to IPv4 or IPv6 traffic. Choices:
|
|
Shaping policy name. |
|
Per-IP traffic shaper to apply with this policy. |
|
Schedule name. |
|
Service and service group names. |
|
IPv4 source address and address group names. |
|
IPv6 source address and address group names. |
|
One or more incoming (ingress) interfaces. |
|
Enable/disable this traffic shaping policy. Choices:
|
|
ToS (Type of Service) value used for comparison. |
|
Non-zero bit positions are used for comparison while zero bit positions are ignored. |
|
Enable negated TOS match. Choices:
|
|
Traffic shaper to apply to traffic forwarded by the firewall policy. |
|
Traffic shaper to apply to response traffic received by the firewall policy. |
|
IDs of one or more FortiGuard Web Filtering categories that this shaper applies traffic shaping to. |
|
Apply this traffic shaping policy to individual users that have authenticated with the FortiGate. |
|
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 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: 300 |
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
- name: gathering fortimanager facts
hosts: fortimanager00
gather_facts: no
connection: httpapi
collections:
- fortinet.fortimanager
vars:
ansible_httpapi_use_ssl: True
ansible_httpapi_validate_certs: False
ansible_httpapi_port: 443
tasks:
- name: retrieve all the shaping policies
fmgr_fact:
facts:
selector: 'pkg_firewall_shapingpolicy'
params:
adom: 'ansible'
pkg: 'ansible' # package name
shaping-policy: ''
- hosts: fortimanager00
collections:
- fortinet.fortimanager
connection: httpapi
vars:
ansible_httpapi_use_ssl: True
ansible_httpapi_validate_certs: False
ansible_httpapi_port: 443
tasks:
- name: Configure shaping policies.
fmgr_pkg_firewall_shapingpolicy:
bypass_validation: False
adom: ansible
pkg: ansible # package name
state: present
pkg_firewall_shapingpolicy:
dstaddr: all
dstintf: any
id: 1
ip-version: 4 #<value in [4, 6]>
schedule: always
service: ALL
srcaddr: all
status: disable
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The full url requested Returned: always Sample: “/sys/login/user” |
|
The status of api request Returned: always Sample: 0 |
|
The descriptive message of the api response Returned: always Sample: “OK.” |
Authors
Link Zheng (@chillancezen)
Jie Xue (@JieX19)
Frank Shen (@fshen01)
Hongbin Lu (@fgtdev-hblu)