cisco.catalystcenter.network_device_maintenance_schedules module -- Resource module for Network Device Maintenance Schedules
Note
This module is part of the cisco.catalystcenter collection (version 2.2.2).
To install it, use: ansible-galaxy collection install cisco.catalystcenter.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: cisco.catalystcenter.network_device_maintenance_schedules.
New in cisco.catalystcenter 6.17.0
Synopsis
Manage operation create of the resource Network Device Maintenance Schedules. - > API to create maintenance schedule for network devices. The state of network device can be queried using API `GET /dna/intent/api/v1/networkDevices`. The `managementState` attribute of the network device will be updated to `UNDER_MAINTENANCE` when the maintenance window starts.
Note
This module has a corresponding action plugin.
Requirements
The below requirements are needed on the host that executes this module.
catalystcentersdk >= 3.1.3.0.0
python >= 3.5
Parameters
Parameter |
Comments |
|---|---|
The Cisco Catalyst Center port. Default: :ansible-option-default:`443` |
|
Flag for Cisco Catalyst Center SDK to enable debugging. Choices: |
|
The Cisco Catalyst Center hostname. |
|
The Cisco Catalyst Center password to authenticate. |
|
The Cisco Catalyst Center username to authenticate. Default: :ansible-option-default:`"admin"` |
|
Flag to enable or disable SSL certificate verification. Choices: |
|
Informs the SDK which version of Cisco Catalyst Center to use. Default: :ansible-option-default:`"2.3.7.6"` |
|
A brief narrative describing the maintenance schedule. |
|
Network Device Maintenance Schedules's maintenanceSchedule. |
|
End time indicates the ending of the maintenance window in Unix epoch time in milliseconds. |
|
Network Device Maintenance Schedules's recurrence. |
|
Interval for recurrence in days. The interval must be longer than the duration of the schedules. The maximum allowed interval is 365 days. |
|
The end date for the recurrence in Unix epoch time in milliseconds. Recurrence end time should be greater than maintenance end date/time. |
|
Start time indicates the beginning of the maintenance window in Unix epoch time in milliseconds. |
|
List of network device ids. This field is applicable only during creation of schedules; for updates, it is read-only. |
|
Flag for Cisco Catalyst Center SDK to enable the validation of request bodies against a JSON schema. Choices: |
Notes
Note
SDK Method used are devices.Devices.create_maintenance_schedule_for_network_devices,
Paths used are post /dna/intent/api/v1/networkDeviceMaintenanceSchedules,
Does not support
check_modeThe plugin runs on the control node and does not use any ansible connection plugins,
but instead uses the embedded connection manager from Cisco CATALYST SDK
See Also
See also
- Cisco DNA Center documentation for Devices CreateMaintenanceScheduleForNetworkDevices
Complete reference of the CreateMaintenanceScheduleForNetworkDevices API.
Examples
---
- name: Create
cisco.catalystcenter.network_device_maintenance_schedules:
catalystcenter_host: "{{catalystcenter_host}}"
catalystcenter_username: "{{catalystcenter_username}}"
catalystcenter_password: "{{catalystcenter_password}}"
catalystcenter_verify: "{{catalystcenter_verify}}"
catalystcenter_api_port: "{{catalystcenter_api_port}}"
catalystcenter_version: "{{catalystcenter_version}}"
catalystcenter_debug: "{{catalystcenter_debug}}"
state: present
description: string
maintenanceSchedule:
endTime: 0
recurrence:
interval: 0
recurrenceEndTime: 0
startTime: 0
networkDeviceIds:
- 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 CATALYST Python SDK Returned: always Sample: :ansible-rv-sample-value:`{"response": {"taskId": "string", "url": "string"}, "version": "string"}` |