cisco.dnac.pnp_device_claim_to_site module – Resource module for Pnp Device Claim To Site
Note
This module is part of the cisco.dnac collection (version 6.6.0).
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.pnp_device_claim_to_site.
New in version 3.1.0: of cisco.dnac
Synopsis
- Manage operation create of the resource Pnp Device Claim To Site. 
- Claim a device based on DNA-C Site based design process. Different parameters are required for different device platforms. 
Note
This module has a corresponding action plugin.
Requirements
The below requirements are needed on the host that executes this module.
- dnacentersdk >= 2.5.4 
- python >= 3.5 
Parameters
| Parameter | Comments | 
|---|---|
| Pnp Device Claim To Site’s configInfo. | |
| Pnp Device Claim To Site’s configId. | |
| Pnp Device Claim To Site’s configParameters. | |
| Pnp Device Claim To Site’s key. | |
| Pnp Device Claim To Site’s value. | |
| Pnp Device Claim To Site’s deviceId. | |
| 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” | |
| Pnp Device Claim To Site’s gateway. | |
| Pnp Device Claim To Site’s hostname. | |
| Pnp Device Claim To Site’s imageId. | |
| Pnp Device Claim To Site’s imageInfo. | |
| Pnp Device Claim To Site’s imageId. | |
| Skip flag. Choices: 
 | |
| Pnp Device Claim To Site’s ipInterfaceName. | |
| RemoveInactive flag. Choices: 
 | |
| Pnp Device Claim To Site’s rfProfile. | |
| Pnp Device Claim To Site’s siteId. | |
| Pnp Device Claim To Site’s staticIP. | |
| Pnp Device Claim To Site’s subnetMask. | |
| Pnp Device Claim To Site’s type. | |
| Flag for Cisco DNA Center SDK to enable the validation of request bodies against a JSON schema. Choices: 
 | |
| Pnp Device Claim To Site’s vlanId. | 
Notes
Note
- SDK Method used are device_onboarding_pnp.DeviceOnboardingPnp.claim_a_device_to_a_site, 
- Paths used are post /dna/intent/api/v1/onboarding/pnp-device/site-claim, 
- 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 Device Onboarding (PnP) ClaimADeviceToASite
- Complete reference of the ClaimADeviceToASite API. 
Examples
- name: Create
  cisco.dnac.pnp_device_claim_to_site:
    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}}"
    configInfo:
      configId: string
      configParameters:
      - key: string
        value: string
    deviceId: string
    gateway: string
    hostname: string
    imageId: string
    imageInfo:
      imageId: string
      skip: true
    ipInterfaceName: string
    removeInactive: true
    rfProfile: string
    siteId: string
    staticIP: string
    subnetMask: string
    type: string
    vlanId: 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: {“response”: “string”, “version”: “string”} |