cisco.dnac.pnp_device_history_info – Information module for Pnp Device History

Note

This plugin is part of the cisco.dnac collection (version 4.2.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.pnp_device_history_info.

New in version 3.1.0: of cisco.dnac

Synopsis

  • Get all Pnp Device History.

  • Returns history for a specific device. Serial number is a required parameter.

Note

This module has a corresponding action plugin.

Requirements

The below requirements are needed on the host that executes this module.

  • dnacentersdk >= 2.4.4

  • python >= 3.5

Parameters

Parameter

Comments

dnac_debug

boolean

Flag for Cisco DNA Center SDK to enable debugging.

Choices:

  • no ← (default)

  • yes

dnac_host

string / required

The Cisco DNA Center hostname.

dnac_password

string

The Cisco DNA Center password to authenticate.

dnac_port

string

The Cisco DNA Center port.

Default: 443

dnac_username

aliases: user

string

The Cisco DNA Center username to authenticate.

Default: “admin”

dnac_verify

boolean

Flag to enable or disable SSL certificate verification.

Choices:

  • no

  • yes ← (default)

dnac_version

string

Informs the SDK which version of Cisco DNA Center to use.

Default: “2.2.3.3”

headers

dictionary

Additional headers.

serialNumber

string

SerialNumber query parameter. Device Serial Number.

sort

list / elements=string

Sort query parameter. Comma seperated list of fields to sort on.

sortOrder

string

SortOrder query parameter. Sort Order Ascending (asc) or Descending (des).

validate_response_schema

boolean

Flag for Cisco DNA Center SDK to enable the validation of request bodies against a JSON schema.

Choices:

  • no

  • yes ← (default)

Notes

Note

  • SDK Method used are device_onboarding_pnp.DeviceOnboardingPnp.get_device_history

  • Paths used are get /dna/intent/api/v1/onboarding/pnp-device/history

  • Supports 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

Examples

- name: Get all Pnp Device History
  cisco.dnac.pnp_device_history_info:
    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}}"
    headers:
      custom: value
    serialNumber: string
    sort: []
    sortOrder: string
  register: result

Return Values

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

Key

Description

dnac_response

dictionary

A dictionary or list with the response returned by the Cisco DNAC Python SDK

Returned: always

Sample: “{\n \”response\”: [\n {\n \”timestamp\”: 0,\n \”details\”: \”string\”,\n \”historyTaskInfo\”: {\n \”name\”: \”string\”,\n \”type\”: \”string\”,\n \”timeTaken\”: 0,\n \”workItemList\”: [\n {\n \”state\”: \”string\”,\n \”command\”: \”string\”,\n \”startTime\”: 0,\n \”endTime\”: 0,\n \”timeTaken\”: 0,\n \”outputStr\”: \”string\”\n }\n ],\n \”addnDetails\”: [\n {\n \”key\”: \”string\”,\n \”value\”: \”string\”\n }\n ]\n },\n \”errorFlag\”: true\n }\n ],\n \”statusCode\”: 0\n}\n”

Authors

  • Rafael Campos (@racampos)