Prime Infrastructure Client Data Stale by Five Minutes?

Troubleshoot client connectivity

Answer Correct answer: C — Enable client Assoc/Disassoc and Auth/Deauth SNMP traps on the controller so Prime Infrastructure receives immediate client state and AP updates.

An engineer attempts to troubleshoot client connectivity issues in Cisco Prime Infrastructure. The Cisco Prime Infrastructure GUI is performing as expected, but the client detail information that is displayed is not current. The displayed client state and connected AP are up to 5 minutes old. Which action resolves this issue?

Change the data retention settings to 5 seconds.
Use a different browser to access the web interface.
Enable client Assoc/Disassoc and Auth/Deauth SNMP traps on the controller. Correct Answer
Optimize the Cisco Prime Infrastructure database.

Community Votes

75%

25%

75% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The exam tests why Prime Infrastructure wireless client detail lags and relies on WLC event traps, with the trap being that database tuning or browser changes seem plausible but do not fix the five-minute polling delay.

Cisco Prime Infrastructure can display client state and connected AP information up to five minutes old when controller client SNMP traps are missing; this page establishes that enabling Assoc/Disassoc and Auth/Deauth traps (C) restores near-real-time client detail.

Selecting database optimization (D) because stale data sounds like a performance bottleneck; however, compacting or optimizing the PI database improves general responsiveness, not the specific five-minute delay caused by missing client Assoc/Disassoc and Auth/Deauth traps.

Community Discussion (3 comments)

rrahim 👍 1 Selected: C

The issue described is that the client detail information in Cisco Prime Infrastructure (PI) is not current and is delayed by up to 5 minutes. This delay is often caused by the lack of real-time updates from the Wireless LAN Controller (WLC) to Cisco PI. Enabling client Assoc/Disassoc and Auth/Deauth SNMP traps on the WLC ensures that Cisco PI receives immediate notifications about client connection and disconnection events, providing up-to-date client information.

Gumpy1 👍 1 Selected: D

D is correct, follow this link and search for "compact the Prime Infrastructure Database", under How to improve the performance of Prime Infrastructure. https://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-4/admin/guide/bk_CiscoPrimeInfastructure_3_4_AdminGuide/bk_CiscoPrimeInfastructure_3_4_AdminGuide_chapter_0100.html

robi1020 👍 2 Selected: C

The issue described suggests that the client detail information displayed in Cisco Prime Infrastructure (PI) is not current and is up to 5 minutes old. To resolve this issue, one needs to ensure that Cisco Prime Infrastructure is receiving real-time updates regarding client states and connected access points. The correct action to resolve this issue is: C. Enable client Assoc/Disassoc and Auth/Deauth SNMP traps on the controller. Enabling client Assoc/Disassoc and Auth/Deauth SNMP traps on the controller allows the controller to send real-time notifications to Cisco Prime Infrastructure whenever clients associate, disassociate, authenticate, or deauthenticate from the wireless network. This ensures that Cisco Prime Infrastructure has up-to-date information about client connectivity status and the access points they are associated with. Therefore, option C is the appropriate action to resolve the issue of outdated client detail information in Cisco Prime Infrastructure.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Prime Infrastructure's client detail page depends on WLC event information; if client association, disassociation, authentication, and deauthentication SNMP traps are not enabled on the controller, PI learns client state only during its periodic polling cycle, producing the observed five-minute staleness. Enabling those traps pushes session changes to PI almost immediately, so the displayed client state and connected AP become current without changing retention, browser, or database settings. The symptom is specific to client data rather than the entire GUI, which matches a missing trap path rather than a resource problem. As robi1020 and rrahim note, the delay points to lack of real-time updates from the WLC to Prime Infrastructure.

Why the Other Options Are Wrong

Changing data retention to 5 seconds affects how long PI stores historical data, not how quickly live client session events arrive; it can even increase database load. A different browser would address GUI rendering or compatibility issues, but the question states the GUI performs as expected, so browser choice cannot explain a consistent five-minute client-state lag. Optimizing or compacting the PI database may improve general performance and report responsiveness, and Gumpy1 points to Cisco's database-compaction guidance, but that guidance does not target the precise client/AP five-minute staleness caused by absent client traps. Database maintenance could be useful for unrelated slowness, yet it does not make PI receive client state changes in real time.

Community Comment Notes

The useful comments by robi1020 and rrahim converge on option C, explaining that without client Assoc/Disassoc and Auth/Deauth traps PI lacks immediate notifications about client connectivity. Gumpy1 votes D and references Cisco's documentation on compacting the Prime Infrastructure database, which is a legitimate performance task but is aimed at general database health. That distinction matters: the exam scenario isolates client detail freshness, not overall GUI or database responsiveness. So the community majority is directionally right, while the dissenting database advice addresses a different failure mode.

Official Reference

https://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-4/admin/guide/bk_CiscoPrimeInfastructure_3_4_AdminGuide/bk_CiscoPrimeInfastructure_3_4_AdminGuide_chapter_0100.html

Exam Strategy

When a PI symptom is limited to client detail freshness, look for the event-delivery path first: the WLC client traps must be enabled. Broad remedies such as database optimization or browser changes affect the whole GUI and are distractors. Match the five-minute interval to PI's default polling behavior when client traps are absent.

Frequently Asked Questions

Why isn't optimizing the Prime Infrastructure database the right fix?

Database optimization addresses general PI slowness, not the specific five-minute delay in client state and AP detail. That delay is eliminated by receiving client Assoc/Disassoc and Auth/Deauth traps from the WLC.

What do client Assoc/Disassoc and Auth/Deauth SNMP traps change in Prime Infrastructure?

They push near-real-time client session events from the controller to PI instead of PI waiting for its periodic polling cycle, so the client detail page reflects current state and connected AP.

Related Analysis

← Back to 300-430 Study Guide