PART 13 - BEST WIRELESS CLIENT TROUBLESHOOTING STEPS

FOLLOW BELOW STEPS FOR WIRELESS CLIENT TROUBLESHOOTING 

Part 1:

-          At the WLC run the following debugs:

WLC > debug client <client MAC address>

-          Try to connect.

-          Once you are connected collect:

WLC > show client detail <client MAC address>

**If the client is not in RUN state stop here.

Part 2:

-          Once the client is in Run state:

Ping the client GW. Does it receive a response? (get a screenshot).

Ping 8.8.8.8. Does it receive a response? (get a screenshot).

**If the client is receiving response from the GW stop here.

Part 3:

-          If no response from the GW follow these steps:

1.       Run “debug client <client MAC address>” on the WLC.

2.       Collect wired captures from the AP switch port.

3.       Collect “show client detail <client MAC address>” from the WLC.

4.       Ping the GW multiple times.

5.       Ping 8.8.8.8 multiple times.

Please find the following steps to collect wired packet captures from the WLC:

-          Connect a PC to the switch in which the WLC is connecting to.

-          Type the following command in the switch CLI :

Switch(config)# monitor session 1 source interface ( the WLC interface ) if you are using LAG then it's the port channel

Switch(config)# monitor session 1 destination interface ( the interface  in which the PC is connecting to )

-          Start running the Wireshark capture on the PC.

-          Keep it connecting till the issue is re-produced.

"WLC proxy enabled, then WLC will use its dynamic interface (in my case vlan 1422) assigned to WLAN to relay this 

Discovery msg to DHCP server. This is how DHCP server get to know which subnet IP to be allocated to this client."

"Once WLC hear from WLC (DHCP Offer) then it will pass that to the client. Note that WLC use its virtual address as source IP

 when passing it to client (DHCP proxy). This will provide the offered IP detail & other DHCP option to client."