OVERVIEW
This Cisco validated runbook is designed only as a follow on from the Spaces OS Runbook. If you have not completed that runbook yet, please go back and ensure that the deployment has been validated against that before continuing here.
With the standard expectation of users to always be connected to the internet no matter where they are, it is paramount that users can be connected securely and seamlessly. Wi-Fi onboarding allows users a frictionless onboarding experience and a seamless handover when roaming between cellular and Wi-Fi.
OpenRoaming enables secure, seamless, and automatic network connectivity by eliminating tedious Wi-Fi guest onboarding processes and the risk of connecting to rogue SSIDs. This is especially helpful for a mobile device user trying to access the internet because OpenRoaming removes the need to choose between multiple SSIDs, or enter insecure, shared credentials on poorly designed captive portals.
This runbook will look at OpenRoaming to onboard customers. For information about integrating with Carrier Offload with Partner Apps (such as AT&T Auto-Attach), please refer to the Knowledge Article: Carrier Offload with a Partner App (AT&T Auto-Attach)
SUPPORT AND ONBOARDING
Please follow the link below to find out about the different ways to get support for Cisco Spaces.
PREREQUISITES
This runbook should only be used as a follow on from the Spaces OS Runbook. All the prerequisite steps are covered in the Spaces OS runbook and should be completed before progressing here.
Namely, OpenRoaming requires the following prerequisites met:
-
An active Cisco Spaces account.
-
A Cisco wireless network. Both controller-based (Cisco AireOS or Cisco Catalyst wireless controller) and cloud-based (Cisco Meraki) networks are supported.
-
Add the wireless network to your Cisco Spaces account.
-
For controller-based architecture, the Cisco Spaces Connector must be used.
-
For Cisco Meraki networks, add the Cisco Meraki account to your Cisco Spaces account.
-
OpenRoaming Prerequisites
Network Components
|
C9800 WLC*1 |
-16.12.1 or above
|
|
AireOS WLC* |
- Only AireOS 8.10.x supported
|
|
Meraki |
-Wi-Fi 7, Wi-Fi 6E, Wi-Fi 6 APs: R31.1.6 and above -Wi-Fi 5, Wave 2 APs: R30.7.2 and above -Admin access required for Meraki Account to activate SSID for OpenRoaming -At least one unconfigured SSID on Meraki Dashboard in “Disabled state” If you do not meet one or more of the above prerequisites, you can manually activate OpenRoaming on your Meraki network by installing a Cisco Spaces Connector. In this scenario, please raise a support case for deployment support and describe your scenario. |
|
Cisco Spaces Connector2 |
-Highly Recommended version 3.x -Minimum version 2.3.2 or above. Starting December 2023 Connector 2.x entered software maintenance mode. Security updates will continue through June 2024 and support for critical bug fixes will continue through October 2024. ( EoL Notice ) |
|
CMX Tethering |
Not Supported |
|
AP Support |
All 9100 Series Access Points Catalyst Wave 1 and Wave 2 Access Points All MR Wi-Fi 5 wave 2 (that can be upgraded to at least MR 31.1.6), Wi-Fi 6 and Wi-Fi 6E APs |
1 Embedded Wireless Controller (EWC) on Catalyst 9100 and the Embedded Wireless on Catalyst 9000 switches are NOT supported.
2 Cannot be configured with HTTP/HTTPS proxy enabled.
-
See WLC release notes for supported APs per release
OpenRoaming Client Matrix
|
Device Support |
-Samsung Devices: Android 10 or higher -Google Pixel: Android 11 or higher -Apple devices running iOS 13.3 or higher |
|
OS Support |
-Apple devices running iOS 13.3 or higher -Android phones running Android 9 or higher |
|
Cisco Spaces SDK |
-iOS 13.3 or higher -XCode version 12 or higher -Android 9 or higher |
|
Service Providers (today) |
-T-Mobile -AT&T -Comcast |
SSID broadcasting must be enabled for OpenRoaming to function
OpenRoaming Firewall Rules
In addition to ports opened to allow basic functionality, OpenRoaming will require a security policy configured on the network firewall to allow inbound traffic. By default, all inbound traffic is disallowed.
IMPLEMENTATION
To complete these steps, an admin will require read/write permissions within Spaces for OpenRoaming and DNA Spaces, as well as read/write access to Meraki Dashboard and/or WLC, and read access to connector for verification.
With the prerequisites covered, implementing OpenRoaming requires four main steps:
-
Create an OpenRoaming Profile
-
Enable Hotspot Connector
-
Configure Network Controller
-
Configure the OpenRoaming SSID
Each of the main steps will be discussed.
Create an OpenRoaming Profile
An OpenRoaming profile contains information about the network SSID and specifies which user identities are allowed to access the guest network. You can also configure carrier offload in the OpenRoaming profile.
To create an OpenRoaming profile, the following substeps need to be performed:
Substep 1: Set Access Policy
Substep 2: Configure an SSID
Substep 3 (Optional): Configure Carrier Offload
Substep 4: Review and Confirm Settings
Click here for a video guided demo
Set Access Policy
Set your policy on who can access your OpenRoaming network.
-
Go to OpenRoaming app within Cisco Spaces Dashboard.
Access the OpenRoaming App
Or alternatively, through the side-menu by clicking the Dashboard drag-down.
-
Click on Setup. If this is the first time that you are setting up OpenRoaming, when you click Setup, a Terms and Conditions dialog box is displayed. Click I Agree to proceed.
-
In the OpenRoaming Profiles section, click Create OpenRoaming Profile.
The Create an OpenRoaming Profile configuration wizard is displayed.
-
Click Proceed.
-
Under Access Policy, specify who can access your OpenRoaming network. Select the types of identities that can access the OpenRoaming network as well as if real identities are required.
The options available are:
i) Accept all authenticated users: This is the default option.
ii) Accept only users who provide their identity: An example of an accepted identity is a real identity, such as an email ID.
iii) Accept users with specified identity types: Choose the desired identity types from the list that is displayed. Enable the Require real identity knob if you want users to enter their real identities. The identity types chosen here is displayed adjacent to their real or anonymous identity settings, in a table next to this list.
iv) Accept only your users: If you choose this option, you will need to be added as an identity provider.
-
Under Preferred Credentials, choose the desired option from those listed below by clicking the corresponding radio button. This option will set your policy on who can access your OpenRoaming network:
i) I do not have preferred credentials
If you have selected Accept only your users in the Access Policy section, this option will be disabled.
ii) I have preferred credentials, which I want to use: If you choose this option, you must select a domain from the list of domains that are displayed or click Add a Custom Domain.
-
Click Continue.
The SSID Details window is displayed.
Configure an SSID
Enter the SSID details for this OpenRoaming Profile - this is a secure SSID different from your guest SSID.
-
In the SSID Details section, enter the SSID name in the corresponding field. This is the SSID that will be broadcast for OpenRoaming.
For Catalyst and AireOS deployments, if the name that you enter is an existing SSID, ensure that the SSID name is an exact match of what is in the network.
For Meraki deployments, a new unique SSID name must be used. You must have a unused SSID available.
-
(Optional) In the Advanced section, you can choose among the following options by clicking the corresponding radio button:
i) Default Status: Choose between Enable or Disable by clicking the corresponding radio button. The default option is Enable.
ii) Fast Transition (802.11r): Choose between Adaptive, Enable or Disable by clicking the corresponding radio button. The default option is Adaptive.
802.11r is to significantly reduce the length of time that connectivity is interrupted between a mobile device and Wi-Fi infrastructure.
When 'Enable' is selected, the controller allows all clients to use Fast Transition, even if they don't support it.
The 'Adaptive' option enables Fast Transition only for clients that support it. The controller will dynamically determine which clients are Fast Transition capable and allow them to use Fast Transition. Clients that do not support Fast Transition will fall back to regular reauthentication processes.
The Create an OpenRoaming Profile configuration wizard is displayed.
-
Click Next.
The Carrier Offload window is displayed.
Review and Confirm Settings
Review and confirm the OpenRoaming profile configuration.
After you have configured the access policy, SSID, and the optional carrier offload, you can review your OpenRoaming profile configuration and modify it if required before saving these settings.
-
In the Review Your Configuration window, verify the settings and do one of the following:
By default, the OpenRoaming profile name is the same as the SSID name. You can choose to retain the OpenRoaming profile name as the SSID name or modify the profile name.
i) If you are satisfied with the configuration, proceed with the next step by clicking Done.
ii) If you have to make changes, click the Edit link next to the section whose configuration has to be modified and make changes. Continue to click Next until you arrive at the Review Your Configuration window. On successful modification of the OpenRoaming Profile configuration, proceed with the next step by clicking Done.
-
Click Done to complete the creation of the OpenRoaming profile.
A success message appears briefly, and a confirmation window is displayed.
Enable Hotspot Connector
A Hotspot Connector is not usually needed for Meraki. This functionality is handled via APIs to Meraki cloud.
Meraki implementations should validated their API integration is active only.
Configure Network
Depending on your wireless network, follow the corresponding procedure to associate an OpenRoaming profile with the controller and configure the network:
Check Activation
Check the OpenRoaming activation status on Cisco Spaces dashboard:
If using Meraki, you can check client connection by navigating to Network-wide > Clients. Check the device is connected.
You can also validate the API calls were made from Space to Meraki to complete the activation in Organization > Monitor > Change Log
Test Your OpenRoaming Network
You can test your OpenRoaming network configuration through the following methods:
-
Cloud/Social: To use this method, download the OpenRoaming mobile app from the iOS App Store or Google Play Store to your mobile device.
-
Device Manufacturer: Use this method to test your OpenRoaming network natively on a Samsung or Google mobile device.
-
Other Methods: In addition to the above two methods, you can also test your OpenRoaming network using the following two options:
-
Carrier Offload: If you have set up a Carrier Offload solution, a mobile phone from the supported carrier will automatically get attached to your OpenRoaming network.
-
Cisco Spaces SDK: If you have integrated your brand’s mobile app with Cisco Spaces SDK, a mobile phone with your mobile app will automatically get attached to your OpenRoaming network.
For more information about Cisco Spaces SDK, see Knowledge Article: https://runbooks.ciscospaces.io/docs/openroaming-cisco-spaces-sdk-integration & Developer Docs: https://developer.cisco.com/docs/dna-spaces-sdk/. Log in using your Cisco credentials, if prompted.
-
View OpenRoaming Reports
To view your OpenRoaming reports, click > Home.
The following reports are available in the OpenRoaming dashboard:
-
Unique Devices
-
Devices by IDP
-
Devices by Manufacturer
-
Data Usage
-
Average Visit Duration
-
Data Consumed per User
-
Connections per Day
-
Connections per Hour
APPENDIX
Enable Hotspot on Cisco Spaces Connector 2.x
Cisco highly recommends using Spaces Connector 3.x. But if Hotspot needs to be enabled on Spaces Connector 2.x, follow the steps in this section.
Click here for a video guided demo [From 2:35min]
-
In the OpenRoaming window, click Set Up OpenRoaming or choose
> Setup.
If you have completed the OpenRoaming Profile configuration as per the previous Step 1, click Continue OR Setup in the configuration wizard to proceed.
The OpenRoaming Setup window is displayed.
A list of all the Cisco Spaces Connectors, along with their status is displayed in the Hotspot-enabled Connectors section.
-
Under the AireOS/Catalyst tab, click the Enable Hotspot for Connector(s) link.
The OpenRoaming - Add Hotspot window is displayed.
-
Select the Cisco Spaces Connector for which you want to enable the hotspot and click Continue.
-
A token is generated, and a Hotspot created successfully message is displayed. This token is used by the Cisco Spaces Connector to download the hotspot connector container.
-
Under Token Generated, click Copy.
-
Go to the web interface for the Cisco Spaces Connector
-
Click the Gear Icon and select Configure Token
-
Paste this token in the Configure Token window of the Cisco Spaces Connector GUI.
Note that a token can only be used once for a single Cisco Spaces connector.
If a token is used more than once, the hotspot-enabled connector will not work. If the connectors are in active-active mode and share a connector token, you will need different hotspot tokens for each connector.
-
Click Save.
The Connector will then download and install the Hotspot Connector image.
When a new software version of the hotspot container becomes available, the DMS service will notify the connector, and the connector will display the availability of the new software release in the connector UI. The upgrade process mirrors the process of a new install, except that no token configuration is required because it is already configured. Upgrade is a single click. The Connector downloads the new software release, stops the old container, and starts new container.
-
Refresh the OpenRoaming Setup window.
The new hotspot-enabled connector is now displayed in the listing in the Hotspot-enabled Connectors section. In the Hotspot tab, verify the status of the hotspot-enabled Connector. If the status is Running
REFERENCE
For more information about OpenRoaming in a Cisco Spaces setup, see the following documents:
For all Cisco Spaces documentation, see:
https://www.cisco.com/c/en/us/support/wireless/dna-spaces/series.html