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

100

101

7-56

Cisco Wireless LAN Controller Configuration Guide

OL-13826-01

Chapter 7 Controlling Lightweight Access Points

Configuring Backup Controllers

Using the CLI to Debug WGB Issues

Use the commands in this section if you experience any problems with the WGB.

1. To enable debugging for IAPP messages, errors, and packets, enter these commands:

• debug iapp all enable—Enables debugging for IAPP messages.

• debug iapp error enable—Enables debugging for IAPP error events.

• debug iapp packet enable—Enables debugging for IAPP packets.

2. If you experience a roaming issue, enter this command:

debug mobility handoff enable

3. If you experience an IP assignment issue and DHCP is used, enter these commands:

• debug dhcp message enable

• debug dhcp packet enable

4. If you experience an IP assignment issue and static IP is used, enter these commands:

• debug dot11 mobile enable

• debug dot11 state enable

Configuring Backup Controllers

A single controller at a centralized location can act as a backup for access points when they lose the

primary controller in the local region. Centralized and regional controllers need not be in the same

mobility group. Using the controller CLI, you can specify a primary, secondary, and tertiary controller

for your network’s access points. In controller software release 4.2, you can specify the IP address of the

backup controller, which allows the access points to fail over to controllers outside of the mobility group.

This feature is currently supported only through the controller CLI.

Note When an access point’s primary controller comes back online, the access point disassociates from the

backup controller and reconnects to its primary controller. The access point falls back to its primary

controller and not to any secondary controller for which it is configured. For example, if an access point

is configured with primary, secondary, and tertiary controllers, it fails over to the tertiary controller when

the primary and secondary controllers become unresponsive and waits for the primary controller to come

back online so that it can fall back to the primary controller. The access point does not fall back from the

tertiary controller to the secondary controller if the secondary controller comes back online; it stays

connected to the tertiary controller until the primary controller comes back up.

Using the CLI to Configure Backup Controllers

Using the CLI, follow these steps to configure primary, secondary, and tertiary controllers for specific

access points.

Step 1 To configure a primary controller for a specific access point, enter this command:

config ap primary-base controller_name Cisco_AP [controller_ip_address]

1 2 ... 361 362 363 364 365 366 367 368 369 370 371 ... 635 636

Comentarios a estos manuales

Sin comentarios

Cisco Cisco Access Registrar 4.2 Especificaciones Pagina 366

Comentarios a estos manuales