Cisco Cisco 2106 Wireless LAN Controller

Página de 44
 
19
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 6.0.188.0
OL-31336-01
  Important Notes for Controllers and Non-Mesh Access Points
b.
Click Wireless LAN Controllers.
c.
Click Standalone Controllers.
d.
Click Cisco 5500 Series Wireless LAN Controllers.
e.
Click Cisco 5508 Wireless LAN Controller.
f.
Choose the USB driver file.
g.
Save the file to your hard drive.
Step 2
Connect the Type A connector to a USB port on your PC.
Step 3
Connect the mini Type B connector to the USB console port on the controller.
Step 4
When prompted for a driver, browse to the USB_Console.inf file on your PC. Follow the prompts to 
install the USB driver.
Note
Some systems might also require an additional system file. You can download the Usbser.sys file 
from the Microsoft website
The USB driver is mapped to COM port 6. Some terminal emulation programs do not recognize a port 
higher than COM 4. If necessary, change the Cisco USB systems management console COM port to an 
unused port of COM 4 or lower. To do so, follow these steps:
Step 1
From your Windows desktop, right-click My Computer and choose Manage.
Step 2
From the list on the left side, choose Device Manager.
Step 3
From the device list on the right side, double-click Ports (COM & LPT).
Step 4
Right-click Cisco USB System Management Console 0108 and choose Properties.
Step 5
Click the Port Settings tab and click the Advanced button.
Step 6
From the COM Port Number drop-down box, choose an unused COM port of 4 or lower.
Step 7
Click OK to save; then close the Advanced Settings dialog box.
Step 8
Click OK to save; then close the Communications Port Properties dialog box.
Important Notes for Controllers and Non-Mesh Access Points
This section describes important information about controllers and non-mesh lightweight access points.
One-Time Password (OTP) Support
One Time Passwords (OTP) are supported on the Wireless Lan Controller (WLC) using TACACS and 
RADIUS. In this configuration, the controller acts as a transparent pass-thru device. The controller 
forwards all client requests to the TACACS/RADIUS server without inspecting the client behavior.  
When using OTP the client must only establish a single connection to the controller to function properly.  
The controller currently does not have any intelligence or checks to correct a client that is trying to 
establish multiple connections.