WLAN Infrastructure Connections and LAG

22 questions

Question 1Question

A network administrator is establishing link aggregation between a Cisco AireOS Wireless LAN Controller (WLC) and an upstream Cisco Catalyst switch to increase bandwidth and provide interface redundancy. The administrator configures ports GigabitEthernet 1/0/1 through 1/0/4 on the Catalyst switch using the command 'channel-group 10 mode active' and enables LAG on the WLC. However, after the WLC reboots, the EtherChannel fails to negotiate successfully. Which condition is causing this link aggregation failure?

Show answer & explanation

Answer: The upstream switch ports are configured for dynamic LACP negotiation, but Cisco AireOS WLCs only support static EtherChannel bundles configured with mode on.

Answer

The upstream switch ports are configured for dynamic LACP negotiation, but Cisco AireOS WLCs only support static EtherChannel bundles configured with mode on.
Cisco AireOS Wireless LAN Controllers require all connected distribution system ports to be bundled into a single static EtherChannel. Because AireOS does not support LACP (IEEE 802.3ad) or PAgP negotiation protocols, the upstream switch interfaces must be configured with 'mode on'. When the switch ports are configured with 'mode active', the switch expects LACP packets that the AireOS controller never sends, preventing the link aggregation bundle from establishing.

Step-by-Step Solution

1
Identify the protocol support for Link Aggregation (LAG) on Cisco AireOS Wireless LAN Controllers.
AireOS controllers do not support dynamic EtherChannel negotiation protocols such as LACP or PAgP.
LAG on AireOS bundles all physical distribution system ports into a single logical channel that requires unconditional static bundling on the connected switch.
2
Evaluate the switch port configuration command 'channel-group 10 mode active'.
The 'mode active' keyword enables LACP dynamic negotiation on the Catalyst switch ports.
Because the WLC will not transmit or respond to LACP control packets, the switch ports remain in an unbundled or suspended state waiting for LACP negotiation.
3
Determine the necessary configuration change on the switch interfaces.
Change the switch port channel command to 'channel-group 10 mode on'.
Configuring 'mode on' forces the switch ports into a static EtherChannel without attempting LACP or PAgP negotiation, matching the WLC requirements.

Key Concept

Cisco AireOS WLC Link Aggregation (LAG) EtherChannel Mode Requirements
Question 2Question

An administrator needs to enable Link Aggregation (LAG) on a Cisco Wireless LAN Controller (WLC) connected to an upstream switch stack. Place the configuration and operational steps in the correct chronological sequence from start to finish.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with saving the WLC configuration, enabling LAG in the controller settings, saving and rebooting the WLC to apply the change, and finally configuring the connected switch ports as a static EtherChannel (mode on).
The sequence follows the standard Cisco procedure for turning on controller-wide Link Aggregation (LAG). First, current configuration state is saved. Second, LAG is enabled in the WLC settings menu. Third, the WLC configuration is saved and the controller is rebooted to apply the change. Fourth, the corresponding switch ports are configured into a static EtherChannel using 'channel-group mode on' to complete the physical and logical aggregation.

Step-by-Step Solution

1
Save the existing WLC configuration
Establishes a baseline configuration state before initiating a system reboot
It is essential to safeguard existing controller configuration prior to changing structural hardware modes.
2
Enable LAG in WLC settings
Places the WLC into a pending LAG state
The controller feature knob for LAG must be explicitly enabled before hardware interface aggregation takes effect.
3
Save and reboot the WLC
The controller reboots with LAG operational across all physical distribution system ports
Enabling LAG on a Cisco WLC requires a reboot to reconfigure internal interface mappings.
4
Configure static EtherChannel on the upstream switch
The switch ports bundle into a single logical link matching the WLC LAG mode
Cisco WLC LAG requires static frame grouping ('mode on') on the switch side since WLCs do not support LACP or PAgP negotiation.

Key Concept

WLC Link Aggregation (LAG) configuration workflow and switch port requirements
Question 3Question

A network engineer transitions several Cisco Lightweight Access Points (LAPs) deployed at a branch office from default Local mode to FlexConnect mode with local switching enabled for the corporate employee wireless network. The switch ports connected to these APs are currently configured as Layer 2 access ports assigned to VLAN 10 (Management). Following the transition, AP-to-WLC CAPWAP control connectivity remains healthy, but wireless clients connecting to the employee SSID (mapped to VLAN 20) fail to obtain IP addresses or communicate with local resources. Which configuration change must be applied to the access switch ports to restore client connectivity on the employee WLAN?

Show answer & explanation

Answer: Reconfigure the switch ports as 802.1Q trunk ports with VLAN 10 configured as the native VLAN and allow VLAN 20 on the trunk.

Answer

Reconfigure the switch ports as 802.1Q trunk ports with VLAN 10 configured as the native VLAN and allow VLAN 20 on the trunk.
When a Cisco LAP operates in FlexConnect mode with local switching, client traffic is broken out locally at the AP's physical switch port. To carry untagged AP management traffic alongside tagged client VLAN traffic (such as VLAN 20), the connected switch port must be configured as an 802.1Q trunk with the AP management VLAN (VLAN 10) specified as the native VLAN.

