cisco.dnac.assurance_issue_workflow_manager module – Resource module for managing assurance global profile settings and issue resolution in Cisco Catalyst Center

Note

This module is part of the cisco.dnac collection (version 6.39.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. You need further requirements to be able to use this module, see Requirements for details.

To use it in a playbook, specify: cisco.dnac.assurance_issue_workflow_manager.

New in cisco.dnac 6.31.0

Synopsis

  • This module allows the management of assurance global profile settings and issues in Cisco Catalyst Center.

  • It supports creating, updating, and deleting configurations for issue settings and issue resolution functionalities.

  • This module interacts with Cisco Catalyst Center’s Assurance settings to configure thresholds, rules, KPIs, and more for issue settings and issue resolution.

  • The functionality for updating ‘Global and Customized Settings’, including custom profiles site assignment, is currently unavailable due to an API/SDK upgrade. It will be accessible under the ‘Network Assurance Profile Workflow Manager’ once the updated API is released

Requirements

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

  • dnacentersdk >= 2.8.6

  • python >= 3.9

Parameters

Parameter

Comments

config

list / elements=dictionary / required

A list of settings and parameters to be applied. It consists of different sub-configurations for managing assurance settings such as issue settings, health score, ICAP settings, issue resolution, and command execution.

assurance_issue

list / elements=dictionary

Allow to resolve, ignore, or execute commands based on the issue settings assurance in Cisco Catalyst Center.

device_name

string

A filter to select issues based on the device name that is associated with the issue (e.g., `NY-EN-9300.cisco.local`).

end_datetime

string

A filter to select issues that ended at or before this date and time. The format is “YYYY-MM-DD HH:MM:SS”.

ignore_duration

string

Specifies how long to ignore the issue. The value is a string with a numeric value followed by a time unit suffix. Supported units: - ‘h’ for hours (e.g., ‘1h’ for 1 hour, ‘24h’ for 24 hours). - ‘d’ for days (e.g., ‘3d’ for 3 days, ‘30d’ for 30 days). The range is from ‘1h’ to ‘30d’. The default value is ‘24h’. This parameter is available from Cisco Catalyst Center version 2.3.7.10 onwards. Example valid values: ‘1h’, ‘3d’, ‘24h’. Example invalid values: ‘24’, ‘3days’, ‘h3’, ‘0h’, ‘31d’, ‘2.5h’.

Default: "24h"

issue_name

string / required

The name of the issue to be processed (either resolved, ignored, or command executed). This field is required when creating or updating an issue.

issue_process_type

string / required

Defines the action to be taken on the issue. Possible values: resolution: Resolves the issue. ignore: Ignores the issue. command_execution: Executes commands to address the issue.

issue_status

string

A filter to select issues based on their status. Acceptable values are: ACTIVE: The issue is currently open. RESOLVED: The issue has been resolved. IGNORED: The issue has been ignored. type: str required: false

mac_address

string

A filter to select issues based on the MAC address of the device associated with the issue.

network_device_ip_address

string

A filter to select issues based on the network device’s IP address associated with the issue.

priority

string

A filter to select issues based on their priority. Acceptable values are: - P1 (Highest Priority) - P2 - P3 - P4 (Lowest Priority) type: str required: false

site_hierarchy

string

A filter to select issues based on the site location hierarchy. The format is “Global/Region/Location/Building”, where each level is separated by a slash.

start_datetime

string

A filter to select issues that started at or after this date and time. The format is “YYYY-MM-DD HH:MM:SS”.

assurance_system_issue_settings

list / elements=dictionary

Manages system issue settings for assurance in Cisco Catalyst Center.

description

string / required

Provides a detailed explanation of the system issue setting, including the specific threshold fields that require updates for the defined issue names. This field is essential for understanding which parameters need adjustment to align with the current system configurations and alerting criteria.

device_type

string / required

Specifies the type of device to which the issue configuration applies. For example, choices: - ROUTER - SWITCH_AND_HUB - UNIFIED_AP - WIRELESS_CLIENT - WIRED_CLIENT - WIRELESS_CONTROLLER - THIRD_PARTY_DEVICE - APPLICATION - SENSOR

issue_enabled

boolean / required

A boolean value that determines whether the issue is enabled or disabled. Accepts “true” or “false”.

Choices:

  • false

  • true

name

string / required

The name of the system issue setting, used to identify the configuration in the system. Required when creating or updating an issue setting.

priority

string / required

Specifies the priority level of the issue.

Choices:

  • "P1"

  • "P2"

  • "P3"

  • "P4"

synchronize_to_health_threshold

boolean

A boolean value indicating whether the system issue should be synchronized to the health threshold. Accepts “true” or “false”.

Choices:

  • false

  • true

threshold_value

integer

The threshold value that triggers the issue. This is usually specified as a percentage or a numerical value depending on the nature of the issue. For example, for the issue “Wireless client exhibiting sticky behavior,” the threshold could be a maximum RSSI value (e.g., -70 dBm). Similarly, for a “WLC Memory High Utilization”, a threshold like 90% can be used. - **Percentage-based thresholds**: Must not exceed 100%. - **dBm (decibel-milliwatts) thresholds**: Must not exceed 0 dBm, meaning it should be a negative value.

assurance_user_defined_issue_settings

list / elements=dictionary

Configures user-defined issue settings for assurance in Cisco Catalyst Center. Allows defining issue names, descriptions, severity, priority, and rules governing network issues.

description

string

A brief explanation of the issue for clarity in reports and dashboards.

is_enabled

boolean

Enables or disables the issue setting.

Choices:

  • false

  • true

is_notification_enabled

boolean

Boolean value to specify if notifications for this issue setting should be enabled.

Choices:

  • false

  • true

name

string / required

The name of the issue setting, used for identification in the system. Required when creating a new setting or updating an existing one.

prev_name

string

The previous name of the issue setting (used when updating an existing issue setting).

priority

string

Specifies the priority of the issue.

Choices:

  • "P1"

  • "P2"

  • "P3"

  • "P4"

rules

list / elements=dictionary

A set of rules that define the parameters for triggering the issue. Includes severity, facility, mnemonic, pattern, occurrences, and duration.

duration_in_minutes

integer

The duration, in minutes, for which the issue pattern must persist to be considered valid.

facility

string

The facility type that the rule applies to.

Choices:

  • "CI"

  • "PLATFORM_ENV"

  • "PLATFORM_THERMAL"

  • "PLATFORM_FEP"

  • "ENVMON"

  • "HARDWARE"

  • "SYS"

  • "ENVM"

  • "PLATFORM"

  • "CTS"

  • "THERMAL"

  • "SPA"

  • "IOSXE_RP_ALARM"

  • "ENVIRONMENT"

  • "SPANTREE"

  • "CMRP_ENVMON"

  • "LISP"

  • "PM"

  • "UDLD"

  • "IP"

  • "SW_MATM"

  • "CMRP_PFU"

  • "C4K_IOSMODPORTMAN"

  • "C6KENV"

  • "MAC_MOVE"

  • "OSP"

  • "SFF8472"

  • "DUAL"

  • "DMI"

  • "BGP"

  • "REDUNDANCY"

  • "IFDAMP"

  • "CAPWAPAC_SMGR_TRACE_MESSAGE"

  • "OSPF"

  • "DOT1X"

  • "ILPOWER"

  • "IOSXE_OIR"

  • "TRANSCEIVER"

  • "SMART_LIC"

  • "STANDBY"

  • "IOSXE_PEM"

  • "PLATFORM_STACKPOWER"

  • "ENV_MON"

  • "IOSXE_INFRA"

  • "STACKMGR"

mnemonic

string

A system-generated identifier or label representing the issue.

Choices:

  • "SHUT_LC_FANGONE"

  • "SHUTFANGONE"

  • "SHUTFANFAIL"

  • "SHUT_LC_FANFAIL"

  • "FRU_PS_FAN_FAILED"

  • "RPS_FAN_FAILED"

  • "FRU_PS_FAN_OK"

  • "FAN"

  • "FAN_NOT_PRESENT"

  • "FRU_FAN_OK"

  • "PLATFORM_FAN_CRITICAL"

  • "RPS_PS_FAN_FAILED"

  • "FRU_FAN_FAILURE"

  • "FRU_FAN_RECOVERY"

  • "FAN_CRITICAL"

  • "FRU_FAN_NOT_PRESENT"

  • "FRU_FAN_DISABLED"

  • "FRU_FAN_INSUFFICIENTFANTRAYSDETECTEDPOWERDOWN"

  • "FRU_PS_SIGNAL_FAULTY"

  • "FAN_FAILURE_LC_SHUT"

  • "FAN_MISSING"

  • "TOTALFANFAIL"

  • "NOFAN"

  • "THERMAL_CRITICAL"

  • "OVERTEMP"

  • "OVERTEMP_ALERT"

  • "PFM_ALERT"

  • "PFU_FAN_FAILED"

  • "MODULECRITICALTEMP"

  • "CRITICALTEMP"

  • "AUTHZ_POLICY_SGACL_ACE_FAILED"

  • "THERMAL_YELLOW_THRESHOLD"

  • "THERMAL_RED_THRESHOLD"

  • "TEMP_CRITICAL"

  • "PEM"

  • "FANOK"

  • "FAN_FAULT"

  • "PS_RED_MODE_CHG"

  • "PS_FAIL"

  • "PS_DETECT"

  • "PS_ABSENT"

  • "BLOCK_BPDUGUARD"

  • "MAJORTEMPALARM"

  • "PEER_MONITOR"

  • "SWITCHOVER"

  • "STANDBY_LOST"

  • "PARTIAL_FAN_FAIL"

  • "PARTFANFAIL"

  • "PSFANFAIL"

  • "DUPADDR"

  • "PEMCHASFSERR"

  • "PEMFAIL"

  • "FAN_FAIL_SHUTDOWN"

  • "FANFAIL"

  • "TEMP_SYS_SHUTDOWN_PENDING"

  • "TEMP_WARN_CRITICAL"

  • "TEMP_FRU_SHUTDOWN_PENDING"

  • "MAP_CACHE_WARNING_THRESHOLD_REACHED"

  • "LOCAL_EID_NO_ROUTE"

  • "LOCAL_EID_MAP_REGISTER_FAILURE"

  • "CEF_DISABLED"

  • "ERR_DISABLE"

  • "UNDER_BUDGET"

  • "VERSION_MISMATCH"

  • "TOO_MANY_ERRORS"

  • "INSUFFICIENT_PWR"

  • "REDUNDANCY_LOSS"

  • "UDLD_PORT_DISABLED"

  • "DUPADDR"

  • "MACFLAP_NOTIF"

  • "PFU_FAN_WARN"

  • "MODULETEMPHIGH"

  • "POWERSUPPLYBAD"

  • "CRITICALTEMP"

  • "MODULECRITICALTEMP"

  • "TEMPHIGH"

  • "FANTRAYREMOVED"

  • "TERMINATOR_PS_TEMP_MAJORALARM"

  • "NOTIF"

  • "THRESHOLD_VIOLATION"

  • "NBRCHANGE"

  • "SUCCESS"

  • "FAIL"

  • "SYNC_NEEDED"

  • "SYNC_START"

  • "ADJCHANGE"

  • "PEER_MONITOR_EVENT"

  • "UPDOWN"

  • "AP_JOIN_DISJOIN"

  • "ADJCHG"

  • "ILPOWER_POWER_DENY"

  • "REMSPA"

  • "INSSPA"

  • "OFFLINECARD"

  • "REMOVED"

  • "INSERTED"

  • "AGENT_READY"

  • "HA_ROLE_CHANGED"

  • "AGENT_ENABLED"

  • "STATECHANGE"

  • "REMPEM_FM"

  • "PEMOK"

  • "CABLE_EVENT"

  • "LINK_EVENT"

  • "REMPEM"

  • "HASTATUS_DETAIL"

  • "HASTATUS"

  • "PROCPATH_CLIENT_HOG"

  • "STACK_LINK_CHANGE"

occurrences

integer

The number of times the issue pattern must occur before triggering the issue.

pattern

string

A pattern or regular expression defining the issue detection criteria.

severity

string

Specifies the severity level of the issue. The severity value can be an integer (0 to 6) or its corresponding string representation.

Choices:

  • "0"

  • "1"

  • "2"

  • "3"

  • "4"

  • "5"

  • "6"

  • "Emergency"

  • "Alert"

  • "Critical"

  • "Error"

  • "Warning"

  • "Notice"

  • "Info"

config_verify

boolean

Set to `true` to enable configuration verification on Cisco Catalyst Center after applying the playbook config. This will ensure that the system validates the configuration state after the change is applied.

Choices:

  • false ← (default)

  • true

dnac_api_task_timeout

integer

Defines the timeout in seconds for API calls to retrieve task details. If the task details are not received within this period, the process will end, and a timeout notification will be logged.

Default: 1200

dnac_debug

boolean

Indicates whether debugging is enabled in the Cisco Catalyst Center SDK.

Choices:

  • false ← (default)

  • true

dnac_host

string / required

The hostname of the Cisco Catalyst Center.

dnac_log

boolean

Flag to enable/disable playbook execution logging.

When true and dnac_log_file_path is provided, - Create the log file at the execution location with the specified name.

When true and dnac_log_file_path is not provided, - Create the log file at the execution location with the name ‘dnac.log’.

When false, - Logging is disabled.

If the log file doesn’t exist, - It is created in append or write mode based on the “dnac_log_append” flag.

If the log file exists, - It is overwritten or appended based on the “dnac_log_append” flag.

Choices:

  • false ← (default)

  • true

dnac_log_append

boolean

Determines the mode of the file. Set to True for ‘append’ mode. Set to False for ‘write’ mode.

Choices:

  • false

  • true ← (default)

dnac_log_file_path

string

Governs logging. Logs are recorded if dnac_log is True.

If path is not specified, - When ‘dnac_log_append’ is True, ‘dnac.log’ is generated in the current Ansible directory; logs are appended. - When ‘dnac_log_append’ is False, ‘dnac.log’ is generated; logs are overwritten.

If path is specified, - When ‘dnac_log_append’ is True, the file opens in append mode. - When ‘dnac_log_append’ is False, the file opens in write (w) mode. - In shared file scenarios, without append mode, content is overwritten after each module execution. - For a shared log file, set append to False for the 1st module (to overwrite); for subsequent modules, set append to True.

Default: "dnac.log"

dnac_log_level

string

Sets the threshold for log level. Messages with a level equal to or higher than this will be logged. Levels are listed in order of severity [CRITICAL, ERROR, WARNING, INFO, DEBUG].

CRITICAL indicates serious errors halting the program. Displays only CRITICAL messages.

ERROR indicates problems preventing a function. Displays ERROR and CRITICAL messages.

WARNING indicates potential future issues. Displays WARNING, ERROR, CRITICAL messages.

INFO tracks normal operation. Displays INFO, WARNING, ERROR, CRITICAL messages.

DEBUG provides detailed diagnostic info. Displays all log messages.

Default: "WARNING"

dnac_password

string

The password for authentication at the Cisco Catalyst Center.

dnac_port

string

Specifies the port number associated with the Cisco Catalyst Center.

Default: "443"

dnac_task_poll_interval

integer

Specifies the interval in seconds between successive calls to the API to retrieve task details.

Default: 2

dnac_username

aliases: user

string

The username for authentication at the Cisco Catalyst Center.

Default: "admin"

dnac_verify

boolean

Flag to enable or disable SSL certificate verification.

Choices:

  • false

  • true ← (default)

dnac_version

string

Specifies the version of the Cisco Catalyst Center that the SDK should use.

Default: "2.2.3.3"

state

string

Specifies the desired state for the configuration. If `merged`, the module will create or update the configuration, adding new settings or modifying existing ones. If `deleted`, it will remove the specified settings.

Choices:

  • "merged" ← (default)

  • "deleted"

validate_response_schema

boolean

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

Choices:

  • false

  • true ← (default)

Notes

Note

  • SDK Methods used are issues.AssuranceSettings.get_all_the_custom_issue_definitions_based_on_the_given_filters issues.AssuranceSettings.creates_a_new_user_defined_issue_definitions issues.AssuranceSettings.deletes_an_existing_custom_issue_definition issues.AssuranceSettings.resolve_the_given_lists_of_issues issues.AssuranceSettings.ignore_the_given_list_of_issues issues.AssuranceSettings.execute_suggested_action_commands

  • Paths used are POST /dna/intent/api/api/v1/customIssueDefinitions POST /dna/intent/api/v1/assuranceIssues/resolve POST /dna/intent/api/v1/execute-suggested-actions-commands POST /dna/intent/api/v1/assuranceIssues/ignore POST /dna/intent/api/v1/flow-analysis/${flowAnalysisId} POST /dna/intent/api/v1/flow-analysis PUT /dna/intent/api/v1/systemIssueDefinitions/${id} DELETE /dna/intent/api/v1/flow-analysis/{flowAnalysisId} DELETE /dna/intent/api/v1/customIssueDefinitions/{id}

  • Does not support check_mode

  • The plugin runs on the control node and does not use any ansible connection plugins instead embedded connection manager from Cisco Catalyst Center SDK

  • The parameters starting with dnac_ are used by the Cisco Catalyst Center Python SDK to establish the connection

Examples

---
- hosts: dnac_servers
  vars_files:
    - credentials.yml
  gather_facts: false
  connection: local
  tasks:
    - name: Create issue settings
      cisco.dnac.assurance_issue_workflow_manager:
        dnac_host: "{{ dnac_host }}"
        dnac_port: "{{ dnac_port }}"
        dnac_username: "{{ dnac_username }}"
        dnac_password: "{{ dnac_password }}"
        dnac_verify: "{{ dnac_verify }}"
        dnac_debug: "{{ dnac_debug }}"
        dnac_version: "{{ dnac_version }}"
        dnac_log: true
        dnac_log_level: DEBUG
        dnac_log_append: true
        state: merged
        config_verify: true
        config:
          - assurance_user_defined_issue_settings:
              - name: High CPU Usage Alert
                description: Triggers an alert when
                  CPU usage exceeds threshold
                rules:
                  - severity: Warning
                    facility: redundancy
                    mnemonic: peer monitor event
                    pattern: issue test
                    occurrences: 1
                    duration_in_minutes: 2
                is_enabled: false
                priority: P1
                is_notification_enabled: false
    - name: update issue settings
      cisco.dnac.assurance_issue_workflow_manager:
        dnac_host: "{{ dnac_host }}"
        dnac_port: "{{ dnac_port }}"
        dnac_username: "{{ dnac_username }}"
        dnac_password: "{{ dnac_password }}"
        dnac_verify: "{{ dnac_verify }}"
        dnac_debug: "{{ dnac_debug }}"
        dnac_version: "{{ dnac_version }}"
        dnac_log: true
        dnac_log_level: DEBUG
        dnac_log_append: true
        state: merged
        config_verify: true
        config:
          - assurance_user_defined_issue_settings:
              - prev_name: High CPU Usage Alert
                name: Excessive CPU Utilization Alert
                description: testing
                rules:
                  - severity: "2"
                    facility: redundancy
                    mnemonic: peer monitor event
                    pattern: issue test
                    occurrences: 1
                    duration_in_minutes: 2
                is_enabled: false
                priority: P1
                is_notification_enabled: false
    - name: Delete issue settings
      cisco.dnac.assurance_issue_workflow_manager:
        dnac_host: "{{ dnac_host }}"
        dnac_port: "{{ dnac_port }}"
        dnac_username: "{{ dnac_username }}"
        dnac_password: "{{ dnac_password }}"
        dnac_verify: "{{ dnac_verify }}"
        dnac_debug: "{{ dnac_debug }}"
        dnac_version: "{{ dnac_version }}"
        dnac_log_level: DEBUG
        dnac_log: true
        state: deleted
        config_verify: true
        config:
          - assurance_user_defined_issue_settings:
              - name: High CPU Usage Alert
- hosts: dnac_servers
  vars_files:
    - credentials.yml
  gather_facts: false
  connection: local
  tasks:
    - name: Update System issue
      cisco.dnac.assurance_issue_workflow_manager:
        dnac_host: "{{ dnac_host }}"
        dnac_port: "{{ dnac_port }}"
        dnac_username: "{{ dnac_username }}"
        dnac_password: "{{ dnac_password }}"
        dnac_verify: "{{ dnac_verify }}"
        dnac_debug: "{{ dnac_debug }}"
        dnac_version: "{{ dnac_version }}"
        dnac_log: true
        dnac_log_level: debug
        dnac_log_append: true
        state: merged
        config_verify: true
        config:
          - assurance_system_issue_settings:
              - name: "Assurance telemetry status is
                  poor"
                description: RF Noise (5GHz)
                device_type: WIRED_CLIENT
                synchronize_to_health_threshold: true
                priority: P1
                issue_enabled: false
                threshold_value: -10
- hosts: dnac_servers
  vars_files:
    - credentials.yml
  gather_facts: false
  connection: local
  tasks:
    - name: Resolving Issues
      cisco.dnac.assurance_issue_workflow_manager:
        dnac_host: "{{ dnac_host }}"
        dnac_port: "{{ dnac_port }}"
        dnac_username: "{{ dnac_username }}"
        dnac_password: "{{ dnac_password }}"
        dnac_verify: "{{ dnac_verify }}"
        dnac_debug: "{{ dnac_debug }}"
        dnac_version: "{{ dnac_version }}"
        dnac_log: true
        dnac_log_level: debug
        dnac_log_append: true
        state: merged
        config_verify: true
        config:
          - assurance_issue:
              - issue_name: Fabric BGP session status
                  is down with Peer Device  # required field
                issue_process_type: resolution  # required field
                start_datetime: "2024-12-11 16:00:00"  # optional field
                end_datetime: "2024-12-11 18:30:00"  # optional field
                site_hierarchy: Global/USA/San Jose/BLDG23  # optional field
                device_name: NY-EN-9300.cisco.local  # optional field
                priority: P4  # optional field
                issue_status: ACTIVE  # optional field
                mac_address: e4:38:7e:42:bc:40  # optional field
                network_device_ip_address: 204.1.2.4  # optional field
    - name: Ignoring issues
      cisco.dnac.assurance_issue_workflow_manager:
        dnac_host: "{{ dnac_host }}"
        dnac_port: "{{ dnac_port }}"
        dnac_username: "{{ dnac_username }}"
        dnac_password: "{{ dnac_password }}"
        dnac_verify: "{{ dnac_verify }}"
        dnac_debug: "{{ dnac_debug }}"
        dnac_version: "{{ dnac_version }}"
        dnac_log: true
        dnac_log_level: debug
        dnac_log_append: true
        state: merged
        config_verify: true
        config:
          - assurance_issue:
              - issue_name: Fabric BGP session status
                  is down with Peer Device  # required field
                issue_process_type: ignore  # required field
                ignore_duration: 4h
                start_datetime: "2024-12-11 16:00:00"  # optional field
                end_datetime: "2024-12-11 18:30:00"  # optional field
                site_hierarchy: Global/USA/San Jose/BLDG23  # optional field
                device_name: NY-EN-9300.cisco.local  # optional field
                priority: P4  # optional field
                issue_status: ACTIVE  # optional field
                mac_address: e4:38:7e:42:bc:40  # optional field
                network_device_ip_address: 204.1.2.4  # optional field
    - name: Execute suggested commands
      cisco.dnac.assurance_issue_workflow_manager:
        dnac_host: "{{ dnac_host }}"
        dnac_port: "{{ dnac_port }}"
        dnac_username: "{{ dnac_username }}"
        dnac_password: "{{ dnac_password }}"
        dnac_verify: "{{ dnac_verify }}"
        dnac_debug: "{{ dnac_debug }}"
        dnac_version: "{{ dnac_version }}"
        dnac_log: true
        dnac_log_level: debug
        dnac_log_append: true
        state: merged
        config_verify: true
        config:
          - assurance_issue:
              - issue_name: Fabric BGP session status
                  is down with Peer Device  # required field
                issue_process_type: command_execution  # required field
                start_datetime: "2024-12-11 16:00:00"  # optional field
                end_datetime: "2024-12-11 18:30:00"  # optional field
                site_hierarchy: Global/USA/San Jose/BLDG23  # optional field
                device_name: NY-EN-9300.cisco.local  # optional field
                priority: P4  # optional field
                issue_status: ACTIVE  # optional field
                mac_address: e4:38:7e:42:bc:40  # optional field
                network_device_ip_address: 204.1.2.4  # optional field

Return Values

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

Key

Description

Response

list / elements=dictionary

The response object containing execution details of suggested action commands.

Returned: always

Sample: [{"executionId": "dbde5a27-c2aa-4045-ac5d-b0c216da7513", "executionStatusUrl": "/dna/intent/api/v1/dnacaap/management/execution-status/dbde5a27-c2aa-4045-ac5d-b0c216da7513", "message": "The request has been accepted for execution"}]

response_create

dictionary

Details of the response returned by the assurance settings create API.

Returned: always

Sample: {"response": {"createdTime": 1672531200, "description": "string", "id": "string", "isDeletable": true, "isEnabled": true, "isNotificationEnabled": true, "lastUpdatedTime": 1672617600, "name": "string", "priority": "P1", "profileId": "string", "rules": [{"durationInMinutes": 15, "facility": "string", "mnemonic": "string", "occurrences": 3, "pattern": "string", "severity": 1, "type": "string"}], "triggerId": "string"}}

Response_ignore

dictionary

The response after ignoring issues in Cisco Catalyst Center.

Returned: always

Sample: {"response": {"failureIssueIds": ["string"], "successfulIssueIds": ["string"]}, "version": "string"}

response_resolved

dictionary

The response after resolving issues in Cisco Catalyst Center.

Returned: always

Sample: {"response": {"failureIssueIds": ["string"], "successfulIssueIds": ["string"]}, "version": "string"}

response_update

dictionary

Details of the response returned by the assurance settings update API.

Returned: always

Sample: {"response": {"createdTime": 1672531200, "description": "string", "id": "string", "isDeletable": true, "isEnabled": true, "isNotificationEnabled": true, "lastUpdatedTime": 1672617600, "name": "string", "priority": "P1", "profileId": "string", "rules": [{"durationInMinutes": 10, "facility": "string", "mnemonic": "string", "occurrences": 5, "pattern": "string", "severity": 1, "type": "string"}], "triggerId": "string"}}

response_update_system_issue

dictionary

The response object containing detailed information about the issue or configuration.

Returned: always

Sample: {"response": {"categoryName": "string", "defaultPriority": "string", "definitionStatus": "string", "description": "string", "deviceType": "string", "displayName": "string", "id": "string", "issueEnabled": "boolean", "lastModified": "string", "name": "string", "priority": "string", "profileId": "string", "synchronizeToHealthThreshold": "boolean", "thresholdValue": "number"}}

Authors

  • A Mohamed Rafeek (@mabdulk2)

  • Megha Kandari (@mekandar)

  • Madhan Sankaranarayanan (@madhansansel)