fmgd_system_wireless_settings – Wireless radio configuration.

Added in version 1.0.0.

Synopsis

  • This module is able to configure a FortiManager device.

  • Examples include all parameters and values need to be adjusted to data sources before usage.

  • Tested with FortiManager v7.x.

Requirements

The below requirements are needed on the host that executes this module.

  • ansible-core>=2.16.0

FortiManager Version Compatibility

Supported Version Ranges: v7.2.6 -> v7.2.12, v7.4.3 -> latest

Parameters

  • access_token -The token to access FortiManager without using username and password. type: str required: false
  • bypass_validation - Only set to True when module schema diffs with FortiManager API structure, module continues to execute without validating parameters. type: bool required: false default: False
  • enable_log - Enable/Disable logging for task. type: bool required: false default: False
  • forticloud_access_token - Access token of forticloud managed API users, this option is available with FortiManager later than 6.4.0. type: str required: false
  • proposed_method - The overridden method for the underlying Json RPC request. type: str required: false choices: set, update, add
  • rc_succeeded - The rc codes list with which the conditions to succeed will be overriden. type: list required: false
  • rc_failed - The rc codes list with which the conditions to fail will be overriden. type: list required: false
  • workspace_locking_adom - Acquire the workspace lock if FortiManager is running in workspace mode. type: str required: false choices: global, custom adom including root
  • workspace_locking_timeout - The maximum time in seconds to wait for other users to release workspace lock. type: integer required: false default: 300
  • device - The parameter in requested url type: str required: true
  • system_wireless_settings - Wireless radio configuration. type: dict
    • band Band. type: str choices: [802.11b, 802.11a, 802.11g, 802.11n, 802.11ac, 802.11n-5G, 802.11g-only, 802.11n-only, 802.11ng-only, 802.11ac-only, 802.11acn-only, 802.11n-5G-only] more...
    • beacon_interval (Alias name: beacon-interval) Beacon level (25 - 1000). type: int more...
    • bgscan Enable/disable background rogue ap scan. type: str choices: [disable, enable] more...
    • bgscan_idle (Alias name: bgscan-idle) Interval between scanning channels (100 - 1000 ms). type: int more...
    • bgscan_interval (Alias name: bgscan-interval) Interval between two rounds of scanning (15 - 3600 sec). type: int more...
    • channel Channel. type: int more...
    • channel_bonding (Alias name: channel-bonding) Supported channel width. type: str choices: [disable, enable] more...
    • geography Geography. type: str choices: [World, Americas, EMEA, Israel, Japan] more...
    • mode Mode. type: str choices: [AP, CLIENT, SCAN] more...
    • power_level (Alias name: power-level) Power level (0 - 17). type: int more...
    • rogue_scan (Alias name: rogue-scan) Enable/disable rogue scan. type: str choices: [disable, enable] more...
    • rogue_scan_mac_adjacency (Alias name: rogue-scan-mac-adjacency) Mac adjacency (0-31). type: int more...
    • short_guard_interval (Alias name: short-guard-interval) Enable/disable short guard interval. type: str choices: [disable, enable] more...

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: Example playbook (generated based on argument schema)
  hosts: fortimanagers
  connection: httpapi
  gather_facts: false
  vars:
    ansible_httpapi_use_ssl: true
    ansible_httpapi_validate_certs: false
    ansible_httpapi_port: 443
  tasks:
    - name: Wireless radio configuration.
      fortinet.fmgdevice.fmgd_system_wireless_settings:
        # bypass_validation: false
        # workspace_locking_adom: <global or your adom name>
        # workspace_locking_timeout: 300
        # rc_succeeded: [0, -2, -3, ...]
        # rc_failed: [-2, -3, ...]
        device: <your own value>
        system_wireless_settings:
          # band: <value in [802.11b, 802.11a, 802.11g, ...]>
          # beacon_interval: <integer>
          # bgscan: <value in [disable, enable]>
          # bgscan_idle: <integer>
          # bgscan_interval: <integer>
          # channel: <integer>
          # channel_bonding: <value in [disable, enable]>
          # geography: <value in [World, Americas, EMEA, ...]>
          # mode: <value in [AP, CLIENT, SCAN]>
          # power_level: <integer>
          # rogue_scan: <value in [disable, enable]>
          # rogue_scan_mac_adjacency: <integer>
          # short_guard_interval: <value in [disable, enable]>

Return Values

Common return values are documented: https://docs.ansible.com/ansible/latest/reference_appendices/common_return_values.html#common-return-values, the following are the fields unique to this module:

  • meta - The result of the request.returned: always type: dict
    • request_url - The full url requested. returned: always type: str sample: /sys/login/user
    • response_code - The status of api request. returned: always type: int sample: 0
    • response_data - The data body of the api response. returned: optional type: list or dict
    • response_message - The descriptive message of the api response. returned: always type: str sample: OK
    • system_information - The information of the target system. returned: always type: dict
  • rc - The status the request. returned: always type: int sample: 0
  • version_check_warning - Warning if the parameters used in the playbook are not supported by the current FortiManager version. returned: if at least one parameter not supported by the current FortiManager version type: list

Status

  • This module is not guaranteed to have a backwards compatible interface.

Authors

  • Xinwei Du (@dux-fortinet)

  • Xing Li (@lix-fortinet)

  • Jie Xue (@JieX19)

  • Link Zheng (@chillancezen)

  • Frank Shen (@fshen01)

  • Hongbin Lu (@fgtdev-hblu)