Step-by-Step Solution

1
Analyze AP mode traffic behavior differences between Local mode and FlexConnect mode.
In Local mode, all client traffic is encapsulated in CAPWAP and sent to the WLC, requiring only a simple switch access port in the AP management VLAN. In FlexConnect local switching mode, client traffic is switched locally onto the Ethernet switch port.
Understanding how traffic leaves the AP determines the required switch port mode.
2
Identify the VLAN requirements for the FlexConnect AP connection.
The AP requires management traffic on VLAN 10 (untagged CAPWAP traffic) and wireless client traffic tagged for VLAN 20.
Carrying both tagged client traffic and untagged management traffic over a single physical cable requires an 802.1Q trunk.
3
Determine the necessary switch port trunk settings.
The switch port must be set to trunk mode (`switchport mode trunk`), with VLAN 10 set as the native VLAN (`switchport trunk native vlan 10`) so CAPWAP management traffic remains untagged, while allowing VLAN 20 for client traffic.
This allows the AP to maintain its CAPWAP tunnel while successfully bridging tagged client packets to the local switch.

Key Concept

FlexConnect AP Switch Port Infrastructure Trunking
Estimated Time:2m 0s
Question 4Question

A network engineer is configuring Link Aggregation (LAG) on a Cisco Wireless LAN Controller (WLC) connected to an access layer switch stack. The deployment includes central site Local mode APs and remote branch FlexConnect APs using local traffic switching. Which TWO configuration statements correctly describe the requirements and behavior of this WLAN infrastructure connection setup? (Select two.)

Select all that apply

Show answer & explanation

Answer: All distribution system physical ports on the Cisco WLC are bundled into a single logical link, requiring the connected switch ports to be configured as a single static EtherChannel (mode ON) without dynamic LACP or PAgP negotiation.; Switch ports connecting directly to FlexConnect APs operating in local switching mode must be configured as 802.1Q trunks (or VLAN-tagged access ports) to locally bridge client WLAN traffic to the infrastructure switch.

Answer

The correct requirements are: 1) Switch ports connected to the WLC must be bundled into a static EtherChannel using mode ON because Cisco WLCs do not support dynamic EtherChannel protocols like LACP or PAgP. 2) Switch ports connected to FlexConnect APs using local switching must be configured with appropriate 802.1Q VLAN trunking so local client traffic can be bridged directly to the local network infrastructure.
Enabling LAG on a Cisco WLC consolidates all distribution ports into a single logical link requiring the adjacent switch ports to be placed into a single static EtherChannel (mode ON). Additionally, FlexConnect APs configured for local switching require their direct access switch connections to be configured as 802.1Q trunks (or appropriately tagged ports) so that client VLAN traffic can be locally switched into the wired LAN infrastructure.

Step-by-Step Solution

1
Analyze WLC LAG behavior and switch link aggregation requirements.
Cisco AireOS WLCs merge all physical distribution ports into a single logical interface that requires static EtherChannel grouping (mode ON) on the connected switch.
The WLC does not support dynamic negotiation protocols such as LACP or PAgP.
2
Analyze FlexConnect AP infrastructure port requirements for local switching mode.
Traffic from SSIDs configured for local switching is mapped directly to VLAN tags on the AP's physical switch interface.
The switch port connecting to the FlexConnect AP must be an 802.1Q trunk (or access port supporting the required VLAN setup) to correctly forward local data frames without sending them through the central WLC CAPWAP tunnel.

Key Concept

WLAN Infrastructure Link Aggregation (LAG) and FlexConnect AP Switch Port Requirements
Estimated Time:2m 0s
Question 5Question

An enterprise network requires redundant, high-bandwidth connectivity between a Cisco AireOS Wireless LAN Controller (WLC) distribution port bundle and a Cisco Catalyst distribution switch. The network team decides to enable Link Aggregation (LAG) on the controller. Which TWO switch-side configurations and behaviors are mandatory for this infrastructure connection to operate correctly? (Select two.)

Select all that apply

Show answer & explanation

Answer: The switch member ports must be statically bundled using channel-group mode on because AireOS LAG does not negotiate using dynamic protocols like LACP or PAgP.; The switch port-channel interface must be configured as an 802.1Q trunk carrying all necessary wireless client and management VLANs with matching native VLAN settings.

Answer

The mandatory switch-side configurations are configuring member ports in static EtherChannel mode (channel-group mode on) and setting the port-channel interface as an 802.1Q trunk carrying the required VLANs with matching native VLAN configurations.
On Cisco AireOS controllers, enabling LAG aggregates all physical distribution ports into a single logical channel. Because AireOS does not support dynamic negotiation protocols (LACP or PAgP), the upstream switch member ports must be statically bound using mode on. Additionally, because multiple VLANs (management, dynamic client WLANs, AP manager) travel across this aggregate link, the port-channel interface on the Catalyst switch must be configured as an 802.1Q trunk with properly aligned native and allowed VLANs.

Step-by-Step Solution

