cisco.dnac.inventory_intent module – Resource module for Network Device
Note
This module is part of the cisco.dnac collection (version 6.13.3).
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.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: cisco.dnac.inventory_intent.
New in cisco.dnac 6.8.0
Synopsis
Manage operations create, update and delete of the resource Network Device.
Adds the device with given credential.
Deletes the network device for the given Id.
Sync the devices provided as input.
Requirements
The below requirements are needed on the host that executes this module.
dnacentersdk >= 2.6.0
python >= 3.9
Parameters
Parameter |
Comments |
|---|---|
List of devices with credentails to perform Add/Update/Delete/Resync operation |
|
This operation will take dictionary as a parameter and in this we give details to create/update/delete/assign multiple UDF to a device. |
|
Info about the global user defined field. Also used while updating interface details. |
|
Name of Global User Defined Field. Required for creating/deleting UDF and then assigning it to device. |
|
Value to assign to tag with or without the same user defined field name. |
|
Required if need to delete the Provisioned device by clearing current configuration. Choices:
|
|
The essential prerequisite for adding Network devices is the specification of the transport protocol (either SSH or Telnet) used by the device. |
|
Indicates whether a device is a compute device. Choices:
|
|
Make this as true needed for the updation of device credentials and other device details. Choices:
|
|
Make this as true needed for the resyncing of device. Choices:
|
|
Password required for enabling configurations on the device. |
|
This operation take dictionary as parameter and export the device details as well as device credentials details in a csv file. |
|
enum(CREDENTIALDETAILS, DEVICEDETAILS) 0 to export Device Credential Details Or 1 to export Device Details. CREDENTIALDETAILS - Used for exporting device credentials details like snpm credntials, device crdentails etc. DEVICEDETAILS - Used for exporting device specific details like device hostname, serial number, type, family etc. |
|
List of device parameters that needs to be exported to file.(For example, [“componentName”, “SerialNumber”, “Last Sync Status”]) |
|
Specifies the password for the encryption of file while exporting the device credentails into the file. |
|
Indicates the exact location where the wired device will be provisioned. This is a string value that should represent the complete hierarchical path of the site (For example, “Global/USA/San Francisco/BGL_18/floor_pnp”). |
|
Additional discovery information for the device. |
|
If forcesync is true then device sync would run in high priority thread if available, else the sync will fail. Choices:
|
|
A list of hostnames representing devices. Operations such as updating, deleting, resyncing, or rebooting can be performed as alternatives to using IP addresses. |
|
HTTP password required for adding compute, Meraki, and Firepower Management Devices. |
|
HTTP port number required for adding compute and Firepower Management Devices. |
|
Flag indicating HTTP security. Choices:
|
|
HTTP username required for adding compute and Firepower Management Devices. |
|
A list of the IP addresses for the devices. It is required for tasks such as adding, updating, deleting, or resyncing devices, with Meraki devices being the exception. |
|
A list of MAC addresses representing devices. Operations such as updating, deleting, resyncing, or rebooting can be performed as alternatives to using IP addresses. |
|
Specifies the port number for connecting to devices using the Netconf protocol. Netconf (Network Configuration Protocol) is used for managing network devices. Ensure that the provided port number corresponds to the Netconf service port configured on your network devices. NETCONF with user privilege 15 is mandatory for enabling Wireless Services on Wireless capable devices such as Catalyst 9000 series Switches and C9800 Series Wireless Controllers. The NETCONF credentials are required to connect to C9800 Series Wireless Controllers as the majority of data collection is done using NETCONF for these Devices. |
|
Password for accessing the device and for file encryption during device export. Required for adding Network Device. Also needed for file encryption while exporting device in a csv file. |
|
This parameter takes a list of dictionaries. Each dictionary provides the IP address of a wired device and the name of the site where the device will be provisioned. |
|
Specifies the IP address of the wired device. This is a string value that should be in the format of standard IPv4 or IPv6 addresses. |
|
Determines the total number of retry attempts for checking if the device has reached a managed state during the provisioning process. If unspecified, the default value is set to 200 retries. Default: |
|
Sets the interval, in seconds, at which the system will recheck the device status throughout the provisioning process. If unspecified, the system will check the device status every 2 seconds by default. Default: |
|
Indicates the exact location where the wired device will be provisioned. This is a string value that should represent the complete hierarchical path of the site (For example, “Global/USA/San Francisco/BGL_18/floor_pnp”). |
|
Make this as true needed for the Rebooting of Access Points. Choices:
|
|
Role of device which can be ACCESS, CORE, DISTRIBUTION, BORDER ROUTER, UNKNOWN. ALL - This role typically represents all devices within the network, regardless of their specific roles or functions. UNKNOWN - This role is assigned to devices whose roles or functions have not been identified or classified within Cisco Catalsyt Center. This could happen if the platform is unable to determine the device’s role based on available information. ACCESS - This role typically represents switches or access points that serve as access points for end-user devices to connect to the network. These devices are often located at the edge of the network and provide connectivity to end-user devices. BORDER ROUTER - These are devices that connect different network domains or segments together. They often serve as gateways between different networks, such as connecting an enterprise network to the internet or connecting multiple branch offices. DISTRIBUTION - This role represents function as distribution switches or routers in hierarchical network designs. They aggregate traffic from access switches and route it toward the core of the network or toward other distribution switches. CORE - This role typically represents high-capacity switches or routers that form the backbone of the network. They handle large volumes of traffic and provide connectivity between different parts of network, such as connecting distribution switches or providing interconnection between different network segments. |
|
A list of serial numbers representing devices. Operations such as updating, deleting, resyncing, or rebooting can be performed as alternatives to using IP addresses. |
|
SNMP authentication passphrase required for adding network, compute, and third-party devices. |
|
SNMP authentication protocol. SHA (Secure Hash Algorithm) - cryptographic hash function commonly used for data integrity verification and authentication purposes. Default: |
|
Device’s snmp Mode refer to different SNMP (Simple Network Management Protocol) versions and their corresponding security levels. NOAUTHNOPRIV - This mode provides no authentication or encryption for SNMP messages. It means that devices communicating using SNMPv1 do not require any authentication (username/password) or encryption (data confidentiality). This makes it the least secure option. AUTHNOPRIV - This mode provides authentication but no encryption for SNMP messages. Authentication involves validating the source of the SNMP messages using a community string (similar to a password). However, the data transmitted between devices is not encrypted, so it’s susceptible to eavesdropping. AUTHPRIV - This mode provides both authentication and encryption for SNMP messages. It offers the highest level of security among the three options. Authentication ensures that the source of the messages is genuine, and encryption ensures that the data exchanged between devices is confidential and cannot be intercepted by unauthorized parties. |
|
SNMP private passphrase required for adding network, compute, and third-party devices. |
|
SNMP private protocol required for adding network, compute, and third-party devices. |
|
SNMP retry count. Default: |
|
SNMP Read-Only community required for adding V2C devices. |
|
SNMP Read-Write community required for adding V2C devices. |
|
SNMP timeout duration. Default: |
|
SNMP username required for adding network, compute, and third-party devices. |
|
It is a standard protocol used for managing and monitoring network devices. v2 - In this communication between the SNMP manager (such as Cisco Catalyst) and the managed devices (such as routers, switches, or access points) is based on community strings.Community strings serve as form of authentication and they are transmitted in clear text, providing no encryption. v3 - It is the most secure version of SNMP, providing authentication, integrity, and encryption features. It allows for the use of usernames, authentication passwords, and encryption keys, providing stronger security compared to v2. |
|
Select Device’s type from NETWORK_DEVICE, COMPUTE_DEVICE, MERAKI_DASHBOARD, THIRD_PARTY_DEVICE, FIREPOWER_MANAGEMENT_SYSTEM. NETWORK_DEVICE - This refers to traditional networking equipment such as routers, switches, access points, and firewalls. These devices are responsible for routing, switching, and providing connectivity within the network. COMPUTE_DEVICE - These are computing resources such as servers, virtual machines, or containers that are part of the network infrastructure. Cisco Catalyst Center can integrate with compute devices to provide visibility and management capabilities, ensuring that the network and compute resources work together seamlessly to support applications and services. MERAKI_DASHBOARD - It is cloud-based platform used to manage Meraki networking devices, including wireless access points, switches, security appliances, and cameras. THIRD_PARTY_DEVICE - This category encompasses devices from vendors other than Cisco or Meraki. Cisco Catalyst Center is designed to support integration with third-party devices through open standards and APIs. This allows organizations to manage heterogeneous network environments efficiently using Cisco Catalyst Center’s centralized management and automation capabilities. FIREPOWER_MANAGEMENT_SYSTEM - It is a centralized management console used to manage Cisco’s Firepower Next-Generation Firewall (NGFW) devices. It provides features such as policy management, threat detection, and advanced security analytics. Default: |
|
This operation will take dictionary as a parameter and in this we give details to update interface details of device. |
|
Status of Interface of a device, it can be (UP/DOWN). |
|
Set this to true if you need to clear the MAC address table for a specific device’s interface. It’s a boolean type, with a default value of False. Choices:
|
|
Preview/Deploy [Preview means the configuration is not pushed to the device. Deploy makes the configuration pushed to the device] Default: |
|
Specifies the description of the interface of the device. |
|
Specify the list of interface names to update the details of the device interface. (For example, GigabitEthernet1/0/11, FortyGigabitEthernet1/1/2) |
|
Unique Id number assigned to a VLAN within a network used only while updating interface details. |
|
Identifier used to distinguish a specific VLAN that is dedicated to voice traffic used only while updating interface details. |
|
List of updated management IP addresses for network devices. |
|
Device’s existing Mgmt IpAddress. |
|
Device’s new Mgmt IpAddress. |
|
Username for accessing the device. Required for Adding Network Device. |
|
Set to True to verify the Cisco Catalyst Center config after applying the playbook config. Choices:
|
|
Defines the timeout in seconds for API calls to retrieve task details. If the task details are not received within this period, the process will end, and a timeout notification will be logged. Default: |
|
Flag for Cisco DNA Center SDK to enable debugging. Choices:
|
|
The Cisco DNA Center hostname. |
|
Flag to enable/disable playbook execution logging. When true and dnac_log_file_path is provided, - Create the log file at the execution location with the specified name. When true and dnac_log_file_path is not provided, - Create the log file at the execution location with the name ‘dnac.log’. When false, - Logging is disabled. If the log file doesn’t exist, - It is created in append or write mode based on the “dnac_log_append” flag. If the log file exists, - It is overwritten or appended based on the “dnac_log_append” flag. Choices:
|
|
Determines the mode of the file. Set to True for ‘append’ mode. Set to False for ‘write’ mode. Choices:
|
|
Governs logging. Logs are recorded if dnac_log is True. If path is not specified, - When ‘dnac_log_append’ is True, ‘dnac.log’ is generated in the current Ansible directory; logs are appended. - When ‘dnac_log_append’ is False, ‘dnac.log’ is generated; logs are overwritten. If path is specified, - When ‘dnac_log_append’ is True, the file opens in append mode. - When ‘dnac_log_append’ is False, the file opens in write (w) mode. - In shared file scenarios, without append mode, content is overwritten after each module execution. - For a shared log file, set append to False for the 1st module (to overwrite); for subsequent modules, set append to True. Default: |
|
Sets the threshold for log level. Messages with a level equal to or higher than this will be logged. Levels are listed in order of severity [CRITICAL, ERROR, WARNING, INFO, DEBUG]. CRITICAL indicates serious errors halting the program. Displays only CRITICAL messages. ERROR indicates problems preventing a function. Displays ERROR and CRITICAL messages. WARNING indicates potential future issues. Displays WARNING, ERROR, CRITICAL messages. INFO tracks normal operation. Displays INFO, WARNING, ERROR, CRITICAL messages. DEBUG provides detailed diagnostic info. Displays all log messages. Default: |
|
The Cisco DNA Center password to authenticate. |
|
The Cisco DNA Center port. Default: |
|
Specifies the interval in seconds between successive calls to the API to retrieve task details. Default: |
|
The Cisco DNA Center username to authenticate. Default: |
|
Flag to enable or disable SSL certificate verification. Choices:
|
|
Informs the SDK which version of Cisco DNA Center to use. Default: |
|
The state of Cisco Catalyst Center after module completion. Choices:
|
|
Flag for Cisco DNA Center SDK to enable the validation of request bodies against a JSON schema. Choices:
|
Notes
Note
SDK Method used are devices.Devices.add_device, devices.Devices.delete_device_by_id, devices.Devices.sync_devices,
Paths used are post /dna/intent/api/v1/network-device, delete /dna/intent/api/v1/network-device/{id}, put /dna/intent/api/v1/network-device,
Removed ‘managementIpAddress’ options in v4.3.0.
Renamed argument ‘ip_address’ to ‘ip_address_list’ option in v6.12.0.
Removed ‘serial_number’, ‘device_added’, ‘role_source’, options in v6.12.0.
Added ‘add_user_defined_field’, ‘update_interface_details’, ‘export_device_list’ options in v6.13.1.
Removed ‘provision_wireless_device’, ‘reprovision_wired_device’ options in v6.13.1.
Added the parameter ‘admin_status’ options in v6.13.1.
Removed ‘device_updated’ options in v6.13.1.
Does not support
check_modeThe 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 Catalyst Center documentation for Devices AddDevice2
Complete reference of the AddDevice2 API.
- Cisco Catalyst Center documentation for Devices DeleteDeviceById
Complete reference of the DeleteDeviceById API.
- Cisco Catalyst Center documentation for Devices SyncDevices2
Complete reference of the SyncDevices2 API.
Examples
- name: Add new device in Inventory with full credentials
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- cli_transport: ssh
compute_device: False
password: Test@123
enable_password: Test@1234
extended_discovery_info: test
http_username: "testuser"
http_password: "test"
http_port: "443"
http_secure: False
ip_address_list: ["1.1.1.1", "2.2.2.2"]
netconf_port: 830
snmp_auth_passphrase: "Lablab@12"
snmp_auth_protocol: SHA
snmp_mode: AUTHPRIV
snmp_priv_passphrase: "Lablab@123"
snmp_priv_protocol: AES256
snmp_retry: 3
snmp_timeout: 5
snmp_username: v3Public
snmp_version: v3
type: NETWORK_DEVICE
username: cisco
- name: Add new Compute device in Inventory with full credentials.Inputs needed for Compute Device
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
http_username: "testuser"
http_password: "test"
http_port: "443"
snmp_auth_passphrase: "Lablab@12"
snmp_auth_protocol: SHA
snmp_mode: AUTHPRIV
snmp_priv_passphrase: "Lablab@123"
snmp_priv_protocol: AES256
snmp_retry: 3
snmp_timeout: 5
snmp_username: v3Public
compute_device: True
username: cisco
type: "COMPUTE_DEVICE"
- name: Add new Meraki device in Inventory with full credentials.Inputs needed for Meraki Device.
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- http_password: "test"
type: "MERAKI_DASHBOARD"
- name: Add new Firepower Management device in Inventory with full credentials.Input needed to add Device.
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
http_username: "testuser"
http_password: "test"
http_port: "443"
type: "FIREPOWER_MANAGEMENT_SYSTEM"
- name: Add new Third Party device in Inventory with full credentials.Input needed to add Device.
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
snmp_auth_passphrase: "Lablab@12"
snmp_auth_protocol: SHA
snmp_mode: AUTHPRIV
snmp_priv_passphrase: "Lablab@123"
snmp_priv_protocol: AES256
snmp_retry: 3
snmp_timeout: 5
snmp_username: v3Public
type: "THIRD_PARTY_DEVICE"
- name: Update device details or credentails in Inventory
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- cli_transport: telnet
compute_device: False
password: newtest123
enable_password: newtest1233
ip_address_list: ["1.1.1.1", "2.2.2.2"]
type: NETWORK_DEVICE
credential_update: True
- name: Update new management IP address of device in inventory
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- ip_address_list: ["1.1.1.1"]
credential_update: True
update_mgmt_ipaddresslist:
- exist_mgmt_ipaddress: "1.1.1.1"
new_mgmt_ipaddress: "12.12.12.12"
- name: Associate Wired Devices to site and Provisioned it in Inventory
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- provision_wired_device:
- device_ip: "1.1.1.1"
site_name: "Global/USA/San Francisco/BGL_18/floor_pnp"
resync_retry_count: 200
resync_retry_interval: 2
- device_ip: "2.2.2.2"
site_name: "Global/USA/San Francisco/BGL_18/floor_test"
resync_retry_count: 200
resync_retry_interval: 2
- name: Update Device Role with IP Address
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
role: ACCESS
- name: Update Interface details with IP Address
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
update_interface_details:
description: "Testing for updating interface details"
admin_status: "UP"
vlan_id: 23
voice_vlan_id: 45
deployment_mode: "Deploy"
interface_name: ["GigabitEthernet1/0/11", FortyGigabitEthernet1/1/1]
clear_mac_address_table: True
- name: Export Device Details in a CSV file Interface details with IP Address
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
export_device_list:
password: "File_password"
operation_enum: "0"
parameters: ["componentName", "SerialNumber", "Last Sync Status"]
- name: Create Global User Defined with IP Address
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
add_user_defined_field:
- name: Test123
description: "Added first udf for testing"
value: "value123"
- name: Test321
description: "Added second udf for testing"
value: "value321"
- name: Resync Device with IP Addresses
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
device_resync: True
force_sync: False
- name: Reboot AP Devices with IP Addresses
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: merged
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
reboot_device: True
- name: Delete Provision/Unprovision Devices by IP Address
cisco.dnac.inventory_intent:
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}}"
dnac_log: False
dnac_log_level: "{{dnac_log_level}}"
state: deleted
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
clean_config: False
- name: Delete Global User Defined Field with name
cisco.dnac.inventory_intent:
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}}"
dnac_log_level: "{{dnac_log_level}}"
dnac_log: False
state: deleted
config:
- ip_address_list: ["1.1.1.1", "2.2.2.2"]
add_user_defined_field:
- name: Test123
- name: Test321
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 Catalyst Center Python SDK Returned: always Sample: |