About this content

Flexible Report

Catalyst Center platform supports a new entity under Flexible reports called Network Interface.

Use the new Network Interface entity to generate Trend, TopN, Summary, and Distribution reports. This update integrates enhanced KPIs and advanced filtering to optimize data retrieval and provide granular visibility into network performance and health.

For more information, see Generate a flexible report.

Assurance Events

Catalyst Center platform supports these new events:

• NETWORK-DEVICES-4-401: This event triggers when the URWB AP Node is experiencing Packet Error Rate (PER) that is exceeding the defined URWB Critical PER threshold.

• NETWORK-DEVICES-4-402: This event triggers when the URWB AP Node is experiencing MCS Index that is lower than the defined URWB Critical MCS Index threshold.

• NETWORK-DEVICES-4-403: This event triggers when the URWB Link is experiencing Link Error Rate (LER) that is exceeding the defined URWB Critical LER threshold.

• NETWORK-DEVICES-4-404: This event triggers when the URWB Link is experiencing RSSI that is lower than the defined URWB Link RSSI threshold.

• NETWORK-DEVICES-2-900: This event triggers when there is a Traffic Steering Policy configuration failure.

• NETWORK-FABRIC_WIRED-1-339: This event triggers when Fabric Control Plane Node loses connectivity to one or more Wireless Controllers.

• NETWORK-DEVICES-2-157: This event triggers when the standby unit in Catalyst 9800 HA SSO pair is down, indicating redundancy failure.

Rogue Events

Catalyst Center platform now provides email support to these existing events:

• NETWORK-THREATS-ROGUE-01

• NETWORK-THREATS-AWIPS-01

Note

We recommend that you use webhooks instead of email notifications if you anticipate a high volume of alerts due to scaling.

Clients API Operations

With this release, Catalyst Center platform supports these API operations:

• GET <cluster-ip>/dna/intent/api/v1/trackedClients

  Read tracked-client configurations.

• POST <cluster-ip>/dna/intent/api/v1/trackedClients

  Create a tracked-client configuration.

• POST <cluster-ip>/dna/intent/api/v1/trackedClients/query

  Query tracked-client configurations with request-body filters.

• GET <cluster-ip>/dna/intent/api/v1/trackedClients/{id}

  Read a tracked-client configuration by client identifier.

• PUT <cluster-ip>/dna/intent/api/v1/trackedClients/{id}

  Partially update a tracked-client configuration.

• DELETE <cluster-ip>/dna/intent/api/v1/trackedClients/{id}

  Delete a tracked-client configuration.

• POST <cluster-ip>/dna/intent/api/v1/trackedClients/bulkCreate

  Bulk create tracked-client configurations.

• POST <cluster-ip>/dna/intent/api/v1/trackedClients/bulkUpdate

  Bulk partially update tracked-client configurations.

• POST <cluster-ip>/dna/intent/api/v1/trackedClients/bulkDelete

  Bulk delete tracked-client configurations.

To access the new Clients API operations, click the menu icon and choose Platform > Developer Toolkit > APIs.

Expand the Know Your Network drop-down list and choose Clients.

Connectivity API Operations

With this release, Catalyst Center platform supports these API operations:

• GET <cluster-ip>/dna/campus/api/v1/networks

  Get all networks.

• GET <cluster-ip>/dna/campus/api/v1/networks/${id}

  Get network by ID.

• GET <cluster-ip>/dna/campus/api/v1/networks/count

  Get total number of networks.

• PUT <cluster-ip>/dna/campus/api/v1/networks/${id}

  Update network.

• POST <cluster-ip>/dna/campus/api/v1/networks

  Create a network.

• DELETE <cluster-ip>/dna/campus/api/v1/networks/${id}

  Delete a network.

To access the new Connectivity API operations, click the menu icon and choose Platform > Developer Toolkit > APIs.

Devices API Operations

