A corner of a ward suddenly goes weak and clients there drop. Coverage-hole detection is available on the controller. An engineer waits for the next cloud AI-RRM cycle to raise power. What should react to this corner?
Select an answer to reveal the explanation.
Short Explanation
The corner went weak now, and the cloud cycle is not the reflex for that. Your controller can run coverage-hole detection for a local drop like this. A guest password will not turn the power up.
Full Explanation
AI-Enhanced RRM plans channel, power, and width in the cloud on a cycle. A sudden coverage hole is time-sensitive, and coverage-hole detection on the controller is the feature built to react locally. Waiting only for the next cloud cycle leaves the ward corner down in the meantime. Coverage-hole detection can raise power. That is the point of it. Resetting a guest account does not change radio power. A shorter beacon adds airtime overhead. It does not fill a hole where the signal itself collapsed. A corner suddenly goes weak. Coverage-hole detection on the controller reacts locally. Waiting for the cloud AI-RRM cycle is the wrong tool for that moment. Check one live client after the change and leave the rest of the floor alone until that client matches the result you expected. Read the live counters after you retest. Exam caveat: a hole caused by a dead access point is not fixed by raising a neighbor until the dead radio is restored. See whether the access point in that corner is still joined. Operational check: confirm coverage-hole detection is enabled, reproduce the weak corner, and see whether the neighboring radio raises power without waiting for the cloud cycle.