1
Identify the link aggregation capabilities and requirements of Cisco AireOS Wireless LAN Controllers.
AireOS controllers support a single LAG interface bundle that aggregates all distribution ports into one logical connection without supporting dynamic negotiation protocols (LACP/PAgP).
Since AireOS cannot participate in LACP or PAgP handshake negotiation, the upstream Catalyst switch must be configured manually for static EtherChannel using mode on.
2
Determine the trunking and VLAN requirements for WLC distribution port bundles.
All WLC logical interfaces (management, dynamic client VLANs, manager ports) pass over this unified LAG bundle requiring 802.1Q VLAN encapsulation.
The upstream switch port-channel and physical member ports must be configured as 802.1Q trunks with consistent native VLANs and allowed VLAN lists to prevent frame drops or VLAN leakage.
3
Evaluate and eliminate incorrect statements regarding LAP mode traffic routing and dynamic negotiation.
Dynamic negotiation modes like LACP passive or PAgP fail, and Local mode LAPs do not require switch trunk ports since CAPWAP tunnels all client data to the controller.
Local mode APs tunnel data to the WLC rather than switching locally, so AP switch ports remain in access mode, whereas FlexConnect mode APs would utilize switch trunking.

Key Concept

Cisco AireOS WLC Link Aggregation (LAG) and Upstream Switch Trunking
Estimated Time:1m 30s
Question 6Question

An enterprise wireless administrator is integrating a Cisco 5520 Wireless LAN Controller (running AireOS) with a Cisco Catalyst switch stack. The administrator connects four physical distribution system ports on the controller to switch interfaces GigabitEthernet1/0/1 through 1/0/4. The switch interfaces are configured as an 802.1Q trunk bundle using the command `channel-group 1 mode active`. Although Link Aggregation (LAG) has been enabled on the WLC and the controller has been rebooted, the EtherChannel fails to form and all controller distribution links remain down. Which modification on the Catalyst switch stack will resolve this connection failure?

Show answer & explanation

Answer: Change the negotiation protocol on the switch interfaces by executing `channel-group 1 mode on`.

Answer

Change the switch port EtherChannel configuration to static ON mode using `channel-group 1 mode on`.
When Link Aggregation (LAG) is enabled on a Cisco AireOS Wireless LAN Controller, all physical distribution system ports are merged into a single logical interface. AireOS controllers do not support dynamic negotiation protocols such as Link Aggregation Control Protocol (LACP) or Port Aggregation Protocol (PAgP). Therefore, the connected switch ports must be explicitly configured with static link aggregation using the command `channel-group <id> mode on`. Configuring `mode active` forces the switch to expect LACP frames, which the WLC will never transmit, causing the channel to remain down.

Step-by-Step Solution

1
Identify the controller platform and operating system requirements for Link Aggregation (LAG).
Cisco AireOS Wireless LAN Controllers require static EtherChannel bonding across all active distribution system ports.
AireOS software does not support dynamic link aggregation protocols such as LACP (`mode active`/`mode passive`) or PAgP (`mode desirable`/`mode auto`).
2
Analyze the current switch configuration.
The switch interfaces are set to `channel-group 1 mode active`, which requires LACP negotiation packets from the connected device.
Because the AireOS WLC never sends LACP frames, the switch ports remain suspended in an unbundled state awaiting negotiation.
3
Determine the necessary configuration change on the switch ports.
Change `channel-group 1 mode active` to `channel-group 1 mode on` on all connecting interfaces.
Configuring `mode on` disables negotiation protocol requirements and forces the switch interfaces into a functional EtherChannel bundle matching the WLC behavior.

Key Concept

WLAN Controller Link Aggregation (LAG) EtherChannel Switch Configuration
Question 7Question

When implementing Link Aggregation (LAG) between a Cisco Wireless LAN Controller and an upstream switch, specific configuration rules apply to the physical interfaces and channel grouping. Which two statements describe valid operational characteristics or configuration requirements for this LAG deployment? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Every physical distribution port on the wireless controller is combined into one single logical interface.; The switch ports attached to the controller must be statically bundled into an EtherChannel using mode 'on'.

Answer

Enabling LAG on a Wireless LAN Controller bundles all physical distribution system ports into a single logical interface, and the connected switch ports must be statically configured in EtherChannel mode 'on'.
Enabling Link Aggregation (LAG) on a Cisco Wireless LAN Controller aggregates all physical distribution system ports into a single logical EtherChannel. Because the controller does not participate in dynamic negotiation protocols like LACP or PAgP, the corresponding switch ports must be statically configured using EtherChannel mode 'on'.

Step-by-Step Solution

1
Identify the multi-port bundling behavior on a Cisco WLC when LAG is enabled.
Recognize that enabling LAG aggregates all physical distribution system ports into a single logical interface.
Cisco WLC architecture requires all distribution ports to form one unified EtherChannel pipe rather than multiple independent links.
2
Determine the supported EtherChannel negotiation mode on the connected switch interfaces.
Confirm that switch ports must be configured manually using 'channel-group mode on'.
The controller does not send or process LACP or PAgP negotiation frames when LAG is active.

