cisco.dnac.network_device_module_info module – Information module for Network Device Module
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.network_device_module_info.
New in version 3.1.0: of cisco.dnac
Synopsis
Get all Network Device Module.
Get Network Device Module by id.
Returns Module info by ‘module id’.
Returns modules by specified device id.
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 |
|---|---|
DeviceId query parameter. |
|
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” |
|
Additional headers. |
|
Id path parameter. Module id. |
|
Limit query parameter. |
|
NameList query parameter. |
|
Offset query parameter. |
|
OperationalStateCodeList query parameter. |
|
PartNumberList query parameter. |
|
Flag for Cisco DNA Center SDK to enable the validation of request bodies against a JSON schema. Choices:
|
|
VendorEquipmentTypeList query parameter. |
Notes
Note
SDK Method used are devices.Devices.get_module_info_by_id, devices.Devices.get_modules,
Paths used are get /dna/intent/api/v1/network-device/module, get /dna/intent/api/v1/network-device/module/{id},
Supports
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 Devices GetModuleInfoById
Complete reference of the GetModuleInfoById API.
- Cisco DNA Center documentation for Devices GetModules
Complete reference of the GetModules API.
Examples
- name: Get all Network Device Module
cisco.dnac.network_device_module_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}}"
deviceId: string
limit: string
offset: string
nameList: []
vendorEquipmentTypeList: []
partNumberList: []
operationalStateCodeList: []
register: result
- name: Get Network Device Module by id
cisco.dnac.network_device_module_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}}"
id: string
register: result
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”: {“assemblyNumber”: “string”, “assemblyRevision”: “string”, “attributeInfo”: {}, “containmentEntity”: “string”, “description”: “string”, “entityPhysicalIndex”: “string”, “id”: “string”, “isFieldReplaceable”: “string”, “isReportingAlarmsAllowed”: “string”, “manufacturer”: “string”, “moduleIndex”: 0, “name”: “string”, “operationalStateCode”: “string”, “partNumber”: “string”, “serialNumber”: “string”, “vendorEquipmentType”: “string”}, “version”: “string”} |