A hospital uses Cisco Spaces for floor maps, and the maps stay empty. The controller is not sending location information toward Spaces. Which integration is missing?
Select an answer to reveal the explanation.
Short Explanation
Spaces cannot draw people it never hears about. Your maps are empty because the location feed from the wireless network is not arriving. The SIEM log is a different pipe, and a channel number is not a floor plan.
Full Explanation
Cisco Spaces builds location and maps from location data it receives from the wireless infrastructure. If the controller or the connected wireless system is not sending that information, the maps stay empty even though clients are on the network. The missing integration is that location feed. An RF tag binds radio profiles. It does not draw a floor plan from channel numbers, and channel assignment is not a coordinate. A guest anchor tunnels guest traffic to a DMZ. It does not store map coordinates, and guest termination is unrelated to whether Spaces hears RSSI reports. Syslog to a SIEM is an event archive for the NOC. Spaces does not use that SIEM feed as its map source. Sending syslog and sending location are two integrations, and only the location path fills the maps. Exam caveat: a feed that arrives for the wrong site or the wrong floor still looks empty on the map you are staring at. Confirm the map is the one those access points were placed on. Operational check: verify the location connection from the wireless system to Spaces, then walk a test client and confirm the dot moves on the correct floor.