Key Concept

WLAN Infrastructure Link Aggregation (LAG) Requirements
Question 8Question

A network administrator enables Link Aggregation (LAG) on a Cisco Wireless LAN Controller (WLC) to combine its physical distribution system ports into a single logical interface. How must the connected ports on the upstream switch be configured to establish this link aggregation successfully?

Show answer & explanation

Answer: Configured as a static EtherChannel using the command channel-group mode on without dynamic negotiation protocols.

Answer

The switch ports connected to the Wireless LAN Controller must be configured as a static EtherChannel using the channel-group mode on command.
When Link Aggregation (LAG) is enabled on a Cisco Wireless LAN Controller, all physical distribution system ports are bundled into a single logical channel that carries all VLANs as an 802.1Q trunk. Because the controller does not use dynamic negotiation protocols such as LACP or PAgP, the corresponding connected interfaces on the adjacent switch must be configured as a static EtherChannel using the `channel-group mode on` command.

Step-by-Step Solution

1
Identify WLC Link Aggregation (LAG) operational characteristics
Determine that Cisco WLC LAG bundles all physical distribution ports into a single logical interface that acts as an 802.1Q trunk.
WLC LAG does not run dynamic link aggregation negotiation protocols (LACP or PAgP).
2
Determine the matching switch port configuration requirements
Select static EtherChannel configuration (channel-group mode on) for all member switch interfaces connected to the WLC.
Because the controller does not transmit negotiation packets, the switch ports must force the EtherChannel into an operational state unconditionally.

Key Concept

WLC Link Aggregation (LAG) Switchport Configuration
Question 9Question

A network technician is installing a new Cisco Lightweight Access Point (LAP) that will operate in default Local mode. The access point connects directly to an access-layer Catalyst switch port and will tunnel all user traffic back to the central Wireless LAN Controller (WLC) via CAPWAP. Which switch port configuration is required to properly support this access point connection?

Show answer & explanation

Answer: An access port assigned to the dedicated VLAN used for AP management traffic.

Answer

An access port assigned to the dedicated VLAN used for AP management traffic.
When a Cisco Access Point operates in standard Local mode, all client traffic is encapsulated within CAPWAP tunnels and sent directly to the Wireless LAN Controller (WLC). The AP itself only requires an IP address on the management network to build the CAPWAP control and data tunnels. Therefore, the connected switch port should be configured as a standard access port assigned to the AP management VLAN.

Step-by-Step Solution

1
Identify the operating mode of the Cisco Lightweight Access Point.
The AP operates in Local mode.
Local mode APs encapsulate all wireless client data inside CAPWAP tunnels back to the WLC.
2
Determine the physical infrastructure switch port requirements for a Local mode AP.
The AP only sends and receives untagged management traffic to establish its CAPWAP tunnel.
Because client VLANs are not locally bridged at the access layer switch, an 802.1Q trunk is unnecessary.
3
Select the correct switch port configuration mode.
Configure the switch interface as an access port in the AP management VLAN.
This provides IP reachability for the AP to discover and join the WLC.

Key Concept

Switch port configuration requirements for Local mode lightweight AP infrastructure connections
Estimated Time:45s
Question 10Question

An enterprise network deployment incorporates a Cisco Wireless LAN Controller (WLC) connected via four physical distribution system ports to a Cisco Catalyst switch stack. The network engineer enables Link Aggregation (LAG) globally on the controller and reboots the device. On the switch stack, the engineer attempts to establish the EtherChannel by configuring `channel-group 1 mode active` across ports GigabitEthernet 1/0/1 through 1/0/4. Following the WLC reboot, the controller loses all network management connectivity, and the switch logs indicate that the port-channel interface is down due to a negotiation failure. Which switch configuration modification will restore network connectivity while maintaining LAG operational on the controller?

Show answer & explanation

Answer: Change the channel group negotiation mode on all participating switch interfaces to mode on.

Answer

Change the channel group negotiation mode on all participating switch interfaces to mode on.
When Link Aggregation (LAG) is enabled on a Cisco Wireless LAN Controller (running AireOS), the controller bundles all physical distribution system ports into a single operational interface. AireOS controllers do not support dynamic link negotiation protocols such as Link Aggregation Control Protocol (LACP) or Port Aggregation Protocol (PAgP). Therefore, the connected interfaces on the upstream Cisco Catalyst switch must be configured as a static EtherChannel using `channel-group <id> mode on`.

Step-by-Step Solution

1
Analyze the WLC Link Aggregation (LAG) signaling requirements.
Cisco AireOS Wireless LAN Controllers require static EtherChannel bundling without dynamic LACP or PAgP negotiation frames.
The controller firmware bundles all physical distribution system ports into a single non-negotiated logical port.
2
Identify the cause of the port-channel down state on the switch.
The switch was configured with `channel-group 1 mode active`, expecting LACP LACPDU negotiation packets that the WLC never sends.
Because LACP negotiation times out without receiving LACPDUs from the WLC, the switch keeps the port-channel in a suspended/down state.
3
Determine the necessary configuration change on the switch stack.
Change the interface configuration to `channel-group 1 mode on` across all attached switch ports.
Mode `on` forces the switch ports into a static EtherChannel bundle without waiting for negotiation frames.

