cisco.dnac.sda_fabric_control_plane_device module – Resource module for Sda Fabric Control Plane Device
Note
This module is part of the cisco.dnac collection (version 6.5.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 cisco.dnac
.
To use it in a playbook, specify: cisco.dnac.sda_fabric_control_plane_device
.
New in version 3.1.0: of cisco.dnac
Synopsis
Manage operations create and delete of the resource Sda Fabric Control Plane Device.
Add control plane device in SDA Fabric.
Delete control plane device in SDA Fabric.
Note
This module has a corresponding action plugin.
Requirements
The below requirements are needed on the host that executes this module.
dnacentersdk >= 2.5.0
python >= 3.5
Parameters
Parameter |
Comments |
---|---|
DeviceManagementIpAddress query parameter. |
|
Flag for Cisco DNA Center SDK to enable debugging. Choices:
|
|
The Cisco DNA Center hostname. |
|
The Cisco DNA Center password to authenticate. |
|
The Cisco DNA Center port. Default: 443 |
|
The Cisco DNA Center username to authenticate. Default: “admin” |
|
Flag to enable or disable SSL certificate verification. Choices:
|
|
Informs the SDK which version of Cisco DNA Center to use. Default: “2.3.3.0” |
|
Sda Fabric Control Plane Device’s payload. |
|
Management Ip Address of the Device which is provisioned successfully. |
|
SiteNameHierarchy of the Provisioned Device(site should be part of Fabric Site(site should be part of Fabric Site). |
|
Flag for Cisco DNA Center SDK to enable the validation of request bodies against a JSON schema. Choices:
|
Notes
Note
SDK Method used are sda.Sda.add_control_plane_device, sda.Sda.delete_control_plane_device,
Paths used are post /dna/intent/api/v1/business/sda/control-plane-device, delete /dna/intent/api/v1/business/sda/control-plane-device,
Does not support
check_mode
The plugin runs on the control node and does not use any ansible connection plugins, but instead the embedded connection manager from Cisco DNAC SDK
The parameters starting with dnac_ are used by the Cisco DNAC Python SDK to establish the connection
See Also
See also
- Cisco DNA Center documentation for SDA AddControlPlaneDeviceInSDAFabric
Complete reference of the AddControlPlaneDeviceInSDAFabric API.
- Cisco DNA Center documentation for SDA DeleteControlPlaneDeviceInSDAFabric
Complete reference of the DeleteControlPlaneDeviceInSDAFabric API.
Examples
- name: Delete all
cisco.dnac.sda_fabric_control_plane_device:
dnac_host: "{{dnac_host}}"
dnac_username: "{{dnac_username}}"
dnac_password: "{{dnac_password}}"
dnac_verify: "{{dnac_verify}}"
dnac_port: "{{dnac_port}}"
dnac_version: "{{dnac_version}}"
dnac_debug: "{{dnac_debug}}"
state: absent
deviceManagementIpAddress: string
- name: Create
cisco.dnac.sda_fabric_control_plane_device:
dnac_host: "{{dnac_host}}"
dnac_username: "{{dnac_username}}"
dnac_password: "{{dnac_password}}"
dnac_verify: "{{dnac_verify}}"
dnac_port: "{{dnac_port}}"
dnac_version: "{{dnac_version}}"
dnac_debug: "{{dnac_debug}}"
state: present
payload:
- deviceManagementIpAddress: string
siteNameHierarchy: string
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
A dictionary or list with the response returned by the Cisco DNAC Python SDK Returned: always Sample: “{\n \”status\”: \”string\”,\n \”description\”: \”string\”,\n \”taskId\”: \”string\”,\n \”taskStatusUrl\”: \”string\”,\n \”executionStatusUrl\”: \”string\”,\n \”executionId\”: \”string\”\n}\n” |
Authors
Rafael Campos (@racampos)