About Release Notes
![]() Note |
Cisco DNA Spaces is now Cisco Spaces. We are in the process of updating our documentation with the new name. This includes updating GUIs and the corresponding procedures, screenshots, and URLs. For the duration of this activity, you might see occurrences of both Cisco DNA Spaces and Cisco Spaces. We take this opportunity to thank you for your continued support. |
We recommend that you use the latest version of Cisco Spaces: Connector. To migrate from connector 2.x to connector 3, see Migrate from Connector 2.x to Connector 3.
This release notes document describes what is new or changed, instructions to install or upgrade to the latest version of the Cisco Spaces: Connector, and open and resolved caveats for each release. Unless otherwise noted, in this document, Cisco Spaces: Connector is referred to as connector.
Introduction to Connector 3
Cisco Spaces: Connector Release 3 (subsequently referred to as Connector 3) is a fully redesigned version of the Cisco Spaces: Connector Release 2.x, with the capability to efficiently manage multiple services that connect to different network devices such as wireless controllers, access points (APs), and switches. connector gathers and aggregates data from these devices and sends the data to Cisco Spaces.
With connector 3, you can do the following:
-
Add or remove new services from Cisco Spaces.
-
Perform advanced troubleshooting with the debugging, log upload, and restart functionalities in Cisco Spaces.
-
Obtain detailed metrics for each service, such as, CPU, memory, connectivity, and up or down status.
-
Configure Virtual IP address (VIP) pairs or active-active pairs that allow for high availability. You can view details of each instance that is a part of a high-availability pair.
-
Monitor connector 3 and device status that are aggregated from each instance of connector.
-
View how services are running on each instance, their upgrade status, and so on.
-
Perform actions on an instance, such as restarting of services.
-
Configure instances for connector. Device status is aggregated from each connector instance for monitoring.
Connector 3 sends data to Cisco Spaces over HTTPS; a proxy can also be used to route data.
See Initial Setup, Upgrading the Connector, and Migrating from Connector 2.x to Connector 3.
![]() Note |
The term wireless controller is used in this document to collectively refer to the following:
|
Upgrade Path for Release 3
From Version |
To Version |
Upgrade Method |
---|---|---|
Sep 2022 |
July 2024 |
Use the connectoros upgrade command. |
Nov 2022 |
July 2024 |
Use the connectoros upgrade command. |
Jan 2023 |
July 2024 |
Use the connectoros upgrade command. |
May 2023 |
July 2024 |
Use the connectoros upgrade command. |
Jan 2024 |
July 2024 |
Use the connectoros upgrade command. |
May 2024 |
July 2024 |
Use the connectoros upgrade command. |
Compatibility Matrix for Cisco Spaces: Connector: Location service
Hardware or Application Name |
Support for Cisco Spaces: Connector |
||
---|---|---|---|
Cisco AireOS Wireless Controller |
|
||
Cisco Catalyst 9800 Series Wireless Controllers |
|
||
Cisco Embedded Wireless Controller on Cisco Catalyst Access Points (Cisco EWC-AP) |
Supported versions are:
Supported access points are:
|
||
Cisco Catalyst 9300 and 9400 Series Switches |
Supported versions are 17.3.3 and later | ||
Cisco Prime Infrastructure |
Supported | ||
Catalyst Center | Supported | ||
Cisco Spaces: IoT Service |
|
||
Supported wireless controllers for Cisco FastLocate |
|
||
Supported wireless controllers for Cisco Hyperlocation |
|
||
Connector Active-Active Mode |
|
||
Tested VMware Environments |
|
||
Tested Proxies |
|
||
Tested Access Points for Cisco FastLocate |
|
||
Tested Access Points for Cisco FastLocate (Wi-Fi 6) |
|
||
Tested Access Points for Cisco Hyperlocation |
|
||
Tested Access Points |
|
Compatibility Matrix for IoT Service (Wireless)
Application Name |
Support for Cisco Spaces: IoT Service |
||
---|---|---|---|
Supported wireless controllers |
|
||
Cisco Spaces: Connector Docker |
2.0.455 and later |
||
Cisco Spaces: Connector OVA |
2.3 and later |
||
Cisco Prime Infrastructure |
Cisco Prime Infrastructure Release 3.8 MR1 and later |
||
Catalyst Center (for map import) |
Catalyst Center Release 2.1.1 and later |
||
Access Points for advanced BLE gateway (Wi-Fi 6) |
|
||
Access points for basic BLE gateway |
|
||
Cisco IOx App Version |
1.0.46 and later
|
IoT Service is not supported on the following:
-
Directly connected and CMX Tethering connectors.
The following table lists the compatibility of the Advanced BLE Gateway for BLE and the Base BLE Gateway App with various AP modes. This table is not applicable to Cisco Embedded Wireless Controller on Cisco Catalyst Access Points (Cisco EWC-AP).
AP Mode |
Advanced BLE Gateway App |
Base BLE Gateway App |
---|---|---|
PI: Local |
|
|
P1: Flex |
|
|
P2: Fabric |
|
|
P3: Mesh |
|
|
Compatibility Matrix for IoT Service (Wired)
Application Name |
Support for IoT Service (Wired) |
---|---|
Cisco Spaces: Connector Docker |
2.0.455 and later |
Cisco Spaces: Connector OVA |
2.3 and later |
Cisco Prime Infrastructure |
Cisco Prime Infrastructure Release 3.8 MR1 |
Catalyst Center (for map import) |
Catalyst Center Release 2.1.1 and later |
Switch as a gateway |
Cisco IOS XE Amsterdam 17.3.x and later releases. |
Wired Application Version |
1.0.46 and later |
IoT service (wired) is not supported with Cisco Spaces tenants or deployments leveraging the following configurations:
- Connecting directly with controller
- CMX Tethering
Related Documentation
Cisco Spaces: Connector3 Configuration Guide
Cisco Spaces: Connector3 Command Reference Guide
Release Notes for Cisco Spaces: Connector
Release Notes for Cisco Spaces