Cisco 2504 Specifications download pdf (Page 59)

4-59

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 4 Configuring Controller Settings

Configuring Client Roaming

00:13:02:23:82:ad 0:20

Using the CLI to View an Access Point’s Multicast Client Table

To help troubleshoot roaming events, you can view an access point’s multicast client table from the

controller by performing a remote debug of the access point.

To view an access point’s multicast client table using the controller CLI, follow these steps:

Step 1 Initiate a remote debug of the access point by entering this command:

debug ap enable Cisco_AP

Step 2 See all of the MGIDs on the access point and the number of clients per WLAN by entering this

command:

debug ap command “show capwap mcast mgid all” Cisco_AP

Step 3 See all of the clients per MGID on the access point and the number of clients per WLAN by entering this

command:

debug ap command “show capwap mcast mgid id mgid_value” Cisco_AP

Configuring Client Roaming

The Cisco UWN Solution supports seamless client roaming across lightweight access points managed

by the same controller, between controllers in the same mobility group on the same subnet, and across

controllers in the same mobility group on different subnets. Also, in controller software release 4.1 or

later releases, client roaming with multicast packets is supported.

You can adjust the default RF settings (RSSI, hysteresis, scan threshold, and transition time) to fine-tune

the operation of client roaming using the controller GUI or CLI.

Intra-Controller Roaming

Each controller supports same-controller client roaming across access points managed by the same

controller. This roaming is transparent to the client as the session is sustained, and the client continues

using the same DHCP-assigned or client-assigned IP address. The controller provides DHCP

functionality with a relay function. Same-controller roaming is supported in single-controller

deployments and in multiple-controller deployments.

Inter-Controller Roaming

Multiple-controller deployments support client roaming across access points managed by controllers in

the same mobility group and on the same subnet. This roaming is also transparent to the client because

the session is sustained and a tunnel between controllers allows the client to continue using the same

DHCP- or client-assigned IP address as long as the session remains active. The tunnel is torn down, and

the client must reauthenticate when the client sends a DHCP Discover with a 0.0.0.0 client IP address or

a 169.254.*.* client auto-IP address or when the operator-set session timeout is exceeded.

1 2 ... 54 55 56 57 58 59 60 61 62 63 64 ... 121 122

No comments

Cisco 2504 Specifications Page 59