WAN limitations for Hreap?

The correct answer is A. you must create hreap group for seamless roaming. For seamless client roaming in H-REAP (now FlexConnect) deployments across a WAN, access points must be explicitly configured into H-REAP groups. This grouping allows for local client authentication and data switching, which is crucial when the WAN link to the central…

Troubleshooting Wireless Infrastructure

Question

Options

Ayou must create hreap group for seamless roaming

How the community answered

(15 responses)

A
100% (15)

Why each option

For seamless client roaming in H-REAP (now FlexConnect) deployments across a WAN, access points must be explicitly configured into H-REAP groups. This grouping allows for local client authentication and data switching, which is crucial when the WAN link to the central controller is down.

Ayou must create hreap group for seamless roamingCorrect

To ensure seamless roaming for clients within a branch office when H-REAP (FlexConnect) APs are operating in standalone mode or connected over a WAN, it is essential to create H-REAP groups. This grouping allows APs to share client context and security keys locally, enabling fast and secure transitions between APs without requiring communication with the central controller over the potentially latent or unreliable WAN link.

Concept tested: Cisco H-REAP/FlexConnect roaming requirements

Source: https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_01000.html

Topics

#HREAP#WAN limitations#seamless roaming

Community Discussion

No community discussion yet for this question.

Full 300-370 Practice