With this release, Catalyst Center platform supports these API operations:

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks

  Gets the URWB Network details based on the provided query parameters.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/count

  Gets the total URWB Network counts based on the provided query parameters.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{id}

  Get the URWB Network data for the given network ID.

• POST <cluster-ip>/dna/data/api/v1/urwbNetworks/{id}/trendAnalytics

  The Trend analytics data for the URWB Network in the specified time range.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/query

  Gets the list of URWB Networks based on the provided complex filters and aggregation functions.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/query/count

  Gets the total number of URWB Networks based on the provided complex filters.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/summaryAnalytics

  Gets the summary analytics data related to URWB Networks.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/topNAnalytics Gets the Top-N analytics data for URWB Networks.

  GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/links

  Gets the URWB Link details for a specific network.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/links/count

  Gets the total URWB Link counts for a specific network.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/links/{id}

  Get the URWB Link data for the given link ID.

• POST <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/links/{id}/trendAnalytics

  The Trend analytics data for the URWB Link in the specified time range.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/links/query

  Gets the list of URWB Links based on the provided complex filters and aggregation functions.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/links/query/count

  Gets the total number of URWB Links based on the provided complex filters.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/links/summaryAnalytics

  Gets the summary analytics data related to URWB Links.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/links/topNAnalytics

  Gets the Top-N analytics data for URWB Links.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/nodes

  Gets the URWB Node details for a specific network.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/nodes/count

  Gets the total URWB Node counts for a specific network.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/nodes/{id}

  Get the URWB Node data for the given node ID.

• POST <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/nodes/{id}/trendAnalytics

  The Trend analytics data for the URWB Node in the specified time range.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/nodes/query

  Gets the list of URWB Nodes based on the provided complex filters and aggregation functions.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/nodes/query/count

  Gets the total number of URWB Nodes based on the provided complex filters.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/nodes/summaryAnalytics

  Gets the summary analytics data related to URWB Nodes.

• GET <cluster-ip>/dna/data/api/v1/urwbNetworks/{urwbNetworkId}/nodes/topNAnalytics

  Gets the Top-N analytics data for URWB Nodes.

To access the new Devices API operations, click the menu icon and choose Platform > Developer Toolkit > APIs.

Expand the Know Your Network drop-down list and choose Devices.

Device Replacement API Operations

With this release, Catalyst Center platform supports these API operations:

• GET <cluster-ip>/dna/intent/api/v1/networkDevices/refresh

  Requests Retrieve the status of all device refresh workflows.

• POST <cluster-ip>/dna/intent/api/v1/networkDevices/refresh

  Requests Mark a network device for refresh.

• GET <cluster-ip>/dna/intent/api/v1/networkDevices/refreshRequests/count

  Return refresh devices count.

• GET <cluster-ip>/dna/intent/api/v1/networkDevices/refreshRequests/{id}

  Retrieve the status of a specific device refresh workflow.

• DELETE <cluster-ip>/dna/intent/api/v1/networkDevices/refreshRequests/{id}

  Unmark a network device marked for refresh.

• POST <cluster-ip>/dna/intent/api/v1/networkDevices/refreshRequests/bulk

  Mark network devices for refresh.

• DELETE <cluster-ip>/dna/intent/api/v1/networkDevices/refreshRequests/bulkDelete

  Unmark network devices marked for refresh.

• POST <cluster-ip>/dna/intent/api/v1/networkDevices/refreshRequests/deploy

  Deploy network device refresh workflows.

• POST <cluster-ip>/dna/intent/api/v1/networkDevices/refreshRequests/validations

  Validate device compatibility for bulk refresh.

To access the new Device Replacement API operations, click the menu icon and choose Platform > Developer Toolkit > APIs.

Expand the Site Management drop-down list and choose Device Replacement.

Industrial Configuration API Operations

With this release, Catalyst Center platform supports these API operations:

