Руководство По Проектированию для Cisco Cisco Aironet 350 Mini-PCI Wireless LAN Client Adapter
10-20
Enterprise Mobility 4.1 Design Guide
OL-14435-01
Chapter 10 Cisco Unified Wireless Guest Access Services
Guest Access Configuration
Adding the Anchor WLC as a Mobility Group Member of a Foreign WLC
As described in
, each foreign WLC
maps the guest WLAN into an EoIP tunnel that terminates on the anchor WLC. Therefore, the anchor
WLC(s) must be defined as a mobility group member in each foreign controller. In the example below,
note that the group name entry for the anchor WLC is 'ANC' (see
WLC(s) must be defined as a mobility group member in each foreign controller. In the example below,
note that the group name entry for the anchor WLC is 'ANC' (see
) whereas the other WLCs that comprise the enterprise wireless
deployment are members of the mobility group: 'SRND’.
Step 1
Click New to add the anchor WLC's IP, MAC address, and Group Name to the mobility members table.
Step 2
Repeat these steps for each additional foreign controller. (See
.)
Figure 10-14
Adding Anchor Controller(s) to Foreign WLC
Note
If guest N+1 anchor redundancy capability is being deployed, two or more anchor WLC entries are
added to each foreign WLC’s Mobility Group Members list.
added to each foreign WLC’s Mobility Group Members list.
Guest WLAN Configuration
The following section describes how to configure a single guest WLAN. The guest WLAN is configured
on every foreign WLC that manages APs where guest access is required. Even though the anchor
WLC(s) is not specifically used to manage LAPs associated with a guest WLAN, it must also be
configured with the guest WLAN because the anchor WLC is a logical extension of the WLAN where
user traffic is ultimately bridged (using LWAPP between the AP and the foreign controller, and EoIP
between the foreign controller and the anchor controller) to an interface/VLAN on the anchor WLC.
on every foreign WLC that manages APs where guest access is required. Even though the anchor
WLC(s) is not specifically used to manage LAPs associated with a guest WLAN, it must also be
configured with the guest WLAN because the anchor WLC is a logical extension of the WLAN where
user traffic is ultimately bridged (using LWAPP between the AP and the foreign controller, and EoIP
between the foreign controller and the anchor controller) to an interface/VLAN on the anchor WLC.
Note
It is extremely important to note that all parameters defined in the WLAN Security, QoS, and Advanced
settings tabs, must be configured identically in both the anchor and foreign WLC(s).
settings tabs, must be configured identically in both the anchor and foreign WLC(s).
shows
a high level diagram illustrating the WLAN configuration discussed below.