advertisement
C H A P T E R
2
Getting Started
This chapter describes how to prepare WCS for operation. It contains these sections:
•
•
•
•
•
•
•
Installing WCS for Windows, page 2-4
Installing WCS for Linux, page 2-9
Logging into the WCS User Interface, page 2-12
Using the Cisco WCS User Interface, page 2-14
OL-12623-01
Cisco Wireless Control System Configuration Guide
2-1
Chapter 2 Getting Started
Prerequisites
Prerequisites
Before installing the Cisco WCS, ensure that you have completed the following:
•
Met the necessary hardware and software requirements as listed in
“System Requirements” section on page 2-2
for Cisco WCS.
•
Updated your system with the necessary critical updates and service packs.
Note
Refer to the latest release notes for information on the service packs and patches required for correct operation of Cisco WCS.
•
•
Made a backup of the existing Cisco WCS database. For more information on doing a Windows backup, refer to
“Backing Up the WCS Database” section on page 11-4
.
Uninstalled the older version of the Cisco WCS. For more information on uninstalling Cisco WCS, refer to the
“Uninstalling WCS” section on page 11-14
.
System Requirements
Cisco WCS can be run on a workstation/server class system and access points can be distributed unevenly across controllers. It requires the followingCisco WCS:
High End Server
–
Up to 3000 Cisco Aironet lightweight access points and 750 Cisco wireless LAN controllers.
–
–
3.15-GHz Intel Xeon Quad processor with 8-GB RAM and 200-GB hard drive.
80-GB minimum free disk space on your hard drive.
Note
The free disk space listed is a minimum requirement but may be different for your system, depending on the number of backups.
The following operating system is supported:
–
Windows 2003/SP1 or later with all critical and security Windows updates installed.
Note
Cisco WCS is supported only on English or Japanese versions of the Windows 2003 operating system. Display problems sometimes occur when you install and run Cisco
WCS on operating systems translated to other languages or with locale settings other than English or Japanese.
–
Red Hat Enterprise Linux Enterprise Server 4.0 or Advanced Server 4.0. Only 32-bit OS installations are supported. 64-bit installations are not supported.
–
Windows 2003 version support on VmWare ESX 3.0.1 version and above.
2-2
Cisco Wireless Control System Configuration Guide
OL-12623-01
Chapter 2 Getting Started
System Requirements
OL-12623-01
Note
When running WCS on a dedicated VmWare server, these minimum hardware requirements are necessary based on WCS high-end server hardware specifications:
— Quad CPU running at 3.15 GHz
— 8 GBs RAM
— 200 GB hard drive
•
Standard Server
–
–
Up to 2000 Cisco Aironet lightweight access points and 500 Cisco wireless LAN controllers.
3.2-GHz Intel Dual Core processor with 4-GB RAM and 80-GB hard drive.
–
40-GB minimum of free disk space on your hard drive.
The following operating systems are supported:
–
Windows 2003/SP1 or later with all critical and security Windows updates installed.
Note
Cisco WCS is supported only on English or Japanese versions of the Windows 2003 operating system. Display problems sometimes occur when you install and run Cisco
WCS on operating systems translated to other languages or with locale settings other than English or Japanese.
•
–
Red Hat Enterprise Linux Enterprise Server 4.0 or Advanced Server 4.0. Only 32-bit OS installations are supported. 64-bit installations are not supported.
Low End Server
–
Up to 500 Cisco Aironet lightweight access points and 125 Cisco wireless LAN controllers.
–
–
3.06-GHz Intel processor with 2-GB RAM and 30-GB hard drive.
30-GB minimum free disk space on your hard drive.
The following operating systems are supported:
–
Windows 2003/SP1 or later with all critical and security Windows updates installed.
Note
Cisco WCS is supported only on English or Japanese versions of the Windows 2003 operating system. Display problems sometimes occur when you install and run Cisco
WCS on operating systems translated to other languages or with locale settings other than English or Japanese.
•
–
–
–
Red Hat Enterprise Linux Enterprise Server 4.0 or Advanced Server 4.0. Only 32-bit OS installations are supported. 64-bit OS installations are not supported.
WCS on WLSE
–
Up to 1500 Cisco Aironet lightweight access points and 100/375 Cisco wireless LAN controllers.
3-GHz Intel Pentium4 processor with 3 GB RAM
38-GB of free space on your hard drive.
Cisco Wireless Control System Configuration Guide
2-3
Chapter 2 Getting Started
Installing WCS for Windows
•
Requirements for Cisco WCS User Interface—The Cisco WCS user interface requires Internet
Explorer 6.0/SP1 or later, with the Flash plug-in. The Cisco WCS user interface has been tested and verified using Internet Explorer 6.0 on a Windows workstation.
Note
The screen resolution should be set to 1024 x 76 pixels for both WCS and Navigator.
Installing WCS for Windows
This section describes how to install Cisco WCS for Windows operating systems. Before installing Cisco
WCS, refer to the “Prerequisites” section on page 2-2
and the
prior to the installation. You must have administrator privileges on Windows and root on Linux. If installing WCS for Linux, see the
“Installing WCS for Linux” section on page 2-9
.
Guidelines Before Installing WCS
Note •
•
You cannot install the WCS software if the username used to log into the server contains special characters such as exclamation marks (!). To ensure successful installation, log into the server using a username with no special characters before installing the software.
Cisco WCS does not support the underscore character (_) in the name of the Windows server running the WCS software. If the server name contains an underscore, you can install the WCS software, but
WCS fails to start.
•
You must install WCS on a dedicated Windows server with no other services running (including those running as primary or secondary domain controllers) to avoid conflict with WCS.
To install Cisco WCS, follow these steps:
Step 1
Step 2
Insert the Windows Cisco WCS CD into the CD-ROM drive and double click the
WCS-STANDARD-K9-4.0.X.Y.exe file where 4.0.X.Y is the software build. If you received the installer from Cisco.com, double click the WCS-STANDARD-WB-K9-4-0-X-Y.exe file that you downloaded to your local drive.
The Install Anywhere window appears and prepares the system for installation. After a few seconds, the
Introduction window appears. Click Next to open the Check Ports window (see
).
2-4
Cisco Wireless Control System Configuration Guide
OL-12623-01
Chapter 2 Getting Started
Figure 2-1 Check Ports Window
Installing WCS for Windows
Step 3
In the Check Ports window, change the default HTTP and HTTPS ports if necessary and click Next to open the Choose Install Type window (see
Figure 2-2 ). The default ports for HTTP and HTTPS are 80
and 443, respectively.
OL-12623-01
Cisco Wireless Control System Configuration Guide
2-5
Installing WCS for Windows
Figure 2-2 Choose Install Type Window
Chapter 2 Getting Started
Step 4
In the Choose Install Type window, choose either Application or Service and click Next. The FTP File
Server window appears.
•
•
To manually launch the Cisco WCS after installation and have it run on the desktop, select
Application. WCS does not start automatically.
To launch Cisco WCS as a service at reboot and run it in the background (especially useful when the Cisco WCS is to always be online), select Service. WCS automatically starts.
Note
Cisco recommends that you always install WCS as a service because it is designed to run all the time. Use the application selection when you will not be running WCS full time (such as when using it in a product demonstration or in laptop-based troubleshooting).
Step 5
Step 6
Eenter and re-enter the root password. The rules for a strong password are as follows:
•
•
•
•
•
•
The minimum password length is 8.
The password cannot contain the username or the reverse of the username.
The password cannot be Cisco or ocsic (Cisco reversed).
The root password cannot be public.
No character can be repeated more than three times consecutively in the password.
The password must contain a combination of uppercase, lowercase, numbers, and special characters.
Enter the root FTP password.
2-6
Cisco Wireless Control System Configuration Guide
OL-12623-01
Chapter 2 Getting Started
Installing WCS for Windows
Step 7
From the FTP Server File window, choose a folder in which to store the FTP server files and click Next to bring up the TFTP File Server window.
Note
Store the FTP server files in a folder outside the main installation folder. This ensures that the
FTP server files are not deleted if Cisco WCS is uninstalled.
Step 8
From the TFTP Server File window, choose a folder in which to store the TFTP server files and click
Next.
Note
Store the TFTP server files in a folder outside the main installation folder. This ensures that the
TFTP server files are not deleted if Cisco WCS is uninstalled.
If you are installing Cisco WCS on a multi-homed server (a server having multiple interfaces), the installer automatically detects the presence of multiple interfaces and opens the Multi-Homed Server
Detected window (see
Figure 2-3 Multi-Homed Server Detected Window
OL-12623-01
Note
The Multi-Homed Server Detected window does not appear if you install Cisco WCS on a server that has only one interface.
Cisco Wireless Control System Configuration Guide
2-7
Chapter 2 Getting Started
Installing WCS for Windows
Step 9
Click Yes and then Next to configure specific interfaces on the server for communicating with controllers, location appliances, remote FTP servers, and clients. The Select Local Interfaces window appears (see
Figure 2-4 ). Click No if you do no want to configure specific interfaces.
Figure 2-4 Select Local Interfaces Window
Step 10
Step 11
From the Select Local Interfaces window, select the interfaces that are used by the server for communicating with controllers, location appliances and remote FTP servers, and clients. Click Next to open the Choose Install Folder window.
Choose a folder in which to install the Cisco WCS and click Next to open the Choose Shortcut Folder window (see
).
2-8
Cisco Wireless Control System Configuration Guide
OL-12623-01
Chapter 2 Getting Started
Figure 2-5 Choose Shortcut Folder Window
Installing WCS for Linux
Step 12
Step 13
Step 14
In the Choose Shortcut Folder window, choose a location in which to create product icons and click
Next.
Follow the prompts that appear on the screen to complete the installation. After the installation is complete, the Install Complete window appears.
Click Done to complete the installation.
Note
The system must be rebooted to complete the Cisco WCS installation.
Installing WCS for Linux
This section describes how to install Cisco WCS for Linux operating systems.
Note
Before reinstalling or updating Cisco WCS, you may want to back up the Cisco WCS database. After you have a backup, uninstall the old release.
Step 1
Step 2
If not already done, log in as root, and open an X terminal session.
Using the command line, perform one of the following:
a.
If you are installing from a CD, switch to the /media/cdrom directory.
OL-12623-01
Cisco Wireless Control System Configuration Guide
2-9
Chapter 2 Getting Started
Installing WCS for Linux
2-10
Step 3
Step 4
Step 5
Step 6 b.
If you are installing from Cisco.com, switch to the directory that the install file was downloaded to.
For example, if the install file was placed in /root/Desktop, enter cd /root/Desktop.
Enter ./WCS-STANDARD-K9-4.0.X.Y.bin (for CD users) or
./WCS-STANDARD-LB-K9-4-0-X-Y.bin (for Cisco.com users) to start the install script.
The install script prepares the install environment, and several windows of the license agreement display.
You will then be asked if you accept the terms of the license agreement.
Finally, a Check HTTP Port prompt appears. Change the default HTTP port if necessary (the default is
80).
Change the default HTTPS port if necessary (the default is 443).
At the Get User Input prompt, choose either 1 for Application or 2 for Service. To manually launch the
Cisco WCS after installation and have it run on the desktop, select Application. To launch Cisco WCS as a service at reboot and run in the background (especially useful when the Cisco WCS is to always be online), select Service.
Note
Cisco recommends that you always install WCS as a service because it is designed to run all the time.
Step 7
Step 8
Step 9
Step 10
Step 11
Enter and re-enter the root password. The rules for a strong password are as follows:
•
•
•
•
The minimum password length is 8.
The password cannot contain the username or the reverse of the username.
The password cannot be Cisco or ocsic (Cisco reversed).
•
•
The root password cannot be public.
No character can be repeated more than three times consecutively in the password.
The password must contain a combination of uppercase, lowercase, numbers, and special characters.
Enter the root FTP password.
Choose a folder to store the FTP server files. It is recommended that the folder is outside of the WCS installation path so that it is not removed during an uninstall. If the folder does not already exist, you must do mkdir and create it.
Choose a folder to store the TFTP server files. It is recommended that the folder is outside of the WCS installation path so that it is not removed during an uninstall. If the folder does not already exist, you must do mkdir and create it.
If you are installing Cisco WCS on a multi-homed server (a server having multiple interfaces), the installer automatically detects the presence of multiple interfaces and prompts with the multi-homed server detected prompt. You need to choose which interface is used for which application functions. To configure specific interfaces on the server for communicating with controllers, location appliances, remote FTP servers, and clients, type 1 for Yes (recommended). Type 2 for No if you do not want to.
Note
If you do not select a specific interface, Cisco WCS randomly selects an interface and uses this interface to communicate with the devices. This might lead to loss of communication between the interface and the device. Cisco recommends that you always select a specific interface for each device.
Step 12
At the Select Local Interfaces prompt, choose the interfaces to be used by the server for communicating with controllers, location appliances, remote FTP servers, and clients. Enter the number for the interface you want to select.
Cisco Wireless Control System Configuration Guide
OL-12623-01
Chapter 2 Getting Started
Starting WCS
Step 13
Step 14
Step 15
At the Choose Install Folder prompt, choose a folder in which to install the Cisco WCS. Enter an absolute path or press Enter to accept the default.
At the Choose Link Location prompt, choose a folder in which to put the links for the installed software.
This directory houses the StartWCS, StopWCS, Backup, Restore, and UinstallWCS components. The options are to type 1 for the default (opt/WCS4.0), 2 for your home folder, 3 to enter a location, or 4 to not create links.
A pre-installation summary and installing message is displayed to show that the software installation has begun.
Note
You must manually start WCS after installation.
Starting WCS
This section provides instructions for starting WCS on either a Windows or Linux server.
Note
You can check the status of WCS at any time. To do so, follow the instructions in the
Status of WCS” section on page 11-2 .
Starting WCS on Windows
Follow these steps to start WCS when it is installed as a Windows application or Windows service.
Note
When WCS is installed as a Windows service, WCS runs automatically upon system bootup.
Step 1
Step 2
Log into the system as administrator.
Perform one of the following:
•
From the Windows Start menu, click Programs > Wireless Control System> StartWCS.
•
From the command prompt, navigate to the WCS installation directory (C:\Program
Files\WCS32\bin) and enter WCS Admin start.
The WCS Admin window appears and displays messages indicating that WCS is starting.
Note
If WCS is installed as a service, messages also appear to indicate that the Nms_Server service is starting.
Note
If you are starting WCS after a restore from release 4.0.66.0 or earlier, the startup may take longer than expected. The WCS Admin window may even indicate that starting WCS has failed.
Refer to the task viewer to see whether Java is progressively taking CPU space. If so, WCS is up and running.
Step 3
Close the WCSAdmin window when the Close button becomes active.
OL-12623-01
Cisco Wireless Control System Configuration Guide
2-11
Chapter 2 Getting Started
Logging into the WCS User Interface
Step 4
WCS is ready to host WCS user interfaces (clients). Go to the
Starting WCS on Linux
Follow these steps to start WCS when it is installed as a Linux application or Linux service.
Note
To see the version of WCS you currently have installed, enter nmsadmin.sh version.
Note
When WCS is installed as a Linux service, WCS runs automatically upon system bootup.
Step 1
Step 2
Step 3
Log into the system as root.
Using the Linux command line interface (CLI), perform one of the following:
•
•
Navigate to the /opt/WCS32 directory (or the directory chosen during installation) and enter ./StartWCS.
Navigate to the opt/WCS32/bin directory and enter WCSAdmin start.
The CLI displays messages indicating that WCS is starting.
WCS is ready to host WCS user interfaces (clients). Go to the
Logging into the WCS User Interface
Follow these steps to log into the WCS user interface through a web browser.
Step 1
Launch Internet Explorer 6.0 or later on a different computer than the one on which you installed and started WCS.
Note
Some WCS features may not function properly if you use a web browser other than Internet
Explorer 6.0 on a Windows workstation.
Step 2
Step 3
Step 4
In the browser’s address line, enter https://wcs-ip-address, where wcs-ip-address is the IP address of the computer on which you installed and started WCS.
When the WCS user interface displays the Login window, enter the root password which was created during installation.
Click Submit to log into WCS. The WCS user interface is now active and available for use. The Network
Summary page appears. This page provides a summary of the Cisco Unified Wireless Network Solution, including coverage areas, the most recently detected rogue access points, access point operational data,
reported coverage holes, and client distribution over time. Figure 2-6
shows a typical Network Summary page.
2-12
Cisco Wireless Control System Configuration Guide
OL-12623-01
Chapter 2 Getting Started
Logging into the WCS User Interface
Note
When you use WCS for the first time, the Network Summary page shows that the Controllers,
Coverage Areas, Most Recent Rogue APs, Top 5 APs, and Most Recent Coverage Holes databases are empty. It also shows that no client devices are connected to the system. After you configure the WCS database with one or more controllers, the Network Summary page provides updated information.
Figure 2-6 Network Summary Page
OL-12623-01
Note
To exit the WCS user interface, close the browser window or click Logout in the upper right corner of the page. Exiting a WCS user interface session does not shut down WCS on the server.
Cisco Wireless Control System Configuration Guide
2-13
Chapter 2 Getting Started
Using the Cisco WCS User Interface
Note
When a system administrator stops the WCS server during your WCS session, your session ends, and the web browser displays this message: “The page cannot be displayed.” Your session does not reassociate to WCS when the server restarts. You must restart the WCS session.
Using the Cisco WCS User Interface
A typical Cisco WCS user interface page consists of the areas illustrated in
Figure 2-7 WCS User Interface
The following sections describe the Cisco WCS user interface page areas and how to use them:
•
•
•
•
•
•
Administrative Tools, page 2-17
Menu Bar
2-14
There are five menus on each window: Monitor, Reports, Configure, Location, Administration, and
Help. When you move the mouse over any of the menus, a drop-down menu appears.
Cisco Wireless Control System Configuration Guide
OL-12623-01
Chapter 2 Getting Started
Using the Cisco WCS User Interface
Note
The Location menu is displayed only in Cisco WCS Location version.
Monitor Menu
The Monitor menu provides you with a top level description of the devices on your network. You can monitor your network, maps, various devices, security, alarms, events, or reports.
Configure Menu
The Configure menu allows you to configure templates, controllers, and access points on your network.
Administration Menu
The Administration menu allows you to schedule tasks like making a backup, checking a device status, auditing your network, synchronizing the location server, and so on. You can also choose Logging to enable various logging modules and specify restart requirements. You can also choose AAA for user administration such as changing passwords, establishing groups, setting application security settings, and so on.
Location Menu
The Location menu allows you to configure location appliances. A location appliance is a Cisco server that collects and stores up to 30 days of historical location data for up to 2,500 laptop clients, palmtop clients, VoIP telephone clients, active RFID (Radio Frequency Identifier) asset tags, rogue access points, and rogue access point clients.
Note
The Location menu is displayed only in Cisco WCS location version.
For more information on location appliances, refer to the Cisco 2700 Series Location Appliance
Installation and Configuration Guide.
Note
Read/Write permissions are used by the location function of the location appliance. Write permissions allow a client application or location appliance operator to modify location data only (such as asset information), while Read permissions only allow a client to read location data.
Help Menu
Note
Full permissions are required for administration. All functions under the Locate menu in Cisco WCS are administrative functions. An administrator must always have full permissions.
The Help menu allows you to access online help and check the version of Cisco WCS.
To check the version of WCS, click About the Software. The product name, version number, copyright statement, and Apache Software Foundation statement is displayed.
OL-12623-01
Cisco Wireless Control System Configuration Guide
2-15
Chapter 2 Getting Started
Using the Cisco WCS User Interface
Sidebar Area
The sidebar area allows you to choose a new configuration panel under the currently selected menu area.
You may choose to display or configure any of the available data. The selector area options vary based on which menu you have chosen.
Some windows contain a group of menus in this area. Click the menu item to reveal a submenu and then click the item to chose it.
Alarm Dashboard
When Cisco WCS receives alarm messages from a controller, the Cisco WCS user interface displays an alarm indicator in the lower left corner in an alarm summary panel known as the alarm dashboard. The alarm dashboard only appears when the Macromedia flash is installed.
Alarms indicate the current fault or state of an element that needs attention. These are usually generated by one or more events. The alarm can be cleared, but the event remains. An example of an alarm is AP
down, which means that the current status of the access point is down.
Alarms are color coded as follows:
•
Clear = No alarm
•
•
Red = Critical alarm
Orange = Major alarm
•
Yellow = Minor alarm
You can click any of the various types of alarms (such as rogues, coverage, security, controllers, and access points) to display details.
Command Buttons
The Cisco WCS user interface uses a number of command buttons throughout its windows. The most common of these are as follows:
•
Apply to Controllers: Applies the selected information to the controllers
•
•
•
•
•
Delete: Deletes the selected information
Cancel: Cancels new information entered on the current window and return to the previous window
Save: Saves the current settings
Audit: Discovers the present status of this access point
Place AP: Fixes the position of the selected access point on the graphic map display and updates the display of its coordinates
Main Data Page
The main data page is determined by the required parameter information. Active areas on the data pages include the following:
•
•
Text fields into which data may be entered using the keyboard
Pull-downs from which one of several options may be chosen
2-16
Cisco Wireless Control System Configuration Guide
OL-12623-01
Chapter 2 Getting Started
Using the Cisco WCS User Interface
•
•
•
Check boxes in lists allow you to choose one or more items from the displayed list
Radio buttons allow you to turn a parameter on or off
Hyperlinks take you to other pages in the Cisco WCS user interface
Input fields are black text on a white background. When data is entered or selected, it is not sent to the controller, but it is saved in the field until the Go button is selected.
Administrative Tools
This area provides shortcuts to administration functions (such as logged in as, logout, refresh, and help) that are used on a regular basis when configuring a controller through the web user interface.
OL-12623-01
Cisco Wireless Control System Configuration Guide
2-17
Using the Cisco WCS User Interface
Chapter 2 Getting Started
2-18
Cisco Wireless Control System Configuration Guide
OL-12623-01
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 1 Cisco Wireless Control System Configuration Guide
- 3 Contents
- 17 Preface
- 18 Audience
- 18 Purpose
- 18 Organization
- 19 Conventions
- 19 Related Publications
- 19 Obtaining Documentation, Obtaining Support, and Security Guidelines
- 21 Overview
- 22 Overview of the Cisco Unified Wireless Network Solution
- 23 Overview of WCS
- 24 WCS Versions
- 24 WCS Base
- 25 WCS Base + Location
- 25 Relationship with Cisco Location Appliances
- 26 Comparison of WCS Base and WCS Location
- 27 WCS User Interface
- 27 Cisco WCS Navigator
- 29 Getting Started
- 30 Prerequisites
- 30 System Requirements
- 32 Installing WCS for Windows
- 32 Guidelines Before Installing WCS
- 37 Installing WCS for Linux
- 39 Starting WCS
- 39 Starting WCS on Windows
- 40 Starting WCS on Linux
- 40 Logging into the WCS User Interface
- 42 Using the Cisco WCS User Interface
- 42 Menu Bar
- 43 Monitor Menu
- 43 Configure Menu
- 43 Administration Menu
- 43 Location Menu
- 43 Help Menu
- 44 Sidebar Area
- 44 Alarm Dashboard
- 44 Command Buttons
- 44 Main Data Page
- 45 Administrative Tools
- 47 Configuring Security Solutions
- 48 Cisco Unified Wireless Network Solution Security
- 48 Layer 1 Solutions
- 48 Layer 2 Solutions
- 48 Layer 3 Solutions
- 49 Single Point of Configuration Policy Manager Solutions
- 49 Rogue Access Point Solutions
- 49 Rogue Access Point Challenges
- 49 Tagging and Containing Rogue Access Points
- 49 Integrated Security Solutions
- 50 Using WCS to Convert a Cisco Unified Wireless Network Solution from Layer 3 to Layer 2 Mode
- 51 Configuring a Firewall for WCS
- 51 Access Point Authorization
- 52 Management Frame Protection (MFP)
- 53 Guidelines for Using MFP
- 54 Configuring Intrusion Detection Systems (IDS)
- 54 Viewing IDS Sensors
- 54 Viewing Shunned Clients
- 55 Configuring IDS Signatures
- 55 Uploading IDS Signatures
- 56 Downloading IDS Signatures
- 57 Enabling or Disabling IDS Signatures
- 60 Viewing IDS Signature Events
- 60 Enabling Web Login
- 61 Downloading Customized Web Authentication
- 64 Connecting to the Guest WLAN
- 64 Deleting a Guest User
- 67 Performing System Tasks
- 68 Adding System Components to the WCS Database
- 68 Adding a Controller to the WCS Database
- 68 Adding a Location Appliance to the WCS Database
- 69 Additional Functionality with Location Appliance
- 70 Using WCS to Update System Software
- 70 Downloading Vendor Device Certificates
- 71 Downloading Vendor CA Certificates
- 72 Using WCS to Enable Long Preambles for SpectraLink NetLink Phones
- 73 Creating an RF Calibration Model
- 75 Adding and Using Maps
- 76 Creating Maps
- 76 Adding a Campus
- 77 Adding Buildings
- 77 Adding a Building to a Campus Map
- 78 Adding a Standalone Building
- 78 Adding Outdoor Areas
- 79 Searching Maps
- 80 Adding and Enhancing Floor Plans
- 80 Adding Floor Plans to a Campus Building
- 82 Adding Floor Plans to a Standalone Building
- 83 Using the Map Editor to Enhance Floor Plans
- 83 General Notes and Guidelines for Using the Map Editor
- 84 Using the Map Editor to Draw Polygon Areas
- 87 Using Planning Mode to Calculate Access Point Requirements
- 92 Adding Access Points
- 94 Access Point Placement
- 95 Guidelines for Placing Access Points
- 97 Creating a Network Design
- 97 Designing a Network
- 103 Changing Access Point Positions by Importing and Exporting a File
- 104 Using Chokepoints to Enhance Tag Location Reporting
- 104 Adding Chokepoints to the WCS Database and Map
- 110 Removing Chokepoints from the WCS Database and Map
- 111 Monitoring Maps
- 112 Monitoring Predicted Coverage
- 113 Access Point Layer
- 114 AP Mesh Info Layer
- 115 Clients Layer
- 116 802.11 Tags Layer
- 117 Rogue APs Layer
- 118 Rogue Clients Layer
- 119 Monitoring Channels on a Floor Map
- 119 Monitoring Transmit Power Levels on a Floor Map
- 120 Monitoring Coverage Holes on a Floor Map
- 121 Monitoring Clients on a Floor Map
- 122 Monitoring Outdoor Areas
- 123 Importing or Exporting WLSE Map Data
- 127 Creating and Applying Calibration Models
- 130 Modifying the Appearance of Floor Maps
- 130 Monitoring Calibration Models
- 131 Analyzing Element Location Accuracy Using Testpoints
- 132 Assigning Testpoints to a Selected Area
- 137 Monitoring Wireless Devices
- 138 Monitoring Rogue Access Points
- 138 Rogue AP Details
- 138 Rogue Access Point Location, Tagging, and Containment
- 139 Detecting and Locating Rogue Access Points
- 141 Acknowledging Rogue Access Points
- 141 WLAN Client Troubleshooting
- 152 Finding Clients
- 155 Receiving Radio Measurements
- 156 Finding Coverage Holes
- 156 Pinging a Network Device from a Controller
- 157 Viewing Controller Status and Configurations
- 158 Monitoring Mesh Networks Using Maps
- 158 Monitoring Mesh Link Statistics Using Maps
- 161 Monitoring Mesh Access Points Using Maps
- 163 Monitoring Mesh Access Point Neighbors Using Maps
- 164 Monitoring Mesh Health
- 166 Mesh Security Statistics for an Access Point
- 168 Viewing the Mesh Network Hierarchy
- 170 Using Filtering to Modify Map Display
- 172 Running a Link Test
- 174 Retrieving the Unique Device Identifier on Controllers and Access Points
- 179 Managing WCS User Accounts
- 180 Adding WCS User Accounts
- 182 Changing Passwords
- 182 Monitoring Active Sessions
- 184 Viewing or Editing User Information
- 184 Viewing or Editing Group Information
- 186 Viewing the Audit Trail
- 187 Deleting WCS User Accounts
- 187 Creating Guest User Accounts
- 187 Creating a Lobby Ambassador Account
- 188 Logging in to the WCS User Interface
- 189 Managing WCS Guest User Accounts
- 189 Adding Guest User Accounts
- 190 Viewing and Editing Guest Users
- 191 Deleting Guest User Templates
- 192 Scheduling WCS Guest User Accounts
- 193 Print or Email WCS Guest User Details
- 193 Logging the Lobby Ambassador Activities
- 195 Configuring Mobility Groups
- 196 Overview of Mobility
- 199 Symmetric Tunneling
- 199 Overview of Mobility Groups
- 201 When to Include Controllers in a Mobility Group
- 201 Configuring Mobility Groups
- 202 Prerequisites
- 204 Mobility Anchors
- 204 Configuring Mobility Anchors
- 206 Configuring Multiple Country Codes
- 209 Creating Config Groups
- 209 Adding New Group
- 210 Configuring Config Groups
- 211 Adding or Removing Controllers from Config Group
- 211 Adding or Removing Templates from the Config Group
- 212 Applying Config Groups
- 212 Auditing Config Groups
- 213 Rebooting Config Groups
- 213 Downloading Software
- 214 Downloading IDS Signatures
- 215 Downloading Customized WebAuth
- 219 Configuring Controllers and Access Points
- 220 Adding Controllers
- 221 Setting Multiple Country Codes
- 222 Searching Controllers
- 223 Managing User Authentication Order
- 223 Configuring Audit Reports
- 223 Enabling Load-Based CAC for Controllers
- 225 Enabling High Density
- 225 Requirements
- 225 Optimizing the Controller to Support High Density
- 228 Configuring 802.3 Bridging
- 228 Configuring Access Points
- 232 Searching Access Points
- 235 Using Templates
- 235 Adding Controller Templates
- 237 Configuring an NTP Server Template
- 237 Configuring General Templates
- 240 Configuring QoS Templates
- 241 Configuring a Traffic Stream Metrics QoS Template
- 243 Configuring WLAN Templates
- 245 Security
- 245 Layer 2
- 247 Layer 3
- 248 AAA Servers
- 250 QoS
- 251 Advanced
- 252 Configuring a File Encryption Template
- 254 Configuring a RADIUS Authentication Template
- 256 Configuring a RADIUS Accounting Template
- 257 Configuring a LDAP Server Template
- 258 Configuring a TACACS+ Server Template
- 259 Configuring a Network Access Control Template
- 260 Configuring a Local EAP General Template
- 261 Configuring a Local EAP Profile Template
- 262 Configuring an EAP-FAST Template
- 263 Configuring Network User Credential Retrieval Priority Templates
- 264 Configuring a Local Network Users Template
- 266 Configuring Guest User Templates
- 267 Configuring a User Login Policies Template
- 267 Configuring a MAC Filter Template
- 268 Configuring an Access Point Authorization
- 269 Configuring a Manually Disabled Client Template
- 270 Configuring a CPU Access Control List (ACL) Template
- 271 Configuring a Rogue Policies Template
- 272 Configuring a Trusted AP Policies Template
- 273 Configuring a Client Exclusion Policies Template
- 275 Configuring an Access Point Authentication and MFP Template
- 276 Configuring a Web Authentication Template
- 277 Downloading a Customized Web Authentication Page
- 280 Configuring Access Control List Templates
- 281 Configuring a Policy Name Template (for 802.11a or 802.11b/g)
- 284 Configuring High Density Templates
- 286 Configuring a Voice Parameter Template (for 802.11a or 802.11b/g)
- 287 Configuring a Video Parameter Template (for 802.11a or 802.11b/g)
- 288 Configuring a Roaming Parameters Template (for 802.11a or 802.11b/g)
- 289 Configuring an RRM Threshold Template (for 802.11a or 802.11b/g)
- 290 Configuring an RRM Interval Template (for 802.11a or 802.11b/g)
- 291 Configuring an 802.11h Template
- 292 Configuring a Mesh Template
- 294 Configuring a Known Rogue Access Point Template
- 295 Configuring a Trap Receiver Template
- 295 Configuring a Trap Control Template
- 297 Configuring a Telnet SSH Template
- 298 Configuring a Syslog Template
- 299 Configuring a Local Management User Template
- 300 Configuring a User Authentication Priority Template
- 301 Applying Controller Templates
- 301 Adding Access Point Templates
- 302 Configuring Access Point/Radio Templates
- 307 Maintaining WCS
- 308 Checking the Status of WCS
- 308 Checking the Status of WCS on Windows
- 308 Checking the Status of WCS on Linux
- 309 Stopping WCS
- 309 Stopping WCS on Windows
- 309 Stopping WCS on Linux
- 310 Backing Up the WCS Database
- 310 Scheduling Automatic Backups
- 311 Performing a Manual Backup
- 311 Backing Up the WCS Database (for Windows)
- 311 Backing Up the WCS Database (for Linux)
- 312 Restoring the WCS Database
- 312 Restoring the WCS Database (for Windows)
- 313 Restoring the WCS Database (for Linux)
- 313 Importing the Location Appliance into WCS
- 316 Importing and Exporting Asset Information
- 316 Importing Asset Information
- 316 Exporting Asset Information
- 317 Auto-Synchronizing Location Appliances
- 318 Backing Up Location Appliance Data
- 320 Uninstalling WCS
- 320 Uninstalling WCS on Windows
- 320 Uninstalling WCS on Linux
- 321 Upgrading WCS
- 321 Upgrading WCS on Windows
- 322 Upgrading WCS on Linux
- 322 Upgrading the Network
- 322 Recovering the WCS Password
- 325 Configuring Hybrid REAP
- 326 Overview of Hybrid REAP
- 326 Hybrid-REAP Authentication Process
- 328 Hybrid REAP Guidelines
- 328 Configuring Hybrid REAP
- 328 Configuring the Switch at the Remote Site
- 330 Configuring the Controller for Hybrid REAP
- 333 Configuring an Access Point for Hybrid REAP
- 336 Connecting Client Devices to the WLANs
- 337 Running Reports
- 337 Choosing a Report
- 338 Enabling or Disabling a Schedule
- 339 Deleting a Report
- 339 Accessing the Schedule Panel
- 340 Access Point Reports
- 340 Viewing or Modifying Access Point Reports
- 341 Creating a New Access Point Report
- 341 Client Reports
- 342 Viewing or Modifying Client Reports
- 342 Creating a New Client Report
- 343 Inventory Reports
- 343 Viewing or Modifying Inventory Reports
- 343 Creating a New Inventory Report
- 344 Mesh Reports
- 344 Viewing or Modifying Mesh Reports
- 345 Creating a New Mesh Report
- 345 Performance Reports
- 346 Viewing or Modifying Performance Reports
- 346 Creating a New Performance Report
- 347 Security Reports
- 347 Viewing or Modifying Security Reports
- 347 Creating a New Security Report
- 349 Alarms and Events
- 350 Alarm Dashboard
- 352 Setting Search Filters for Alarms
- 356 Alarm and Event Dictionary
- 356 Notification Format
- 357 Traps Added in Release 2.0
- 357 AP_BIG_NAV_DOS_ATTACK
- 357 AP_CONTAINED_AS_ROGUE
- 357 AP_DETECTED_DUPLICATE_IP
- 357 AP_HAS_NO_RADIOS
- 358 AP_MAX_ROGUE_COUNT_CLEAR
- 358 AP_MAX_ROGUE_COUNT_EXCEEDED
- 359 AUTHENTICATION_FAILURE (From MIB-II standard)
- 359 BSN_AUTHENTICATION_FAILURE
- 359 COLD_START (FROM MIB-II STANDARD)
- 359 CONFIG_SAVED
- 360 IPSEC_IKE_NEG_FAILURE
- 360 IPSEC_INVALID_COOKIE
- 360 LINK_DOWN (FROM MIB-II STANDARD)
- 360 LINK_UP (FROM MIB-II STANDARD)
- 361 LRAD_ASSOCIATED
- 361 LRAD_DISASSOCIATED
- 361 LRADIF_COVERAGE_PROFILE_FAILED
- 362 LRADIF_COVERAGE_PROFILE_PASSED
- 362 LRADIF_CURRENT_CHANNEL_CHANGED
- 362 LRADIF_CURRENT_TXPOWER_CHANGED
- 363 LRADIF_DOWN
- 363 LRADF_INTERFERENCE_PROFILE_FAILED
- 363 LRADIF_INTERFERENCE_PROFILE_PASSED
- 364 LRADIF_LOAD_PROFILE_FAILED
- 364 LRADIF_LOAD_PROFILE_PASSED
- 364 LRADIF_NOISE_PROFILE_FAILED
- 365 LRADIF_NOISE_PROFILE_PASSED
- 365 LRADIF_UP
- 365 MAX_ROGUE_COUNT_CLEAR
- 366 MAX_ROGUE_COUNT_EXCEEDED
- 366 MULTIPLE_USERS
- 366 NETWORK_DISABLED
- 366 NO_ACTIVITY_FOR_ROGUE_AP
- 367 POE_CONTROLLER_FAILURE
- 367 RADIOS_EXCEEDED
- 367 RADIUS_SERVERS_FAILED
- 368 ROGUE_AP_DETECTED
- 368 ROGUE_AP_NOT_ON_NETWORK
- 369 ROGUE_AP_ON_NETWORK
- 369 ROGUE_AP_REMOVED
- 369 RRM_DOT11_A_GROUPING_DONE
- 370 RRM_DOT11_B_GROUPING_DONE
- 370 SENSED_TEMPERATURE_HIGH
- 370 SENSED_TEMPERATURE_LOW
- 371 STATION_ASSOCIATE
- 371 STATION_ASSOCIATE_FAIL
- 371 STATION_AUTHENTICATE
- 371 STATION_AUTHENTICATION_FAIL
- 372 STATION_BLACKLISTED
- 372 STATION_DEAUTHENTICATE
- 372 STATION_DISASSOCIATE
- 373 STATION_WEP_KEY_DECRYPT_ERROR
- 373 STATION_WPA_MIC_ERROR_COUNTER_ACTIVATED
- 373 SWITCH_DETECTED_DUPLICATE_IP
- 374 SWITCH_DOWN
- 374 SWITCH_UP
- 374 TEMPERATURE_SENSOR_CLEAR
- 375 TEMPERATURE_SENSOR_FAILURE
- 375 TOO_MANY_USER_UNSUCCESSFUL_LOGINS
- 376 Traps Added in Release 2.1
- 376 ADHOC_ROGUE_AUTO_CONTAINED
- 376 ADHOC_ROGUE_AUTO_CONTAINED_CLEAR
- 376 NETWORK_ENABLED
- 377 ROGUE_AP_AUTO_CONTAINED
- 377 ROGUE_AP_AUTO_CONTAINED_CLEAR
- 377 TRUSTED_AP_INVALID_ENCRYPTION
- 378 TRUSTED_AP_INVALID_ENCRYPTION_CLEAR
- 378 TRUSTED_AP_INVALID_RADIO_POLICY
- 378 TRUSTED_AP_INVALID_RADIO_POLICY_CLEAR
- 378 TRUSTED_AP_INVALID_SSID
- 379 TRUSTED_AP_INVALID_SSID_CLEAR
- 379 TRUSTED_AP_MISSING
- 379 TRUSTED_AP_MISSING_CLEAR
- 379 Traps Added in Release 2.2
- 379 AP_IMPERSONATION_DETECTED
- 380 AP_RADIO_CARD_RX_FAILURE
- 380 AP_RADIO_CARD_RX_FAILURE_CLEAR
- 380 AP_RADIO_CARD_TX_FAILURE
- 380 AP_RADIO_CARD_TX_FAILURE_CLEAR
- 381 SIGNATURE_ATTACK_CLEARED
- 381 SIGNATURE_ATTACK_DETECTED
- 381 TRUSTED_AP_HAS_INVALID_PREAMBLE
- 382 TRUSTED_HAS_INVALID_PREAMBLE_CLEARED
- 382 Traps Added in Release 3.0
- 382 AP_FUNCTIONALITY_DISABLED
- 382 AP_IP_ADDRESS_FALLBACK
- 383 AP_REGULATORY_DOMAIN_MISMATCH
- 383 RX_MULTICAST_QUEUE_FULL
- 384 Traps Added in Release 3.1
- 384 AP_AUTHORIZATION_FAILURE
- 384 HEARTBEAT_LOSS_TRAP
- 385 INVALID_RADIO_INTERFACE
- 385 RADAR_CLEARED
- 385 RADAR_DETECTED
- 386 RADIO_CORE_DUMP
- 386 RADIO_INTERFACE_DOWN
- 386 RADIO_INTERFACE_UP
- 387 UNSUPPORTED_AP
- 387 Traps Added in Release 3.2
- 387 LOCATION_NOTIFY_TRAP
- 388 Traps Added In Release 4.0
- 388 CISCO_LWAPP_MESH_POOR_SNR
- 388 CISCO_LWAPP_MESH_PARENT_CHANGE
- 388 CISCO_LWAPP_MESH_CHILD_MOVED
- 389 CISCO_LWAPP_MESH_CONSOLE_LOGIN
- 389 CISCO_LWAPP_MESH_AUTHORIZATION_FAILURE
- 389 CISCO_LWAPP_MESH_CHILD_EXCLUDED_PARENT
- 390 CISCO_LWAPP_MESH_EXCESSIVE_PARENT_CHANGE
- 390 IDS_SHUN_CLIENT_TRAP
- 390 IDS_SHUN_CLIENT_CLEAR_TRAP
- 391 MFP_TIMEBASE_STATUS_TRAP
- 391 MFP_ANOMALY_DETECTED_TRAP
- 391 GUEST_USER_REMOVED_TRAP
- 392 Traps Added/Updated in Release 4.0.96.0
- 392 AP_IMPERSONATION_DETECTED
- 392 RADIUS_SERVER_DEACTIVATED
- 392 RADIUS_SERVER_ACTIVATED
- 393 RADIUS_SERVER_WLAN_DEACTIVATED
- 393 RADIUS_SERVER_WLAN_ACTIVATED
- 393 RADIUS_SERVER_TIMEOUT
- 393 DECRYPT_ERROR_FOR_WRONG_WPA_WPA2
- 394 Traps Added or Updated in Release 4.1
- 394 AP_IMPERSONATION_DETECTED
- 394 INTERFERENCE_DETECTED
- 394 INTERFERENCE_CLEAR
- 395 ONE_ANCHOR_ON_WLAN_UP
- 395 RADIUS_SERVER_DEACTIVATED
- 395 RADIUS_SERVER_ACTIVATED
- 395 RADIUS_SERVER_WLAN_DEACTIVATED
- 396 RADIUS_SERVER_WLAN_ACTIVATED
- 396 RADIUS_SERVER_TIMEOUT
- 396 MOBILITY_ANCHOR_CTRL_PATH_DOWN
- 396 MOBILITY_ANCHOR_CTRL_PATH_UP
- 397 MOBILITY_ANCHOR_DATA_PATH_DOWN
- 397 MOBILITY_ANCHOR_DATA_PATH_UP
- 397 WLAN_ALL_ANCHORS_TRAP_DOWN
- 397 MESH_AUTHORIZATIONFAILURE
- 398 MESH_CHILDEXCLUDEDPARENT
- 398 MESH_PARENTCHANGE
- 398 MESH_CHILDMOVED
- 399 MESH_EXCESSIVEPARENTCHANGE
- 399 MESH_POORSNR
- 399 MESH_POORSNRCLEAR
- 400 MESH_CONSOLELOGIN
- 400 LRADIF_REGULATORY_DOMAIN
- 400 LRAD_CRASH
- 401 LRAD_UNSUPPORTED
- 401 Unsupported Traps
- 402 Configuring Alarm Severity
- 403 Viewing MFP Events and Alarms
- 403 Alarm Emails
- 404 Viewing IDS Signature Attacks
- 405 Wireless LAN IDS Event Correlation
- 407 Administrative Tasks
- 408 Running Background Tasks
- 408 Performing a Task
- 410 Importing Tasks Into ACS
- 410 Adding WCS to an ACS Server
- 411 Adding WCS as a TACACS+ Server
- 412 Adding WCS UserGroups into ACS for TACACS+
- 414 Adding WCS to ACS server for use with RADIUS
- 415 Adding WCS UserGroups into ACS for RADIUS
- 417 Adding WCS to a non-Cisco ACS server for use with RADIUS
- 418 Setting AAA Mode
- 419 Turning Password Rules On or Off
- 420 Configuring TACACS+ Servers
- 421 Configuring RADIUS Servers
- 423 Establishing Logging Options
- 423 Performing Data Management Tasks
- 424 Data Management
- 424 Report
- 425 Mail Server
- 427 Setting User Preferences
- 430 WCS and End User Licenses
- 431 WCS Licenses
- 431 Types of Licenses
- 432 Licensing Enforcement
- 432 Product Authorization Key Certificate
- 433 Determining Which License To Use
- 433 Installing a License
- 434 Managing Licenses
- 434 Adding a License
- 435 Deleting a License
- 435 Backup and Restore License
- 435 End User License Agreement
- 443 Conversion of a WLSE Autonomous Deployment to a WCS Controller Deployment
- 444 Supported Hardware
- 444 Supported Cisco WLSE Management Stations
- 444 Autonomous Access Points Convertible to LWAPP
- 444 Installation and Configuration
- 444 Installing Cisco WCS
- 445 Upgrading to Red Hat Enterprise Linux 4
- 445 Configuring the Converted Appliance
- 448 Licensing
- 448 WLSE Upgrade License
- 449 Index