This command sets the Link Aggregation Group to use LACP in 'active' mode. In LACP, the operational mode (active or passive) is a property of the logical aggregate interface (the group), not the individual physical member ports. Setting the LAG to 'active' mode is the essential step to enable the switch to actively initiate LACP negotiations on all member ports. While the specific command syntax lacp group 1 mode active is not native to ArubaOS-CX, it correctly represents the concept of enabling LACP at the group level, which is the most accurate choice among the options provided. The correct ArubaOS-CX command is lacp mode active under the interface lag context.

A. LACP mode is not configured on physical interfaces, and 'enable' is not a valid LACP mode; 'active' or 'passive' are used.

C. channel-group is Cisco-specific syntax, and the 'auto' mode typically refers to the proprietary PAgP protocol, not the industry-standard LACP.

D. The LACP mode is a property of the logical LAG interface, not configured directly on a physical member port in ArubaOS-CX.

1. ArubaOS-CX 10.12 Fundamentals Guide

Page 268

"Configuring a static LACP LAG". The official documentation shows that LACP is enabled on the logical LAG interface

not the physical port. The command is lacp mode active or lacp mode passive within the interface lag configuration context. This supports the reasoning that the mode is a group-level property

making option B the most conceptually correct answer.

Document Snippet: "The LACP mode can be configured as active or passive. The default mode is passive. switch(config)# interface lag 1 switch(config-lag-if)# lacp mode active"

2. ArubaOS-CX 10.12 Link Aggregation Guide

Page 10

"LACP modes". This guide explicitly states

"LACP can be configured in active or passive mode on a LAG interface." This confirms that the LACP mode is set on the LAG interface itself

reinforcing that options attempting to configure it on a physical port (A and D) are incorrect.