• POST <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/configurationModels/create

  Create configuration model for adding PRP configuration.

• POST <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/configurationModels/update

  Create configuration model for updating PRP configuration.

• POST <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/configurationModels/delete

  Create configuration model for deleting PRP configuration.

• GET <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/configurationModels/{previewActivityId}/networkDeviceStatusDetails

  Retrieve configuration model generation status for PRP.

• GET <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/configurationModels/{previewActivityId}/networkDevices/{networkDeviceId}/config

  Retrieve generated PRP configuration for the given network device and PRP configuration model.

• POST <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/configurationModels/{previewActivityId}/networkDevices/{networkDeviceId}/config

  Generate PRP configuration for the given network device and PRP configuration model.

• POST <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/configurationModels/{previewActivityId}/deploy

  Deploy the configuration model for PRP on network devices.

• DELETE <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/configurationModels/{previewActivityId}

  Delete a PRP configuration model.

• PUT <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/deploy

  Update PRP configuration without generating config preview.

• POST <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/deploy

  Deploy PRP configuration without generating config preview.

• DELETE <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/deploy

  Delete PRP configuration without generating a config preview.

• GET <cluster-ip>/dna/intent/api/v1/iot/fabric/prp

  Retrieve details of the PRP topologies configured.

• GET <cluster-ip>/dna/intent/api/v1/iot/fabric/prp/count

  Retrieve total count of PRP topologies.

• GET <cluster-ip>/dna/intent/api/v1/iot/repRings/query

  Retrieves the list of REP rings.

• POST <cluster-ip>/dna/intent/api/v1/iot/fabric/repRings

  Configure a REP Ring on FABRIC deployment.

• POST <cluster-ip>/dna/intent/api/v1/iot/nonFabric/repRings

  Configure a REP Ring on NON-FABRIC deployment.

• GET <cluster-ip>/dna/intent/api/v1/iot/repRings/{id}

  Get the REP ring based on the ring id.

• DELETE <cluster-ip>/dna/intent/api/v1/iot/fabric/repRings/{id}

  Delete REP ring configured in the FABRIC deployment.

• DELETE <cluster-ip>/dna/intent/api/v1/iot/nonFabric/repRings/{id}

  Delete REP ring configured in the NON-FABRIC deployment.

• GET <cluster-ip>/dna/intent/api/v1/iot/repRings/query/count

  Retrieves the count of REP rings.

To access the new Industrial Configuration API operations, click the menu icon and choose Platform > Developer Toolkit > APIs.

Expand the Know Your Network drop-down list and choose Industrial Configuration.

Network Settings API Operations

With this release, Catalyst Center platform supports these API operations:

• PUT <cluster-ip>/dna/intent/api/v1/sites/${id}/aaaTrustSecSettings

  Set aaa trustsec settings for a site.

• GET <cluster-ip>/dna/intent/api/v1/sites/${id}/aaaTrustSecSettings

  Retrieve aaa trustsec settings for a site

To access the new Network Settings API operations, click the menu icon and choose Platform > Developer Toolkit > APIs.

Expand the Site Management drop-down list and choose Network Settings.

Sensors API Operations

With this release, Catalyst Center platform supports these API operations:

• POST <cluster-ip>/dna/data/api/v1/icap/captureFiles/${id}/analyze

  Analyzes a packet capture file.

• PUT <cluster-ip>/dna/intent/api/v1/icap/settings/${id}

  Updates ICAP related settings.

• GET <cluster-ip>/dna/intent/api/v1/icap/settings

  Fetches ICAP related settings.

To access the new Sensors API operations, click the menu icon and choose Platform > Developer Toolkit > APIs.

Expand the Know Your Network drop-down list and choose Sensors.

Site Design API Operations

With this release, Catalyst Center platform supports these API operations:

• GET <cluster-ip>/dna/intent/api/v1/outdoorAreas/{outdoorAreaId}/accessPointPositions

  Get Outdoor Access Points Positions.