Key Concept

WLAN Controller Link Aggregation (LAG) Switch Configuration Requirements
Question 11Question

A network administrator is preparing to bundle the physical distribution system ports on a Cisco Wireless LAN Controller (WLC) to increase bandwidth and redundancy toward an upstream Cisco Catalyst switch stack. Which two requirements or operational characteristics apply when Link Aggregation (LAG) is enabled on the Cisco WLC?

Select all that apply

Show answer & explanation

Answer: The connected ports on the upstream switch must be combined into a single static EtherChannel bundle using the manual mode 'on'.; Enabling LAG merges all physical distribution system ports into a single logical interface, preventing the creation of multiple separate EtherChannel groups on the controller.

Answer

The correct options are that the upstream switch ports must be configured into a static EtherChannel using mode 'on', and that enabling LAG merges all physical distribution system ports into a single logical interface on the controller.
Enabling LAG on a Cisco Wireless LAN Controller consolidates all physical distribution ports into a single logical EtherChannel. Because the controller does not use dynamic EtherChannel negotiation protocols like LACP or PAgP, the connected upstream switch ports must be manually configured in static EtherChannel mode using the 'channel-group <id> mode on' command.

Step-by-Step Solution

1
Analyze Cisco WLC EtherChannel / LAG negotiation protocol requirements.
Cisco WLC LAG requires static frame distribution without LACP or PAgP signaling.
The WLC does not run LACP or PAgP daemons on its physical ports, requiring the connected switch ports to be set to static EtherChannel ('mode on').
2
Determine how physical ports are grouped when LAG is enabled on the controller.
All physical distribution system ports form one single logical bundle.
On a Cisco WLC, LAG is a global setting that combines all distribution ports into one single logical link bundle; multiple separate EtherChannel groups cannot be defined.
3
Evaluate AP behavior in Local mode vs FlexConnect mode upon WLC link bundle loss.
Local mode APs cease forwarding client traffic because they cannot switch traffic locally.
Local mode APs encapsulate all user data inside CAPWAP tunnels to the WLC. Local switching requires FlexConnect mode.

Key Concept

Cisco WLC Link Aggregation (LAG) Architecture and Trunking Requirements
Question 12Question

A network engineer is implementing Link Aggregation (LAG) using IEEE 802.3ad LACP between a Cisco Catalyst 9800 Series Wireless Controller and an upstream Cisco Catalyst 9300 switch stack. Place the following implementation and verification steps in the correct chronological order required to establish the infrastructure link.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct implementation sequence begins with configuring the physical switch interfaces with LACP mode active, configuring trunking parameters on the resulting switch Port-channel interface, configuring the WLC uplink EtherChannel bundle, verifying Layer 2 bundle operation with 'show etherchannel summary', and finally validating WLC management reachability and CAPWAP tunnel stability.
Establishing a Link Aggregation connection between a Cisco Catalyst 9800 WLC and an upstream switch requires a structured bottom-up approach. First, physical switch ports must be assigned to the LACP channel group ('channel-group 10 mode active'). Second, the resulting logical Port-channel interface must be configured with 802.1Q trunking and VLAN parameters. Third, the controller-side interfaces must be bundled into the corresponding uplink EtherChannel. Fourth, the engineer must verify Layer 2 LACP negotiation using 'show etherchannel summary' to ensure the channel state is 'SU' and member interfaces display 'P'. Finally, end-to-end control plane operation is verified by testing WLC management reachability and AP CAPWAP tunnel stability.

Step-by-Step Solution

1
Define switch member ports
Physical switch ports are associated into channel-group 10 using active LACP negotiation.
Assigning physical member ports creates the logical Port-channel interface on the switch.
2
Configure switch Port-channel interface
The Port-channel interface is set to switchport mode trunk with designated native and allowed VLANs.
Applying trunk configuration to the logical Port-channel ensures consistent trunking behavior across all bundled physical member links.
3
Configure WLC uplink LAG bundle
Controller physical ports are grouped into an uplink EtherChannel bundle.
With the switch ready to negotiate, the controller side is enabled for link aggregation.
4
Verify EtherChannel protocol status
Switch CLI displays 'SU' (Layer 2, In-use) for Port-channel 10 and 'P' (Bundled) for all member ports.
Verifying LACP status ensures physical links negotiated properly without misconfigurations such as mode mismatches or suspended ports.
5
Verify network access and CAPWAP operation
Management traffic reaches the WLC IP and AP CAPWAP tunnels operate successfully over the aggregated link.
End-to-end verification validates overall infrastructure connectivity and wireless control plane operation.

Key Concept

WLAN Infrastructure LAG and Switch EtherChannel Implementation Sequence
Estimated Time:2m 0s
Question 13Question

