Cisco Spaces
Cisco Spaces is the next generation indoor location services platform. The Network Mobility Services Protocol (NMSP) cloud-service of the wireless controller communicates with Cisco Spaces using HTTPS as a transport protocol.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco Spaces is the next generation indoor location services platform. The Network Mobility Services Protocol (NMSP) cloud-service of the wireless controller communicates with Cisco Spaces using HTTPS as a transport protocol.
Follow the procedure given below to configure Cisco Spaces:
Configure DNS—To resolve fully qualified domain names used by NMSP cloud-services, configure a DNS using the ip name-server server_address configuration command as shown in Step 2.
Import 3rd party root CAs—The controller verifies the peer and the host based on the certificate that is sent by the CMX when a connection is established. However, root CAs are not preinstalled on the controller. You have to import a set of root CAs trusted by Cisco to the trustpool of the crypto PKI by using the crypto pki trustpool import url <url> configuration command as shown in Step 3.
A successful registration to Cisco Spaces is required to enable server url and server token parameters configuration which is needed to complete this setup.
Command or Action | Purpose | |
---|---|---|
Step 1 |
configure terminal Example:
|
Enters global configuration mode. |
Step 2 |
ip name-server namesvr-ip-addr Example:
|
Configures the DNS on the controller to resolve the FQDN names used by the NMSP cloud-services. |
Step 3 |
crypto pki trustpool import url url Example:
|
Imports the 3rd party root CA. The controller verifies the peer using the imported certificate. |
Step 4 |
[no] nmsp cloud-services server url url Example:
|
Configures the URL used for cloud services. Use the no form of the command to delete the server url from the configuration. |
Step 5 |
[no] nmsp cloud-services server token token Example:
|
Configures the authentication token for the NMSP cloud service. Use the no form of the command to delete the server token from the configuration. |
Step 6 |
[no] nmsp cloud-services http-proxy proxy-server port Example:
|
(Optional) Configures HTTP proxy details for the NMSP cloud service. Use the no form of the command to disable the use of a HTTP proxy. |
Step 7 |
[no] nmsp cloud-services enable Example:
|
Enables NMSP cloud services. Use the no form of the command to disable the feature. |
Use the following commands to verify the Cisco Spaces configuration.
To view the status of active NMSP connections, use the following command:
Device# show nmsp status
MSE IP Address Tx Echo Resp Rx Echo Req Tx Data Rx Data Transport
----------------------------------------------------------------------------
9.9.71.78 0 0 1 1 TLS
64.103.36.133 0 0 1230 2391 HTTPs
To view the NMSP cloud service status, use the following command:
Device# show nmsp cloud-services summary
CMX Cloud-Services Status
-------------------------
Server: https://yenth8.cmxcisco.com
IP Address: 64.103.36.133
Cmx Service: Enabled
Connectivity: https: UP
Service Status: Active
Last Request Status: HTTP/1.1 200 OK
Heartbeat Status: OK
To view the NMSP cloud service statistics, use the following command:
Device# show nmsp cloud-services statistics
CMX Cloud-Services Statistics
-----------------------------
Tx DataFrames: 3213
Rx DataFrames: 1606
Tx HeartBeat Req: 31785
Heartbeat Timeout: 0
Rx Subscr Req: 2868
Tx DataBytes: 10069
Rx DataBytes: 37752
Tx HeartBeat Fail: 2
Tx Data Fail: 0
Tx Conn Fail: 0
To view the mobility services summary, use the following command:
Device# show nmsp subscription summary
Mobility Services Subscribed:
Index Server IP Services
----- --------- --------
1 209.165.200.225 RSSI, Info, Statistics, AP Monitor, AP Info
2 209.165.200.225 RSSI, Statistics, AP Info