• GET <cluster-ip>/dna/intent/api/v1/outdoorAreas/{outdoorAreaId}/accessPointPositions/count

  Get Access Outdoor Points Positions count.

• POST <cluster-ip>/dna/intent/api/v1/outdoorAreas/{outdoorAreaId}/accessPointPositions/bulkChange

  Bulk change Outdoor Access Points Positions.

• GET <cluster-ip>/dna/intent/api/v1/outdoorAreas/{outdoorAreaId}/plannedAccessPointPositions

  Get Planned Outdoor Access Points Positions.

• DELETE <cluster-ip>/dna/intent/api/v1/outdoorAreas/{outdoorAreaId}/plannedAccessPointPositions/{id}

  Delete Outdoor Planned Access Point Position.

• POST <cluster-ip>/dna/intent/api/v1/outdoorAreas/{outdoorAreaId}/plannedAccessPointPositions/assignAccessPointPositions

  Assign Planned Access Points to operations ones.

• POST <cluster-ip>/dna/intent/api/v1/outdoorAreas/{outdoorAreaId}/plannedAccessPointPositions/bulk

  Bulk change Planned Outdoor Access Point Positions.

• POST <cluster-ip>/dna/intent/api/v1/outdoorAreas/{outdoorAreaId}/plannedAccessPointPositions/bulkChange

  Bulk change Planned Outdoor Access Point Positions.

• GET <cluster-ip>/dna/intent/api/v1/outdoorAreas/{outdoorAreaId}/plannedAccessPointPositions/count

  Get Planned Outdoor Access Points Positions Count.

• POST <cluster-ip>/dna/intent/api/v1/outdoorAreas

  Create outdoor area.

• GET <cluster-ip>/dna/intent/api/v1/outdoorAreas/{id}

  Get outdoor area.

• PUT <cluster-ip>/dna/intent/api/v1/outdoorAreas/{id}

  Update outdoor area.

• DELETE <cluster-ip>/dna/intent/api/v1/outdoorAreas/{id}

  Delete outdoor area.

• POST <cluster-ip>/dna/intent/api/v1/outdoorAreas/{id}/uploadImage

  Upload outdoor area image.

• GET <cluster-ip>/dna/intent/api/v1/maps/accessPointAntennas

  Get Supported Access Point and Antenna Information.

• GET <cluster-ip>/dna/intent/api/v1/maps/accessPointAntennas/count

  Get Supported Access Point and Antenna Information count.

To access the new Site Design API operations, click the menu icon and choose Platform > Developer Toolkit > APIs.

Expand the Site Management drop-down list and choose Site Design.

System Settings API Operations

With this release, Catalyst Center platform supports these API operations:

• GET <cluster-ip>/intent/api/v1/ipam/serverSetting/validationReports

  Retrieves the most recent sync/validation report.

• GET <cluster-ip>/intent/api/v1/ipam/serverSetting/exports

  Retrieves the most recent export report.

• POST <cluster-ip>/intent/api/v1/ipam/serverSetting/validationReports

  API to create external IPAM validation report. Compares pools between Catalyst Center and the external IPAM and identifies conflicting and non-conflicting pools.

• POST <cluster-ip>/intent/api/v1/ipam/serverSetting/exports

  Integrates the external IPAM to Catalyst Center and exports the selected pools to the external IPAM server.

To access the new System Settings API operations, click the menu icon and choose Platform > Developer Toolkit > APIs.

Wireless API Operations

With this release, Catalyst Center platform supports these new Wireless API operations:

• POST <cluster-ip>/dna/intent/api/v1/wirelessSettings/wlanSchedulers

  Create WLAN scheduler.

• GET <cluster-ip>/dna/intent/api/v1/wirelessSettings/wlanSchedulers

  Get all WLAN schedulers.

