Prerequisites for Configuring the Cisco Spaces: Connector
-
Ensure that the necessary ports are open. See Information About Open Ports (Wireless).
-
Ensure that you explicitly allow https://www.cisco.com and cisco.com domains so that the Cisco Spaces: Connector can establish connections with these websites or domains.
-
Ensure that you explicitly allow https://cisco.openroaming.org. if you need to deploy OpenRoaming.
-
For Simple Network Management Protocol (SNMP) v2C and v3, you require read-write permissions for registering the Cisco Spaces: Connector certificate with the Cisco AireOS Wireless Controller.
-
If the Cisco Spaces: Connector is deployed as an AWS instance using AMI, ensure that controllers are reachable from the Connector. It is recommended that the controller and the Connector are in the same virtual private cloud (VPC). Ensure that the controller has a private IP address so that the security group of the Connector does not block the traffic allowing enabled IOT streams to function.
-
Permit all TCP traffic at the VPC level so that the TDL is established without any issues.
-
Disable Cisco Spaces connection services on a Cisco AireOS Wireless Controller before enabling the Cisco Spaces: Connector, using the config cloud-services cmx disable command.
-
Disable Cisco Spaces connection services on a Cisco Catalyst 9800 Series Wireless Controller before enabling the Cisco Spaces: Connector, by running these commands:
-
no nmsp cloud-services server url
-
no nmsp cloud-services server token
-
no nmsp cloud-services enable
-
-
The controller IP you configure in the Cisco Spaces dashboard must be able to reach the Cisco Spaces: Connector.
-
The Cisco Spaces: Connector requires access to a Domain Name System (DNS) server. If you configure an explicit proxy, the Cisco Spaces: Connector must be able to communicate using the proxy.
-
VMware ESXi 6.5 or later.
-
Virtual machine size: Standard option
-
Minimum bandwidth required: 4 Mbps (5000 APs, 60,000 clients).
Note
If you are using captive portals, we recommend a minimum bandwidth of 30 Mbps along with a buffer. The bandwidth allows for a good enduser experience while loading captive portals from Cisco Spaces.