Cisco Cisco Access Registrar 4.2 Spezifikationen PDF herunterladen (Seite 352)

7-42

Cisco Wireless LAN Controller Configuration Guide

OL-13826-01

Chapter 7 Controlling Lightweight Access Points

Autonomous Access Points Converted to Lightweight Mode

This is the format of the TLV block:

• Type: 0xf1 (decimal 241)

• Length: Number of controller IP addresses * 4

• Value: List of the IP addresses of controller management interfaces

In controller software release 4.2, 1000 series access points configured with a static IP address can

retrieve the domain name and server, the syslog server IP address, and a list of controllers by querying

the DHCP server. This capability applies only to 1000 series access points and not to any other

lightweight access points.

Refer to the product documentation for your DHCP server for instructions on configuring DHCP option

43. The Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode document contains

example steps for configuring option 43 on a DHCP server.

Troubleshooting the Access Point Join Process

Access points can fail to join a controller for many reasons, including a pending RADIUS authorization,

self-signed certificates not being enabled on the controller, a regulatory domain mismatch between the

access point and the controller, and so on. In controller software releases prior to 4.2, the only way to

obtain information about an access point that is having a problem joining a controller is to access the

access point through the console port to see the error messages or to enable various LWAPP debug

commands on the controller. These tasks can impact the controller’s performance in cases where a large

number of access points are deployed and few of them have trouble joining the controller. In this

situation, if LWAPP debug commands are enabled, the controller is flooded with LWAPP error messages

and can become unreachable.

To avoid this situation and to better troubleshoot access point joining issues, controller software release

4.2 enables you to configure the access points to send all LWAPP-related errors to a syslog server. You

do not need to enable any debug commands on the controller because all of the LWAPP error messages

can be viewed from the syslog server itself.

The state of the access point is not maintained on the controller until it receives an LWAPP join request

from the access point. Therefore, it can be difficult to determine why the LWAPP discovery request from

a certain access point was rejected. In order to troubleshoot such joining issues without enabling LWAPP

debug commands on the controller, the controller collects information for all access points that send a

discovery message to this controller and maintains information for any access points that have

successfully joined this controller.

The controller collects all join-related information for each access point that sends an LWAPP discovery

request to the controller. Collection begins with the first discovery message received from the access

point and ends with the last configuration payload sent from the controller to the access point.

Table 7-3 VCI Strings For Lightweight Access Points

Access Point VCI String

Cisco 1000 Series Airespace 1200

Cisco Aironet 1130 Series Cisco AP c1130

Cisco Aironet 1200 Series Cisco AP c1200

Cisco Aironet 1240 Series Cisco AP c1240

1 2 ... 347 348 349 350 351 352 353 354 355 356 357 ... 635 636

Kommentare zu diesen Handbüchern

Keine Kommentare

Cisco Cisco Access Registrar 4.2 Spezifikationen Seite 352

Kommentare zu diesen Handbüchern