• GET <cluster-ip>/dna/intent/api/v1/wirelessSettings/wlanSchedulers/${id}

  Get WLAN scheduler by ID.

• DELETE <cluster-ip>/dna/intent/api/v1/wirelessSettings/wlanSchedulers/${id}

  Delete WLAN scheduler.

• GET <cluster-ip>/dna/intent/api/v1/wirelessSettings/wlanSchedulers/count

  Get WLAN scheduler count.

• GET <cluster-ip>/dna/intent/api/v1/wirelessControllers/regulatoryActivations

  Download Regulatory Activation File.

• POST <cluster-ip>/dna/intent/api/v1/wirelessControllers/regulatoryActivations

  Upload Regulatory Activation File.

• DELETE <cluster-ip>/dna/intent/api/v1/wirelessControllers/regulatoryActivations

  Delete Regulatory Activation File.

• POST <cluster-ip>/dna/intent/api/v1/wirelessControllers/regulatoryActivations/${fileId}/deploy

  Deploy Regulatory Activation File.

To access the new Wireless API operations, click the menu icon and choose Platform > Developer Toolkit > APIs.

Expand the Connectivity drop-down list and choose Wireless.

In this release, Catalyst Center platform supports new Beta API operations. To access them, click the menu icon and choose Platform > Developer Toolkit > APIs.

Note

You can identify the Beta API operations by the "BETA" banner on the GUI or the x-rapi-banner field within the swagger documentation.

Compliance API Operations

The deviceRoles attribute is included in the request payload of these API operations. This helps you specify the roles of the network devices to which the rule applies. If value is not provided, the rule will apply to all device roles.

• POST <cluster-ip>/dna/intent/api/v1/compliancePolicys/${policyId}/rules

  Create a new rule.

• PUT <cluster-ip>/dna/intent/api/v1/compliancePolicys/${policyId}/rules/${id}

  Update an existing rule.

• GET <cluster-ip>/dna/intent/api/v1/compliancePolicys/${policyId}/rules/${id}

  Retrieve a specific rule.

• GET <cluster-ip>/dna/intent/api/v1/compliancePolicys/${policyId}/rules

  Retrieve the rules.

potentialNoticeCount is added as a query parameter in these API operations:

• GET <cluster-ip>/dna/intent/api/v1/fieldNotices/results/networkDevices/count

  Get count of field notice network devices.

• GET <cluster-ip>/dna/intent/api/v1/fieldNotices/results/networkDevices

  Get field notice network devices.

With this release, matchRemediationCommandsLanguage, matchRemediationCommands, doesNotMatchRemediationCommandsLanguage, and doesNotMatchRemediationCommands attributes are added in the query of these API operations:

• POST <cluster-ip>/dna/intent/api/v1/compliancePolicys/${policyId}/rules/${ruleId}/conditions

  Create a new condition.

• PUT <cluster-ip>/dna/intent/api/v1/compliancePolicys/${policyId}/rules/${ruleId}/conditions/${id}

  Update an existing condition.

With this release, matchRemediationCommandsLanguage, matchRemediationCommands, doesNotMatchRemediationCommandsLanguage, and doesNotMatchRemediationCommands attributes are available in the response of these API operations:

• GET <cluster-ip>/dna/intent/api/v1/compliancePolicys/${policyId}/rules/${ruleId}/conditions/${id}

  Retrieve a specific condition.

• GET <cluster-ip>/dna/intent/api/v1/compliancePolicys/${policyId}/rules/${ruleId}/conditions

  Retrieve the conditions.

With this release, remediationSupported attribute is available in the response of this API operation:

• GET <cluster-ip>/dna/intent/api/v1/compliance/networkDevices/${networkDeviceId}/detail/policys

  Retrieve the violating policies.

The Compliance Details of Device, Device Compliance Status, Get Compliance Detail, and Get Compliance Status API operations now support the Non-Compliant, Compliant, and Compliant with Warning states.

