fortinet.fortimanager.fmgr_firewall_ldbmonitor module – Configure server load balancing health monitors.

Note

This module is part of the fortinet.fortimanager collection (version 2.8.2).

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

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

access_token

string

The token to access FortiManager without using username and password.

adom

string / required

The parameter (adom) in requested url.

bypass_validation

boolean

Only set to True when module schema diffs with FortiManager API structure, module continues to execute without validating parameters.

Choices:

  • false ← (default)

  • true

enable_log

boolean

Enable/Disable logging for task.

Choices:

  • false ← (default)

  • true

firewall_ldbmonitor

dictionary

The top level parameters set.

dns_match_ip

aliases: dns-match-ip

string

Response IP expected from DNS server.

dns_protocol

aliases: dns-protocol

string

Select the protocol used by the DNS health check monitor to check the health of the server

Choices:

  • "udp"

  • "tcp"

dns_request_domain

aliases: dns-request-domain

string

Fully qualified domain name to resolve for the DNS probe.

http_get

aliases: http-get

string

URL used to send a GET request to check the health of an HTTP server.

http_match

aliases: http-match

string

String to match the value expected in response to an HTTP-GET request.

http_max_redirects

aliases: http-max-redirects

integer

The maximum number of HTTP redirects to be allowed

interval

integer

Time between health checks

name

string / required

Monitor name.

port

integer

Service port used to perform the health check.

retry

integer

Number health check attempts before the server is considered down

src_ip

aliases: src-ip

string

Source IP for ldb-monitor.

timeout

integer

Time to wait to receive response to a health check from a server.

type

string

Select the Monitor type used by the health check monitor to check the health of the server

Choices:

  • "ping"

  • "tcp"

  • "http"

  • "passive-sip"

  • "https"

  • "dns"

forticloud_access_token

string

Authenticate Ansible client with forticloud API access token.

proposed_method

string

The overridden method for the underlying Json RPC request.

Choices:

  • "update"

  • "set"

  • "add"

rc_failed

list / elements=integer

The rc codes list with which the conditions to fail will be overriden.

rc_succeeded

list / elements=integer

The rc codes list with which the conditions to succeed will be overriden.

state

string / required

The directive to create, update or delete an object.

Choices:

  • "present"

  • "absent"

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

The maximum time in seconds to wait for other user to release the workspace lock.

Default: 300

Notes

Note

  • Starting in version 2.4.0, all input arguments are named using the underscore naming convention (snake_case). Please change the arguments such as “var-name” to “var_name”. Old argument names are still available yet you will receive deprecation warnings. You can ignore this warning by setting deprecation_warnings=False in ansible.cfg.

  • 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
  hosts: fortimanagers
  connection: httpapi
  vars:
    ansible_httpapi_use_ssl: true
    ansible_httpapi_validate_certs: false
    ansible_httpapi_port: 443
  tasks:
    - name: Configure server load balancing health monitors.
      fortinet.fortimanager.fmgr_firewall_ldbmonitor:
        bypass_validation: false
        adom: ansible
        state: present
        firewall_ldbmonitor:
          name: "ansible-test"
          port: 1
          type: tcp # <value in [ping, tcp, http, ...]>

- name: Gathering fortimanager facts
  hosts: fortimanagers
  gather_facts: false
  connection: httpapi
  vars:
    ansible_httpapi_use_ssl: true
    ansible_httpapi_validate_certs: false
    ansible_httpapi_port: 443
  tasks:
    - name: Retrieve all the server load balancing health monitors
      fortinet.fortimanager.fmgr_fact:
        facts:
          selector: "firewall_ldbmonitor"
          params:
            adom: "ansible"
            ldb-monitor: "your_value"

Return Values

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

Key

Description

meta

dictionary

The result of the request.

Returned: always

request_url

string

The full url requested.

Returned: always

Sample: "/sys/login/user"

response_code

integer

The status of api request.

Returned: always

Sample: 0

response_data

list / elements=string

The api response.

Returned: always

response_message

string

The descriptive message of the api response.

Returned: always

Sample: "OK."

system_information

dictionary

The information of the target system.

Returned: always

rc

integer

The status the request.

Returned: always

Sample: 0

version_check_warning

list / elements=string

Warning if the parameters used in the playbook are not supported by the current FortiManager version.

Returned: complex

Authors

  • Xinwei Du (@dux-fortinet)

  • Xing Li (@lix-fortinet)

  • Jie Xue (@JieX19)

  • Link Zheng (@chillancezen)

  • Frank Shen (@fshen01)

  • Hongbin Lu (@fgtdev-hblu)