Workgroup Bridge Guidelines; Configuring Vlan And Qos Support (Cli) - Cisco Mesh Access Points Deployment Manual

Multiple VLAN and QoS Support for WGB Wired Clients
You must enable the WGB unified client for multiple VLAN support on the WGB by entering the
workgroup-bridge unified-VLAN-client command. This WGB unified client is disabled by default.
You have to configure subinterfaces on the WGB that corresponds to the VLANs on the switch ports to which
the wired clients are connected.

Workgroup Bridge Guidelines

Follow these guidelines when configuring WGBs:
• A dynamic interface should be created in the controller for each VLAN that is configured in the WGB.
• Only one WLAN (SSID) for a wireless association of the WGB to the access point infrastructure is
supported. This SSID should be configured as an infrastructure SSID and should be mapped to the native
VLAN. The WGB drops everything that is not in the native VLAN in the mesh infrastructure.
• We recommend that you configure the same native VLAN in the switch that connects the WLC, WGB,
and in the switch behind the WGB.
All native VLAN clients on the WGB Ethernet side are part of the same VLAN in which the WGB is
associated. The WGB is part of the VLAN to which the WLAN (in which the WGB has associated) is
mapped.
For example, if in the WGB, the 5-GHz radio (dot11radio 1) is mapped to a native VLAN 184, and the
switch behind WGB has wired clients only in VLAN 185 and 186, then you may not require the native
VLAN to be identical to the native VLAN on the WGB (VLAN 184).
But, if you add one wired client in VLAN 184 and this VLAN client in the WGB belongs to a native
VLAN, you must define the same native VLAN on the switch.
• Intersubnet mobility is supported with this feature for VLAN clients behind the WGB with a limitation
that the dynamic interface for all VLANs of the WGB should be configured in all the controllers.
• Interoperability with a VLAN-pooling feature is not supported. When the VLAN-pooling feature is
enabled, the WGB and its native VLAN clients become part of the same VLAN.
• AAA-override for WGB clients is not supported, but AAA-override for the WGB is supported.
• Only Layer 3 multicast is provided for WGB VLAN clients and there is no support for Layer 2 multicast.
• There is a 20-client limitation in WGB that includes wireless clients.
• Link testing for WGB wired clients is not supported.
• Roaming is supported for wireless and wired clients behind WGB.
• Multicast is supported for wired clients behind WGB.
• Broadcast is supported.

Configuring VLAN and QoS Support (CLI)

In the following example, VLANs 184 and 185 exist on the wired switch behind WGB. WGB's native VLAN
is 184. SSID is auto-wgb mapped to native VLAN 184. Radio 1 (5 GHz) radio is used to connect to the
CAPWAP infrastructure using this SSID.
config t
ap#
ap(config)#
Cisco Mesh Access Points, Design and Deployment Guide, Release 7.3
252
workgroup-bridge unified-VLAN-client
Managing Mesh Access Points with Cisco Prime Infrastructure
OL-27593-01