Devices API Operations

With this release, these network device API operations include a new ENUM REACHABILITY_RECOVERED error code which indicates that a device has successfully transitioned from unreachable to reachable status.The syncProgress and fullSyncDuration attibutes are also included in the response.

• GET <cluster-ip>/dna/intent/api/v1/networkDevices/${id}

  Get details of a single network device.

• POST <cluster-ip>/dna/intent/api/v1/networkDevices/query

  Query network devices with filters.

• GET <cluster-ip>/dna/intent/api/v1/networkDevices

  Retrieve network devices.

With this release, filter keys support is extended to these API operations:

• GET <cluster-ip>/dna/intent/api/v1/networkDevices/query/count

  Count the number of network devices with filters.

• GET <cluster-ip>/dna/intent/api/v1/networkDevices/query

  Query network devices with filters.

Device Replacement API Operation

An optional string parameter called configKey is included for the ‘SWITCH’ and ‘ROUTER’ types in the query of this API operation:

• POST <cluster-ip>/dna/intent/api/v1/networkDeviceReplacements/workflow/deploy

  Deploy device replacement workflow.

LAN Automation API Operations

With this release, there are new enhancements to the existing LAN Automation API operations to support OSPF-based underlay configuration, in addition to the existing IS-IS underlay support. The routingProtocol, processId, areaId, authenticationKey and advertiseLANAutomationRoutesIntoBGP OSPF-related parameters are introduced in the request and response schemas of these API operations:

• POST <cluster-ip>/dna/intent/api/v2/lan-automation

  LAN Automation Start V2.

• GET <cluster-ip>/dna/intent/api/v1/lan-automation/status

  LAN Automation status.

• GET <cluster-ip>/dna/intent/api/v1/lan-automation/status/${id}

  LAN Automation Status by ID.

Network Settings API Operations

These API operations now support RADIUS_OVER_DTLS and TACACS_OVER_TLS protocol.

• PUT <cluster-ip>/dna/intent/api/v1/sites/${id}/aaaSettings

  Set AAA settings for a site.

• GET <cluster-ip>/dna/intent/api/v1/sites/${id}/aaaSettings

  Retrieve AAA settings for a site

  Note

  In these API operations, the primaryServerName and secondaryServerName attributes are introduced to facilitate SAN configuration on the device.

• GET <cluster-ip>/dna/intent/api/v1/authentication-policy-servers

  Get authentication and policy servers.

• POST <cluster-ip>/dna/intent/api/v1/authentication-policy-servers

  Add authentication and policy server access configuration.

• PUT <cluster-ip>/dna/intent/api/v1/authentication-policy-servers

  Edit authentication and policy server access configuration.

  Note

  These API operations now support RADIUS over DTLS and TACACS+ over TLS, introducing the radiusDtlsPort, radiusDtlsIdleTimeout, tacacsTlsPort, and tacacsTlsIdleTimeout attributes, along with the AAA-only radiusDtlsCert and tacacsTlsCert attributes; the serverName attribute has also been added for AAA and ISE configurations.

SDA API Operations

During the migration of a fabric site from LISP BGP to LISP PUBSUB, Catalyst Center platform now supports migration segmentation protocols for fabric sites, virtual networks, and transits to indicate the current stage of migration for each fabric entity.

Each fabric site can now return PHASE_1 or PHASE_2 as networkProtocol value in the response of these API operations:

• GET <cluster-ip>/dna/data/api/v1/fabricSiteHealthSummaries

  Read list of Fabric Sites with their health summary.

• GET <cluster-ip>/dna/data/api/v1/fabricSiteHealthSummaries/${id}

  Read Fabric Sites with health summary from ID.

Each virtual network can now return HYBRID as the networkProtocol value in the response of these API operations:

• GET <cluster-ip>/dna/data/api/v1/transitNetworkHealthSummaries

  Read list of Transit Networks with their health summary.

