Brocade Communications Systems RFS6000 System Reference Manual page 543
Provides centralized wireless lan (wlan)
Hide thumbs
Also See for RFS6000:
- Cli reference manual (839 pages) ,
- System reference manual (574 pages)
Table of Contents
Advertisement
Access Port Adopted, but client is Not Being Associated
Access Port associated with a client is not yet being adopted. The table below provides suggestions
to troubleshoot this issue.
Possible Problem
Unadopted Access Port
Incorrect ESSID applied to
the client
Ethernet port configuration
issues
Incorrect security settings
All else...
Clients Cannot Associate and/or Authenticate with Access Ports
Clients cannot associate and/or authenticate with Access Ports.
The table below provides suggestions to troubleshoot this issue.
Possible Problem
Preamble differences
Device key issues
client is not in Adopt List
Keyguard not set on client
Encryption Problems
Authentication Problems
Encryption or Authentication
Problems
Brocade Mobility RFS4000, RFS6000, and RFS7000 System Reference Guide
53-1002515-01
Suggestions to Correct
Verify that the switch has adopted the Access Port with which the client is trying to
associate.
Verify on the client that the correct ESSID has been applied to the client.
•
Verify that the Ethernet port connected to the network and has a valid
configuration.
•
If DHCP is used, verify that the Ethernet cable is connected to the same NIC
upon which DHCP services are enabled.
Verify that the correct security settings are applied to a WLAN in which the client
is trying to associate.
Contact Brocade Support.
Suggestions to Correct
Verify that the preamble type matches between switch and Clients. Try a different
setting.
Verify in Syslog that there is not a high rate of decryption error messages. This
could indicate that a device key is incorrect.
Verify the device is not in the "do not adopt ACL".
Verify Keyguard is set on the client if the Security/WLAN Policy calls for Keyguard.
If Encryption is being used, verify that the encryption settings on the client and
the switch match.
If WEP Encryption is being used with non-Symbol or Brocade Clients, ensure that
the key being entered is in HEX format and not a Passphrase.
If the switch is configured to use RADIUS authentication, check the RADIUS log
file for any failure information.
If you are using Authentication and/or Encryption on the switch, and the previous
troubleshooting steps have not fixed the problem, try temporarily disabling
Authentication and Encryption to see if that fixes the problem.
B
531
Advertisement
Table of Contents
Troubleshooting
