cisco.dnac.topology_physical_info module – Information module for Topology Physical

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.topology_physical_info.

New in version 3.1.0: of cisco.dnac

Synopsis

  • Get all Topology Physical.

  • Returns the raw physical topology by specified criteria of nodeType.

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

dnac_debug

boolean

Flag for Cisco DNA Center SDK to enable debugging.

Choices:

  • false ← (default)

  • true

dnac_host

string / required

The Cisco DNA Center hostname.

dnac_password

string

The Cisco DNA Center password to authenticate.

dnac_port

integer

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:

  • false

  • true ← (default)

dnac_version

string

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

Default: “2.3.3.0”

headers

dictionary

Additional headers.

nodeType

string

NodeType query parameter.

validate_response_schema

boolean

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

Choices:

  • false

  • true ← (default)

Notes

Note

  • SDK Method used are topology.Topology.get_physical_topology,

  • Paths used are get /dna/intent/api/v1/topology/physical-topology,

  • 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

See Also

See also

Cisco DNA Center documentation for Topology GetPhysicalTopology

Complete reference of the GetPhysicalTopology API.

Examples

- name: Get all Topology Physical
  cisco.dnac.topology_physical_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: "{{my_headers | from_json}}"
    nodeType: 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: {“response”: {“id”: “string”, “links”: [{“additionalInfo”: {}, “endPortID”: “string”, “endPortIpv4Address”: “string”, “endPortIpv4Mask”: “string”, “endPortName”: “string”, “endPortSpeed”: “string”, “greyOut”: true, “id”: “string”, “linkStatus”: “string”, “source”: “string”, “startPortID”: “string”, “startPortIpv4Address”: “string”, “startPortIpv4Mask”: “string”, “startPortName”: “string”, “startPortSpeed”: “string”, “tag”: “string”, “target”: “string”}], “nodes”: [{“aclApplied”: true, “additionalInfo”: {}, “customParam”: {“id”: “string”, “label”: “string”, “parentNodeId”: “string”, “x”: 0, “y”: 0}, “dataPathId”: “string”, “deviceType”: “string”, “family”: “string”, “fixed”: true, “greyOut”: true, “id”: “string”, “ip”: “string”, “label”: “string”, “networkType”: “string”, “nodeType”: “string”, “order”: 0, “osType”: “string”, “platformId”: “string”, “role”: “string”, “roleSource”: “string”, “softwareVersion”: “string”, “tags”: [“string”], “upperNode”: “string”, “userId”: “string”, “vlanId”: “string”, “x”: 0, “y”: 0}]}, “version”: “string”}

Authors

  • Rafael Campos (@racampos)