Enterprise users at the courthouse complain that every AP-to-AP walk feels like a full reconnect. Traces show PMK caching is disabled, forcing full EAP on each roam. How should this be categorized?
Select an answer to reveal the explanation.
Short Explanation
Full EAP on every hop is a long handshake—users feel it as a roam failure. PMK caching (when designed/enabled) shortens that pain. This is a roaming-feature problem, not a console-cable mystery.
Full Explanation
PMK caching and related key-caching behaviors reduce the need for full 802.1X/EAP on every roam. When caching is disabled contrary to design expectations, each roam may repeat full EAP and appear as mobility failure or application drops. Technicians treat this as a roaming-feature issue interacting with Enterprise security, not as DNS, console cabling, or an unfixable law of physics.