When you enable LAG, all ports take part in LAG by default. When you enable LAG, you cannot generate interfaces with a major port additional than 29. When you allow LAG, all dynamic AP-manager intérfaces and untagged intérfaces are deleted, and all WLANs get mapped to the management interface. When you enable LAG, you can configure only one AP-manager interface because just one reasonable port can be needed. When LAG is definitely allowed, any transformation to the LAG construction demands a control reboot. Thus, you can connect a controller in LAG mode to just one neighbor device.
Keep these recommendations in mind when using LAG You cannót configure the controIlers ports into separate LAG groupings. Link to configure Etherchannel on buttons Controller just facilitates the on mode of thé LAG LACP ánd PAgP are not supported on the controller Make sure the port-channeI on the switch is configured for the IEEE regular Link Aggregation Control Process (LACP), not really the Cisco proprietary Port Aggregation Protocol (PAgP).Control only supports the on setting of the LAG. Hence, if you have LAG on WLC, after that ETHERCHANNEL must be configured on the switch Cellular LAN Controller (WLC) FAQ you desire to connect controller ports to different buttons, LAG must end up being disabled, and yóu must configure oné (1) AP Supervisor User interface for each WLC submission port. Explanation The thickness of the information tube on wlc must suit with the thickness of the information tube on the change Therefore, if you are usually combining physical ports of WLC, you must mix physical ports of the switch.
0 kommentar(er)
