fortinet.fortimanager.fmgr_firewall_vip6 module – Configure virtual IP for IPv6.
Note
This module is part of the fortinet.fortimanager collection (version 2.2.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_firewall_vip6
.
New in fortinet.fortimanager 2.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:
|
|
the top level parameters set |
|
Enable/disable adding NAT64 route. Choices:
|
|
Enable to respond to ARP requests for this virtual IP address. Choices:
|
|
Color of icon on the GUI. |
|
Comment. |
|
Dynamic_Mapping. |
|
_Scope. |
|
Name. |
|
Vdom. |
|
Enable/disable adding NAT64 route. Choices:
|
|
Enable to respond to ARP requests for this virtual IP address. Choices:
|
|
Color of icon on the GUI. |
|
Comment. |
|
Enable/disable use of the lower 32 bits of the external IPv6 address as mapped IPv4 address. Choices:
|
|
IP address or address range on the external interface that you want to map to an address or address range on the destin… |
|
Incoming port number range that you want to map to a port number range on the destination network. |
|
Time in minutes that client web browsers should keep a cookie. |
|
Domain that HTTP cookie persistence should apply to. |
|
Enable/disable use of HTTP cookie domain from host field in HTTP. Choices:
|
|
Generation of HTTP cookie to be accepted. |
|
Limit HTTP cookie persistence to the specified path. |
|
Control sharing of cookies across virtual servers. Choices:
|
|
For HTTP multiplexing, enable to add the original client IP address in the XForwarded-For HTTP header. Choices:
|
|
For HTTP multiplexing, enter a custom HTTPS header name. |
|
Enable/disable HTTP multiplexing. Choices:
|
|
Enable/disable redirection of HTTP to HTTPS Choices:
|
|
Enable/disable verification that inserted HTTPS cookies are secure. Choices:
|
|
Custom defined ID. |
|
Range of mapped IP addresses. |
|
IPv4 port number range on the destination network to which the external port number range is mapped. |
|
Method used to distribute sessions to real servers. Choices:
|
|
Mapped IP address range in the format startIP-endIP. |
|
Port number range on the destination network to which the external port number range is mapped. |
|
Maximum number of incomplete connections. |
|
Name of the health check monitor to use when polling to determine a virtual servers connectivity status. |
|
Nat-Source-Vip. Choices:
|
|
Enable/disable DNAT64. Choices:
|
|
Enable/disable DNAT66. Choices:
|
|
Enable/disable this FortiGate units ability to respond to NDP requests for this virtual IP address Choices:
|
|
Enable to add the Front-End-Https header for Microsoft Outlook Web Access. Choices:
|
|
Configure how to make sure that clients connect to the same server every time they make a request that is part of the s… Choices:
|
|
Enable port forwarding. Choices:
|
|
Protocol to use when forwarding packets. Choices:
|
|
description |
|
Only clients in this IP range can connect to this real server. |
|
Enable to check the responsiveness of the real server before forwarding traffic. Choices:
|
|
Time in seconds that the health check monitor continues to monitor an unresponsive server that should be active. |
|
HTTP server domain name in HTTP header. |
|
Real server ID. |
|
IP address of the real server. |
|
Max number of active connections that can directed to the real server. |
|
description |
|
Port for communicating with the real server. |
|
Set the status of the real server to active so that it can accept traffic, or on standby or disabled so no traf… Choices:
|
|
Enable/disable translation of hostname/IP from virtual server to real server. Choices:
|
|
Weight of the real server. |
|
Protocol to be load balanced by the virtual server Choices:
|
|
Source IP6 filter |
|
Enable/disable FFDHE cipher suite for SSL key exchange. Choices:
|
|
Permitted encryption algorithms for SSL sessions according to encryption strength. Choices:
|
|
The name of the SSL certificate to use for SSL acceleration. |
|
description |
|
Cipher suite name. Choices:
|
|
SSL/TLS cipher suites priority. |
|
description Choices:
|
|
Enable/disable support for preventing Downgrade Attacks on client connections Choices:
|
|
Maximum length of data in MB before triggering a client rekey |
|
Allow, deny, or require secure renegotiation of client sessions to comply with RFC 5746. Choices:
|
|
Maximum number of client to FortiGate SSL session states to keep. |
|
Number of minutes to keep client to FortiGate SSL session state. |
|
How to expire SSL sessions for the segment of the SSL connection between the client and the FortiGate. Choices:
|
|
Number of bits to use in the Diffie-Hellman exchange for RSA encryption of SSL sessions. Choices:
|
|
Enable/disable including HPKP header in response. Choices:
|
|
Number of minutes the web browser should keep HPKP. |
|
Certificate to generate backup HPKP pin from. |
|
Indicate that HPKP header applies to all subdomains. Choices:
|
|
Certificate to generate primary HPKP pin from. |
|
URL to report HPKP violations to. |
|
Enable/disable including HSTS header in response. Choices:
|
|
Number of seconds the client should honour the HSTS setting. |
|
Indicate that HSTS header applies to all subdomains. Choices:
|
|
Enable to replace HTTP with HTTPS in the replys Location HTTP header field. Choices:
|
|
Enable/disable HTTP host matching for location conversion. Choices:
|
|
Highest SSL/TLS version acceptable from a client. Choices:
|
|
Lowest SSL/TLS version acceptable from a client. Choices:
|
|
Apply SSL offloading between the client and the FortiGate Choices:
|
|
Select the cipher suites that can be used for SSL perfect forward secrecy Choices:
|
|
Enable/disable sending empty fragments to avoid CBC IV attacks Choices:
|
|
Permitted encryption algorithms for the server side of SSL full mode sessions according to encryption strength. Choices:
|
|
Highest SSL/TLS version acceptable from a server. Choices:
|
|
Lowest SSL/TLS version acceptable from a server. Choices:
|
|
Enable/disable secure renegotiation to comply with RFC 5746. Choices:
|
|
Maximum number of FortiGate to Server SSL session states to keep. |
|
Number of minutes to keep FortiGate to Server SSL session state. |
|
How to expire SSL sessions for the segment of the SSL connection between the server and the FortiGate. Choices:
|
|
Configure a static NAT or server load balance VIP. Choices:
|
|
Universally Unique Identifier |
|
Enable to add an HTTP header to indicate SSL offloading for a WebLogic server. Choices:
|
|
Enable to add an HTTP header to indicate SSL offloading for a WebSphere server. Choices:
|
|
Enable/disable use of the lower 32 bits of the external IPv6 address as mapped IPv4 address. Choices:
|
|
IP address or address range on the external interface that you want to map to an address or address range on the destination ne… |
|
Incoming port number range that you want to map to a port number range on the destination network. |
|
Time in minutes that client web browsers should keep a cookie. |
|
Domain that HTTP cookie persistence should apply to. |
|
Enable/disable use of HTTP cookie domain from host field in HTTP. Choices:
|
|
Generation of HTTP cookie to be accepted. |
|
Limit HTTP cookie persistence to the specified path. |
|
Control sharing of cookies across virtual servers. Choices:
|
|
For HTTP multiplexing, enable to add the original client IP address in the XForwarded-For HTTP header. Choices:
|
|
For HTTP multiplexing, enter a custom HTTPS header name. |
|
Enable/disable HTTP multiplexing. Choices:
|
|
Enable/disable redirection of HTTP to HTTPS Choices:
|
|
Enable/disable verification that inserted HTTPS cookies are secure. Choices:
|
|
Custom defined ID. |
|
Range of mapped IP addresses. |
|
IPv4 port number range on the destination network to which the external port number range is mapped. |
|
Method used to distribute sessions to real servers. Choices:
|
|
Mapped IP address range in the format startIP-endIP. |
|
Port number range on the destination network to which the external port number range is mapped. |
|
Maximum number of incomplete connections. |
|
Name of the health check monitor to use when polling to determine a virtual servers connectivity status. |
|
Virtual ip6 name. |
|
Enable to perform SNAT on traffic from mappedip to the extip for all egress interfaces. Choices:
|
|
Enable/disable DNAT64. Choices:
|
|
Enable/disable DNAT66. Choices:
|
|
Enable/disable this FortiGate units ability to respond to NDP requests for this virtual IP address Choices:
|
|
Enable to add the Front-End-Https header for Microsoft Outlook Web Access. Choices:
|
|
Configure how to make sure that clients connect to the same server every time they make a request that is part of the same session. Choices:
|
|
Enable port forwarding. Choices:
|
|
Protocol to use when forwarding packets. Choices:
|
|
Realservers. |
|
Only clients in this IP range can connect to this real server. |
|
Enable to check the responsiveness of the real server before forwarding traffic. Choices:
|
|
Time in seconds that the health check monitor continues to monitor an unresponsive server that should be active. |
|
HTTP server domain name in HTTP header. |
|
Real server ID. |
|
IPv6 address of the real server. |
|
Max number of active connections that can directed to the real server. |
|
Name of the health check monitor to use when polling to determine a virtual servers connectivity status. |
|
Port for communicating with the real server. |
|
Set the status of the real server to active so that it can accept traffic, or on standby or disabled so no traffic is sent. Choices:
|
|
Enable/disable translation of hostname/IP from virtual server to real server. Choices:
|
|
Weight of the real server. |
|
Protocol to be load balanced by the virtual server Choices:
|
|
Source IP6 filter |
|
Enable/disable FFDHE cipher suite for SSL key exchange. Choices:
|
|
Permitted encryption algorithms for SSL sessions according to encryption strength. Choices:
|
|
The name of the SSL certificate to use for SSL acceleration. |
|
Ssl-Cipher-Suites. |
|
Cipher suite name. Choices:
|
|
SSL/TLS cipher suites priority. |
|
SSL/TLS versions that the cipher suite can be used with. Choices:
|
|
Enable/disable support for preventing Downgrade Attacks on client connections Choices:
|
|
Maximum length of data in MB before triggering a client rekey |
|
Allow, deny, or require secure renegotiation of client sessions to comply with RFC 5746. Choices:
|
|
Maximum number of client to FortiGate SSL session states to keep. |
|
Number of minutes to keep client to FortiGate SSL session state. |
|
How to expire SSL sessions for the segment of the SSL connection between the client and the FortiGate. Choices:
|
|
Number of bits to use in the Diffie-Hellman exchange for RSA encryption of SSL sessions. Choices:
|
|
Enable/disable including HPKP header in response. Choices:
|
|
Number of minutes the web browser should keep HPKP. |
|
Certificate to generate backup HPKP pin from. |
|
Indicate that HPKP header applies to all subdomains. Choices:
|
|
Certificate to generate primary HPKP pin from. |
|
URL to report HPKP violations to. |
|
Enable/disable including HSTS header in response. Choices:
|
|
Number of seconds the client should honour the HSTS setting. |
|
Indicate that HSTS header applies to all subdomains. Choices:
|
|
Enable to replace HTTP with HTTPS in the replys Location HTTP header field. Choices:
|
|
Enable/disable HTTP host matching for location conversion. Choices:
|
|
Highest SSL/TLS version acceptable from a client. Choices:
|
|
Lowest SSL/TLS version acceptable from a client. Choices:
|
|
Apply SSL offloading between the client and the FortiGate Choices:
|
|
Select the cipher suites that can be used for SSL perfect forward secrecy Choices:
|
|
Enable/disable sending empty fragments to avoid CBC IV attacks Choices:
|
|
Permitted encryption algorithms for the server side of SSL full mode sessions according to encryption strength. Choices:
|
|
Ssl-Server-Cipher-Suites. |
|
Cipher suite name. Choices:
|
|
SSL/TLS cipher suites priority. |
|
SSL/TLS versions that the cipher suite can be used with. Choices:
|
|
Highest SSL/TLS version acceptable from a server. Choices:
|
|
Lowest SSL/TLS version acceptable from a server. Choices:
|
|
Enable/disable secure renegotiation to comply with RFC 5746. Choices:
|
|
Maximum number of FortiGate to Server SSL session states to keep. |
|
Number of minutes to keep FortiGate to Server SSL session state. |
|
How to expire SSL sessions for the segment of the SSL connection between the server and the FortiGate. Choices:
|
|
Configure a static NAT VIP. Choices:
|
|
Universally Unique Identifier |
|
Enable to add an HTTP header to indicate SSL offloading for a WebLogic server. Choices:
|
|
Enable to add an HTTP header to indicate SSL offloading for a WebSphere server. 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 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
- 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 scripts
fmgr_fact:
facts:
selector: 'firewall_vip6'
params:
adom: 'ansible'
vip6: 'your_value'
- 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 virtual IP for IPv6.
fmgr_firewall_vip6:
bypass_validation: False
adom: ansible
state: present
firewall_vip6:
arp-reply: disable
color: 1
comment: 'ansible-comment'
id: 1
name: 'ansible-test-vip6'
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 |