fortinet.fortimanager.fmgr_firewall_address6_dynamicmapping – Configure IPv6 firewall addresses.

Note

This plugin is part of the fortinet.fortimanager collection (version 2.1.4).

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_address6_dynamicmapping.

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 Choices/Defaults Comments
address6
string / required
the parameter (address6) in requested url
adom
string / required
the parameter (adom) in requested url
bypass_validation
boolean
    Choices:
  • no ←
  • yes
only set to True when module schema diffs with FortiManager API structure, module continues to execute without validating parameters
enable_log
boolean
    Choices:
  • no ←
  • yes
Enable/Disable logging for task
firewall_address6_dynamicmapping
dictionary
the top level parameters set
_image-base64
string
_Image-Base64.
_scope
list / elements=string
no description
name
string
Name.
vdom
string
Vdom.
cache-ttl
integer
Minimal TTL of individual IPv6 addresses in FQDN cache.
color
integer
Integer value to determine the color of the icon in the GUI (range 1 to 32, default = 0, which sets the value to 1).
comment
string
Comment.
country
string
Country.
end-ip
string
Final IP address (inclusive) in the range for the address (format: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx).
end-mac
string
Last MAC address in the range.
fabric-object
string
    Choices:
  • disable
  • enable
Security Fabric global object setting.
fqdn
string
Fully qualified domain name.
global-object
integer
Global-Object.
host
string
Host Address.
host-type
string
    Choices:
  • any
  • specific
Host type.
ip6
string
IPv6 address prefix (format: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/xxx).
macaddr
string
no description
obj-id
string
Object ID for NSX.
sdn
string
    Choices:
  • nsx
SDN.
start-ip
string
First IP address (inclusive) in the range for the address (format: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx).
start-mac
string
First MAC address in the range.
subnet-segment
list / elements=string
no description
name
string
Name.
type
string
    Choices:
  • any
  • specific
Subnet segment type.
value
string
Subnet segment value.
tags
string
Tags.
template
string
IPv6 address template.
type
string
    Choices:
  • ipprefix
  • iprange
  • nsx
  • dynamic
  • fqdn
  • template
  • mac
  • geography
Type of IPv6 address object (default = ipprefix).
uuid
string
Universally Unique Identifier (UUID; automatically assigned but can be manually reset).
visibility
string
    Choices:
  • disable
  • enable
Enable/disable the visibility of the object in the GUI.
proposed_method
string
    Choices:
  • update
  • set
  • add
The overridden method for the underlying Json RPC request
rc_failed
list / elements=string
the rc codes list with which the conditions to fail will be overriden
rc_succeeded
list / elements=string
the rc codes list with which the conditions to succeed will be overriden
state
string / required
    Choices:
  • present
  • absent
the directive to create, update or delete an object
workspace_locking_adom
string
the adom to lock for FortiManager running in workspace mode, the value can be global and others including root
workspace_locking_timeout
integer
Default:
300
the maximum time in seconds to wait for other user to release the workspace lock

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: fortimanager00
  collections:
    - fortinet.fortimanager
  connection: httpapi
  vars:
     ansible_httpapi_use_ssl: True
     ansible_httpapi_validate_certs: False
     ansible_httpapi_port: 443
  tasks:
   - name: Configure dynamic mappings of IPv6 address
     fmgr_firewall_address6_dynamicmapping:
        bypass_validation: False
        adom: ansible
        address6: 'ansible-test' # name
        state: present
        firewall_address6_dynamicmapping:
           _scope:
             -
                 name: FGT_AWS # need a valid device name
                 vdom: root # need a valid vdom name under the device
           cache-ttl: 0
           color: 22
           comment: 'ansible-test-comment'
           end-ip: '::100'
           host: '::'
           host-type: any #<value in [any, specific]>
           ip6: '::/128'
           start-ip: '::'
           type: iprange #<value in [ipprefix, iprange, nsx, ...]>
           visibility: enable

- 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 dynamic mappings of IPv6 address
     fmgr_fact:
       facts:
           selector: 'firewall_address6_dynamicmapping'
           params:
               adom: 'ansible'
               address6: 'ansible-test' # name
               dynamic_mapping: ''

Return Values

Common return values are documented here, the following are the fields unique to this module:

Key Returned Description
request_url
string
always
The full url requested

Sample:
/sys/login/user
response_code
integer
always
The status of api request

response_message
string
always
The descriptive message of the api response

Sample:
OK.


Authors

  • Link Zheng (@chillancezen)

  • Jie Xue (@JieX19)

  • Frank Shen (@fshen01)

  • Hongbin Lu (@fgtdev-hblu)