How do I enable lag on WLC CLI?
--> Link Aggregation (LAG) in the WLC is the way of configuring the Ether channel in switches. --> LAG simplifies the controller operation by removing the need of configuring the primary and secondary port
for each interface. --> If any of the port in LAG fails, traffic automatically forwarded to other ports in LAG. --> We can configure LAG during initial configuration or after initial configuration of Wireless Lan Controller. --> Wireless Controller does not support any dynamic EtherChannel protocols such as LACP and Pagp because no negotiation can be done between wireless controller and switch. --> Wireless Controller does not answer any negotiation frames and LAG does not form in case of Dynamic EtherChannel Protocols. --> It is not possible to configure multiple LAG on Wireless Lan Controller.Only one LAG is supported by Wireless Lan Controller. --> Any changes to Link Aggregation in Wireless Controller requires the reboot. Chapter 27 Link Aggregation Control Protocol Aruba Networks, Inc.implementation of Link Aggregation Control Protocol (LACP) is based on the standards specified in 802.3ad. LACP provides a standardized means for exchanging information, with partner systems, to form a link aggregation group (LAG). LACP avoids port channel misconfiguration. Two devices (actor and partner) exchange LACP data units (DUs) in the process of forming a LAG. Once multiple ports in the system have the same actor system ID, actor key, partner system ID, and partner key, they belong to the same LAG. The maximum number of supported port-channels is 8. With the introduction of LACP, this number remains the same. In essence, a port-channel group (LAG) is created either statically or dynamically via LACP. This chapter contains:
Important Points to Remember
Configuring LACP Two LACP configured devices exchange LACPDUs to form a LAG. A device is configurable as an active or passive participant. In active mode, the device initiates DUs irrespective of the partner state; passive mode devices respond only to the incoming DUs sent by the partner device. Hence, to form a LAG group between two devices, one device must be an active participant. For detailed information on the LACP commands, see the ArubaOS Command Line Reference Guide. In the CLI LACPDUs exchange their corresponding system identifier/priority along with their port’s key/priority. This information determines the LAG of a given port. The LAG for a port is selected based on it’s keys; the port is placed in that LAG only when it’s system ID/key and partner's system ID/key matches the other ports in the LAG (if the group has ports). 1. Enable LACP and configure the per-port specific LACP. The group number range is 0 to 7. lacp group
2. Set the timeout for the LACP session. The timeout value is the amount of time that a port-channel interface waits for a LACPDU from the remote system before terminating the LACP session. The default time out value is long (90 seconds); short is 3 seconds lacp timeout {long | short} 3. Set the port priority. lacp port-priority The higher the priority value the lower the priority. Range is 1 to 65535 and default is 255. 4. View your LACP configuration. The port uses the group number +1 as the “actor admin key”. By default, all the ports use the long timeout value (90 seconds). (TechPubs)#show lacp 0 neighbor Flags: S - Device is requesting Slow LACPDUs F - Device is requesting fast LACPDUs A - Device is in active mode P - Device is in passive mode Partner's information --------------------- Port Flags Pri OperKey State Num Dev Id ---- ----- ---- ------- ----- ---- ---------------- FE 1/1 SA 1 0x10 0x45 0x5 00:0b:86:51:1e:70 FE 1/2 SA 1 0x10 0x45 0x6 00:0b:86:51:1e:70 When a port in a LAG, is misconfigured (that is, the partner device is different than the other ports) or the neighborship timesout or can not exchange LACPDUs with the partner, the port status is displayed as “DOWN” (see the following example). (TechPubs)#show lacp 0 internal Flags: S - Device is requesting Slow LACPDUs F - Device is requesting fast LACPDUs A - Device is in active mode P - Device is in passive mode Port Flags Pri AdminKey OperKey State Num Status ---- ----- ---- -------- -------- ----- ---- ------- FE 1/1 SA 1 0x1 0x1 0x45 0x2 DOWN FE 1/2 SA 1 0x1 0x1 0x45 0x3 UP In the WebUI Access LACP from the Configuration->Network->Porttabs. Use the drop down menus to enter the LACP values.
Best Practices
Sample Configuration The following sample configuration is for FastEthernet (FE) port/slot 1/0, 1/1, and 1/2 interface fastethernet 1/0 description "FE1/0" trusted vlan 1-4094 lacp group 0 mode active ! interface fastethernet 1/1 description "FE1/1" trusted vlan 1-4094 lacp timeout short lacp group 0 mode active ! interface fastethernet 1/2 description "FE1/2" trusted vlan 1-4094 lacp group 0 mode passive ! What is LAG mode in WLC?LAG is a partial implementation of the 802.3ad port aggregation standard. It bundles all the ports of the controller into a single 802.3ad port channel. The controller manages redundancy and load balancing of all the APs across the ports.
How do I set static LAG?You can configure LAG in two ways: static LAG and LACP (Link Aggregation Control Protocol). The member ports are manually added to the LAG.. Select an LAG for configuration. Group ID. ... . Select the member ports for the LAG. It is multi-optional.. Click Apply.. What is one reason to implement LAG on a Cisco WLC?LAG removes the requirement for supporting multiple AP-manager interfaces. When you enable LAG, all dynamic AP-manager interfaces and untagged interfaces are deleted, and all WLANs get mapped to the management interface.
What is a requirement when configuring or removing LAG on a WLC?What is a requirement when configuring or removing LAG on a WLC? A. The incoming and outgoing ports for traffic flow must be specified if LAG is enabled.
|