• GET <cluster-ip>/dna/data/api/v1/transitNetworkHealthSummaries/${id

  Read transit network with its health summary from ID.

• GET <cluster-ip>/dna/data/api/v1/virtualNetworkHealthSummaries

  Read list of Virtual Networks with their health summary.

• GET <cluster-ip>/dna/data/api/v1/virtualNetworkHealthSummaries/${id}

  Read virtual network with its health summary from ID.

This release provides enhanced health visibility for Wireless LAN Controllers (WLCs) in multisite fabric deployments.

The wirelessControllerGoodHealthPercentage, wirelessControllerTotalHealthDeviceCount, wirelessControllerPoorHealthDeviceCount, wirelessControllerFairHealthDeviceCount and wirelessControllerNoDataDeviceCount attributes are now available in the response of these fabricSiteHealthSummariesAPI operations:

• GET <cluster-ip>/dna/data/api/v1/fabricSiteHealthSummaries

  Read list of Fabric Sites with their health summary.

• GET <cluster-ip>/dna/data/api/v1/fabricSiteHealthSummaries/${id}/trendAnalytics

  The Trend analytics data for a fabric site in the specified time range.

• GET <cluster-ip>/dna/data/api/v1/fabricSiteHealthSummaries/count

  Read fabric site count.

• GET <cluster-ip>/dna/data/api/v1/fabricSiteHealthSummaries/${id}

  Read Fabric Sites with health summary from ID.

Site Design API Operation

System Settings API Operations

This update extends the IpamProvider schema by introducing BLUECAT_V2API as a new enum value, allowing clients to configure BlueCat v2 as an external IPAM provider. BLUECAT_V1API continues to be supported for now but is planned for deprecation in a future release.

Task API Operation

OccurrenceCount and RepeatInterval attributes are included in the response of the Get activities by ID API operation. This addition extends support to recurring schedules via the Intent API.

Wireless API Operations

With this release, these wireless profile API operations now include "wlanProfileName": "trialSSIDProfile" in the response for mapping wlans to SSIDs.

• GET <cluster-ip>/dna/intent/api/v1/wirelessProfiles

  Get wireless profiles.

• POST <cluster-ip>/dna/intent/api/v1/wirelessProfiles

  Create wireless profile.

• GET <cluster-ip>/dna/intent/api/v1/wirelessProfiles/${id}

  Get wireless profile by ID.

• PUT <cluster-ip>/dna/intent/api/v1/wirelessProfiles/${id}

  Update wireless profile.

• DELETE <cluster-ip>/dna/intent/api/v1/wirelessProfiles/${id}

  Delete wireless profile.

• GET <cluster-ip>/dna/intent/api/v1/wirelessProfiles/count

  Get wireless profiles count.

With this release, these wireless profile API operations now include the macSecSetting object in the query to support MACsec (Media Access Control Security) configuration for AP authentication.

• POST <cluster-ip>/dna/intent/api/v1/wirelessSettings/apProfiles

  Create AP Profile.

• GET <cluster-ip>/dna/intent/api/v1/wirelessSettings/apProfiles

  Get AP Profiles.

• GET <cluster-ip>/dna/intent/api/v1/wirelessSettings/apProfiles/${id}

  Get AP Profile by ID.

• PUT <cluster-ip>/dna/intent/api/v1/wirelessSettings/apProfiles/${id}

  Update AP Profile by ID.

With this release, the Get RF Profiles, Update RF Profile, Get RF Profile by ID and Create RF Profile API operations now include minDbsWidth and maxDbsWidth attributes under the 5-GHz radioTypeAProperties schema. The default value for both fields is 40. For 6-GHz, the minDbsWidth and maxDbsWidth values default to 80.

The Wireless PDC and MDC API operations are streamlined by removing unused attributes, including Layer 2 VTP. They now support AP Priming with related child profiles and matchServerIdentities under TACACS servers.