Download and Deploy the Cisco Spaces Connector OVA

• STEP 1

  Download the Cisco Spaces Connector OVA from here: Cisco Spaces OVA

• STEP 2

  Deploy the downloaded Cisco Spaces OVA file on your virtual machine.

• STEP 3

  Once the OVA is deployed, you can log into the VMware console using the default username and password provided in the console.

• STEP 4

  Enter the network settings.
  

• STEP 5

  Enter NTP settings or leave it blank.

• STEP 6

  Set the password for the root user and dnasadmin user

  • The connector is operating in restricted mode, if they want root access in CLI that will be restricted. For security reasons the root access is disabled.
• STEP 7

  When prompted, reboot the device and open the WebUI using the address provided.

  

  NOTE:

  2.x will use dnasadmin
  3.x will use spacesadmin
  2.x and 3.x is selected when the customer selects the ova file download
  Connector Configuration guide: https://www.cisco.com/c/en/us/td/docs/wireless/cisco-dna-spaces/connector/config/b_connector/m_ova.html

Adding a Connector in Cisco Spaces

• STEP 1

  In the Cisco Spaces dashboard, click on “Setup” on the Menu
  

• STEP 2

  Select “Wireless Networks” ​
  

• STEP 3

  Click on “Get Started” button ​
  

• STEP 4

  Select “Cisco AireOS/Catalyst”
  

• STEP 5

  Select “via Spaces Connector”, then select “Continue Setup” button
  
  
  

• STEP 6

  Under step 2 “Configure Spaces Connector”, click on “Create Connector”
  
  

• STEP 7

  In the “Connector Name” field, enter a name for the connector and click on “Save”.
  
  

• Setting up the Cisco Spaces Connector

  You now need to copy the Connector token from Cisco Spaces dashboard and configure it in Spaces Connector VM GUI. Follow these steps to copy the Token:

• STEP 8

  On the Customized Setup page step 2 “Configure Spaces Connector”, click on “View Connectors”
  

• STEP 9

  You will see the list of Connectors you’ve created. Select the desired Connector.
  

• STEP 10

  Click on ‘Generate Token’

• STEP 11

  Copy the token that appears on the following screen of the Cisco Spaces dashboard
  

• STEP 12

  Launch the Cisco Spaces Connector using the HTTP address provided at the OVA deployment, https://< IP-address >/. In the Cisco Spaces Connector window that opens up, enter the username and password that was configured earlier.
  

• STEP 13

  (For a 2.3.x instance) on “Configure Token” click on ‘Setup’

• STEP 14

  (For a 2.3.x instance) Paste the generated token copied from Cisco Spaces dashboard and click “Save”. You may need to wait a few minutes for Cisco Spaces connector to start as images may take some time to download. The wait time is dependent on the speed of your connection
  

• STEP 15

  Once the Cisco Spaces Connector is displayed, you can observe the health of various connections, as illustrated in the image below:
  

  • Running: Status in the top-right indicates that the Cisco Spaces Connector is up and running.
  • Control Channel: Health of connection between Cisco Spaces Connector and Cisco Spaces Cloud.
  • Data Channel: Health of connection between Cisco Spaces Connector and Cisco Spaces Cloud.
  • Connector Details: NMSP connection between Cisco Spaces Connector and Cisco Wireless Controller (WLC).

Adding a Controller in Cisco Spaces

• STEP 1

  On the Customized Setup page step 3, click on “Add Controllers”
  

• STEP 2

  Select the Connector you’ve just created from the drop-down
  

• STEP 3

  Add the IP address of the Controller

• STEP 4

  Add the name of the Controller

• STEP 5

  Select Controller Type

• STEP 6

  Add details based on your controller type.

  For WLC (AireOS) – Select Controller SNMP version depending on your controller’s SNMP version. Read/Write permissions are needed for V2C and V3

  • For V2C SNMP, provide SNMP Community.
  • For V3 SNMP, provide username, password, select authentication Protocol and enter Privacy password.

  For Catalyst WLC / Catalyst 9800 – Add the following credentials

  • Enter Netconf Username and Password.
  • Enter Enable password of the controller.
  • Verify the interface: NMSP will only be sent from the interface configured as the “wireless management interface”. Interfaces used as a service-port (e.g., gig0/0 for an appliance) cannot send NMSP traffic.
• STEP 7

  Click “Save & Add Next Controller” if you want to add another controller. If not, Click “Save & Close”.

Import your Maps into the Location Hierarchy

After the Spaces Connector is configured and starts running, you need to import your locations into the location hierarchy.

• If you have maps in Cisco Prime or DNA Center version 1.3.1 & above, you may import locations in the same hierarchical structure as defined in Cisco Prime or DNA Center by importing the maps file from these products.
• If you don’t have maps on Cisco Prime or DNA Center version 1.3.1 & above, then you may import controllers in location hierarchy and manually group them into business locations on your Cisco Spaces dashboard.

Please Note: Cisco Prime/DNAC maps are required for Detect & Locate, Asset tracker, IoT services, and Proximity Reporting.

Please contact dnaspaces-onboarding@cisco.com if you don’t have DNA Center or Cisco Prime Maps

• STEP 1

  Import maps from Cisco Prime or sync from DNA Center.

  • For importing maps from Cisco Prime
    Here are the steps to download the maps file from Cisco Prime
  • To sync maps from DNA Center
    • Integrate DNAC with Cisco Spaces (version higher than 2.2.1.0)
      Here are the steps to Integrate with DNA Center

    
    

• STEP 2

  Go to Customized Setup page step 4 “Import Maps”, click on “Import/Sync Maps”
  

  Please select the respective product from where you want to import the maps.

  

  Upload the map file that you have downloaded from Cisco Prime or DNAC

  

  You have successfully connected your network with Cisco Spaces. You may now organize the Location Hierarchy.

  If you don’t have maps on Cisco Prime or DNA Center, then follow Step 3 to import controllers in location hierarchy and group APs into business locations manually in Cisco Spaces dashboard.

• STEP 3

  Go to Step 5 of Customized Setup page “Setup location hierarchy”, and click on “Add Locations”
  

  Please select “No, add location using AP prefix”

  

  Please choose the destination where you want to import controllers and click “Next”. (If you’re importing controllers for the first time, you will see the default location i.e. your Cisco Spaces account name. If not, you will also see the controllers that you had imported earlier)

  

  Choose the controller/networks you want to import and click “Finish”.

  • If the APs of the controllers are grouped as networks based on an existing naming convention, those network names will appear. If you want to retain the same grouping, just select the networks. However, if your APs are not grouped, network names will not be displayed.

  With Grouped Network names

  

  Without Network names

  

  You have successfully connected your network with Cisco Spaces. You may now organize the Location Hierarchy.