Prerequisites of IoT Service (Wireless)
Cisco Spaces: Connector Scale and Size Guidance for IoT Service
This section guides you on choosing a size for the Connector based on your scale of your deployment, such as
-
number of APs in your network
-
the messages that the Connector may have to send, and
-
and the number of devices handled.
![]() Note |
|
![]() Note |
It is recommended to use the Advanced1 Connector sizing in most cases because IoT Wireless increases resource constraints. |
Connector Size | Scale |
---|---|
Standard Connector (2vCPU, 4 GB RAM) |
The Standard Connector can
|
Advanced1 Connector (4vCPU, 8 GB RAM) |
Advanced1 Connector can
|
Prerequisites
The following prerequisites can get you started with Cisco Spaces: IoT Service.
-
Install Cisco Spaces: Connector in your network.
-
Install a Cisco Catalyst 9800 Series Wireless Controller with a Cisco IOS XE 17.12.4 or 17.12.5 image version.
Note
There are significant improvements in Cisco Spaces: IoT Service on Cisco IOS XE 17.9.5. However, the minimum recommended version is Cisco IOS XE 17.9.6 for better performance.
-
Deploy supported APs in your network (see the Compatibility Matrix for IoT Service (Wireless)).
-
Ensure that Cisco Spaces is configured with maps either from Cisco Prime Infrastructure or Catalyst Center.
-
If the Cisco Spaces: Connector is an Amazon Elastic Compute Cloud (EC2) Instance from Amazon Machine Images (AMI), ensure that the wireless controller and connector are in the same virtual private cloud (VPC). Ensure that the wireless controller has a private IP address so that the security group of connector does not block the traffic, allowing enabled IOT streams to function.
-
Permit all the TCP traffic at the Virtual private clouds (VPC) level so that the Telemetry Data Logger (TDL) is established without any issues.
-
Before adding a Cisco Catalyst 9800 Series Wireless Controller to a connector, run the following commands on the Catalyst 9800 controller in a sequence:
-
aaa new-model
-
aaa authentication login default local
-
aaa authorization exec default local
-
-
Cisco Spaces: IoT Service and Intelligent Capture (iCAP) feature can now co-exist on Cisco Catalyst 9800 Series Wireless Controller Cisco IOS XE Cupertino 17.7.x release and later. For releases earlier than Cisco IOS XE Cupertino 17.7.x, disable iCAP, if already enabled on the controller.
-
Perform NTP synchronization over wireless controllers, a connector, and APs in the network.
-
If a USB BLE module is inserted in an AP, reboot the AP.
-
NETCONF must be enabled in Cisco Catalyst 9800 Series Wireless Controller in port 830, along with permission to use NETCONF.
Caution
The application (app) installed and running over the AP uses the default 17.17.0.0/16 subnet. So, using this subnet for other purposes might create network issues.
-
IPv6 is not supported on Cisco Spaces: Connector.
-
If your require two connectors installed with 3.x to work with IoT service (wireless) and function as a high-availability pair, you must configure the connectors as Virtual IP (VIP) pair.
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 |
3.x 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
|
![]() Note |
IoT Service (Wireless) is not supported with a directly connected controller, CMX Tethering, and AireOS connector. The only supported configuration is the Cisco Catalyst 9800 Wireless Controller and the connector. |
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 |
|
|