Refer to the exhibit. Both controllers are in the same mobility group. Which result occurs when client 1 roams between APs that are registered to different controllers in the same WLAN?
A.
The client database entry moves from controller A to controller B
B.
A CAPWAP tunnel is created between controller A and controller B
C.
Client 1 uses an EoIP tunnel to contact controller A
D.
Client 1 contacts controller B by using an EoIP tunnel
A - this question seems client based to me, and although the database entry does not 'move' between controllers in a sense of ownership, the entry is copied from anchor to foreign.
B - If two 9800 WLCs are in use, CAPWAP or Secure Mobility should be formed already
C - the client does not use EOIP, two Aire0S controllers would form an EOIP tunnel
D - same as above really
The client remains anchored to the original controller (Controller A)
Even though Client 1 is now connected to AP 2 (which belongs to Controller B), it still maintains its session with Controller A.
An EoIP (Ethernet over IP) tunnel is established between Controller A and Controller B
Controller A remains the anchor and Controller B acts as the foreign controller.
Traffic from the client is tunneled via EoIP from Controller B to Controller A, ensuring seamless roaming.
It's B , Ignore my previous answer , my only problem is that from Cisco course ENCOR that i've bought , I have stated clearly that it's EoIP but i know that is a mistake from their part. It's CAPWAP, because i know EoIP it's not even Cisco proprietary but in their course they keeping shoving EoIP tunnels in your head.
Last Answer B, Cisco does not Use EoIP this is MikroTik proprietary.
No CAPWAP in this case , same WLAN, same subnet , same IP, DB entry moved and AP field gets updated with new AP, there is no need for CAPWAP because no mobility tunnel is required
keep on reading , i'll help you with the WLAN , same WLAN means same SSID , you can only do roaming without losing connection in the same WLAN. IF you use different WLAN (SSID) you need other authentication with other credentials .
Megon 1 week, 5 days ago
well, new CAPWAP tunnel is established as the old WLC will be anchor and new WLC will be foreign and by this roaming is seamless and the end device keeps its IPs and all traffic will be sent back to the anchor WLC
If it is in the same VLAN it does not have to anchor the AP so it will just transfer the database. If the controller doesn't share the same VLAN that is when it has to anchor to place the client on their original VLAN to avoid changing IP and dropping connection.
This is called Inter Controller-L2 Roaming. Inter-Controller (normally layer 2) roaming occurs when a client
roam between two APs registered to two different controllers, where each controller has an interface in the
client subnet. In this instance, controllers exchange mobility control messages (over UDP port 16666) and the
client database entry is moved from the original controller to the new controller.
B. A CAPWAP tunnel is created between controller A and controller B.
When a client roams between access points that are registered to different controllers in the same WLAN, a CAPWAP (Control And Provisioning of Wireless Access Points) tunnel is established between the controllers to allow for seamless roaming. This allows the client to maintain its connection without interruption as it moves between APs, and allows the controllers to keep track of the client's location and status in the network.
I could be wrong, but I think the CAPWAP tunnel has already been established before, because the controllers are in the same mobility group. It's not a result of a client roaming to a different controller. But it does cause the client database entry to move.
I think you're correct, CAPWAP tunnels are established between members of the same mobility group as they share the context and state of client devices with a list of their access points so that they do not consider each other’s access points as rogue devices.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/7-3/configuration/guide/b_cg73/b_wlc-cg_chapter_01111.html#:~:text=Controllers%20in%20the%20same%20mobility%20group%20can%20share%20the%20context%20and%20state%20of%20client%20devices%20as%20well%20as%20their%20list%20of%20access%20points%20so%20that%20they%20do%20not%20consider%20each%20other%E2%80%99s%20access%20points%20as%20rogue%20devices.
well, new CAPWAP tunnel is established as the old WLC will be anchor and new WLC will be foreign and by this roaming is seamless and the end device keeps its IPs and all traffic will be sent back to the anchor WLC
A is correct, if this is Intercontroller Layer 2 Roaming (the client database entry is moved to the new controller).
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/overview.html
upvoted 2 times
...
This section is not available anymore. Please use the main Exam Page.350-401 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
chmacnp
1 month, 3 weeks agomatass_md
2 months, 2 weeks agomatass_md
2 months agozbeugene7
7 months agomatass_md
2 months, 2 weeks agosharonmiller
9 months, 1 week agoBeehurls
8 months, 2 weeks agomatass_md
2 months, 2 weeks ago[Removed]
11 months, 1 week agorafaelinho88
2 years, 3 months agosnarkymark
2 years, 3 months agoBigbongos
2 years, 3 months agoTim1992
10 months, 1 week agoAbdullahMohammad251
7 months, 2 weeks agoMegon
9 months, 3 weeks agosharonmiller
9 months, 1 week ago9d3b6c3
10 months, 2 weeks agoCer_Pit
2 years, 6 months ago