An enterprise deploys a Cisco Lightweight Access Point (LAP) operating in FlexConnect mode at a remote branch office. The AP is configured to perform local switching for WLANs mapped to VLAN 10 (Sales) and VLAN 20 (Guests). The AP management traffic must be assigned to VLAN 100 and transmitted untagged over the physical link. The connected Cisco Catalyst switch port is configured as an 802.1Q trunk. Which switchport configuration command must be applied to the switch port to ensure AP management traffic and locally switched WLAN traffic function properly?

Show answer & explanation

Answer: switchport trunk native vlan 100

Answer

The switch interface must be configured with 'switchport trunk native vlan 100'.
When a Cisco Lightweight AP in FlexConnect mode is configured for local traffic switching across multiple VLANs (VLAN 10 and VLAN 20), the switch port must be an 802.1Q trunk. Because the AP sends its management traffic untagged by default, the switch port's native VLAN must match the AP's management VLAN (VLAN 100). The command 'switchport trunk native vlan 100' ensures untagged management frames are mapped into VLAN 100 while carrying tagged frames for the client VLANs.

Step-by-Step Solution

1
Identify the AP deployment mode and traffic requirements.
The AP operates in FlexConnect mode with local switching for VLAN 10 and VLAN 20, requiring an 802.1Q trunk port.
FlexConnect APs supporting multiple locally switched SSIDs mapped to different VLANs must connect to switch ports configured as 802.1Q trunks.
2
Determine how the AP management traffic is framed.
AP management traffic is assigned to VLAN 100 and sent untagged by default.
Cisco Lightweight APs send their CAPWAP management traffic untagged unless AP VLAN tagging is explicitly enabled.
3
Select the appropriate 802.1Q trunk configuration command.
Apply 'switchport trunk native vlan 100' on the switch port.
Setting the native VLAN to 100 ensures untagged frames received from the AP are mapped to VLAN 100 on the switch, while tagged frames for VLAN 10 and VLAN 20 are trunked appropriately.

Key Concept

FlexConnect AP Switch Port Infrastructure Trunking and Native VLAN Configuration
Estimated Time:1m 30s
Question 14Question

A network administrator is connecting a Cisco Wireless LAN Controller (WLC) to an upstream Cisco Catalyst switch using multiple physical distribution system ports. To increase throughput and provide interface redundancy, the administrator enables Link Aggregation (LAG) on the controller. Which two configuration requirements must be met on the upstream switch to support proper EtherChannel operation with the WLC? (Select two.)

Select all that apply

Show answer & explanation

Answer: All physical switch interfaces connected to the WLC distribution ports must be grouped into a single EtherChannel interface.; The switch ports connected to the WLC physical ports must be configured with identical attributes, including 802.1Q trunking mode and allowed VLAN lists.

Answer

The upstream switch must group all physical interfaces connected to the controller into a single EtherChannel bundle, and all member switch ports must share identical trunking and VLAN configurations.
When Link Aggregation (LAG) is enabled on a Cisco Wireless LAN Controller, all physical distribution system ports are combined into a single logical link. Consequently, the connected upstream switch must aggregate all corresponding physical ports into a single matching EtherChannel (port-channel) group. Additionally, because EtherChannel bundle members must operate with consistent interface parameters, all participating switch ports must share identical configuration attributes, such as 802.1Q trunk mode and allowed VLAN lists.

Step-by-Step Solution

1
Analyze WLC Link Aggregation (LAG) behavioral requirements.
Enabling LAG on a Cisco WLC merges all physical distribution system ports into a single logical link for load distribution and failover.
Because the controller treats all connected ports as one logical interface, the upstream switch must mirror this behavior by assigning all connected ports to a single switchport EtherChannel (port-channel) group.
2
Verify switchport trunking requirements for WLC infrastructure connections.
Member switch ports in an EtherChannel must match in configuration parameters (speed, duplex, 802.1Q trunking mode, and allowed VLANs).
Since WLC interfaces transport multiple VLANs corresponding to different SSIDs and management interfaces, the underlying port-channel and its physical member ports must be configured as 802.1Q trunks with consistent attributes.

Key Concept

WLAN Infrastructure Connections and Switch Link Aggregation (LAG)
Estimated Time:1m 30s
Question 15Question

A network administrator is connecting four physical distribution system ports of a Cisco AireOS Wireless LAN Controller to an upstream Cisco Catalyst switch. Link Aggregation (LAG) is enabled on the controller to increase bandwidth and provide redundancy. Which port-channel configuration must be applied to the upstream Catalyst switch interfaces?

Show answer & explanation

Answer: Configure all connected switch interfaces into a single port-channel group using static mode 'on' with 802.1Q trunking enabled.

Answer

Configure all connected switch interfaces into a single port-channel group using static mode 'on' with 802.1Q trunking enabled.
When LAG is enabled on a Cisco AireOS Wireless LAN Controller, all physical distribution system ports are bundled into a single logical interface. The connected Cisco Catalyst switch must be configured with all corresponding physical ports in a single EtherChannel port-channel set to static mode 'on' and operating as an 802.1Q trunk.

Step-by-Step Solution

