
5-33
Cisco Wireless LAN Controller Configuration Guide
OL-13826-01
Chapter 5 Configuring Security Solutions
Configuring the System for SpectraLink NetLink Telephones
Step 13 If necessary, you can use these commands to troubleshoot local EAP sessions:
• debug aaa local-auth eap method {all | errors | events | packets | sm} {enable | disable}—
Enables or disables debugging of local EAP methods.
• debug aaa local-auth eap framework {all | errors | events | packets | sm} {enable | disable}—
Enables or disables debugging of the local EAP framework.
Note In these two debug commands, sm is the state machine.
• clear stats local-auth—Clears the local EAP counters.
Configuring the System for SpectraLink NetLink Telephones
For best integration with the Cisco UWN Solution, SpectraLink NetLink Telephones require an extra
operating system configuration step: enable long preambles. The radio preamble (sometimes called a
header) is a section of data at the head of a packet that contains information that wireless devices need
when sending and receiving packets. Short preambles improve throughput performance, so they are
enabled by default. However, some wireless devices, such as SpectraLink NetLink phones, require long
preambles.
Use one of these methods to enable long preambles:
• Using the GUI to Enable Long Preambles, page 5-33
• Using the CLI to Enable Long Preambles, page 5-34
Using the GUI to Enable Long Preambles
Use this procedure to use the GUI to enable long preambles to optimize the operation of SpectraLink
NetLink phones on your wireless LAN.
Step 1 Click Wireless > 802.11b/g/n > Network to open the 802.11b/g Global Parameters page.
Step 2 If the Short Preamble check box is checked, continue with this procedure. However, if the Short
Preamble check box is unchecked (which means that long preambles are enabled), the controller is
already optimized for SpectraLink NetLink phones and you do not need to continue this procedure.
Step 3 Uncheck the Short Preamble check box to enable long preambles.
Step 4 Click Apply to update the controller configuration.
Note If you do not already have an active CLI session to the controller, Cisco recommends that you
start a CLI session to reboot the controller and watch the reboot process. A CLI session is also
useful because the GUI loses its connection when the controller reboots.
Komentáře k této Příručce