Deploying and Troubleshooting Cisco Wireless LAN Controllers

Troubleshooting WLC Issues (Cisco Wireless LAN Controllers)

How would you begin to troubleshoot an AP that does not register with a WLC issue? You can start by using one of the most basic but important debug commands: debug lwapp events enable. Note If you are enabling large amounts of debugs or global debugs—debugs that apply to all devices—the console can become unresponsive […]

AP Discovery and Join Process (Cisco Wireless LAN Controllers)

Access point (AP) registration consists of a discovery and join process. Registration is the first step in getting your wireless network up and running. If you understand how the discovery and join process works, your job will be much easier when you have to trou-bleshoot it. One of the major selling points of the AP […]

Troubleshooting Network Connectivity and AP Registration (Cisco Wireless LAN Controllers)

The following section can help you troubleshoot connectivity issues between the AP and the WLC. In most cases, registration and join issues can be resolved with debugs and analysis of configurations. In other situations a wireless trace is needed—sometimes concurrent. This also includes the use of wireless sniffers. Verifying VLAN Configuration The configuration of the […]

Understanding the AP Discovery and AP Join Process (Cisco Wireless LAN Controllers)

In a CAPWAP environment, a LAP discovers a controller by using CAPWAP discovery mechanisms and then sends the controller a CAPWAP join request. The controller sends the AP a CAPWAP join response, allowing the AP to join the controller. When the AP joins the controller, the controller manages its configuration, firmware, control transactions, and data […]

Troubleshooting the AP Discovery and AP Join Process (Cisco Wireless LAN Controllers)

Many people cringe when faced with the complicated task of troubleshooting. The debugs might look like another language, but the key here is to practice. The more you practice, the easier the debugs are to perform and read. If you break down the debugs that are available to you, you will have the following commands. […]

Client Roaming/Mobility Events (Cisco Wireless LAN Controllers)

A mobility event occurs if a client roams between access points (AP) or between controllers. If the wireless LAN (WLAN) is secured, 802.1x or Wi-Fi Protected Access (WPA), the client must reauthenticate to comply with the 802.11i IEEE standard. You want this process to have low latency and appear as transparent to the user as […]

AP Groups (Cisco Wireless LAN Controllers)

When you create a WLAN on the controller, you have to assign an interface to that WLAN for the client traffic to use. Imagine that you have a 4404 series controller with 100 registered APs and 25 clients per AP on the same WLAN. You now have 2500 clients on the same subnet. The initial […]

Mobility Groups (Cisco Wireless LAN Controllers)

A mobility group is a collection of controllers that share RF, client, and AP information. Mobility has two categories: mobility domains (or lists) and mobility groups. If controllers are in the same mobility domain, they are present in the mobility configuration lists of the others, and the controllers listed recognize and communicate with one another. […]

Mobility Messaging (Cisco Wireless LAN Controllers) Part 1

Controllers use mobility messages to hand off client state and set up a mobility tunnel session among group members for a mobile client. The Mobility Protocol is the protocol that controllers use for this message exchange. The Mobility Protocol employs a series of announcements, handoffs, and session termination messages as clients roam between controllers in […]

Mobility Messaging (Cisco Wireless LAN Controllers) Part 2

Mobility Session Termination Message A Mobility Session termination will be sent only when the controllers need to end an Export Foreign-Export Anchor relationship. The session termination may be initiated by either the foreign or anchor controller and requires only two packets. The termination might be required because of a client disconnect, timeout, or for administrative […]

← Previous Entries

Next Entries →