1
Identify the Link Aggregation (LAG) characteristics supported on Cisco AireOS Wireless LAN Controllers.
AireOS controllers support LAG only as a single logical EtherChannel bundle across all distribution system ports, requiring static EtherChannel mode ('on') without dynamic negotiation protocols (LACP/PAgP).
The controller software architecture requires all physical DS ports to participate in a single static EtherChannel bundle.
2
Determine switchport encapsulation and trunking requirements for WLC connectivity.
The switchport interface connecting to the WLC LAG bundle must be an 802.1Q trunk port to transport management and WLAN VLAN traffic.
Wireless controllers handle multiple wireless networks mapped to separate 802.1Q VLAN tags.

Key Concept

WLAN Infrastructure Connections and WLC LAG Switch Configuration
Estimated Time:1m 30s
Question 16Question

A network administrator needs to deploy Link Aggregation (LAG) on a Cisco AireOS Wireless LAN Controller (WLC) connected to an upstream Cisco Catalyst switch. Place the operational steps required to enable and establish the LAG connection in the correct sequential order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequential order to deploy LAG on an AireOS WLC is: 1) Enable LAG in WLC settings, 2) Save configuration and reboot the WLC, 3) Configure connected upstream switch ports into an EtherChannel using mode 'on', and 4) Verify operational status of the aggregated bundle.
To successfully deploy LAG on an AireOS Wireless LAN Controller, the feature must first be enabled in WLC global controller settings. Because enabling LAG reorganizes physical ports into a single logical interface, the configuration must be saved and the controller rebooted to take effect. Following the reboot, the upstream Catalyst switch physical ports must be configured into a single EtherChannel using mode 'on' (static aggregation, since AireOS does not negotiate via LACP or PAgP). Finally, the network engineer verifies that the Port-Channel is operational and passing traffic across mapped WLAN VLANs.

Step-by-Step Solution

1
Enable LAG feature on the WLC
The controller prepares the internal distribution system interfaces for multi-port bundling.
Global LAG setting must be changed prior to restarting the appliance.
2
Save configuration and restart WLC
The WLC reboots and binds all physical distribution ports into a single logical LAG interface.
AireOS hardware architecture requires a system reboot to apply LAG implementation across distribution ports.
3
Configure switch ports with static EtherChannel
The upstream Catalyst switch binds its corresponding interfaces into a single port-channel using mode 'on'.
AireOS WLCs do not support dynamic EtherChannel negotiation protocols like LACP or PAgP.
4
Verify port-channel operation and data flow
Operational status is confirmed and WLAN VLAN traffic flows across the unified bundle.
Ensures that all bundled interfaces forward traffic properly without port mismatches or STP blocking.

Key Concept

AireOS WLC Link Aggregation deployment workflow and static switch EtherChannel requirements.
Question 17Question

An infrastructure team is provisioning access layer switch interfaces for newly deployed Cisco Lightweight Access Points (LAPs) operating strictly in Local mode. All wireless client traffic will be encapsulated within CAPWAP tunnels back to the central Wireless LAN Controller (WLC). Which switch port configuration must be applied to the switch interfaces connecting directly to these Access Points?

Show answer & explanation

Answer: Configure each interface as a standard Layer 2 access port assigned to the AP management VLAN.

Answer

The switch interfaces must be configured as standard Layer 2 access ports assigned to the AP management VLAN.
Local mode APs send all wireless user traffic through CAPWAP tunnels to the Wireless LAN Controller. Because the AP itself only requires network access to obtain an IP address and reach the WLC IP, the switch interface connecting to the AP only needs to be configured as a standard access port in the AP management VLAN.

Step-by-Step Solution

1
Analyze the operational mode of the Access Points
The APs operate in Local mode.
Local mode APs do not switch wireless client traffic locally onto the access switch; instead, all data and control traffic are encapsulated into CAPWAP tunnels sent directly to the central WLC.
2
Determine the VLAN and switchport requirements for Local mode APs
The AP requires only an IP address in the AP management VLAN to establish its CAPWAP tunnel.
Because client VLAN tags are encapsulated within the CAPWAP data payload, the physical switch port connected to the AP does not need to trunk multiple client VLANs.
3
Select the appropriate switchport mode configuration
Set the switch port mode to access and assign it to the AP management VLAN.
An access port provides untagged Layer 2 connectivity for the AP to receive an IP address via DHCP and communicate with the WLC.

Key Concept

Local mode AP switchport requirements vs FlexConnect mode requirements
Question 18Question

A network engineer is connecting multiple physical distribution system ports of a Cisco AireOS Wireless LAN Controller (WLC) to an upstream Cisco Catalyst switch using Link Aggregation (LAG). Which two configuration requirements must be implemented on the switch interfaces to establish successful aggregation and traffic transport? (Select two.)

Select all that apply

Show answer & explanation

Answer: Configure the EtherChannel bundle mode on the switch interfaces to static 'on' state.; Configure the switch interface or port-channel as an 802.1Q trunk port to carry traffic across multiple VLANs.

Answer

