fortinet.fortimanager.fmgr_dvmdb_device – Device table, most attributes are read-only and can only be changed internally.
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_dvmdb_device
.
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:
|
|
the parameter (device) in requested url |
|
the top level parameters set |
|
no description |
|
Adm_Usr. |
|
App_Ver. |
|
Av_Ver. |
|
Beta. |
|
Branch_Pt. |
|
Build. |
|
Checksum. |
|
Conf_Status. Choices:
|
|
Conn_Mode. Choices:
|
|
Conn_Status. Choices:
|
|
Db_Status. Choices:
|
|
Desc. |
|
Dev_Status. Choices:
|
|
Fap_Cnt. |
|
Faz.Full_Act. |
|
Faz.Perm. |
|
Faz.Quota. |
|
Faz.Used. |
|
Fex_Cnt. |
|
no description Choices:
|
|
VM Meter vCPU count. |
|
VM Meter DR Site status. Choices:
|
|
VM Meter first deployment time (in UNIX timestamp). |
|
VM Meter last synchronized time (in UNIX timestamp). |
|
VM Meter device RAM size (in MB). |
|
VM Meter license type. Choices:
|
|
no description Choices:
|
|
Fsw_Cnt. |
|
Ha_Group_Id. |
|
Ha_Group_Name. |
|
enabled - Value reserved for non-FOS HA devices. Choices:
|
|
Hdisk_Size. |
|
Hostname. |
|
Hw_Rev_Major. |
|
Hw_Rev_Minor. |
|
Hyperscale. |
|
Ip. |
|
Ips_Ext. |
|
Ips_Ver. |
|
Last_Checked. |
|
Last_Resync. |
|
Latitude. |
|
Lic_Flags. |
|
Lic_Region. |
|
Location_From. |
|
Logdisk_Size. |
|
Longitude. |
|
Maxvdom. Default: 10 |
|
no description |
|
Mgmt_Id. |
|
Mgmt_If. |
|
Mgmt_Mode. Choices:
|
|
Mgt_Vdom. |
|
Module_Sn. |
|
Mr. Default: -1 |
|
Unique name for the device. |
|
Nsxt_Service_Name. |
|
Os_Type. Choices:
|
|
Os_Ver. Choices:
|
|
Patch. |
|
Platform_Str. |
|
Prefer_Img_Ver. |
|
Prio. |
|
Private_Key. |
|
Private_Key_Status. |
|
Psk. |
|
Role. Choices:
|
|
Unique value for each device. |
|
no description |
|
Comments. |
|
no description |
|
Name. |
|
Opmode. Choices:
|
|
Rtm_Prof_Id. |
|
Status. |
|
Vpn_Id. |
|
Version. |
|
Vm_Cpu. |
|
Vm_Cpu_Limit. |
|
Vm_Lic_Expire. |
|
Vm_Mem. |
|
Vm_Mem_Limit. |
|
Vm_Status. |
|
Enable/Disable logging for task Choices:
|
|
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: Delete first FOS devices from FMG In a specific adom
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
device_adom: 'root'
tasks:
- name: fetch all devices
fmgr_fact:
facts:
selector: 'dvmdb_device'
params:
adom: '{{ device_adom }}'
device: ''
register: alldevices
- when: alldevices.meta.response_data != []
debug:
msg:
- 'We are going to delete device: {{ alldevices.meta.response_data[0].name }}'
- 'IP of the device is: {{ alldevices.meta.response_data[0].ip }}'
- when: alldevices.meta.response_data != [] and False
name: Create The Task To Delete The Device
fmgr_dvm_cmd_del_device:
dvm_cmd_del_device:
device: '{{ alldevices.meta.response_data[0].name }}'
adom: '{{ device_adom }}'
flags:
- 'create_task'
- 'nonblocking'
register: uninstalling_task
- when: alldevices.meta.response_data != [] and False
name: poll the task
fmgr_fact:
facts:
selector: 'task_task'
params:
task: '{{uninstalling_task.meta.response_data.taskid}}'
register: taskinfo
until: taskinfo.meta.response_data.percent == 100
retries: 30
delay: 5
failed_when: taskinfo.meta.response_data.state == 'error'
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)