Exam 350-401 topic 1 question 133 discussion

Correct Option is B.

Layer 3 intercontroller is correct because the mobility peer IP address is in different subnet from the client IP address

B is correct

I Think B is correct because only on l3 roaming is the achoring feature used, and also seen the mobility ip address is different than local address

B: Layer 3 is correct

100% L3 Inter controller. You can review this post: https://mrncciew.com/2013/03/17/l3-inter-controller-roaming/ The client in Anchor WLC is seen with "mobility role" = Anchor and "AP type" Mobile

Many people are saying L3 Roaming capable, which I agree... but they are saying it because the Mobility Role is set to Anchor.... If it was L2 capable or not capable at all, what would the other entries look like? I cannot seem to find much documentation about the mobility roles. Also, "because the mobility peer IP is in a different subnet from the client IP." What does this mean? Why would the mobility peer ip have anything to do with the client IP. I'll keep reading until I find an answer, but I have not found anything yet. Comments appreciated until then.

B is correct answer, tin this case client roaming to a different eco on a different subnet, the new capwap tunnel will be built between the eco and the client, the client up address won’t change, and the original wcl is the anchor wcl

The correct answer is: B. Layer 3 intercontroller

The client cannot have an anchor role. Perhaps this is the role of this controller from the point of view of the client, which means that he has not moved anywhere. The client's settings are shown. How can you figure out which roaming the controller supports? For this you do not need topology and configuration of controller interfaces?

D for sure, Guys! The client still connect to the Anchor, it doesn't roam to the foreign, so no roaming happens here. It's just a tricky question. They just throw the word Anchor to make you think about L3.

B is the correct answer

correct Option is D intercontroller layer 2

If the clients roam between APs registered to different controllers and the client WLAN on the two controllers is on different subnet, then it is called inter-controller L3 roam. In this situation as well controllers exchange mobility messages. Client database entry change is completely different that to L2 roam(instead of move, it will copy). In this situation the original controller marks the client entry as “Anchor” where as new controller marks the client entry as “Foreign“.The two controllers now referred to as “Anchor controller” & “Foreign Controller” respectively. Client will keep the original IP address & that is the real advantage. Note: 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.

If its marked as an Anchor the other will be marked as Foreign. This is only used when you have 2 WLCs in different vlans so its L3 intra roaming

B, it is so clear... "Layer 3 roaming is similar to Layer 2 roaming in that the controllers exchange mobility messages on the client roam. However, instead of moving the client database entry to the new controller, the original controller marks the client with an “Anchor” entry in its own client database. The database entry is copied to the new controller client database and marked with a “Foreign” entry in the new controller. The roam remains transparent to the wireless client, and the client maintains its original IP address. " https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/overview.html

Answer should be B https://www.youtube.com/watch?v=N5jAStIozQw