How to Display Interferers on Cisco Prime Infrastructure Maps?
An administrator receives reports of many interferes in the wireless network and wants to get these interferes' location from the maps in Cisco Prime Infrastructure. When looking at the floor plans/maps, the administrator does not see any interferes but can see all wireless clients located successfully. What must be configured to get the location?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests MSE interferer tracking configuration for Prime Infrastructure maps, and the trap is assuming that because clients are located, all location services are already fully configured.
To display interferers on Cisco Prime Infrastructure floor maps, you must enable interferer tracking on the MSE. This guide explains why option B is correct and why client location visibility already rules out MSE or NMSP problems.
A common mistake is choosing option A (add MSE and synchronize), because the fact that wireless clients appear on maps proves the MSE is already added and synchronized.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The MSE performs all location calculations for Cisco Prime Infrastructure, including client, rogue, and interferer tracking. Client location is already working, which proves the MSE is properly integrated, synchronized, and communicating with the WLC via NMSP. However, interferer tracking is a separate feature that is not enabled by default. To see interferers on Prime Infrastructure floor maps, you must explicitly enable interferer tracking on the MSE, as described in option B. Once enabled, CleanAir-capable APs will report interferer data to the MSE, and the interferers will appear on the maps.Why the Other Options Are Wrong
Option A is wrong because the MSE is already added and synchronized—otherwise clients would not be located. Option C is wrong because NMSP communication with the WLC is already functioning for client location, so there is no need to activate it. Option D is wrong because SNMP between Prime Infrastructure and the WLC is used for monitoring and management, not for computing or displaying interferer location. None of these options address the missing interferer tracking configuration.Community Comment Notes
The community consensus strongly supports option B. As rrahim explained, the MSE is responsible for location services, and interferer tracking must be explicitly enabled. McMurphy provided a direct quote from the Cisco MSE configuration guide: "Select the Enable check box to enable tracking of the interferers by the mobility services engine." This confirms the exact setting needed. MaxMusti also confirmed the provided answer was correct. All comments align with the technical analysis that enabling interferer tracking on the MSE is the required step.Official Reference
Exam Strategy
When location is partially working (e.g., clients appear but interferers do not), isolate the missing device type and check its specific tracking configuration on the MSE. Always verify basic connectivity (MSE added, NMSP active) before assuming a complex integration problem.
Frequently Asked Questions
Why is enabling interferer tracking on the MSE necessary?
By default, the MSE tracks clients and rogue devices but not interferers; you must explicitly enable interferer tracking to see them on Prime Infrastructure maps.
If clients are already located, why is option A (add MSE) incorrect?
Successful client location proves the MSE is already added, synchronized, and communicating via NMSP, so no additional MSE integration is required.