Specifications

Troubleshooting AOS-W Environments 591

Chapter 27

z Ensure that the wireless network is operational and that no APs or

switches have failed. If part of the network has failed, it is likely that mul-

tiple users will report problems. Note that in a standard dense-mode Alca-

tel deployment, multiple APs will normally be able to provide service to one

user, so the failure of one AP is unlikely to cause this symptom.

z Enable client debugging for the client device in question. From the Alcatel

CLI, use the command “aaa user debug mac <MAC address of client>”.

Log output from the debug process can be viewed by issuing the com-

mand “show log intuser 30” (to display the last 30 lines of the log file).

Verify that the switch is receiving probe requests from the client.

z Perform a wireless packet capture through the Alcatel system for the

appropriate area where the user is located. Filter the capture for the user’s

MAC address. A packet capture is a sure way to find out if the client is

transmitting probe-requests, if the probe-requests contain the correct

ESSID, and if an AP is answering probe-requests.

z Reset the client NIC or operating system. In the case of malfunctioning cli-

ent software, this does not fix the underlying problem but is often the fast-

est way to get the user back on the network.

z Replace the client NIC. If a packet capture appears normal and client

mis-configuration has been ruled out, it is possible that the client NIC has

failed.

Client’s list of available networks contains some entries, but not

the correct ESSID

Consider the following possible fixes:

z If responses to broadcast probe-requests have been disabled in the Alcatel

network, ensure that the client has been configured with the proper ESSID.

If the ESSID is incorrect, the client will not be able to locate any APs.