cisco.dnac.transit_peer_network module – Resource module for Transit Peer Network
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.transit_peer_network.
New in version 6.5.0: of cisco.dnac
Synopsis
Manage operations create and delete of the resource Transit Peer Network.
Add Transit Peer Network in SD-Access.
Delete Transit Peer Network from SD-Access.
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 |
|---|---|
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” |
|
Transit Peer Network’s ipTransitSettings. |
|
Autonomous System Number (e.g.,1-65535). |
|
Routing Protocol Name. |
|
Transit Peer Network’s sdaTransitSettings. |
|
Transit Peer Network’s transitControlPlaneSettings. |
|
Device Management Ip Address of provisioned device. |
|
Site Name Hierarchy where device is provisioned. |
|
TransitPeerNetworkName query parameter. Transit Peer Network Name. |
|
Transit Peer Network Type. |
|
Flag for Cisco DNA Center SDK to enable the validation of request bodies against a JSON schema. Choices:
|
Notes
Note
SDK Method used are ..add_transit_peer_network, ..delete_transit_peer_network,
Paths used are post /dna/intent/api/v1/business/sda/transit-peer-network, delete /dna/intent/api/v1/business/sda/transit-peer-network,
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 DNA Center documentation for AddTransitPeerNetwork
Complete reference of the AddTransitPeerNetwork API.
- Cisco DNA Center documentation for DeleteTransitPeerNetwork
Complete reference of the DeleteTransitPeerNetwork API.
Examples
- name: Delete all
cisco.dnac.transit_peer_network:
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
transitPeerNetworkName: string
- name: Create
cisco.dnac.transit_peer_network:
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
ipTransitSettings:
autonomousSystemNumber: string
routingProtocolName: string
sdaTransitSettings:
transitControlPlaneSettings:
- deviceManagementIpAddress: string
siteNameHierarchy: string
transitPeerNetworkName: string
transitPeerNetworkType: 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: {“description”: “string”, “executionId”: “string”, “executionStatusUrl”: “string”, “status”: “string”, “taskId”: “string”, “taskStatusUrl”: “string”} |