Release Notes for Cisco Catalyst Center 2.3.7.x on ESXi
Catalyst Center on ESXi is a form factor that supports Catalyst Center in a virtual environment. The virtual form factor helps customers rapidly deploy and operate Catalyst Center. For customers who are running Cisco Prime Infrastructure on a virtual machine (VM), Catalyst Center on ESXi provides a migration path to take advantage of Catalyst Center features.
This document describes the features, limitations, and bugs for Catalyst Center on ESXi.
![]() Note |
|
Change history
The following table lists changes to this document since its initial release.
Date |
Change |
Location |
---|---|---|
2025-08-28 |
Added the list of packages in Catalyst Center 2.3.7.10 on ESXi. |
|
Added the open bugs for Catalyst Center 2.3.7.10 on ESXi. |
||
Added the resolved bugs for Catalyst Center 2.3.7.10 on ESXi. |
||
2025-07-21 |
Noted general availability of the Catalyst Center 2.3.7.9.70301.10 software maintenance update. |
|
2025-06-12 |
Added information about the 2.3.7.9.75403.10 software maintenance update. |
|
2025-05-28 |
Updated the unsupported features information and added data migration information. |
|
2025-04-04 |
Updated the System package version from 2.7.72 to 2.7.74 in Catalyst Center 2.3.7.9 on ESXi. The change contains a fix for CSCwo37187. |
Package versions |
2025-03-25 |
Added information about 2.3.7.7-75902-CSCwn89323.SMU. |
|
2025-02-27 |
Added the list of packages in Catalyst Center 2.3.7.9 on ESXi. |
|
Added the open bugs for Catalyst Center 2.3.7.9 on ESXi. |
||
Added the resolved bugs for Catalyst Center 2.3.7.9 on ESXi. |
||
2024-11-18 |
Added the list of packages in Catalyst Center 2.3.7.7 on ESXi. |
|
Added the resolved bugs for Catalyst Center 2.3.7.7 on ESXi. |
||
2024-08-30 |
Updated with information about Catalyst Center 2.3.7.6 on ESXi. |
— |
2024-04-08 |
Updated with information about Catalyst Center 2.3.7.5 on ESXi. |
— |
2023-12-20 |
Initial release. |
— |
Package versions
Package Name |
Release 2.3.7.10 |
Release 2.3.7.9 |
Release 2.3.7.7 |
Release 2.3.7.6 |
Release 2.3.7.5 | Release 2.3.7.4 | ||
---|---|---|---|---|---|---|---|---|
Release Build Version |
||||||||
Release Version |
2.3.7.10.75226 |
2.3.7.9.75403.10 |
2.3.7.9.75335 |
2.3.7.7-75902- CSCwn89323.SMU |
2.3.7.7.75051 |
2.3.7.6.75360 |
2.3.7.5.75367 |
2.3.7.4.75326 |
System Updates | ||||||||
System |
2.7.77 |
2.7.74 |
2.6.57 |
2.6.54 |
2.5.64 |
2.3.132 |
||
System Commons |
2.723.65398 |
2.722.65506 |
2.722.65411 |
2.720.66038 |
2.720.65100 |
2.718.65458 |
2.715.65430 |
2.714.65447 |
Package Updates |
||||||||
Access Control Application |
2.723.65398 |
2.722.65506 |
2.722.65411 |
2.720.66038 |
2.720.65100 |
2.718.65458 |
2.715.65430 |
2.714.65447 |
AI Endpoint Analytics |
1.11.1426 |
1.11.1325 |
1.11.1186 |
1.11.1180 |
1.11.1148 |
1.11.919 |
1.11.726 |
|
AI Network Analytics |
3.3.67 |
3.3.59 |
3.3.58 |
3.1.41 |
3.1.41 |
3.1.39 |
3.1.30 |
|
Application and Service Remediation |
2.0.2 |
2.0.2 |
— |
— |
— |
— |
||
Application Hosting |
2.3.225072904 |
2.3.224120911 |
2.3.124050804 |
2.3.124050804 |
2.3.124020205 |
2.3.123120506 |
||
Application Visibility and Policy |
2.723.117889 |
2.722.118005 |
2.722.117961 |
2.720.117585 |
2.718.117879 |
2.715.1175429 |
2.714.1175142 |
|
Assurance |
2.370.10157 |
2.370.9218 |
2.370.9216 |
2.370.7007 |
2.370.7003 |
2.370.6243 |
2.370.5148 |
2.370.4191 |
Assurance - Sensor |
2.370.10143 |
2.370.9219 |
2.370.9176 |
2.370.7002 |
2.370.6211 |
— |
— |
|
Automation - Intelligent Capture |
2.723.65398 |
2.722.65506 |
2.722.65411 |
2.720.66038 |
2.720.65100 |
2.718.65458 |
2.715.65430 |
2.714.65422 |
Automation - Sensor |
2.723.65398 |
2.722.65506 |
2.722.65411 |
2.720.66038 |
2.720.65100 |
2.718.65458 |
— |
— |
Catalyst Center API Catalog |
6.7.110 |
6.7.93-1 |
6.7.93 |
6.6.50 |
6.6.50 |
6.5.142 |
— |
|
Cisco Catalyst Center Global Search |
6.7.6 |
6.7.6 |
6.6.4 |
6.6.3 |
6.6.3 |
6.5.14 |
6.3.8 |
|
Cisco Catalyst Center Platform |
6.7.120 |
6.7.53 |
6.6.53 |
6.6.51 |
6.6.40 |
6.5.185 |
6.3.138 |
|
Cisco Catalyst Center Pre Upgrade |
1.0.5 |
— |
— |
— |
— |
— |
||
Cisco Catalyst Center UI |
3.4.254 |
3.4.253 |
3.3.176 |
3.3.176 |
3.2.350 |
3.1.69 |
||
Cisco Identity Services Engine Bridge |
2.723.5 |
2.719.12 |
2.719.11 |
2.716.90701 |
2.716.90701 |
2.715.90505 |
2.714.90200 |
|
Cloud Connectivity |
6.5.22 |
6.5.21 |
6.4.33 |
6.4.33 |
6.3.18 |
6.1.45 |
||
Cloud Connectivity - Contextual Content |
6.7.4 |
6.7.4 |
6.5.8 |
6.5.8 |
6.4.18 |
6.2.15 |
||
Cloud Connectivity - Digestor |
6.7.6 |
6.7.5 |
6.6.2 |
6.6.2 |
6.4.15 |
6.2.10 |
||
Core-Addons |
0.9.21 |
0.9.20 |
0.8.11 |
0.8.10 |
— |
— |
||
Core Platform |
0.9.106 |
0.9.103 |
0.8.100 |
0.8.96 |
0.7.78 |
0.5.200 |
||
DxHub Cloud Connectivity |
6.7.18 |
6.7.17 |
6.6.35 |
6.6.35 |
6.5.16 |
6.3.14 |
||
Gateway |
0.9.13 |
0.9.11 |
0.8.13 |
0.8.13 |
— |
— |
||
Group-Based Policy Analytics |
3.10.3 |
3.9.11 |
3.7.100 |
3.7.6 |
— |
— |
||
Identity and Access Management |
5.3.32 |
5.3.27 |
5.3.26 |
5.2.35 |
5.2.35 |
5.1.21 |
4.0.33 |
|
Identity and Access Management - UI |
5.3.18 |
5.3.17 |
5.2.15 |
5.2.15 |
5.1.12 |
3.1.11 |
||
Multiple Cisco Catalyst Center |
2.723.65398 |
2.722.65411 |
2.720.65100 |
2.718.65458 |
2.715.65430 |
2.714.65422 |
||
Network Controller Platform |
2.723.65398 |
2.722.65506 |
2.722.65411 |
2.720.66038 |
2.720.65100 |
2.718.65458 |
2.715.65430 |
2.714.65422 |
Network Data Platform - Base Analytics |
2.370.1000211 |
2.370.950205 |
2.370.750149 |
2.370.750050 |
2.370.60118 |
2.370.50207 |
2.370.40107 |
|
Network Data Platform - Caching Infra |
6.5.9 |
6.5.8 |
6.4.7 |
6.4.6 |
6.3.22 |
6.2.8 |
||
Network Data Platform - Core |
6.5.518 |
6.5.515 |
6.4.510 |
6.4.509 |
6.3.513 |
6.2.34 |
||
Network Data Platform - Ingestion Infra |
6.5.14 |
6.5.14 |
6.4.3 |
6.4.3 |
6.3.44 |
6.2.17 |
||
Network Data Platform - Manager |
6.5.1 |
6.5.1 |
6.4.3 |
6.4.3 |
6.3.103 |
6.2.13 |
||
Network Data Platform - Pipeline Infra |
6.5.523 |
6.5.521 |
6.4.521 |
6.4.521 |
6.3.522 |
6.2.27 |
||
Network Data Platform - Storage Management |
6.5.36 |
6.5.31 |
6.4.15 |
6.4.9 |
6.3.51 |
6.2.54 |
||
RCA-Scripts Package |
0.3.7 |
0.3.7 |
0.2.2 |
0.2.2 |
0.2.2 |
0.1.11 |
||
Rogue and aWIPS |
2.9.1015 |
2.9.812 |
2.9.809 |
2.9.652 |
2.9.651 |
2.9.605 |
2.9.408 |
2.9.210 |
SD-Access |
2.723.65398 |
2.722.65506 |
2.722.65411 |
2.720.66038 |
2.720.65100 |
2.718.65458 |
2.715.65430 |
2.714.65422 |
Shared Managed Services |
0.9.5 |
0.9.5 |
0.8.8 |
0.8.8 |
— |
— |
||
Stealthwatch Security Analytics |
2.723.1095236 |
2.722.1095263 |
2.720.1095090 |
2.718.1095210 |
— |
— |
||
System Management Operations |
1.5.23 |
1.5.20 |
1.4.52 |
1.4.52 |
1.3.51 |
1.1.1108 |
||
System Remediation |
— |
— |
1.1.0 |
1.1.0 |
1.0.1 |
— |
||
Telemetry |
3.6.9 |
3.6.8 |
3.5.14 |
3.5.14 |
3.4.14 |
3.2.18 |
||
Wide Area Bonjour |
2.723.755007 |
2.722.755006 |
2.720.755002 |
2.718.77018 |
— |
— |
Features
New and changed features
New and changed features for Catalyst Center 2.3.7.10 on ESXi
Catalyst Center 2.3.7.10 on ESXi has no new features.
New and changed features for Catalyst Center 2.3.7.7 on ESXi
Catalyst Center 2.3.7.7 on ESXi has no new features.
New and changed features for Catalyst Center 2.3.7.6 on ESXi
Feature |
Description |
---|---|
Group-Based Policy Analytics (VA) |
This feature is now supported on ESXi VA. Group-Based Policy Analytics is an application on Catalyst Center that helps administrators visualize group-to-group interactions, and helps to build policies by using discovered ports and protocols used between groups. For information, see the Cisco Catalyst Center User Guide, Release 2.3.7.x. |
Wide-Area Bonjour |
This feature is now supported on ESXi VA. Cisco Wide Area Bonjour enables global service routing beyond a single IP gateway for traditional LAN and WLAN networks. For information, see the Cisco Wide Area Bonjour Application on Cisco Catalyst Center User Guide. |
Stealthwatch Security Analytics (SSA) |
This feature is now supported on ESXi VA. The Stealthwatch Security Analytics service on Catalyst Center, in conjunction with Cisco Stealthwatch, provides real-time monitoring of all network traffic. For information, see the Stealthwatch Security Analytics Service 2.3.7.x User Guide. |
1800S Sensor Support on Assurance (VA) |
This feature is now supported on ESXi VA. Assurance supports the 1800S sensor. This feature includes wireless performance analytics, real-time client troubleshooting, and proactive health assessment. For information, see the Cisco Catalyst Assurance User Guide, Release 2.3.7.x. |
New and changed features for Catalyst Center 2.3.7.5 on ESXi
Catalyst Center 2.3.7.5 on ESXi has no new features.
New and changed features for Catalyst Center 2.3.7.4 on ESXi
Feature |
Description |
---|---|
Default Single Network Interface Card (NIC) |
By default, one NIC is enabled when you install Catalyst Center 2.3.7.4 as a virtual appliance on ESXi. See "Deploy a Virtual Appliance" for setup instructions in the Cisco Catalyst Center 2.3.7.x on ESXi Deployment Guide. |
Second NIC Installation (Day-N) |
As an option, after you install Catalyst Center 2.3.7.4 on ESXi, you can add an additional NIC to your deployment. For information, see "Configure an Additional Network Adapter" in the Cisco Catalyst Center 2.3.7.x on ESXi Deployment Guide. |
ESXi Launcher App Enhancements |
You can configure a virtual appliance using the ESXi Launcher App in interactive mode or silent mode. For information, see the following topics in the Cisco Catalyst Center 2.3.7.x on ESXi Deployment Guide.
|
Diagnostics Center Validation Tool |
The validation tool ( ) is supported with some limitations. |
Unsupported features
Catalyst Center 2.3.7.x on ESXi supports all of the features that Catalyst Center supports, except for the following features:
-
Automation: Cisco DNA Traffic Telemetry Appliance.
-
Wireless: Cisco User-Defined Network (UDN), Cisco Umbrella.
-
Setting Page: Authentication API Encryption.
-
Telemetry: VM- and host-level telemetry.
-
System Performance APIs: The following APIs aren't supported:
-
/dna/intent/api/v1/diagnostics/system/performance
-
/dna/intent/api/v1/diagnostics/system/performance/history
-
VA requirements
Catalyst Center on ESXi is intended for enterprise environments, such as manufacturing or education, where a large-scale requirement is present within a single physical environment.
The following requirements must be met in order to successfully deploy a Catalyst Center on ESXi virtual appliance. For performance tips that cover the most performance-critical areas of VMware vSphere, see:
-
VMware vSphere Client 7.0: Performance Best Practices for VMware vSphere 7.0 (PDF)
-
VMware vSphere Client 8.0: Performance Best Practices for VMware vSphere 8.0 (PDF)
Feature | Description |
---|---|
Virtualization platform and hypervisor |
VMware vSphere (which includes ESXi and vCenter Server) 7.0.x or later, including all patches |
Processors |
Intel 2.1-GHz and above CPU 32 vCPUs with 64-GHz reservation must be dedicated to the VM |
Memory |
256-GB DRAM with 256-GB reservation must be dedicated to the VM |
Storage |
3-TB solid-state drive (SSD) If you plan to create backups of your virtual appliance, also reserve additional datastore space. For information, see "Backup Server Requirements" in the Cisco Catalyst Center on ESXi Administrator Guide. |
IO Bandwidth |
180 MB/sec |
IOPS |
2000-2500 |
Latency |
Catalyst Center on ESXi to network device connectivity: 200 ms |
Guidelines and limitations
Catalyst Center on ESXi has these guidelines and limitations.
-
Virtual machines do not support SD-Access business APIs.
-
In 2.3.7.6, the API rate limit policies that are documented in the official API documentation aren’t enforced. As a result, users might exceed the recommended API request limits without being automatically throttled or blocked by the system with an error response 429.
While exceeding the API rate limits is not recommended, it is unlikely to cause immediate service disruption or security vulnerabilities. However, excessive API usage could lead to:
-
Performance degradation: High API request volumes could impact the overall performance of the Catalyst Center platform, potentially causing slower response times or temporary unavailability.
-
Resource contention: Increased API activity could consume additional system resources, affecting other platform functions or user experiences.
-
Unexpected behavior: In some cases, exceeding the API rate limits could trigger unexpected platform behavior or errors.
To ensure optimal platform performance and stability, we recommend that you adhere to the documented API rate limit policies.
-
-
For Group-Based Policy Analytics, the summary for the 24-hour and 12-hour Sankey charts isn't available in Catalyst Center on ESXi.
-
Unlike the Catalyst Center platform, you cannot connect VMs to create three-node clusters. To achieve high availability, you need to use VMware vSphere. For more information, see the "High Availability" section in the Cisco Catalyst Center on ESXi Administrator Guide.
-
Catalyst Center on ESXi does not support the following VMware vSphere features:
-
Fault tolerance
-
Suspending and resuming VMs
-
Cloning VMs
-
Snapshot (as backup)
-
-
With Catalyst Center on ESXi, application telemetry is not supported for Cisco Catalyst 9500 Series Switches.
-
To configure the Management interface and the Enterprise interface, manually create a virtual machine using the VMware vSphere UI and then configure both interfaces using either the Maglev Configuration wizard or the Install Configuration wizard. For more information, see the "Deploy a Virtual Appliance" section in the Cisco Catalyst Center on ESXi Deployment Guide.
Multiple Catalyst Centers—Limited Availability
Multiple Catalyst Center allows you to define a single global set of virtual networks for software-defined access across multiple Catalyst Center clusters integrated with a single Cisco ISE system. This Multiple Catalyst Center functionality is a Limited Availability offering in Catalyst Center on ESXi.
To facilitate global administration of Cisco SD-Access across multiple Catalyst Center clusters with a consistent set of virtual networks, the Multiple Catalyst Center feature leverages the existing secure connection with Cisco ISE to propagate virtual networks, Security Group Tags (SGTs), access contracts, and Group-Based Access Control (GBAC) Policy from one cluster to another cluster, all integrated with the same Cisco ISE deployment. Cisco ISE takes the information learned from one cluster (the Author node) and propagates it to the other clusters (Reader nodes).
Because there are significant caveats for the Multiple Catalyst Center functionality, the Cisco SD-Access Design Council reviews the requests and provides guidance for use of the Multiple Catalyst Center to participants in the Limited Availability program.
Contact your account team to submit a request to the Cisco SD-Access Design Council to participate in the Limited Availability program.
Customers who are using Cisco ISE Version 3.1 or earlier must request and install the Limited Availability package before enabling Multiple Catalyst Center.
![]() Note |
After this functionality is enabled, it can be disabled only by deleting Cisco ISE. In addition, if this functionality is enabled, because pxGrid is a required component of the solution, pxGrid cannot be disabled subsequently. |
Deploy Catalyst Center on ESXi
For information about how to deploy Catalyst Center in a VMware vSphere environment, see the Cisco Catalyst Center on ESXi Deployment Guide. The guide also covers configurations we recommend you make before you use the product.
Data migration
For more information about how to migrate data from a Catalyst Center hardware appliance to a Catalyst Center on ESXi virtual appliance, see "Scenario 16: Migrate data to a Catalyst Center on ESXi virtual appliance" in the Cisco Catalyst Center Data Migration Guide.
Bugs
Open bugs
This table lists high-severity open bugs in Catalyst Center on ESXi for this release.
![]() Note |
You can use the Cisco Bug Search Tool to search for a specific bug or to search for all open bugs in this release. To search for a documented Cisco product issue, type in the browser: <bug_number> site:cisco.com |
Bug identifier | Headline |
---|---|
For Catalyst Center 2.3.7.10 on ESXi, external authentication fallback is not enabled by default. |
Resolved bugs
Catalyst Center 2.3.7.10 on ESXi
This table lists the resolved bugs in the Catalyst Center 2.3.7.10 on ESXi.
Bug identifier | Headline |
---|---|
Unable to back up and restore from Catalyst Center Release 2.3.7.9 to Catalyst Center Release 3.1.3 because it gets stuck. |
|
An IPv6 Catalyst Center on ESXi cluster upgrade from Catalyst Center Release 2.3.7.7 to Catalyst Center Release 2.3.7.9 failed with an Access Control Application (ACA) chart download error. |
|
The dnacaap-app-services package upgrade failed. |
|
A back up and restore from a Catalyst Center appliance to Catalyst Center on ESXi failed because of legacy ES indices. |
|
After logging in to the Catalyst Center GUI with valid credentials, the system returns an invalid page with the 404 error of "Not Found". |
|
The OID is visible in Catalyst Center on ESXi but not in the Catalyst Center appliance. |
Catalyst Center 2.3.7.7-75902-CSCwn89323.SMU Software Maintenance Upgrade on ESXi
This table lists the resolved bugs in Catalyst Center 2.3.7.7-75902-CSCwn89323.SMU (software maintenance update) on ESXi.
![]() Note |
|
Bug Identifier |
Headline |
---|---|
CSCwj55104 and CSCwk74459 |
After upgrading Catalyst Center 2.3.5.3 to 2.3.7.5, Cisco Catalyst 9800 Series wireless controller provisioning fails with this error:
|
SWIM update operations on a tagged golden image with add-ons succeed, but Catalyst Center indicates that the device software image is noncompliant, and on the Inventory window, the OS Update Status field lists Activation Pending. |
|
The Catalyst Center Image Repository may indicate that no images are available for a managed device family, even though the files have actually been uploaded. |
|
In a 1+1+1 disaster recovery setup running Cisco DNA Center 2.3.5.5, user-defined templates may not be displayed as expected after a failover to the recovery site. |
|
Disabling application telemetry on a wireless controller results in this error:
|
|
After a software upgrade of Cisco Industrial Ethernet 2000 Series switches, some of these switches were booted up from an SD card instead the local device flash. Since the current running configuration was not copied to the SD cards, these devices started up without the configuration. |
|
The RAPI client offset ranges from 1 to 10,000 clients, even though Catalyst Center supports more than 10,000 clients. |
|
Unable to receive rogue and aWIPS event notifications after restarting RabbitMQ. |
|
OUI download doesn't work when the schemaregistry service is down. |
|
The PoE dashboard Estimated AP Power Saving tile indicates that no power has been consumed, even though PoE-capable devices are connected to Assurance. |
|
In a Catalyst Center 2.3.7.6 instance deployed as a virtual machine, searching for a wired client by username may result in a page that cites an undefined error. |
|
After running a Catalyst Center migration script on a backup server and restoring the corresponding backup file to a Catalyst Center VA on ESXi, the migration may fail with this error:
|
|
When Catalyst Center upgrades the Cisco IOS XE software on Cisco Catalyst IE3400H Series switches, the file is configured on the internal flash memory device (flash:) instead of the external SD flash card (sdflash:). |
|
Unable to view API documentation after backing up a second-generation Catalyst Center appliance and restoring the backup file to a three-node cluster of XL third-generation appliances. |
|
Can't enable application telemetry for a wireless profile whose name contains a space. |
|
Migration of IPv4 pools to IPv6 pools fails. Fabric edge devices don't receive IPv6 configurations after migrating from a single-stack pool to a dual-stack pool. |
|
After upgrading to Catalyst Center 2.3.7.6, notifications are not sent after a device unreachable event in Assurance has been resolved. |
|
When upgrading from either Catalyst Center 2.3.5.5 or 2.3.5.6 to 2.3.7.6, unable to upgrade the base-provision-core:2.1.718.60779 package. |
|
After upgrading to Catalyst Center 2.3.7.6, a NullPointerException error occurs when provisioning a Cisco SD-Access fabric with virtual network anchoring configured. |
|
After upgrading to Catalyst Center 2.3.7.6.70319-CSCwn31915.SMU, an unknown error occurs after trying to import a subordinate CA certificate. |
|
After upgrading to Catalyst Center 2.3.7.x, this error occurs when starting LAN automation:
|
|
A DeviceInterfaceInfo migrator exception occurs when the device owning entity ID can't be found. |
|
Removing an inherited virtual network removes the wireless controllers from the anchor site LISP configuration. |
|
Unable to migrate from Catalyst Center 2.3.7.7 to Catalyst Center 2.3.7.7 on ESXi by running the migration script. |
|
Kafka drops topology messages larger than 1 MB, resulting in missing topology exports. |
|
MongoDB's endpoint-analytics folder is bloated, which can cause backups to fail or result in disk utilization errors for MongoDB. |
|
A deleted template is not removed from the cache after a disaster recovery failover. |
|
Authentication and policy servers ignore read-only parameters. |
|
Cisco IMC firmware version checks are not working properly in Catalyst Center 2.3.7.7. |
|
After upgrading to Catalyst Center 2.3.7.7-70047-CSCwn89323.SMU, a NullPointerException error occurs when provisioning a Cisco SD-Access fabric with virtual network anchoring configured. |
Catalyst Center 2.3.7.7 on ESXi
This table lists the resolved bugs in Catalyst Center 2.3.7.7 on ESXi.
Bug Identifier |
Headline |
---|---|
Wireless controller provisioning fails for the policyprofile_bk key constraint. |
|
When you create a template in the Catalyst Center CLI Templates, hints may not show for variables in the provisioning workflow. |
|
"pipelineruntime-taskmgr-spa-apps" encounters an out of memory error due to a large SXPBindings string. |
|
The System Certificates window displays the EJBCA Service as unavailable to complete the service request. |
|
When you generate a report that uses authentication and choose to receive it by email, the report is generated successfully, but no email is received. |
|
The upgrade workflow fails because an error occurred during the polling of the device ISSU activation status. |
|
When you view traffic for security groups on the Group-Based Access Control window, no matching records are found. |
|
A client summary report fails to generate when Group By is chosen for the area. |
|
You can't place an AP on the floor map when another AP that's configured with an ultra wide band radio is also placed on the same floor map. |
|
With the IP Address Manger, deleting a FIAB from the fabric takes a long time. |
|
Most fabric provisioning tasks are blocked because the border autonomous system number is 65540. |
|
When performing an image update readiness check, the following message for the file transfer check may display:
|
|
You can't LAN automate the 10G/25G interface with the C9400-SUP-1XL-Y supervisor as the device to be onboarded. |
|
After an upgrade to Catalyst Center 2.3.7.x, LAN automation may try to reuse the allocated IP address of the overlapping pool. |
|
The Catalyst Center REST API for the managed device count may return a 404 error. |
|
When trying to provision a device, it gets stuck in the configuring state. |
|
Credentials can't be updated because of too many unreachable devices. |
|
When starting a Catalyst Center LAN automation session, the network orchestration service triggers exit code 137. |
|
Wireless LAN controller provisioning (or the config preview of what is to be provisioned) may fail when managed locations are only at the floor level with a site-level override. |
|
When a static port assignment is completed or an assigned port is cleared, "macro auto global processing" is pushed to the fabric edge node. |
|
While upgrading a node, the release download precheck fails because of a kubelet certificate issue. |
|
Wireless controller provisioning fails and displays the following error message:
|
|
The Link Add feature may assign duplicate IP addresses if the pool specified is an overlapping pool and the devices are LAN automated using the overlapping pool. |
|
The automated lambda request isn't triggered. No error messages are displayed and no audit logs are captured in the provisioning service. |
|
Wireless controller provisioning may fail with the following error message:
|
|
Fabric border provisioning fails because of the following error:
|
|
An Inventory report fails with a Catalyst Center scaled setup because of the API response time. |
|
The ThousandEyes Enterprise Agent Tests tab displays no data on Catalyst Center. |
|
The Catalyst Center 2.3.7.3 on ESXi maglev account is locked in the system manager service. |
|
A port assignment may fail and display the following error message:
|
|
Catalyst Center tries to push an unexpected IPv6 configuration without IPv6 pools added to the fabric. |
Catalyst Center 2.3.7.6 on ESXi
There are no resolved bugs in Catalyst Center 2.3.7.6 on ESXi.
Catalyst Center 2.3.7.5 on ESXi
This table lists the resolved bugs in Catalyst Center 2.3.7.5 on ESXi.
Bug Identifier |
Headline |
---|---|
Client data and AP health aren't displayed in the Assurance Custom Dashboard Library. |
|
Under scale conditions, the Catalyst Center on ESXi UI is not accessible for several hours while restoring data. |
|
When the managed service is restored, the mongo database is restored in the end. |
|
An event doesn't trigger an email notification. |
|
PnP fails to onboard an AP. |
|
The first time you display the Fabric site table, it displays only 10 sites. |
|
Login fallback, although enabled, fails to function when an external TACACS authorization timeout occurs. |
|
Email notification for reports includes a link that contains the management IP address instead of the Enterprise IP address. |
|
Cisco Wireless AireOS Controller is unable to send Cisco AireOS Network Assurance telemetry due to an unauthorized JSON Web Token (JWT). |
|
Import of the System Certificate in the wrong file format causes IOS-XE-based devices to be reported as not managed in Assurance. |
|
When using TACACs for external authentication with a case-sensitive username that contains mixed or uppercase letters, authentication succeeds, but the browser enters a redirect loop between login and home page. |
Catalyst Center 2.3.7.4 on ESXi
This table lists the resolved bugs in Catalyst Center 2.3.7.4 on ESXi.
Bug Identifier |
Headline |
---|---|
When a user performs an advanced fresh installation with a proxy server for authentication, the installation fails, and the proxy server details are not set in the KVstore yaml in kvstore.config.cluster file. |
Communications, services, and additional information
-
To receive timely, relevant information from Cisco, sign up at Cisco Profile Manager.
-
To get the business impact you’re looking for with the technologies that matter, visit Cisco Services.
-
To submit a service request, visit Cisco Support.
-
To discover and browse secure, validated enterprise-class apps, products, solutions, and services, visit Cisco DevNet.
-
To obtain general networking, training, and certification titles, visit Cisco Press.
-
To find warranty information for a specific product or product family, access Cisco Warranty Finder.
Cisco Bug Search Tool
Cisco Bug Search Tool (BST) is a gateway to the Cisco bug-tracking system, which maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. The BST provides you with detailed defect information about your products and software.
Documentation feedback
To provide feedback about Cisco technical documentation, use the feedback form available in the right pane of every online document.
Related documentation
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)