it seams like B and C might be right:
B - When you disable LAG, you must assign an AP-manager interface to each port on the controller.
C - When LAG is enabled, any change to the LAG configuration requires a controller reboot
https://community.cisco.com/t5/wireless-mobility-knowledge-base/lag-link-aggregation/ta-p/3128669#toc-hId--766763784
You are right after reading it again i think B might be "more correct"
because C states after enabling OR reconfiguring, which would imply you need to reboot when you enable LAG and again after configuring it, which would seem a bit strange and unpractical. Good catch Piotr.
https://community.cisco.com/t5/wireless-mobility-knowledge-base/lag-link-aggregation/ta-p/3128669#:~:text=When%20LAG%20is%20enabled%2C%20any%20change%20to%20the%20LAG%20configuration%20requires%20a%20controller%20reboot.
When LAG is enabled, any change to the LAG configuration requires a controller reboot.
Suggested Answer: C
When you disable LAG, the management, static AP-manager, and dynamic interfaces are moved to port 1.
When you enable LAG or make any changes to the LAG configuration, you must immediately reboot the controller.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/m_configuring_link_aggregation.html
B and C both of them right :
When LAG is enabled, any change to the LAG configuration requires a controller reboot.
When you disable LAG, you must assign an AP-manager interface to each port on the controller.
https://community.cisco.com/t5/wireless-mobility-knowledge-base/lag-link-aggregation/ta-p/3128669#toc-hId--766763784
B and C is correct... missing (choose two)
https://community.cisco.com/t5/wireless-mobility-knowledge-base/lag-link-aggregation/ta-p/3128669#toc-hId--766763784:~:text=for%20all%20interfaces.-,When%20you%20disable%20LAG%2C%20you%20must%20assign%20an%20AP%2Dmanager%20interface%20to%20each%20port%20on%20the%20controller.,-The%20controller%E2%80%99s%20neighbor
Correcting, B is wrong (partially correct) as we assign an AP-manager interface to each WLC port only when we disable the LAG, and answer C is more correct as we must restart the WLC either when removing the LAG or when configuring (in any change). Link: "When LAG is enabled, any change to the LAG configuration requires a controller reset."
(The question asked "configuring or removin" the LAG on the WLC, the letter "C" fits both).
https://community.cisco.com/t5/wireless-mobility-knowledge-base/lag-link-aggregation/ta-p/3128669#toc-hId--766763784:~:text=When%20LAG%20is%20enabled%2C%20any%20change%20to%20the%20LAG%20configuration%20requires%20a%20controller%20reboot.
When you enable LAG or make any changes to the LAG configuration, you must immediately reboot the controller. (https://community.cisco.com/t5/wireless-mobility-knowledge-base/lag-link-aggregation/ta-p/3128669#:~:text=When%20you%20enable%20LAG%20or%20make%20any%20changes%20to%20the%20LAG%20configuration%2C%20you%20must%20immediately%20reboot%20the%20controller.)
When you enable LAG or make any changes to the LAG configuration, you must immediately reboot the controller. When you enable LAG, you can configure only one AP-manager interface because only one logical port is needed. LAG removes the requirement for supporting multiple AP-manager interfaces.
People here in discussion forgot that AP-manager and management interfaces are not the same.
C is correct I think
The management interface is the default interface used to access and manage the WLC. The management interface is also used by the access points to communicate with the WLC. The management interface IP address is the only ping-able IP address and is used by administrators to manage the WLC.
Administrators can log into the WLC’s configuration GUI by entering the management interface IP address in a web browser and logging into the system.
nothing that relates to LAG
https://community.cisco.com/t5/wireless-mobility-knowledge-base/lag-link-aggregation/ta-p/3128669#toc-hId--766763784
When LAG is enabled, any change to the LAG configuration requires a controller reboot.
When you enable LAG, you can configure only one AP-manager interface because only one logical port is needed.
When you disable LAG, you must assign an AP-manager interface to each port on the controller.
This section is not available anymore. Please use the main Exam Page.200-301 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.
PiotrMar
Highly Voted 2 years, 7 months agosplashy
2 years, 7 months agosplashy
2 years, 7 months ago[Removed]
Highly Voted 2 years, 5 months agobri24838
Most Recent 8 months, 1 week ago649c958
10 months, 1 week agoxtraMiles
9 months, 1 week ago[Removed]
1 year, 1 month ago[Removed]
1 year, 7 months agodropspablo
1 year, 9 months agodropspablo
1 year, 8 months agoTibisandres
2 years, 1 month agoCiscoman021
2 years, 1 month agothomson_johnson
2 years, 1 month agolinuxlife
2 years, 1 month agoDevNetAdmin
2 years, 2 months agoSilviu11
2 years, 2 months agoxbobdan
2 years, 2 months agoAnas_Ahmad
2 years, 3 months agoAnas_Ahmad
2 years, 3 months agomhdyqq
2 years, 3 months ago