The correct requirements are configuring the switch interfaces to static EtherChannel mode ('on') and setting the link to operate as an 802.1Q trunk.
Cisco AireOS WLCs utilize static Link Aggregation (LAG) and do not support dynamic EtherChannel negotiation protocols like LACP or PAgP. Consequently, switch ports connected to an AireOS controller must be set to static mode ('channel-group mode on'). Furthermore, since LAG bundles all physical controller ports into a single logical connection handling multiple SSIDs and management traffic, the upstream switch interface must be configured as an 802.1Q trunk port.

Step-by-Step Solution

1
Determine controller LAG protocol support.
AireOS WLCs support static Link Aggregation (LAG) without using dynamic negotiation protocols such as LACP or PAgP.
Because the controller does not exchange LACP or PAgP packets, the switch ports must force EtherChannel creation using 'channel-group mode on'.
2
Determine switchport trunking configuration.
Configure the switch port-channel as an 802.1Q trunk carrying management and dynamic client VLANs.
Enabling LAG on a WLC aggregates all physical distribution ports into a single trunk link capable of carrying untagged management traffic and tagged dynamic client VLAN traffic.

Key Concept

Cisco AireOS WLC Link Aggregation (LAG) and Switchport Trunking Requirements
Question 19Question

A network administrator is connecting a Cisco Catalyst 9800 Series Wireless LAN Controller to an upstream Cisco Catalyst switch using link aggregation (LAG) with LACP. In what logical order should the administrator execute the steps on the Catalyst switch to provision the EtherChannel interface and physical member ports?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with creating the logical port-channel interface on the switch, applying trunking and VLAN parameters to that logical interface, selecting the physical member interfaces, adding the physical interfaces to the EtherChannel using active LACP mode, and finally verifying bundle operation with the 'show etherchannel summary' command.
To establish link aggregation between a Cisco Catalyst switch and a Cisco Wireless LAN Controller using LACP, standard configuration methodology requires initializing the logical port-channel interface first. Trunking settings (such as switchport mode trunk and VLAN assignments) are defined on the logical port-channel. Next, the target physical member interfaces are selected and bound to the channel group using active LACP mode. Finally, running operational verification commands confirms proper link aggregation state.

Step-by-Step Solution

1
Create the virtual port-channel interface
The logical interface Port-channel 1 is initialized.
Creating the logical interface first provides the administrative entity where trunking parameters will be defined.
2
Configure trunking properties on the port-channel
The port-channel interface is set to switchport mode trunk with explicit native and allowed VLAN parameters.
Defining trunk settings directly on the port-channel interface guarantees uniform configuration for all associated physical ports.
3
Select physical switch interfaces
The physical ports connected to the wireless controller are selected via interface range configuration mode.
Grouping physical interfaces prepares them for enrollment into the EtherChannel bundle.
4
Bind physical ports to the channel group using LACP
The command 'channel-group 1 mode active' enables dynamic LACP negotiation on the physical ports.
LACP active mode allows the switch to initiate negotiation with the Wireless LAN Controller.
5
Verify EtherChannel operation
Output displays flag 'SU' for the port-channel and flag 'P' for each active member port.
Verifying status confirms that LACP negotiation succeeded and traffic can be forwarded across the aggregated links.

Key Concept

Cisco switch EtherChannel and LACP configuration for WLC trunking
Question 20Question

A network engineer is configuring link aggregation (LAG) on a Cisco Wireless LAN Controller (WLC) to connect to a Cisco Catalyst switch stack. The WLC distribution system ports are connected to ports GigabitEthernet1/0/1 through GigabitEthernet1/0/4 on the switch stack.

Which behavior accurately describes how the Wireless LAN Controller manages interface traffic and link failures when LAG is enabled?

Show answer & explanation

Answer: All distribution system ports are combined into a single logical port channel, and if an individual physical link fails, traffic is dynamically redistributed across the remaining active links without interrupting wireless traffic.

Answer

All distribution system ports are combined into a single logical port channel, and if an individual physical link fails, traffic is dynamically redistributed across the remaining active links without interrupting wireless traffic.
When Link Aggregation (LAG) is enabled on a Wireless LAN Controller, all physical distribution system ports are combined into a single logical EtherChannel trunk. Traffic across all configured WLANs and management interfaces is load-balanced across the active links. If any physical port in the bundle experiences a failure, the controller and upstream switch immediately re-route traffic over the remaining operational member links without dropping client sessions or requiring manual intervention.

Step-by-Step Solution

1
Identify the operational characteristics of Link Aggregation (LAG) on a Wireless LAN Controller.
Enabling LAG merges all physical distribution system ports into a single logical EtherChannel/port-channel interface.
Bundling ports provides both increased aggregate throughput and full link redundancy for all controller-managed VLANs.
2
Analyze how traffic distribution and fault tolerance function within the unified LAG bundle.
If a physical link within the LAG fails, the WLC immediately redistributes client and management traffic over the remaining operational links.
Redistribution happens transparently at Layer 2 without requiring manual remapping of WLANs or AP management interfaces.

Key Concept

WLAN Infrastructure Connections and LAG Operation
Estimated Time:1m 0s
Page 1 / 2Next