Cisco Cisco Access Registrar 4.2 Especificaciones descargar pdf (Pagina 523)

12-15

Cisco Wireless LAN Controller Configuration Guide

OL-13826-01

Chapter 12 Configuring Hybrid REAPWireless Device Access

Configuring Hybrid REAP

• config ap h-reap vlan native vlan-id Cisco_AP—Enables you to configure a native VLAN for this

hybrid-REAP access point. By default, no VLAN is set as the native VLAN. One native VLAN must

be configured per hybrid-REAP access point (when VLAN tagging is enabled). Make sure the

switchport to which the access point is connected has a corresponding native VLAN configured as

well. If the hybrid-REAP access point’s native VLAN setting and the upstream switchport native

VLAN do not match, the access point cannot transmit packets to and from the controller.

Use these commands on the hybrid-REAP access point to obtain status information:

• show lwapp reap status—Shows the status of the hybrid-REAP access point (connected or

standalone).

• show lwapp reap association—Shows the list of clients associated to this access point and their

SSIDs.

Use these commands on the hybrid-REAP access point to obtain debug information:

• debug lwapp reap—Shows general hybrid-REAP activities.

• debug lwapp reap mgmt—Shows client authentication and association messages.

• debug lwapp reap load—Shows payload activities, which is useful when the hybrid-REAP access

point boots up in standalone mode.

• debug dot11 mgmt interface—Shows 802.11 management interface events.

• debug dot11 mgmt msg—Shows 802.11 management messages.

• debug dot11 mgmt ssid—Shows SSID management events.

• debug dot11 mgmt state-machine—Shows the 802.11 state machine.

• debug dot11 mgmt station—Shows client events.

Connecting Client Devices to the WLANs

Follow the instructions for your client device to create profiles to connect to the WLANs you created in

the “Configuring the Controller for Hybrid REAP” section on page 12-6.

In our example, you would create three profiles on the client:

1. To connect to the “employee” WLAN, you would create a client profile that uses WPA/WPA2 with

PEAP-MSCHAPV2 authentication. Once the client becomes authenticated, it should get an IP

address from the management VLAN of the controller.

2. To connect to the “local-employee” WLAN, you would create a client profile that uses WPA/WPA2

authentication. Once the client becomes authenticated, it should get an IP address from VLAN 101

on the local switch.

3. To connect to the “guest-central” WLAN, you would create a client profile that uses open

authentication. Once the client becomes authenticated, it should get an IP address from VLAN 101

on the network local to the access point. Once the client connects, the local user can type any http

address in the web browser. The user is automatically directed to the controller to complete the

web-authentication process. When the web login page appears, the user enters his or her username

and password.

To see if a client’s data traffic is being locally or centrally switched, click Monitor > Clients on the

controller GUI, click the Detail link for the desired client, and look at the Data Switching parameter

under AP Properties.

1 2 ... 518 519 520 521 522 523 524 525 526 527 528 ... 635 636

Comentarios a estos manuales

Sin comentarios

Cisco Cisco Access Registrar 4.2 Especificaciones Pagina 523

Comentarios a estos manuales