Cisco Wireless Control System Configuration Guide, Release 7.0.172.0
Chapter 16: Performing Administrative Tasks
Downloads: This chapterpdf (PDF - 3.16MB) The complete bookPDF (PDF - 43.47MB) | Feedback

Performing Administrative Tasks

Table Of Contents

Performing Administrative Tasks

Information About Administrative Tasks

Background Tasks

Data Management Tasks (Settings)

Other Background Tasks

Authentication, Authorization, and Accounting (AAA)

Auto Provisioning

Auto Provisioning Device Management (Auto Provisioning Filter List)

High Availability

User Preferences

License Center

WCS License Information

WLC Controller License Information

WLC Controller License Summary

Mobility Services Engine (MSE) License Information

Mobility Services Engine (MSE) License Summary

Performing Background Tasks

Performing a Data Collection Task

Data Collection Tasks

Performing Other Background Tasks

Performing a Configuration Sync

Viewing Controller Configuration Backup Status

Viewing Client Status

Updating Controller License Status

Viewing Data Cleanup Status

Performing Device Data Collection

Viewing Device Status

Performing Guest Accounts Sync

Performing Mobility Service Backup

Viewing Mobility Service Status

Performing Mobility Service Synchronization

Viewing OSS Server Status

Viewing Wireless Status

Performing WCS Server Backup

Other Background Tasks

Importing Tasks Into ACS

Adding WCS to an ACS Server

Adding WCS as a TACACS+ Server

Adding WCS UserGroups into ACS for TACACS+

Adding WCS to an ACS Server for Use with RADIUS

Adding WCS UserGroups into ACS for RADIUS

Adding WCS to a Non-Cisco ACS Server for Use with RADIUS

Configuring Auto Provisioning

Adding an Auto Provisioning Filter

Editing an Auto Provisioning Filter

Deleting Auto Provisioning Filter(s)

Listing Auto Provisioning Filter(s) Device Info

Listing All Auto Provisioning Filter(s) Device Info

Exporting Auto Provisioning Filter(s)

Exporting All Auto Provisioning Filter(s)

Auto Provisioning Primary Search Key Settings

Establishing Logging Options

General Logging Options

SNMP Logging Options

Syslog Options

Using Logging Options to Enhance Troubleshooting

Configuring Administrative Settings

Configuring Alarms

Configuring an Audit

Audit Mode

Audit On

Configuring Clients

Configuring Protocols for CLI Sessions

Configuring Controller Upgrade

Configuring Data Management

WCS Historical Data

Configuring a Guest Account

Configuring Login Disclaimer

Configuring the Mail Server

Configuring the Notification Receiver

Adding a Notification Receiver to WCS

Removing a Notification Receiver

MIB to WCS alert/event mapping

Setting Report

Configuring Server Settings

Severity Configurations

SNMP Credentials

Viewing Current SNMP Credential Details

Adding a New SNMP Credential Entry

SNMP Settings

Switch Port Tracing

Establishing Switch Port Tracing

Switch Port Tracing Details

Switch Port Tracing Troubleshooting

Configuring High Availability

Guidelines and Limitations for High Availability

Failover Scenario

High Availability Status

Configuring High Availability on Primary WCS

Deploying High Availability

Adding a New Primary WCS

Removing a Primary WCS

Setting User Preferences

Managing Individual Licenses

Managing Controller Licenses

Managing WCS Licenses

Managing MSE Licenses

Configuring ACS 5.x

Creating Network Devices and AAA Clients

Adding Groups

Adding Users

Creating Policy Elements or Authorization Profiles

Creating Policy Elements or Authorization Profiles for RADIUS

Creating Policy Elements or Authorization Profiles For TACACS

Creating Authorization Rules

Creating Service Selection Rules for RADIUS

Creating Service Selection Rules for TACACS

Configuring Access Services

Configuring Access Services for RADIUS

Configuring Access Services for TACACS

Managing Licenses

Managing WCS Licenses

Adding a New WCS License File

Deleting a WCS License File

Monitoring Controller Licenses

Managing Mobility Services Engine (MSE) Licenses

Registering Product Authorization Keys

Installing Client and wIPS License Files

Deleting a Mobility Services Engine License File

Configuring AAA

Change Password

AAA Mode

Local Password Policy

Users

Adding a New User

Groups

Viewing or Editing Group Information

Active Sessions

TACACS+

RADIUS


Performing Administrative Tasks


The Administration enables you to schedule tasks, administer accounts, and configure local and external authentication and authorization. Also, set logging options, configure mail servers, and data management related to configuring the data retain periods. Information is available about the types of WCS licenses and how to install a license.

This chapter describes the administrative tasks to perform with Cisco WCS. It contains the following sections:

Information About Administrative Tasks

Performing Background Tasks

Importing Tasks Into ACS

Configuring Auto Provisioning

Configuring Administrative Settings

Establishing Logging Options

Configuring High Availability

Setting User Preferences

Managing Individual Licenses

Configuring ACS 5.x

Managing Licenses

Configuring AAA

Information About Administrative Tasks

Organizations need an easy and cost-effective method to manage and control wireless network segments using a single management platform. They need a solution that supports limiting an individual administrator to manage or control the wireless LAN.

This section contains the following topics:

Background Tasks

Data Management Tasks (Settings)

Other Background Tasks

Authentication, Authorization, and Accounting (AAA)

Auto Provisioning

High Availability

User Preferences

License Center

Background Tasks

A background task is a scheduled program running in the background with no visible pages or other user interfaces. In WCS background tasks can be anything from data collection to taking backups of the configurations.


Note Choose Administration > Background Tasks to view several scheduled tasks. The Background Tasks page appears (see Figure 16-1).


Figure 16-1 Background Tasks Page

You can view the administrative and operating status, task interval, and time of day in which the task occurs. To execute a particular task, select the check box of the desired task and choose Execute Now from the Select a command drop-down list. The task executes based on what you have configured for the specific task.

The tasks are listed in tables with the following columns:

Check box—Select to choose the desired task. Chosen tasks are targets for operations initiated from the Select a command drop-down list including:

Execute Now—Run all of the data sets with a selected check box.

Enable Collection—Enable the data set to run on its scheduled interval.

Disable Collection—Prevent the data set from running on its scheduled interval.

Task—Task name that serves as a link to a configuration page. Click a task name to go to that task configuration page.

Enabled—Indicates that the task is enabled or disabled.

Interval—Time period between executions of task.

Status—Indicates that the task is idle, disabled, or executing.

Data Aggregation (Data Collections only)—If set to Yes, the data set will aggregate data.

Non-Aggregation Data Retain Period (Days) (Data Collections only)—The number of days that non-aggregated data will be retained.


Note See the "WCS Historical Data" section for more information on aggregated and non-aggregated data in WCS.


Last Execution Time—The date and time the task was executed.

Last Execution Status—Indicates if the task executed suffessfully or failed.

This page enables you to view the status of scheduled WCS tasks. Scheduled tasks are divided into two types: "Data Management Tasks (Settings)" section and the "Other Background Tasks" section.

Data Management Tasks (Settings)

Within the Settings page, you can indicate the data that you want to generate for reports and e-mails.

See the "Configuring Alarms" section to specify how to handle old alarms and how to display assigned and acknowledged alarms in the Alarm Summary page.

See "Configuring an Audit" section to configure audit information.

See the "Configuring Clients" section to enable client troubleshooting on a diagnostic channel.

See the "Configuring Protocols for CLI Sessions" section to establish a telnet or SSH session.

See the "Configuring Controller Upgrade" section for information on controller upgrade settings.

See the "Configuring Data Management" section to establish trends for hourly, daily, and weekly data periods.

See the "Configuring a Guest Account" section to designate where the scheduled reports will reside and for how long.

See the "Configuring Login Disclaimer" section to enter disclaimer information.

See the "Configuring the Mail Server" section to set the primary and secondary SMTP server host and port.

See the "Configuring the Notification Receiver" section to configure parameters for notification support of guest access functionality.

See the "Configuring Server Settings" section to turn FTP, TFTP, HTTP, or HTTPS on or off.

See the "Severity Configurations" section to configure the severity level for newly generated alarms.

See the "SNMP Credentials" section to specify which credentials to use for tracing the rogue access points.

See the "SNMP Settings" section to configure global SNMP settings from WCS.

See the "Switch Port Tracing" section to identify the switch port to which a rogue access point is connected.

Other Background Tasks

See the "Configuring AAA" section to view the history and current status of client status polling backups.

See the "Viewing Controller Configuration Backup Status" section to view all configuration data from the controllers.

See the "Viewing Controller Configuration Backup Status" section to view the history and current status of Cisco WLAN Solution configuration backups.

See the "Viewing Client Status" section view the history and current status of Controller License Status polling backups.

See the "Viewing Data Cleanup Status" section view the history and current status of Cisco WLAN Solution database cleanups.

See the "Viewing Device Status" section view the history and current status of Cisco WLAN Solution device status tasks.

See the "Performing Guest Accounts Sync" section view the history and current status of Guest Account Synchronization tasks.

See the "Performing Mobility Service Backup" section to schedule a backup of the mobility services engine database.

See the "Viewing Mobility Service Status" section to view the status of mobility service engine.

See the "Performing Mobility Service Synchronization" section to synchronize mobiloity services engine(s).

See the "Performing WCS Server Backup" section to schedule a backup of the WCS Server.

See the "Viewing Wireless Status" section view the history and current status of wireless status polls.

Authentication, Authorization, and Accounting (AAA)

From Administration > AAA, authentication, authorization, and accounting (AAA) can be configured for WCS. The only username that has permissions to configure WCS AAA is root or SuperUser. Any changes to local users accounts will be in effect when configured for local mode. If using external authentication, for example RADIUS or TACACS+, the user changes must be done on the remote server. This section contains the following topics:

Change Password

Local Password Policy

AAA Mode

Users

Groups

Active Sessions

TACACS+

RADIUS

Auto Provisioning

Auto provisioning allows WCS to automatically configure a new or replace a current wireless LAN controller (WLC). The WCS auto provisioning feature can simplify deployments for customers with a large number of controllers.


Note For Auto Provisioning privileges, you must have Admin, Root, or SuperUser status.



Note To allow or disallow a user Auto Provisioning privileges, edit the permitted tasks using the Administration > AAA > Groups > group name > List of Tasks Permitted section of WCS. Select or unselect the check box to allow or disallow these privileges.



Note As part of the initial configuration of a device, WCS sets the SNMP switch location attribute to a default value. When the device reboots, WCS verifies this attribute. If it has a default value, the device configuration is not erased and auto provisioning is not required for this device. If the SNMP switch location attribute is blank, the device configuration is considered to be erased or the device may be replaced. Auto provisioning is required for this device.



Note As part of the initial configuration of a device, WCS sets the SNMP switch location attribute to a default value. When the device reboots, WCS verifies this attribute. If it has a default value, the device configuration is not erased and auto provisioning is not required for this device. If the SNMP switch location attribute is blank, the device configuration is considered to be erased or the device may be replaced. Auto provisioning is required for this device.



Note A controller radio and b/g networks are initially disabled by the WCS downloaded startup configuration file. If desired, you may turn on those radio networks by using a template, which should be included as one of the automated templates.



Note To specify the Auto Provision filter contents, you can directlyenter the details in the application or import the details from a CSV file. The auto provisioning feature supports the 5500 and non-5500 series of controllers. The non-5500 series controllers have AP manager interface configuration information defined, whereas 5500 series controllers do not have this information.


To access the Auto Provisioning feature, choose Configure > Controller Auto Provisioning.

Auto Provisioning Device Management (Auto Provisioning Filter List)—Allows you to create and edit auto provisioning filters which define the list of allowable devices to be auto provisioned or auto monitored by WCS.

Auto Provisioning Primary Search Key Settings—Provides the ability to set the matching criteria search order.

Auto Provisioning Device Management (Auto Provisioning Filter List)

This feature allows you to create and edit auto provisioning filters which define the list of allowable devices to be auto provisioned or auto monitored by WCS.

Filter parameters include the following:

Filter Name—Identifies the name of the filter.

Filter Enable—Indicates whether or not the filter is enabled.


Note Only enabled filters can participate in the Auto Provisioning process.


Monitor Only—If selected, the WLC defined in this filter is managed by WCS but not configured by WCS if the WLC contacts WCS during the auto provisioning process.

Filter Mode—Indicates the search mode for this filter (Host Name, MAC Address, or Serial Number).

Config Group Name—Indicates the Configuration Group name.


Note All Config-Groups used by auto provision filters should not have any controller defined in them.


Auto Provisioning Options

The Select a command drop-down list has the following options:

Add Filter—Allows you to add an Auto Provisioning filter. See the"Adding an Auto Provisioning Filter" section for more information.

Delete Filter(s)—Allows you to delete the selected Auto Provisioning filter. See "Deleting Auto Provisioning Filter(s)" section for more information.

List Filter(s) Device Info—Allows you to view details for the selected Auto Provisioning filter. See "Listing Auto Provisioning Filter(s) Device Info" section for more information.

List All Filter(s) Device Info—Allows you to view details for all of the Auto Provisioning filter. See "Listing All Auto Provisioning Filter(s) Device Info" section for more information.

High Availability

To ensure continued operation in case of failure, WCS now provides a high availability (or failover framework). When an active (primary) WCS fails, a secondary WCS takes over operations (in less than two minutes) for the failed primary WCS and continues to provide service. Upon failover, a peer of the failed primary WCS is activated on the secondary WCS using the local database and files, and the secondary WCS runs a fully functional WCS. While the secondary host is in failover mode, the database and file backups of other primary WCSs continue uninterrupted.

To activate and use high availability, you must buy a high availability license. The license is deployed on each primary WCS that is supported by a secondary WCS. After the license is validated, you must configure parameters on the WCS administration interface (see the "Configuring High Availability" section).

For more High Availability information, refer to one of the following sections:

Guidelines and Limitations for High Availability

Failover Scenario

Performing Background Tasks

High Availability Status

Configuring High Availability on Primary WCS

Deploying High Availability

User Preferences

Choose Administration > User Preferences to open the User Preferences page. The User Preferences page enables you to control certain display options in WCS.

List Pages

Items Per List—You can set the number of items, such as controllers or access points, to display in pages that list these items. Choose the number of items to display from the Items Per List Page drop-down list.

Home Page

Refresh Home Page—Select the check box if you want to configure a time for the home page to automatically refresh.

Refresh Home Page Every—Choose the frequency of the home page refresh from the drop-down list (every 30 seconds, 1 minute, 2 minutes, or 5 minutes).

User Idle Timeout

Logout idle user—Select the check box if you want to configure the amount of time, in minutes, that a user session can be idle before the server cancels the session.

Logout idle user after—Choose the maximum number of minutes that a server waits for an idle user. The default value is 60 minutes. The minimum value is 15 minutes. The maximum value is 120 minutes.


Note If the Logout idle user check box is unselected, the user session will not be timed out.


Alarms

Refresh Map/Alarms page on new alarm—Select the check box to refresh map and alarm pages each time a new alarm is generated.

Refresh Alarm count in the Alarm Summary every—Choose the frequency of the Alarm Summary refresh from the drop-down list (every 5, seconds, 15 seconds, 30 seconds, 1 minute, 2 minutes, or 5 minutes).

Display Alarm Category in Alarm Summary page—Choose the alarm category that you want to display in the minimized Alarm Summary (Alarm Summary, Malicious AP, Unclassified AP, Coverage Holes, Security, Controllers, Access Points, Mobility Services, Mesh Links, WCS, or Performance).

Disable Alarm Acknowledge Warning Message—When you acknowledge an alarm, a warning displays as a reminder that a recurrence of the problem does not generate another alarm unless this functionality is disabled. Select this check box to stop the warning message from displaying.

Select alarms for Alarm Summary Toolbar—To select alarms for the Alarm Summary Toolbar, click Edit Alarm Categories and select the required alarm categories and sub-categories.

License Center

The License Center allows you to manage WCS, wireless LAN controllers, and MSE licenses. The License Center is available from the WCS Administration menu. To view the License Center page, choose Administration > License Center (see Figure 16-2).


Note Although WCS and MSE licenses can be fully managed from the License Center, WLC licenses can only be viewed. You must use WLC or CLM to manage WLC licenses.



Tip To learn more about WCS License Center, go to Cisco.com to watch a multimedia presentation. Here you can also find the learning modules for a variety of WCS topics. Over future releases, we will add more overview and technical presentations to enhance your learning.


Figure 16-2 License Center

WCS License Information

The WCS Licenses portion of the License Center page displays the following:

Feature—The type of license, either Base or PLUS. A Base license supports standard WCS capabilities, which includes wireless client data access, rogue access point containment functions, Cisco WLAN Solution monitoring and control, and client and rogue access point location to the nearest access point. Cisco WCS PLUS license supports Cisco WCS Base license features and the following capabilities: mobility services enablement and high availability.


Note To upgrade to a PLUS license, you must purchase upgrade licenses with the total count meeting or exceeding your Base license.



Note A Cisco WCS Plus license is backward compatible to existing Cisco WCS Location licenses. The process to provision a Cisco WCS Plus license is the same as provisioning a current Cisco WCS license.


Host—The WCS host name.


Note The host name provides a link to the WCS License Files section.


AP Limit—The total number of licensed access points.

AP Count—The current number of access points using licenses.


Note AP count includes both associated and unassociated access points. When you are near the AP limit, you can delete any unassociated access points to increase available license capacity. For a demo license, you can click the "If you do not have a Product Authorization Key (PAK), please click here for available licenses" link and choose Wireless Control System Trial License.


% Used—The percentage of access points licensed across WCS. If the percentage drops to 75%, the value appears in red. At this level, a message also appears indicating that both associated and unassociated access points are part of the AP count.

Type—Permanent if all licenses are permanent. If any licenses are evaluations (or demos), it shows the number of days remaining on the license that has the fewest number of days until expiration.


Note To add a new license for WCS, go to the Product License Registration link

(https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet)

and provide your Product Authorization Key (PAK) and host name.



Note If you choose Summary > WCS from the left sidebar menu, only the WCS license information is displayed.


See the Cisco Wireless Control System Licensing and Ordering Guide at this URL:
http://www.cisco.com/en/US/prod/collateral/wireless/ps5755/ps6301/ps6305/product_data_sheet0900aecd804b4646.html#wp9000156.

It covers selecting the correct SKU, ordering the SKU, installing the software, registering the PAK certificate, and installing the license file on the server.

See the "WCS Licenses" section for more information on licensing enforcement, PAK certificates, license types, and installing and managing WCS licenses.

WLC Controller License Information

The Controller Licensing portion of the License Center page provides the following information for both WPLUS and Base licenses:

Controller Count—The current number of licensed controllers.


Note Only 5500 series controllers are included in the count. WCS provides only an inventory view and issues warnings if a license is expiring.



Note Choosing the number in this column is the same as choosing Summary > Controller from the left sidebar menu, except that it is sorted by the feature you click. This page provides a summary of active controllers.


AP Limit—The total number of licensed access points.

Type—The four different types of licenses are as follows:


Note For any controllers with a type other than Permanent, the least number of days left to expiration is shown.


Permanent—Licenses are node-locked and have no usage period associated with them. They are issued by Cisco's licensing portal and must be installed using management interfaces on the device. Upon installation of these licenses, you have the necessary permissions across different versions.

Evaluation—Licenses are non-node-locked and are valid only for a limited period. They are used only when no permanent, extension, or grace period licenses exist. Before using an evaluation license, you must accept an End User License Agreement (EULA). Even though they are non-node-locked, their usage is recorded on the device. The number of days remaining on the evaluation license that has the fewest number of days until expiration is shown.

Extension—Licenses are node-locked and metered. They are issued by Cisco's licensing portal and must be installed using management interfaces on the device. Before using an extension license, you must accept a EULA during installation.

Grace Period—Licenses are node-locked and metered. These licenses are issued by Cisco's licensing portal as part of the permission ticket to rehost a license. They are installed on the device as part of the rehost operation, and you must accept a EULA as part of the rehost operation.

If you need to revoke a license from one controller and install it on another, it is called rehosting. You might want to rehost a license to change the purpose of a controller. See the Chapter 4 "Performing Maintenance Operations," of the Cisco Wireless LAN Controller Configuration Guide for information on rehosting a license.


Note The licensing status is updated periodically. To initiate an immediate update, choose Administration > Background Tasks and run the Controller License Status task.


If your network contains various Cisco licensed devices, you might want to consider using the Cisco License Manager (CLM) to manage all of the licenses using a single application. CLM is a secure client/server application that manages Cisco software licenses network wide. You can download the CLM software and access user documentation at this URL: http://www.cisco.com/go/clm. You can either register a PAK certificate with CLM or with the licensing portal found at https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet.

WLC Controller License Summary

If you want to see more details about controller licensing, choose the Summary > Controller option from the left sidebar menu. The License Center page appears (see Figure 16-3). All currently active licenses on the controller are summarized.

Figure 16-3 License Center (Edit View) Page

All licensed controllers and their information in the bulleted list below are displayed. If you want to change how the controller results are displayed, click Edit View. In the Edit View page, highlight License Status, and click Hide to remove the column from the display.

Above the Controller Summary list is a series of filters that allow you to filter the list by Controller Name, Feature, Type, or Greater Than Percent Used. For example, if you enter 50, the list shows any WLCs that have more than 50% of its licenses used.


Note You can also use the Advanced Search link to sort the list of controllers.


Controller Name—Provides a link to the Files > Controller Files page.

Controller IP—The IP address of the controller.

Model—The controller model type.

Feature—The type of license, either Base or WPLUS. The Base license supports the standard software set, and the WPLUS license supports the premium Wireless Plus (WPLUS) software set. The WPLUS software set provides the standard feature set as well as added functionality for OfficeExtend access points, CAPWAP data encryptions, and enterprise wireless mesh.

AP Limit—The maximum capacity of access points allowed to join this controller.

AP Count—The current number of access points using licenses.

% Used—The percentage of licensed access points that are being used. If the percentage is greater than 75%, the bar appears red to indicate that the limit is being approached.

Type—The three different types of licenses are as follows:


Note For any controllers with a type other than Permanent, the least number of days left to expiration is shown.


Permanent—Licenses are node-locked and have no usage period associated with them. They are issued by Cisco's licensing portal and must be installed using management interfaces on the device. Upon installation of these licenses, you have the necessary permissions across different versions.

Evaluation—Licenses are non-node-locked and are valid only for a limited time period. They are used only when no permanent, extension, or grace period licenses exist. Before using an evaluation license, you must accept an End User License Agreement (EULA). Even though they are non-node-locked, their usage is recorded on the device. The number of days remaining on the evaluation license which has the fewest number of days until expiration is shown.

Extension—Licenses are node-locked and metered. They are issued by Cisco's licensing portal and must be installed using management interfaces on the device. Before using an extension license, you must accept a EULA during installation.


Note If a license shows as expired, the controller does not stop functioning. Only upon a reboot will the controller with the expired license become inactive.


Status—In Use, Not in Use, Inactive, or EULA Not Accepted.

Inactive—The license level is being used, but this license is not being used.

Not In Use—The license level is not being used and this license is not currently recognized.

Expired In Use—The license is being used, but is expired and will not be used upon next reboot.

Expired Not In Use—The license has expired and can no longer be used.

Count Consumed—The ap-count license is In Use.

Mobility Services Engine (MSE) License Information

There are three types of licenses:

Permanent—Licenses are node-locked and have no usage period associated with them. They are issued by licensing portal of Cisco and must be installed using management interfaces on the device. Upon installation of these licenses, you have the necessary permissions across different versions.

Evaluation—Licenses are non-node-locked and are valid only for a limited time period. They are used only when no permanent, extension, or grace period licenses exist. Before using an evaluation license, you must accept an End User License Agreement (EULA). Even though they are non-node-locked, their usage is recorded on the device. The number of days remaining on the evaluation license which has the fewest number of days until expiration is shown.

Extension—Licenses are node-locked and metered. They are issued by licensing portal of Cisco and must be installed using management interfaces on the device. Before using an extension license, you must accept a EULA during installation.

The MSE Licenses portion of the License Center page provides information for each service. (See Table 16-1).

Table 16-1 MSE License Information 

Field
Description
CAS Elements

Permanent Limit

The total number of CAS elements with permanent licenses.

Evaluation Limit

The total number of CAS elements with evaluation licenses.

Count

The number of CAS elements currently licensed across MSEs.

% Used

The percentage of CAS elements licensed across MSEs.

wIPS Monitor Mode APs

Permanent Limit

The total number of wIPS Monitor Mode APs with permanent licenses.

Evaluation Limit

The total number of wIPS Monitor Mode APs with evaluation licenses.

Count

The number of wIPS Monitor Mode APs currently licensed across MSEs.

% Used

The percentage of wIPS Monitor Mode APs licensed across MSEs.

Under wIPS Monitor Mode Aps or wIPS Local Mode Aps, an active link takes you to a list of licensed access points. You cannot access a list of licensed clients and tags.

wIPS Local Mode APs

Permanent Limit

The total number of wIPS Local Mode APs with permanent licenses.

Evaluation Limit

The total number of wIPS Local Mode APs with evaluation licenses.

Count

The number of wIPS Local Mode APs currently licensed across MSEs.

% Used

The percentage of wIPS Local Mode APs licensed across MSEs.

Under wIPS Monitor Mode APs or wIPS Local Mode APs, an active link takes you to a list of licensed access points. You cannot access a list of licensed clients and tags.



Note When a license is deleted, the mobility services engine automatically restarts to load the new license limits.


For more information on MSE licenses, see the "Overview of MSE License" section on page 12-80.

Mobility Services Engine (MSE) License Summary

If you want to see more details about MSE licensing, choose Summary > MSE from the left sidebar menu. The License Center page appears (see Figure 16-4).

Figure 16-4 License Center Page

All licensed MSEs are listed in the following columns:

MSE Name—Provides a link to the MSE license file list page.


Note The icon to the left of the MSE Name/UDI indicates whether the mobility services engine is low-end or high-end.
A high-end mobility services engine (3350) has a higher memory capacity and can track up to 18,000 clients and tags. A low-end mobility services engine (3310) can track up to 2000 clients and tags.


Type—Specifies the type of MSE.


Note Under wIPS Monitor Mode APs or wIPS Local Mode APs, an active link takes you to a list of licensed access points. You cannot access a list of licensed clients or tags.


Limit—Displays the total number of client elements licensed across MSEs.

Count—Displays the number of client elements that are currently licensed across MSEs.

Unlicensed Count—Displays the number of client elements that are not licensed.


Note wIPS service does not process the alarms generated from these unlicensed access points.


% Used—Displays the percentage of clients used across all MSEs.

License Type—The three different types of licenses are as follows:

Permanent—Licenses are node-locked and have no usage period associated with them. They are issued by Cisco's licensing portal and must be installed using management interfaces on the device. Upon installation of these licenses, you have the necessary permissions across different versions.

Evaluation—Licenses are non-node-locked and are valid only for a limited time period. They are used only when no permanent, extension, or grace period licenses exist. Before using an evaluation license, you must accept an End User License Agreement (EULA). Even though they are non-node-locked, their usage is recorded on the device. The number of days remaining on the evaluation license which has the fewest number of days until expiration is shown.

Extension—Licenses are node-locked and metered. They are issued by Cisco's licensing portal and must be installed using management interfaces on the device. Before using an extension license, you must accept a EULA during installation.

Status

Active—License is installed and being used by a feature.

Inactive—License is installed but not being used by a feature.

Expired—License has expired.

Corrupted—License is corrupted.

For more information on MSE licenses, see the "Overview of MSE License" section on page 12-80.

Performing Background Tasks

This section contains procedures for crucial background tasks:

Performing a Data Collection Task

Performing Other Background Tasks

For more information on the Data Collection and Other Background Tasks, see "Data Collection Tasks" section and "Other Background Tasks" section.

Performing a Data Collection Task

Data collection tasks are data-set tasks that collect and organize information that may be useful for creating reports.


Note All tasks related to collecting data or any other background task would be handled in a similar manner.



Step 1 Choose Administration > Background Tasks to display the Background Tasks page. This page displays the following information:

Enabled—Whether the tasks have been enabled or disabled.

Interval—Indicates the time period (in minutes) between task executions. You can set the interval from the data collection configuration page for the task.

Status—The present state of the task.

Data Aggregation (Data Collection Tasks only)—If set to Yes, the data set combines data.

Non-Aggregation Data Retain Period (Days) (Data Collection Tasks only)—The number of days that the non-aggregated data is retained. You can set the retention period from the data collection configuration page of the task.

Last Execution Time—The time and date when the task was last run.

Last Execution Status—The status after the last task was run.

Step 2 On this page, perform one of the following:

Execute the task now.

Select the check box of the task you want to execute. From the Select a command drop-down list, choose Execute Now, and click Go.

Enable the task.

Select the check box of the task you want to enable. From the Select a command drop-down list, choose Enable Task, and click Go. The task changes from unavailable to active after enabling is complete.

Disable the task.

Select the check box of the task you want to disable. From the Select a command drop-down list, choose Disable Task, and click Go. The task is grayed out after the disabling is complete.

View details of a task.

Click a URL in the Data Collection Tasks or Other Background Tasks column to view a specific task. The details on that task appear. Data collections are data-set tasks that collect and organize a specific type of information useful for creating reports. For more information on the various Data Collection Tasks, see "Data Collection Tasks" section.

To go to the configuration page of a data set, select the name of the data set in the Data Collection page. Each data set configuration page displays a table of the executions of the data set. The table has following columns:

Executed task information includes the following:

Last Execution Start Time—Indicates the date and time that the data-set task began running.

End Time—Indicates the date and time that the data-set task stopped running.

Elapsed Time (secs)—Indicates the amount of time (in seconds) it took to complete the task.

Result—Indicates the success or failure of the task.

Additional Information—Provides any additional information regarding a specific task.

Each data set configuration page contains the following parameters and information under Collection Set Details:

Description—Provides a brief read-only description of the data set.

Data Aggregation—Indicates whether or not data collected by the data set is aggregated.

Used By Report(s)—Displays names of the reports that use the data set.

CleanAir Air Quality—This data set is used for Worst Air Quality APs and Air Quality versus Time reports.

Interferers—This data set us used for Worst Interferers reports.

Collection Status—Select the Enabled check box to enable data collection.

Interval (min.)—Enter the time (in minutes) for the data set execution interval. Valid value is 1 to 120 minutes.

Each data set configuration page contains the following parameters under Data Management:

Non-Aggregation Data Retain Period (Days)—Enter the number of days to retain non-aggregated data collected by the data set. Valid value is 1 to 31 days.

Retain Aggregation Raw Data—Select the Enable check box to enable the retention of aggregated raw data.


Note The Aggregation Raw Data Retain Period setting is for polled raw data. To configure the retention period for aggregated trend data, choose Administration > Settings, then choose Data Management from the left sidebar menu.



Note See the "Authentication, Authorization, and Accounting (AAA)" section for more information on aggregated and non-aggregated data.



Note For this example, performing an WCS server backup was selected as the task. The screens and fields to enter on the detailed screens vary based on the task you choose.


Step 3 Select the Enabled check box to enable it.

Step 4 Select the Report History Backup check box.

Step 5 In the Max Backups to Keep text box, enter the maximum number of backup files to save on the server.

Range: 7 to 50

Default: 7


Note To prevent the WCS platform from running out of disk space, the server automatically deletes old backup files when the number of files exceeds the value entered for this text box.


Step 6 In the Interval (Days) text box, enter the number of days between each backup. For example, 1 = a daily backup, 2 = a backup every other day, 7 = a weekly backup, and so on.

Range: 1 to 360

Default: 7

Step 7 In the Time of Day text box, enter the back-up start time. It must be in this format: hh:mm AM/PM (for example: 03:00 AM). If no AM/PM notation is designated, the entered hour is always AM. If you want to specify 5PM, you can enter 17:00 or 5:00 PM. When the page is revisited after saving, the time is displayed as hh:mm (in this case 17:00), without the PM designation.


Note Backing up a large database affects the performance of the WCS server. Therefore, we recommend that you schedule backups to run when the WCS server is idle (such as, in the middle of the night).


Step 8 Click Submit to save your settings. The backup file is saved as a .zip file in the ftp-install-dir/ftp-server/root/WCSBackup directory using this format: dd-mmm-yy_ hh-mm-ss.zip
(for example, 11-Nov-05_10-30-00.zip).


Data Collection Tasks

Table 16-2 lists and describes the various data collection tasks in WCS.

Table 16-2 Data Collection Tasks

Task Name
Task Status
Default Schedule
Description

AP Image Pre-Download Status

Disabled

15 minutes

This task is used to see the Image Predownload-status of the associated APs in the Controllers. To see the status of the access points, the Pre-download software to APs option should be selected while downloading software to Controller.

Autonomous AP CPU and Memory Utilization

Enabled

15 minutes

This task is used to collect information about Memory and CPU Utilization of Autonomous APs.

CleanAir Air Quality

Enabled

15 minutes

This task is used to collect information about CleanAir Air Quality.

Client Statistics

Enabled

15 minutes

This task helps you to get the statistical information for the Autonomous and Lightweight clients.

Controller Performance

Enabled

30 minutes

This task is used to collect performance information for Controllers.

Guest Sessions

Enabled

15 minutes

This task is used to collect information about the Guest sessions.

Interferers

Enabled

15 minutes

This task is used to collect information about the Interferers.

Mesh link Performance

Enabled

10 minutes

This task is used to collect information about the performance of Mesh links.

Mesh Link Status

Enabled

5 minutes

This task is used to collect status of the Mesh links.

Mobility Service Performance

Enabled

15 minutes

This task is used to collect information about the performance of mobility service engines.

Media Stream Clients

Enabled

15 minutes

This task is used to collect information about the media stream clients.

Radio Performance

Enabled

15 minutes

This task is used to collect statistics from wireless radios.

Rogue AP

Enabled

120 minutes

This task is used to collect information about the Rogue access points.

Traffic Stream Metrics

Enabled

8 minutes

This task helps you to get traffic stream metrics for the clients.

V5 Client Statistics

Disabled

60 minutes

This task is used to collect the Dot11 and Security statistics for CCX clients >= v5.


Performing Other Background Tasks

You can also perform other background tasks using WCS Administration.

This section contains the procedures for the other WCS background tasks:

Performing a Configuration Sync

Viewing Controller Configuration Backup Status

Viewing Data Cleanup Status

Performing Device Data Collection

Performing Guest Accounts Sync

Updating Controller License Status

Performing Mobility Service Backup

Viewing Mobility Service Status

Performing Mobility Service Synchronization

Viewing Wireless Status

Viewing OSS Server Status

For more information on the Other background tasks, see Other Background Tasks.

Performing a Configuration Sync

To perform a configuration sync, follow these steps:


Step 1 Choose Administration > Background Tasks to display the Background Tasks page (see Figure 16-1).

Step 2 On this page, perform one of the following:

Execute the task now.

Choose the Configuration Sync check box. From the Select a command drop-down list, choose Execute Now, and click Go. You see the status change in the Enabled column.

or

Enable the task.

Choose the Configuration Sync check box. From the Select a command drop-down list, choose Enable Task, and click Go. The task converts from dimmed to active in the Enabled column.

or

Disable the task.

Choose the Configuration Sync check box. From the Select a command drop-down list, choose Disable Task, and click Go. The task is dimmed in the Enabled column after the disabling is complete.

Step 3 To modify the task, click the Configuration Sync link in the Background Tasks column. The Task > Configuration Sync page appears (see Figure 16-5).

Figure 16-5 Task > Configuration Sync

Step 4 Click the background task in the Task column to open the task details page.

The Configuration Sync page displays the following information:

Last Execution Information

Start and end times.

Elapsed time (in seconds) of the task.

Result—Success or error.

Message—Text message regarding this task.

Step 5 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Used By Report(s)—Indicates the WCS reports that use these task results.

Enabled—Select the check box to enable this task.

Network Audit—Select the check box to enable the secondary network audit.

Security Index Calculation—Select the check box to enable security index calculation. The Security Index is available on the Monitor > Security page.

RRM Audit—Select the check box to enable an RRM audit.


Note The Controller audit will find the discrepancies between the values in WCS Database with the device.



Note To Query the SNMP Values from the device, you can use the https://<wcs-IP>/webacs/manObjDiagQueryAction.do URL in WCS.



Note The Network Audit audits on all controllers in the network, and also runs RRM audit and Security audit. These options are selectable from the Administration > Background Tasks > Other Background Tasks > Configuration Sync page.


Time of Day (hh:mm AM|PM)—Indicate the time of day (AM or PM) for the execution of this task.


Note Time of Day (hh:mm AM|PM) must be in this format: hh:mm AM/PM (for example: 03:00 AM). If no AM/PM notation is designated, the entered hour is always AM. If you want to specify 5PM, you could enter 17:00 or 5:00 PM. When the page is revisited after saving, the time is displayed as hh:mm (in this case 17:00), without the PM designation.



Note When WCS is upgraded from 6.0.x to 7.0,x the upgrade script will change the interval for this background task from hours to minutes. The smart sync option is enabled by default with 60 minutes interval. This default setting would override any settings applied in WCS 6.0.x.


Step 6 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Viewing Controller Configuration Backup Status

Choose Administration > Background Tasks, then click Controller Configuration Backup to access this page.

This page enables you to view the history and current status of Cisco WLAN Solution configuration backups.

From the Administration > Background Tasks page, you can execute, enable, or disable this task. To execute, enable, or disable this task from the Administration > Background Tasks page, follow these steps:


Step 1 Choose Administration > Background Tasks.

Step 2 Select the check box(es) of the Background Task(s) that you want to execute, enable, or disable.

Step 3 Use the Select a command drop-down list to perform one of the following tasks:

Execute the task now—Select the check box of the task you want to execute. From the Select a command drop-down list, choose Execute Now, and click Go. The status changes in the Enabled column.

or

Enable the task—Select the check box of the task you want to enable. From the Select a command drop-down list, choose Enable Task, and click Go.

or

Disable the task—Select the check box of the task you want to disable. From the Select a command drop-down list, choose Disable Task, and click Go.


To modify the task, follow these steps:


Step 1 Click the background task in the Task column to open the task details page.

The Controller Configuration Backup page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 2 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Enabled—Select this check box to enable Cisco WCS execute the task at the specified interval.


Note If the Enabled check box is not selected, the task is not executed at the specified time.


Interval—Indicates the frequency (in days) of the task.

Time of Day (hh:mm AM|PM)


Note Time of Day (hh:mm AM|PM) must be in this format: hh:mm AM/PM (for example: 03:00 AM). If no AM/PM notation is designated, the entered hour is always AM. If you want to specify 5PM, you could enter 17:00 or 5:00 PM. When the page is revisited after saving, the time is displayed as hh:mm (in this case 17:00), without the PM designation.


TFTP Server—Select the server or Default Server from the drop-down list.


Note TFTP must be enabled in Administration > Settings > Server Settings for 'Default Server' options.


Step 3 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Viewing Client Status

Choose Administration > Background Tasks, then click Client Status to access this page.

This page enables you to view the history and current status of client status polling backups.

In the Administration > Background Tasks page, you can execute, enable, or disable this task. To execute, enable, or disable this task from the Administration > Background Tasks page, follow these steps:


Step 1 Choose Administration > Background Tasks.

Step 2 Select the check box(es) of the Background Task(s) that you want to execute, enable, or disable.

Step 3 Use the Select a command drop-down list to perform one of the following tasks:

Execute the task now—Select the check box of the task you want to execute. From the Select a command drop-down list, choose Execute Now, and click Go. The status changes in the Enabled column.

or

Enable the task—Select the check box of the task you want to enable. From the Select a command drop-down list, choose Enable Task, and click Go.

or

Disable the task—Select the check box of the task you want to disable. From the Select a command drop-down list, choose Disable Task, and click Go.


To modify the task, follow these steps:


Step 1 Click the background task in the Task column to open the task details page.

The Client Status page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 2 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Enabled—Select this check box to enable WCS to execute the task at the specified interval.


Note If the Enabled check box is not selected, the task is not executed at the specified time.


Interval—Indicates the frequency (in days) of the task.

Step 3 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Updating Controller License Status

To update the controller license status, follow these steps :


Step 1 Choose Administration > Background Tasks to display the Background Tasks page (see Figure 16-6).

Step 2 On this page, perform one of the following:

Execute the task now.

Select the Controller License Status check box. From the Select a command drop-down list, choose Execute Now, and click Go. You see the status change in the Enabled column.

or

Enable the task.

Select the Controller License Status check box. From the Select a command drop-down list, choose Enable Task, and click Go. The task converts from grayed out to active in the Enabled column.

or

Disable the task.

Select the Controller License Status check box. From the Select a command drop-down list, choose Disable Task, and click Go. The task converts from grayed out to active in the Enabled column after the disabling is complete.

Step 3 To modify the controller license reset task, click the Controller License Status link in the Background Tasks column. The Controller License Status page appears (see Figure 16-6).

Figure 16-6 Controller License Status Page

This page shows when the latest license resynchronizations occurred. By default, it runs every 4 hours. From this page, you can disable this task or change the interval.

Step 4 Click the background task in the Task column to open the task details page.

Step 5 The Controller Configuration Backup page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 6 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Enabled—Select this check box to enable Cisco WCS execute the task at the specified interval.


Note If the Enabled check box is not selected, the task is not executed at the specified time.


Interval—Indicates the frequency (in days) of the task.

Step 7 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Viewing Data Cleanup Status

Choose Administration > Background Tasks, then click Database Cleanup to access this page.

This page enables you to view the history and current status of Cisco WLAN Solution database cleanups.

To modify this task, follow these steps:


Step 1 Choose Administration > Background Tasks.

Step 2 Click the background task in the Task column to open the task details page.

The Data Cleanup page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 3 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Time of Day (hh:mm AM|PM)


Note Time of Day (hh:mm AM|PM) must be in this format: hh:mm AM/PM (for example: 03:00 AM). If no AM/PM notation is designated, the entered hour is always AM. If you want to specify 5PM, you can enter 17:00 or 5:00 PM. When the page is revisited after saving, the time is displayed as hh:mm (in this case 17:00), without the PM designation.


Step 4 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Performing Device Data Collection

Follow these steps to perform a device data collection:


Step 1 Choose Administration > Background Tasks to display the Background Tasks page.

Step 2 On this page, perform one of the following:

Execute the task now.

Select the Device Data Collection check box. From the Select a command drop-down list, choose Execute Now, and click Go. You see the status change in the Enabled column.

or

Enable the task.

Select the Device Data Collection check box. From the Select a command drop-down list, choose Enable Task, and click Go. The task converts from grayed out to active in the Enabled column.

or

Disable the task.

Select the Device Data Collection check box. From the Select a command drop-down list, choose Disable Task, and click Go. The task is grayed out in the Enabled column after the disabling is complete.

Step 3 To modify the task, click the Device Data Collection link in the Background Tasks column. The Task > Device Data Collector page appears.

Step 4 Click the background task in the Task column to open the task details page.

The Device Data Collector page displays the following information:

Last Execution Information

Start and end times.

Elapsed time (in seconds) of the task.

Result—Success or error.

Message—Text message regarding this task.

Step 5 View or modify the following in the Edit Task group box:

Description—Read-only. Displays the name of the task.

Enabled—Select the check box to enable this task.

Controller IP address—The IP address of the Controller to collect data from.

CLI Commands—Enter the CLI commands separated by comma, which you would want to run on the specified Controller.

Clean Start—Select or unselect this option to enable or disable a clean start before data collection.

Repeat—Enter the number of times you would want the data collection to happen.

Interval—Enter the interval in days that you would want the data collection to happen. Valid range: 1 to 360 days.

Step 6 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Viewing Device Status

Device status polls controller reachability and WiSM peer information.

Choose Administration > Background Tasks, then click Device Status to access this page.

This page enables you to view the history and current status of Cisco WLAN Solution device status tasks.

From the Administration > Background Tasks page, you can execute, enable, or disable this task. To execute, enable, or disable this task from the Administration > Background Tasks page, follow these steps:


Step 1 Choose Administration > Background Tasks.

Step 2 Select the check box(es) of the Background Task(s) that you want to execute, enable, or disable.

Step 3 Use the Select a command drop-down list to perform one of the following tasks:

Execute the task now—Select the check box of the task you want to execute. From the Select a command drop-down list, choose Execute Now, and click Go. The status changes in the Enabled column.

or

Enable the task—Select the check box of the task you want to enable. From the Select a command drop-down list, choose Enable Task, and click Go.

or

Disable the task—Select the check box of the task you want to disable. From the Select a command drop-down list, choose Disable Task, and click Go.


To modify the task, follow these steps:


Step 1 Click the background task in the Task column to open the task details page.

The Device Status page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 2 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Enabled—Select this check box to enable Cisco WCS execute the task at the specified interval.


Note If the Enabled check box is not selected, the task is not executed at the specified time.


Interval—Indicates the frequency (in days) of the task.

Step 3 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Performing Guest Accounts Sync

Choose Administration > Background Tasks, then click Guest Accounts Sync to access this page.

This page enables you to view the history and current status of Guest Accounts Synchronization tasks.

From the Administration > Background Tasks page, you can execute, enable, or disable this task. To execute, enable, or disable this task from the Administration > Background Tasks page, follow these steps:


Step 1 Choose Administration > Background Tasks.

Step 2 Select the check box(es) of the Background Task(s) that you want to execute, enable, or disable.

Step 3 Use the Select a command drop-down list to perform one of the following tasks:

Execute the task now—Select the check box of the task you want to execute. From the Select a command drop-down list, choose Execute Now, and click Go. The status changes in the Enabled column.

or

Enable the task—Select the check box of the task you want to enable. From the Select a command drop-down list, choose Enable Task, and click Go.

or

Disable the task—Select the check box of the task you want to disable. From the Select a command drop-down list, choose Disable Task, and click Go.


To modify the task, follow these steps:


Step 1 Click the background task in the Task column to open the task details page.

The Guest Accounts Synchronization page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 2 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Enabled—Select this check box to enable Cisco WCS execute the task at the specified interval.


Note If the Enabled check box is not selected, the task is not executed at the specified time.


Interval—Indicates the frequency (in days) of the task.

Time of Day (hh:mm AM|PM)


Note Time of Day (hh:mm AM|PM) must be in this format: hh:mm AM/PM (for example: 03:00 AM). If no AM/PM notation is designated, the entered hour is always AM. If you want to specify 5PM, you can enter 17:00 or 5:00 PM. When the page is revisited after saving, the time is displayed as hh:mm (in this case 17:00), without the PM designation.


Step 3 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Performing Mobility Service Backup

Choose Administration > Background Tasks, then click Mobility Service Backup to access this page.

This page enables you to schedule a backup of the mobility services engine database.

From the Administration > Background Tasks page, you can execute, enable, or disable this task. To execute, enable, or disable this task from the Administration > Background Tasks page, follow these steps:


Step 1 Choose Administration > Background Tasks.

Step 2 Select the check box(es) of the Background Task(s) that you want to execute, enable, or disable.

Step 3 Use the Select a command drop-down list to perform one of the following tasks:

Execute the task now—Select the check box of the task you want to execute. From the Select a command drop-down list, choose Execute Now, and click Go. The status changes in the Enabled column.

or

Enable the task—Select the check box of the task you want to enable. From the Select a command drop-down list, choose Enable Task, and click Go.

or

Disable the task—Select the check box of the task you want to disable. From the Select a command drop-down list, choose Disable Task, and click Go.


To modify the task, follow these steps:


Step 1 Click the background task in the Task column to open the task details page.

The Mobility Service Backup page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 2 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Enabled—Select this check box to enable Cisco WCS execute the task at the specified interval.


Note If the Enabled check box is not selected, the task is not executed at the specified time.


Max backups to keep—Enter the maximum number of location backups to be kept on the backup server.

Interval (days)—Enter the frequency of backup.

Time of the Day (hh:mm AM/PM)—Enter the time at which the backup starts on the scheduled day.


Note Time of Day (hh:mm AM|PM) must be in this format: hh:mm AM/PM (for example: 03:00 AM). If no AM/PM notation is designated, the entered hour is always AM. If you want to specify 5PM, you can enter 17:00 or 5:00 PM. When the page is revisited after saving, the time is displayed as hh:mm (in this case 17:00), without the PM designation.


When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Viewing Mobility Service Status

Choose Administration > Background Tasks, then click Mobility Service Status to access this page.

This page displays the status of the mobility services engine.

From the Administration > Background Tasks page, you can execute, enable, or disable this task. To execute, enable, or disable this task from the Administration > Background Tasks page, follow these steps:


Step 1 Choose Administration > Background Tasks.

Step 2 Select the check box(es) of the Background Task(s) that you want to execute, enable, or disable.

Step 3 Use the Select a command drop-down list to perform one of the following tasks:

Execute the task now—Select the check box of the task you want to execute. From the Select a command drop-down list, choose Execute Now, and click Go. The status changes in the Enabled column.

or

Enable the task—Select the check box of the task you want to enable. From the Select a command drop-down list, choose Enable Task, and click Go.

or

Disable the task—Select the check box of the task you want to disable. From the Select a command drop-down list, choose Disable Task, and click Go.


To modify the task, follow these steps:


Step 1 Click the background task in the Task column to open the task details page.

The Mobility Service Status page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 2 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Enabled—Select this check box to enable Cisco WCS execute the task at the specified interval.


Note If the Enabled check box is not selected, the task is not executed at the specified time.


Interval (days)—Enter the frequency of backup.

Step 3 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Performing Mobility Service Synchronization

Choose Administration > Background Tasks, then click Mobility Service Synchronization to access this page.

This page enables you to synchronize mobility services engine(s).

From the Administration > Background Tasks page, you can execute, enable, or disable this task. To execute, enable, or disable this task from the Administration > Background Tasks page, follow these steps:


Step 1 Choose Administration > Background Tasks.

Step 2 Select the check box(es) of the Background Task(s) that you want to execute, enable, or disable.

Step 3 Use the Select a command drop-down list to perform one of the following tasks:

Execute the task now—Select the check box of the task you want to execute. From the Select a command drop-down list, choose Execute Now, and click Go. The status changes in the Enabled column.

or

Enable the task—Select the check box of the task you want to enable. From the Select a command drop-down list, choose Enable Task, and click Go.

or

Disable the task—Select the check box of the task you want to disable. From the Select a command drop-down list, choose Disable Task, and click Go.


To modify the task, follow these steps:


Step 1 Click the background task in the Task column to open the task details page.

The Mobility Service Synchronization page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 2 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Out of Sync Alerts—When enabled, this generates minor alarms when location server is not synchronized with the WCS changes that you have made.

Auto Synchronization—Use this setting to enable auto synchronization of the location server. This ensures that when you make changes to WCS, the location server auto synchronizes with the changes.

Interval (minutes)—Specify the auto synchronization interval.

Step 3 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Viewing OSS Server Status

Follow these steps to view the OSS Server status:


Step 1 Choose Administration > Background Tasks to display the Background Tasks page.

Step 2 On this page, perform one of the following:

Execute the task now.

Select the OSS Server Status check box. From the Select a command drop-down list, choose Execute Now, and click Go. You see the status change in the Enabled column.

or

Enable the task.

Select the OSS Server Status check box. From the Select a command drop-down list, choose Enable Task, and click Go. The task converts from grayed out to active in the Enabled column.

or

Disable the task.

Select the OSS Server Status check box. From the Select a command drop-down list, choose Disable Task, and click Go. The task converts from grayed out to active in the Enabled column after the disabling is complete.

Step 3 To modify the controller license reset task, click the OSS Server Status link in the Background Tasks column. The OSS Server Status page appears.

Step 4 Click the background task in the Task column to open the task details page.

Step 5 The OSS Server Status page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 6 View or modify the following in the Edit Task group box:

Description—Read-only. Displays the name of the task.

Enabled—Select this check box to enable Cisco WCS execute the task at the specified interval.


Note If the Enabled check box is not selected, the task is not executed at the specified time.


Interval—Indicates the frequency (in days) of the task.

Step 7 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Viewing Wireless Status

Wireless status polls:

Global Dot11 adminStatus on the controller.

Lightweight access point and radio admin and oper status.

Radio profile threshold violations.

Choose Administration > Background Tasks, then click Wireless Status to access this page.

From the Administration > Background Tasks page, you can execute, enable, or disable this task. To execute, enable, or disable this task from the Administration > Background Tasks page, follow these steps:


Step 1 Choose Administration > Background Tasks.

Step 2 Select the check box(es) of the Background Task(s) that you want to execute, enable, or disable.

Step 3 Use the Select a command drop-down list to perform one of the following tasks:

Execute the task now—Select the check box of the task you want to execute. From the Select a command drop-down list, choose Execute Now, and click Go. The status changes in the Enabled column.

or

Enable the task—Select the check box of the task you want to enable. From the Select a command drop-down list, choose Enable Task, and click Go.

or

Disable the task—Select the check box of the task you want to disable. From the Select a command drop-down list, choose Disable Task, and click Go.


To modify the task, follow these steps:


Step 1 Click the background task in the Task column to open the task details page.

The Wireless Status page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 2 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Enabled—Select this check box to enable Cisco WCS execute the task at the specified interval.


Note If the Enabled check box is not selected, the task is not executed at the specified time.


Interval (days)—Enter the frequency of backup.

Step 3 When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Performing WCS Server Backup

Choose Administration > Background Tasks, then click WCS Server Backup to access this page.

This page enables you to schedule a backup of the WCS server.

From the Administration > Background Tasks page, you can execute, enable, or disable this task. To execute, enable, or disable this task from the Administration > Background Tasks page, follow these steps:


Step 1 Choose Administration > Background Tasks.

Step 2 Select the check box(es) of the Background Task(s) that you want to execute, enable, or disable.

Step 3 Use the Select a command drop-down list to perform one of the following tasks:

Execute the task now—Select the check box of the task you want to execute. From the Select a command drop-down list, choose Execute Now, and click Go. The status changes in the Enabled column.

or

Enable the task—Select the check box of the task you want to enable. From the Select a command drop-down list, choose Enable Task, and click Go.

or

Disable the task—Select the check box of the task you want to disable. From the Select a command drop-down list, choose Disable Task, and click Go.


To modify the task, follow these steps:


Step 1 Click the background task in the Task column to open the task details page.

The WCS Server Backup page displays the following information:

Last Execution Information

Start and end times

Elapsed time in seconds

Result—Success or error.

Message—Text message regarding the task execution.

Step 2 View or modify the following in the Edit Task pane:

Description—Read-only. Displays the name of the task.

Enabled—Select this check box to enable Cisco WCS execute the task at the specified interval.


Note If the Enabled check box is not selected, the task is not executed at the specified time.


Report History Backup—Select the check box to enable WCS to back up report histories.

Max Backups to Keep—Enter the maximum number of WCS server backups to be kept on the backup server.

Interval (days)—Enter a value between 1 and 360. The WCS server data is backed up every n days, where n is the value that you have specified in this field.

Time of the Day (hh:mm AM/PM)—Enter the time at which the backup starts on the scheduled day.


Note Time of Day (hh:mm AM|PM) must be in this format: hh:mm AM/PM (for example: 03:00 AM). If no AM/PM notation is designated, the entered hour is always AM. If you want to specify 5PM, you could enter 17:00 or 5:00 PM. When the page is revisited after saving, the time is displayed as hh:mm (in this case 17:00), without the PM designation.


When finished, click Submit to confirm task changes or Cancel to return to the Administration > Background Tasks page with no changes made.


Other Background Tasks

Table 16-3 lists and describes the other background tasks that are available in WCS:

Table 16-3 Other Background Tasks 

Task Name
Default Schedule
Description
Editable Options

Configuration Sync

Daily at 4 am.

This task is used to view the Configuration Synchronization.

Enable—Select or unselect this option to enable or disable Configuration Synchronization. Default: Enabled.

Enable—Select or unselect this option to enable or disable Network Audit. Default: Enabled.

Enable—Select or unselect this option to enable or disable Security Index calculation. Default: Enabled.

Enable—Select or unselect this option to enable or disable RRM audit. Default: Enabled.

Interval—Enter the interval in days that you would want the configuration synchronization to happen. Valid range: 1 to 360 days.

Time of Day—Enter the time of the day at which you would want the configuration synchronization to happen. Valid format: hh:mm AM|PM. Example: 12:49 AM.

For more information, see "Performing a Configuration Sync" section.

Controller Configuration Backup

Daily at 10 pm

This task is used to view the Controller Configuration Backup activities.

Enable—Select or unselect this option to enable or disable Controller Configuration Backup. Default is Disabled.

Interval—Enter the interval in days that you would want the configuration synchronization to happen. Valid range: 1 to 360 days.

Time of Day—Enter the time of the day at which you would want the configuration synchronization to happen. Valid format: hh:mm AM|PM. Example: 12:49 AM.

TFTP Server—Select the IP address of the server to which you want to backup the Controller Configuration.

For more information, see "Viewing Controller Configuration Backup Status" section.

Client Status

5 minutes.

This task is used to schedule the client status polling backups.

Enable—Select or unselect this option to enable or disable client status polling. Default is Enabled.

Interval—Enter the interval in days that you would want the client status polling to happen. Valid range: 1 to 10080 minutes.

For more information, see "Viewing Client Status" section.

Controller License Status

4 hours.

This task is used to schedule the license status polling.

Enable—Select or unselect this option to enable or disable license status polling. Default is Enabled.

Interval—Enter the interval in days that you would want the license status polling to happen. Valid range: 1 to 360 days.

For more information, see "Updating Controller License Status" section.

Data Cleanup

Daily at 2 am.

This task is used to schedule a data cleanup

Time of Day—Enter the time of the day at which you would want the data cleanup to happen. Valid format: hh:mm AM|PM. Example: 12:49 AM. Default is Enabled.

For more information, see "Viewing Data Cleanup Status" section.

Device Data Collector

30 minutes

This task is used to schedule a data collection based on the specified CLI commands at a configured time interval.

Enabled—Select or unselect this option to enable or disable data collection for a specified Controller. Default is Disabled.

Controller IP address—The IP address of the Controller to collect data from.

CLI Commands—Enter the CLI commands separated by comma, which you would want to run on the specified Controller.

Clean Start—Select or unselect this option to enable or disable a clean start before data collection.

Repeat—Enter the number of times you would want the data collection to happen.

Interval—Enter the interval in days that you would want the data collection to happen. Valid range: 1 to 360 days.

For more information, see "Performing Device Data Collection" section.

Device Status

5 minutes.

This task is used to view the history and current status of Cisco WLAN Solution device status tasks

Enable—Select or unselect this option to enable or disable Device status polling. Default is Disabled.

Interval—Enter the interval in minutes that you would want the device polling to happen. Valid range: 1 to 10080 minutes.

For more information, see "Viewing Device Status" section.

Guest Accounts Sync

Daily at 1 am.

This task is used to schedule Guest Account polling and synchronization.

Enable—Select or unselect this option to enable or disable guest account synchronization. Default is Enabled.

Interval—Enter the interval in days that you would want the guest account synchronization to happen. Valid range: 1 to 360 days.

Time of Day—Enter the time of the day at which you would want the guest account synchronization to happen. Valid format: hh:mm AM|PM. Example: 12:49 AM.

For more information, see "Performing Guest Accounts Sync" section.

Mobility Service Backup

Every 7 days at 1 am.

This task is used to schedule mobility services backup polling.

Enable—Select or unselect this option to enable or disable mobility service backup. Default is disabled.

Interval—Enter the interval in days that you would want the mobility services backup to happen. Valid range: 1 to 360 days.

Time of Day—Enter the time of the day at which you would want the mobility services backup to happen. Valid format: hh:mm AM|PM. Example: 12:49 AM.

For more information, see "Performing Mobility Service Backup" section.

Mobility Service Status

5 minutes.

This task is used to schedule mobility services status polling.

Enable—Select or unselect this option to enable or disable mobility services status polling. Default is Enabled.

Interval—Enter the interval in days that you would want the mobility services status polling to happen. Valid range: 1 to 360 days.

For more information, see "Viewing Mobility Service Status" section.

Mobility Service Synchronization

60 minutes.

This task is used to schedule mobility services synchronization.

Out of Sync Alerts—Select this option if you want to enable out of sync alerts.

Smart Synchronization—Select this option if you want to enable smart synchronization. Default is Enabled.

Interval—Enter the interval in minutes that you would want the mobility services synchronization to happen. Valid range: 1 to 10080 minutes.

For more information, see "Performing Mobility Service Synchronization" section.

OSS Server Status

5 minutes.

This task is used to schedule OSS server status polling.

Enable—Select or unselect this option to enable or disable OSS Server polling. Default is Enabled.

Interval—Enter the interval in minutes that you would want the OSS server polling to happen. Valid range: 1 to 10080 minutes.

For more information, see "Viewing OSS Server Status" section.

Wireless Status

5 minutes.

This task is used to schedule wireless devices status polling.

Enable—Select or unselect this option to enable or disable OSS Server polling. Default is Enabled.

Interval—Enter the interval in minutes that you would want the OSS server polling to happen. Valid range: 1 to 10080 minutes.

For more information, see "Viewing OSS Server Status" section.

WCS Server Backup

Every 7 days at 1 am.

This task is used to schedule the WCS server backup.

Enable—Select or unselect this option to enable or disable WCS server backup. Default is Disabled.

Interval—Enter the interval in days that you would want the WCS server backup to happen. Valid range: 1 to 360 days.

Time of Day—Enter the time of the day at which you would want the WCS server backup to happen. Valid format: hh:mm AM|PM. Example: 12:49 AM.

For more information, see "Viewing Wireless Status" section.


Importing Tasks Into ACS

To import tasks into Cisco Secure ACS server, you must add WCS to an ACS server (or non-Cisco ACS server). This section contains the following topics:

Adding WCS to an ACS Server

Adding WCS as a TACACS+ Server

Adding WCS UserGroups into ACS for TACACS+

Adding WCS to an ACS Server for Use with RADIUS

Adding WCS UserGroups into ACS for RADIUS

Adding WCS to a Non-Cisco ACS Server for Use with RADIUS

Adding WCS to an ACS Server

To add WCS to an ACS server, follow these steps:


Note The instructions and illustrations in this section pertain to ACS version 4.1 and may vary slightly for other versions or other vendor types. See the CiscoSecure ACS documentation or the documentation for the vendor you are using.



Step 1 Click Add Entry on the Network Configuration page of the ACS server (see Figure 16-7).

Figure 16-7 ACS Server Network Configuration Page

Step 2 In the AAA Client Hostname text box, enter the WCS hostname.

Step 3 Enter the WCS IP address in the AAA Client IP Address text box.

Step 4 In the Key text box, enter the shared secret that you wish to configure on both the WCS and ACS servers.

Step 5 Choose TACACS+ from the Authenticate Using drop-down list.

Step 6 Click Submit + Apply.


Adding WCS as a TACACS+ Server

To add WCS to a TACACS+ server, follow these steps:


Step 1 Go to the TACACS+ (Cisco IOS) Interface Configuration page (see Figure 16-7).

Step 2 In the New Services portion of the page, add Wireless-WCS in the Service column heading.

Step 3 Enter HTTP in the Protocol column heading.


Note HTTP must be in uppercase.


Step 4 Select the check box in front of these entries to enable the new service and protocol.

Step 5 Click Submit.


Adding WCS UserGroups into ACS for TACACS+

To add WCS UserGroups into an ACS Server for use with TACACS+ servers, follow these steps:


Step 1 Log into WCS.

Step 2 Choose Administration > AAA > Groups. The All Groups page appears (see Figure 16-8).

Figure 16-8 All Groups Page

Step 3 Click the Task List link (the Export right-most column) of the User Group that you wish to add to ACS. The Export Task List page appears (see Figure 16-9).

Figure 16-9 Export Task List Page

Step 4 Highlight the text inside of the TACACS+ Custom Attributes, go to your browser's menu, and choose Edit > Copy.

Step 5 Log in to ACS.

Step 6 Go to Group Setup. The Group Setup page appears (see Figure 16-10).

Figure 16-10 Group Setup Page on ACS Server

Step 7 Choose which group to use and click Edit Settings. Wireless-WCS HTTP appears in the TACACS+ setting.

Step 8 Use Edit > Paste in your browser to place the TACACS+ custom attributes from WCS into this text box.


Note When you upgrade WCS, any permissions on the TACACS+ or RADIUS server must be readded.


Step 9 Select the check boxes to enable these attributes.

Step 10 Click Submit + Restart.

You can now associate ACS users with this ACS group.


Note To enable TACACS+ in WCS, refer to the TACACS+. For information on configuring ACS view server credentials, see the "Configuring ACS View Server Credentials" section. For information on adding WCS Virtual Domains into ACS for TACACS+, see the "Virtual Domain RADIUS and TACACS+ Attributes" section.



Adding WCS to an ACS Server for Use with RADIUS

To add WCS to an ACS server for use with RADIUS servers, follow these steps:

. If you have a non-Cisco ACS server, see the "Adding WCS to a Non-Cisco ACS Server for Use with RADIUS" section.


Step 1 Go to Network Configuration on the ACS server (see Figure 16-11).

Figure 16-11 Network Configuration Page on ACS Server

Step 2 Click Add Entry.

Step 3 In the AAA Client Hostname text box, enter the WCS hostname.

Step 4 In the AAA Client IP Address text box, enter the WCS IP address.

Step 5 In the Key text box, enter the shared secret that you wish to configure on both the WCS and ACS servers.

Step 6 Choose RADIUS (Cisco IOS/PIX 6.0) from the Authenticate Using drop-down list.

Step 7 Click Submit + Apply.

You can now associate ACS users with this ACS group.


Note To enable RADIUS in WCS, see the "RADIUS" section. For information on configuring ACS view server credentials, see the "Configuring ACS View Server Credentials" section.



Adding WCS UserGroups into ACS for RADIUS

To add WCS UserGroups into an ACS Server for use with RADIUS servers, follow these steps:


Step 1 Log into WCS.

Step 2 Choose Administration > AAA > Groups. The All Groups page appears (see Figure 16-12).

Figure 16-12 All Groups Page

Step 3 Click the Task List link (the Export right-most column) of the User Group that you wish to add to ACS. The Export Task List page appears (see Figure 16-13).

Figure 16-13 Export Task List Page

Step 4 Highlight the text inside of the RADIUS Custom Attributes, go to your browser's menu, and choose Edit > Copy.


Note When you upgrade WCS, any permissions on the TACACS+ or RADIUS server must be readded.


Step 5 Log in to ACS.

Step 6 Go to Group Setup. The Group Setup page appears (see Figure 16-14).

Figure 16-14 Group Setup Page on ACS Server

Step 7 Choose which group to use and click Edit Settings. Find [009\001]cisco-av-pair under Cisco IOS/PIX 6.x RADIUS Attributes.

Step 8 Use Edit > Paste in your browser to place the TACACS+ custom attributes from WCS into this text box.


Note When you upgrade WCS, any permissions on the TACACS+ or RADIUS server must be readded.


Step 9 Click the check boxes to enable these attributes.

Step 10 Click Submit + Restart.

You can now associate ACS users with this ACS group.


Note To enable RADIUS in WCS, see the "RADIUS" section. For information on configuring ACS view server credentials, see the "Configuring ACS View Server Credentials" section.



Adding WCS to a Non-Cisco ACS Server for Use with RADIUS

When you use a RADIUS server to log into WCS, the AAA server sends back an access=accept message with a usergroup and a list of available tasks, after the username and password were verified. The access=accept message comes back as a fragmented packet because of the large number of tasks in some user groups. You can look in the following file to see the tasks associated with a given user group: C:\Program Files\WCS5.0\webnms\webacs\WEB-INF\security\usergroup-map.xml. The tasks are passed back as a vendor specific attribute (VSA), and WCS requires authorization information using the VSA (IETF RADIUS attribute number 26). The VSA contains the WCS RADIUS task list information (see Figure 16-15).

Figure 16-15 Extracting Task List

The content of the VSA is as follows:

Type = 26 (IETF VSA number)

Vendor Id = 9 (Cisco vendor ID)

Vendor Type = 1 (Custom attributes)

Vendor Data = The WCS task information (for example Wireless-WCS: task0 = Users and Group)

Each line from the WCS RADIUS task list should be sent in its own RADIUS VSA.

In the data portion of the access=access packet, the truncated output sometimes shows only one role sent back for an Admin user group login. The tasks associated with the role start with task0 and increment with task1, task2, and so on. Table 16-4 defines what these attributes in the access=access packet example signify.

0000 06 6d 0e 59 07 3d 6a 24 02 47 07 35 d2 12 a4 eb .m.Y.=j$G.5...
0010 a2 5a fa 84 38 20 e4 e2 3a 3a bc e5 1a 20 00 00 .Z..8..::..
0020 00 09 01 1a 57 69 72 65 6c 65 73 73 2d 57 43 53 ....Wireless-WCS
0030 3a 72 6f 6c 65 30 3d 41 64 6d 69 6e 1a 2b 00 00 :role0=Admin.+...
0040 00 09 01 25 57 69 72 65 6c 65 73 73 2d 57 43 53 ...%Wireless-WCS
0050 3a 74 61 73 6b 30 3d 55 73 65 72 73 20 61 6e 64 :task0=Users and
0060 20 47 72 6f 75 70 73 1a 27 00 00 00 09 01 21 57 Groups."....!W
0070 69 72 65 6c 65 73 73 2d 57 43 53 3a 74 61 73 6b Wireless-WCS:task
0080 31 3d 41 75 64 69 74 20 54 72 61 69 6c 73 xx xx 1=Audit Trails.*
 
   

Table 16-4 Access=Access Packet Example 

Attribute
Description

1a (26 in decimal)

Vendor attribute

2b (43 bytes in decimal)

Length as the total number of bytes to skip and still reach the next TLV (for task0, Users and Groups)

4-byte field

Vendor Cisco 09

01

Cisco AV pair - a TLV for WCS to read

25 (37 bytes in decimal)

Length

hex text string

Wireless-WCS:task0=Users and Groups

 

The next TLV until the data portion is completely processed.

255.255.255.255

TLV: RADIUS type 8 (framed IP address)

Type 35 (0x19)

A class, which is a string

Type 80 (0x50)

Message authenticator


To troubleshoot, perform the following steps:

Verify if the RADIUS packet is an access accept.

Verify the task names for the user group in the access accept.

Look at the different length fields in the RADIUS packet.

Configuring Auto Provisioning

This section contains the following topics:

Adding an Auto Provisioning Filter

Editing an Auto Provisioning Filter

Deleting Auto Provisioning Filter(s)

Listing Auto Provisioning Filter(s) Device Info

Exporting Auto Provisioning Filter(s)

Exporting All Auto Provisioning Filter(s)

Auto Provisioning Primary Search Key Settings

Adding an Auto Provisioning Filter

To add an Auto Provisioning Filter, follow these steps:


Step 1 Choose Configure > Auto Provisioning. The Auto Provisioning Filter List page appears (see Figure 16-16).

Figure 16-16 Auto Provisioning Filter List

Step 2 From the Select a command drop-down list, choose Add Filter.

Step 3 Click Go.

Step 4 Click Go. The Auto Provisioning Filters > New Filter page appears (see Figure 16-17).

Figure 16-17 Auto Provisioning Filters > New Filter

Step 5 Configure the following information:

General

Enable Filter—Select the check box to enable the new filter.


Note Only enabled filters can participate in the Auto Provisioning process.


Filter Name—Enter a filter name.

Filter Properties

Monitor Only—If selected, the WLC defined in this Filter is managed by WCS but not configured by WCS if the WLC contacts WCS during the auto provisioning process.

Filter Mode—From the drop-down list, choose Host Name, MAC Address, Serial Number to indicate the search mode for this filter.

Config Group Name—From the drop-down list, choose a config group name.

Filter Member Management - Add Member

Input Type—From the drop-down list, choose Single Device or CSV File.

If Single Device is selected, enter the host name, enable LAG configuration (if applicable), and enter the following: management interface IP Address, management interface netmask, management interface gateway, AP manager interface IP address, AP manager interface netmask, AP manager interface gateway, and DHCP IP address.

If CSV File is selected, enter the CSV file or use the Browse button to navigate to the applicable CSV File.


Note You can choose the Download a sample CSV File link to download a sample CSV file to your computer and customize the various configurations.



Note Because MS-Excel can insert additional commas when you edit a CSV file, ensure that you edit the CSV file using a normal text editor application.


A CSV file contains the following sections:

** The first part is the General Config section that contains parameters which are used to construct controller's startup config file.
**
The first line in the CSV file must be keyword
"!!deviceId, LAG, managementIP, managementVlanId, managementNetmask, managementGateway, apManagerIP, apManagerVlanId, apManagerNetmask, apManagerGateway, dhcpServerIP, virtualIPAddress"

deviceId—it can be Host name, Mac address, or Serial number.
LAG—controller's LAG configuration (true/false).
managementIP—controller's Management interface IP address.
managementVlanId—controller's Management interface VLAN Id (0=untagged).
managementNetmask—controller's Management interface Network mask.
managementGateway—controller's Management interface Gateway IP.
apManagerIP—controller's AP Manager Interface IP address, optional for 5500 series controller.
apManagerVlanId—controller's AP Manager Interface VLAN Id (0=untagged), optional for 5500 series controller.
apManagerNetmask—controller's AP Manager Interface Netmask, optional for 5500 series controller.
apManagerGateway—controller's AP Manager Interface Gateway, optional for 5500 series controller.
dhcpServerIP—controller's DHCP IP address.
virtualIPAddress—controller's Virtual IP address.

** The second part is the Dynamic Interface section that contains dynamic interface parameters for a controller. This is an optional section.
** To configure a dynamic interface, the first eight parameters are mandatory and the last four parameters are optional.
"!!deviceId, interfaceName, vlanId, quarantineVlanId, interfaceIP, interfaceNetmask, gateway, primaryPort, secondaryPort, primaryDHCP, secondaryDHCP, aclName"
deviceId—this deviceId must be defined previously in section 1.
interfaceName—name of the dynamic interface.
vlanId—vlan ID used by this interface.
quarantineVlanId—quarantine vlan ID used by this interface.
interfaceIP—IP address of the dynamic interface.
interfaceNetmask—Network Mask of the dynamic interface.
gateway—Gateway IP address of the dynamic interface.
primaryPort—physical primary port number used by the dynamic interface.
secondaryPort—physical secondary port number used by the dynamic interface, this is an optional parameter.
primaryDHCP—the IP address of the primary DHCP used by the dynamic interface, this is an optional parameter.
secondaryDHCP—IP address of the secondary DHCP used by the dynamic interface, this is an optional parameter.

** The third part is the Device Specific Config section, contains other device specific configuration parameters which are optional during auto provisioning.
"!!deviceId, countryCode, mobilityGroupName, mobilityGroupMembers"
deviceId—this deviceId must be defined previously in section 1.
countryCode—country code for the controller, this is an optional parameter.
mobilityGroupName—default name of the mobility group this controller belongs to, this is an optional parameter. If this attribute is not specified then the existing default mobility group name will be used.
mobilityGroupMembers—IP addresses, Mac Addresses and mobility group name of the mobility group members of the controller, which are separated by semi colon, this is an optional parameter. Both IP address and Mac Address are required for a mobility group member, they are separated by forward slash. Mobility group name is an optional attribute in this field. If mobility group name is not present then the default mobility group name for this controller will be used.

If you select the Single Device option, specify the following options:

Device Type—From the drop-down list, choose 5500 Controller or non-5500 Controller.

Host Name

LAG Configuration: Enabled or Disabled.

Management Interface IP Address

Management Interface Netmask

Management Interface Gateway

AP Manager Interface IP Address

AP Manager Interface Netmask

AP Manager Interface Gateway

DHCP IP Address—When the controller comes up after a reset, it uses this IP address to get a DHCP address, and identifies its TFTP server from where the configuration file needs to be picked.

Virtual IP Address—An address which is not routable and usually configured as 209.165.200.227 as a DHCP server at the virtual IP address to wireless clients.

Step 6 Click Submit.


Note You can specify the Dynamic Interface configuration and Device Specific configuration details only when you input a CSV file. These two configurations cannot be performed using the GUI.



Editing an Auto Provisioning Filter

To edit an Auto Provisioning filter, follow these steps:


Step 1 Choose Configure > Auto Provisioning.

Step 2 Click the Filter Name of the filter you want to edit.

Step 3 Make the necessary changes to the current filter parameters.


Note To view detailed information for a filter member, click the Device ID of the member you want to view.
To delete a filter member. select the check box for the member you want to delete in the Filter Member Management - Delete Member section. When you click Submit, that member is deleted.


Step 4 Click Submit.


Deleting Auto Provisioning Filter(s)

To delete an Auto Provisioning Filter, follow these steps:


Step 1 Choose Configure > Auto Provisioning.

Step 2 Select the check box of the filter you want to delete.

Step 3 From the Select a command drop-down list, choose Delete Filter(s).

Step 4 Click Go.

Step 5 Click OK to confirm the deletion.


Listing Auto Provisioning Filter(s) Device Info

To view details for an individual Auto Provisioning Filter, follow these steps:


Step 1 Choose Configure > Auto Provisioning.

Step 2 Select the check box of the filter you want to view.

Step 3 From the Select a command drop-down list, choose List Filter(s) Device Info.

Step 4 Click Go. The Detailed Auto Provisioning Device Information page appears (see Figure 16-18).

Figure 16-18 Detailed Auto Provisioning Device Information

The following information is provided for the selected filter:

Filter Name—Indicates the filter name.

Device ID—Indicates the device ID.

LAG—Indicates the controller LAG status as true or false.

Management IP—Indicates the management interface IP address of the controller.

Management VlanId—Indicates the management VLAN Id of the controller.

Management Netmask—Indicates the netmask mask of the management interface of the controller.

Management Gateway—Indicates the netmask gateway of the management interface of the controller.

AP Mgr IP—Indicates the IP address of the access point manager.

AP Mgr Vlan Id—Indicates the VLAN identifier of the access point manager.

AP Mgr Netmask—Indicates the netmask mask of the access point manager.

AP Mgr Gateway—Indicates the gateway IP address of the access point manager.

Status—Idle, Trap Received, Failed In Trap Processing, Failed In Applying Templates, Failed In Discovery Switch, Managed, Managed partially applied templates, or Unknown Error.

Country—Indicates the country.

Mobility Grp—Indicates the name of the mobility group.

Mobility Grp Members—Indicates the members of the mobility group.

Timestamp—Indicates the date and time of the information.


Listing All Auto Provisioning Filter(s) Device Info

To view details for all Auto Provisioning Filters, follow these steps:


Step 1 Choose Configure > Auto Provisioning.

Step 2 From the Select a command drop-down list, choose List All Filter(s) Device Info.

Step 3 Click Go.

The following information is provided for the selected filter:

Filter Name—Indicates the filter name.

Device ID—Indicates the device ID.

LAG—Indicates the controller LAG status as true or false.

Management IP—Indicates the management interface IP address of the controller.

Management VlanId—Indicates the management Vlan Id of the controller.

Management Netmask—Indicates the netmask mask of the management interface of the controller.

Management Gateway—Indicates the netmask gateway of the management interface of the controller.

AP Mgr IP—Indicates the IP address of the access point manager.

AP Mgr Vlan Id—Indicates the Vlan identifier of the access point manager.

AP Mgr Netmask—Indicates the netmask mask of the access point manager.

AP Mgr Gateway—Indicates the gateway IP address of the access point manager.

Status—Idle, Trap Received, Failed In Trap Processing, Failed In Applying Templates, Failed In Discovery Switch, Managed, Managed partially applied templates, or Unknown Error.

Country—Indicates the country.

Mobility Grp—Indicates the name of the mobility group.

Mobility Grp Members—Indicates the members of the mobility group.

Timestamp—Indicates the date and time of the information.


Exporting Auto Provisioning Filter(s)

To export an Auto Provisioning Filter, follow these steps:


Step 1 Choose Configure > Auto Provisioning.

Step 2 Select the check box of the filter(s) you want to export.

Step 3 From the Select a command drop-down list, choose Export Filter(s) Config (CSV).

Step 4 Click Go.

Step 5 In the File Download dialog box that appears, click Save to save the file to a location on the computer.


Exporting All Auto Provisioning Filter(s)

To export all Auto Provisioning Filters, follow these steps:


Step 1 Choose Configure > Auto Provisioning.

Step 2 From the Select a command drop-down list, choose Export All Filter(s) Config (CSV).

Step 3 Click Go.

Step 4 In the File Download dialog box that appears, click Save to save the file to a location on the computer.


Auto Provisioning Primary Search Key Settings

The Primary Search Key Setting enables you to set the matching criteria search order.

To indicate the Search Key Order, follow these steps:


Step 1 Choose Configure > Auto Provisioning.

Step 2 From the left sidebar menu, choose Auto Provisioning Setting.

Step 3 Click to highlight the applicable search key.

Step 4 Use the Move Up or Move Down buttons to move the search key to a higher or lower priority.

Step 5 Click Save to confirm or Cancel to cancel the changes.


Establishing Logging Options

Choose Administration > Logging to access the Administer Logging Options page. The logging for controller syslog information can be done in the Controller > Management > Syslog page. The following log settings can be configured:

General Logging Options

SNMP Logging Options

Syslog Options

General Logging Options

To enable e-mail logging, follow these steps. The settings you establish are stored and are used by the e-mail server.


Step 1 Choose Administration > Logging. The General Logging Options page appears (see Figure 16-19).

Step 2 Choose General Logging Options from the left sidebar menu.

Figure 16-19 General Logging Options Page

Step 3 Choose a message level option of Trace, Information, or Error.

Step 4 Select the check boxes within the Enable Log Module portion of the page to enable various administration modules:

Message Level—Choose the minimum level of the messages that will be logged including Error, Information, or Trace.

Enable Log Module—You can enable logging for the following administration modules:

Configuration—Used to log controller configurations that you make from WCS.


Note To get complete controller configuration logs, also enable the General log module.



Note To get the configuration values that the WCS sends in logs to controllers, enable Trace Display Values (Administration > Settings > SNMP Settings > Trace Display Value).


Monitor—Used for Alarms, Spectrum Intelligence, CCXV5, Clients/Tags, Client Radio Measurements, SSO, and Mesh.

Fault Analysis—Used by the event and alert subsystem.

General—Contains logs that do not fall under other log module categories.


Note We recommend that you enable this log module.


Navigator—Contains logs to debug issues when WCS does not respond to WCS Navigator's periodic polling through the Northbound Webservice API.

Reports—Used to log messages related to creating, saving, scheduling, and running reports. This module also contains a list of scheduled and saved reports.

Database Administration—Contains logs to debug important database-related operations in WCS.


Note Some functions should be used only for short periods of time during debugging so that the performance is not degraded. For example, trace mode and SNMP meditation should be enabled only during debugging because a lot of log information is generated.


Communication Protocol—Contains logs related to the protocols used in communication.

UI General—Contains generic UI validation logs.

Administration—Contains Adminsitration based logs, where all the configuration changes performed using the administration console is logged.

Tools—Contains logs releated to different plug-in tools.

MSE—Used for MSE-related operations such as adding or deleting an MSE and changing parameters on the MSE. It also enables logging for MSE synchronization including NW designs and controllers.

SOAP Communication—Contains logs that contain the SOAP header messages.

Step 5 In the Log File Settings portion, enter the following settings. These settings will be effective after restarting WCS.

Max. file size—Maximum number of MBs allowed per log file.

Number of files—Maximum number of log files allowed.

File prefix—Log file prefix, which can include the characters "%g" to sequentially number of files.

Step 6 Click the Download button to download the Log File to your local machine.


Note The logs.zip filename includes a prefix with the host name, date, and time so that you can easily identify the stored log file. Included in the zip file is an html file that documents the log files.


Step 7 Enter the Email ID or Email IDs seperated by commas to send the Log file.


Note To send the log file in a mail you must have Email Server Configured.


Step 8 Click Submit.


SNMP Logging Options

To enable SNMP Tracing, follow these steps. The settings you establish are stored and are used by the SNMP server.


Note SNMP server is nothing but the WCS server which uses these settings for SNMP logging.



Step 1 Choose Administration > Logging. The General Logging Options page appears (see Figure 16-20).

Step 2 Choose SNMP Logging Options from the left sidebar menu.

Figure 16-20 SNMP Logging Options

Step 3 Select the Enable SNMP Trace check box to enable sending SNMP messages (along with traps) between controller and WCS.

Step 4 Select the Display Values check box to see the SNMP Message values.

Step 5 Configure the IP address or IP addresses to trace the SNMP traps. You can add up to a maximum of 10 IP addresses in the text box.

Step 6 You can configure the maximum SNMP file size and the number of SNMP files.


Syslog Options

The Syslog protocol is simply designed to transport event messages from the generating device to the collector. Various devices generate syslog messages for system information and alerts. To configure Syslog for WCS, follow these steps:


Step 1 Choose Administration > Logging. The General Logging Options page appears (see Figure 16-19).

Step 2 From the left sidebar menu, choose the Syslog Options.

Figure 16-21 Syslog Logging Options Page

Step 3 Select the Enable Syslog check box to enable collecting and processing system logs.

Step 4 Configure the Syslog Server IP address of the interface from which the message is to be transmitted.

Step 5 Choose the Syslog Facility. You can choose any of the eight local use facilities for sending syslog messages. The local use facilities are not reserved and are available for general use.


Using Logging Options to Enhance Troubleshooting

The logging screen allows you to customize the amount of data WCS collects to debug an issue. For easily reproduced issues, follow these steps prior to contacting TAC. To create a smoother troubleshooting session, follow these steps:


Step 1 Choose Administration > Logging.

Step 2 From the Message Level drop-down list, choose Trace.

Step 3 Select each check box to enable all log modules.

Step 4 Reproduce the current problem.

Step 5 Return to the Logging Options page.

Step 6 Click Download from the Download Log File section.


Note The logs.zip filename includes a prefix with the host name, date, and time so that you can easily identify the stored log file. Included in the zip file is an html file that documents the log files.


Step 7 After you have retrieved the logs, choose Information from the Message Level drop-down list.


Note Leaving the Message Level at Trace can adversely affect performance over a long period of time.



Configuring Administrative Settings

The Settings page contains options for managing the WCS data retention functions. This section describes the available settings and contains the following topics:

Configuring Alarms

Configuring an Audit

Configuring Clients

Configuring Protocols for CLI Sessions

Configuring Controller Upgrade

Configuring Data Management

Configuring a Guest Account

Configuring Login Disclaimer

Configuring the Mail Server

Configuring the Notification Receiver

Setting Report

Configuring Server Settings

Severity Configurations

SNMP Credentials

SNMP Settings

Switch Port Tracing

Configuring Alarms

This Alarms page enables you to handle old alarms and display assigned and acknowledged alarms in the Alarm Summary page.

To open this page, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Alarms. The Administration > Settings > Alarms page appears (see Figure 16-22).

Figure 16-22 Settings > Alarms Page

Step 3 Add or modify the following Alarms parameters:

Alarm Cleanup Options

Delete active and cleared alarms after—Enter the number of days after which active and cleared alarms are deleted. This option can be disabled by unselecting the check box.

Delete cleared security alarms after—Enter the number of days after which Security, Rogue AP, and Adhoc Rogue alarms are deleted.

Delete cleared non-security alarms after—Enter the number of days after which non-security alarms are deleted. Non-security alarms include all alarms that do not fall under the Security, Rogue AP, or Adhoc Rogue categories.


Note Data cleanup tasks run nightly to delete old alarms. In addition to the data cleanup task, WCS has an hourly task to check alarm table size. When the alarm table size exceeds 300 K, the task deletes the oldest cleared alarms until the alarm table size is within 300 K.



Note If you want to keep the cleared alarms for more than 7 days, then you can specify a value more than 7 days in the Delete cleared non-security alarms after text box until the alarm table size reaches 300 K.


Alarm Display Options


Note These preferences only apply to the Alarm Summary page. Quick searches or alarms for any entity display all alarms regardless of the acknowledged or assigned state.


Hide acknowledged alarms—When the check box is selected, Acknowledged alarms do not appear in the Alarm Summary page. This option is enabled by default.


Note E-mails are not generated for acknowledged alarms regardless of severity change.


Hide assigned alarms—When the check box is selected, assigned alarms do not appear in the Alarm Summary page.

Add controller name to alarm messages—Select the check box to add the name of the controller to alarm messages.

Add WCS address to email notifications—Select the check box to add the WCS address to email notifications.

Alarm Email Options

Include alarm severity in the email subject line—Select the check box to include alarm severity in the email subject line.

Include alarm Category in the email subject line—Select the check box to include alarm category in the email subject line.

Include prior alarm severity in the email subject line—Select the check box to include prior alarm severity in the email subject line.

Include custom text in the email subject line—Select the check box to add custom text in the email subject line. You can also replace the email subject line with custom text by selecting the Replace the email subject line with custom text check box.

Include custom text in body of email—Select the check box to add custom text in the body of email.

Include alarm condition in body of email—Select the check box to include alarm condition in the body of email.

Add link to Alarm detail page in body of email—Select the check box to add a link to the Alarm detail page in the body of email.

Enable Secure Message Mode—Select the check box to enable a secure message mode. If you select the Mask IP Address and Mask Controller Name check boxes, the alarm emails are sent in secure mode where all the IP addresses and controller names are masked.

Step 4 Click Save.


Configuring an Audit

The Settings > Audit page allows you to determine the type of audit and on which parameters the audit is performed.

Audit Mode—Choose between basic auditing and template based auditing.

Audit On—Choose to audit on all parameters or on selected parameters for a global audit.

Audit Mode

The audit mode section allows you to choose between basic auditing and template based auditing. Basic audit is selected by default.

Basic Audit—Audits the configuration objects in the WCS database against current WLC device values. Prior to the 5.1.0.0 version of WCS, this was the only audit mode available.


Note Configuration objects refer to the device configuration stored in the WCS database.


Template-based Audit—Audits on the applied templates, config group templates (which have been selected for the background audit), and configuration audits (for which corresponding templates do not exist) against current WLC device values.

To indicate the type of audit you want to perform, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Audit. The Audit page appears (see Figure 16-23).

Figure 16-23 Audit Page

Step 3 Select the Basic Audit or Template based Audit radio button. A basic audit audits the device configuration in the WCS database against the current WLC configuration. A template-based audit audits the applied templates, config group templates, and configuration objects (for which corresponding templates do not exist) against current WLC configuration.

Step 4 Choose if you want the audit to run on all parameters or only on selected parameters. If you select the Selected Parameters radio button, you can access the Configure Audit Parameters configuration page. (See the "Configuring Audit Parameters" section). The Select audit parameters URL appears.

The selected audit parameters are used during network and controller audits.

Step 5 Click Save.


Note These settings are in effect when the controller audit or network audit is performed.



Audit On

The Audit On option allows you to audit all parameters or to select specific parameters for an audit. When the Selected Parameters radio button is selected, you can access the Select Audit Parameters configuration page.

The selected audit parameters are used during network and controller audits.

Configuring Audit Parameters

To configure the audit parameters for a global audit, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Audit.

Step 3 Select the Selected Parameters radio button to display the Select Audit Parameters link.

Step 4 Click Save.

Step 5 Click Select Audit Parameters to choose the required parameters for the audit in the Audit Configuration > Parameter Selection page.

Step 6 Select the parameters that you want audited from each of the tabs. The tabs include System, WLAN, Security, Wireless, and Selected Attributes.

Step 7 When all desired audit parameters are selected, click Submit to confirm the parameters or click Cancel to close the page without saving any audit parameters.

Once you click Submit, the selected audit parameters display under the Selected Attributes tab.

A current Controller Audit Report can be accessed from the Configure > Controllers page by selecting an object from the Audit Status column.


Note You can audit a controller by choosing Audit Now from the Select a command drop-down list in the Configure > Controllers page, or by clicking Audit Now directly from the Controller Audit report. See the "Viewing Audit Status (for Access Points)" section.



Configuring Clients

The client processes are configurable to improve WCS performance and scalability. This section contains the following topics:

Processing Diagnostic Trap

Host Name Lookup

Data Retention

Client Traps

To confirm changes to these client configurations, click Save at the bottom of the page.


Note See the "Client Troubleshooting" section for further information on client troubleshooting.


Processing Diagnostic Trap

The Settings > Client page allows you to enable automatic client troubleshooting on a diagnostic channel.


Note Automatic client troubleshooting is only available for a CCXV5 client.


To enable this automatic client troubleshooting, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Client. The Client page appears (see Figure 16-24).

Figure 16-24 Administration > Settings > Client Page

Step 3 Select the Automatically troubleshoot client on diagnostic channel check box.


Note If the check box is selected, WCS processes the diagnostic association trap. If it is not selected, WCS raises the trap, but automated troubleshooting is not initiated.



Note While processing the diagnostic association trap, the WCS invokes a series of tests on the client. The client is updated on all completed tasks. The automated troubleshooting report is placed in dist/acs/win/webnms/logs. When the test is complete, the location of the log is updated in client details pages:V5 tab:Automated Troubleshooting Report section. An export button allows you to export the logs.


Step 4 Click Save.


Host Name Lookup

DNS lookup can take a considerable amount of time. Because of this, you can enable or disable the DNS lookup for client host name. It is set to Disable by default.

To enable host name lookup, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Client.

Step 3 Select the Lookup client host names from DNS server check box.

Step 4 Enter the number of days that you want the host name to remain in the cache.

Step 5 Click Save.


Data Retention

Client association history can take a lot of database and disk space. This can be an issue for database backup and restore functions. The retaining duration of a client association history can be configured to help manage this potential issue.

To configure data retention parameters, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Client.

Step 3 Enter or edit the following data retention parameters:

Client (days)—Enter the number of days that you want WCS to retain the data. The default is 7 days. The valid range is 1 to 30 days.

Client (records)—Enter the number of client records that you want WCS to retain.

Client session history (days)—The default is 31 days. The maximum is 365 days.

Client session history (records)—The default (and maximum recommended) is 1 million records.

Step 4 Click Save.


Client Traps

In some deployments, WCS may receive large amounts of client association and disassociation traps. Saving these traps as events may cause a slight performance issue. In such cases, other events that may be useful may be aged out sooner than expected.

To ensure that WCS does not save client association and disassociation traps as events, unselect the Save client association and disassociation traps as events check box. Click Save to confirm this configuration change. This option is disabled by default.

If you select the Poll clients when client traps received check box, WCS polls clients to quickly identify client sessions. In a busy network, you may want to disable polling while the client traps are received.

Configuring Protocols for CLI Sessions

Many WCS features such as autonomous access point and controller CLI templates, along with migration templates require executing CLI commands on the autonomous access point or controller. These CLI commands can be executed by establishing telnet or SSH sessions. The CLI session page allows you to select the session protocol. SSH is the default.


Note In CLI templates, you are not required to answer the question responses (such as Yes or No answer to a command, Press enter to continue, and so on). This is automatically performed by WCS.


To configure the protocols for CLI sessions, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose CLI Session.

Step 3 The default controller session protocol SSH is selected. To choose Telnet, select that radio button.

Step 4 The default autonomous access point session protocol SSH is selected. To choose Telnet, select the radio button.

Step 5 Click Save.


Configuring Controller Upgrade

The Controller Upgrade Settings page allows you to auto-refresh after a controller upgrade. To perform an auto-refresh, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Controller Upgrade Settings (see Figure 16-25).

Figure 16-25 Controller Upgrade Settings

Step 3 Select the Auto refresh After Upgrade check box to automatically restore the configuration whenever there is a change in the WLC image.

Step 4 Determine the action WCS will take when a save config trap is received. When this option is enabled, you can choose to retain or delete the extra configurations present on the device but not on WCS. The setting is applied to all controllers managed by WCS.


Note If you select the Auto Refresh on Save Config Trap check box in the Configure > Controllers > Properties > Settings page, it overrides this global setting.



Note It may take up to three minutes for the automatic refresh to occur.


Step 5 Click Save.

Whenever a save config trap is received by WCS this option when enabled will determine the action taken by WCS.

When this option is enabled user can choose to retain or delete the extra configurations present on device and not on WCS.

This setting will be applied to all of the controllers managed by WCS. The setting in the controller > properties page for processing the save config trap will override this global setting.

When there is a change in the WLC image, the configuration from the controller is automatically restored.


Configuring Data Management

To set retention periods for aggregated data used in timed calculations and network audit calculations, follow these steps. You can configure retention periods on an hourly, daily, and weekly basis.


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Data Management. The Data Management page appears (see Figure 16-26).

Figure 16-26 Data Management Page

Step 3 Specify the number of days to keep the hourly data. The valid range is 1 to 31. The default is 31 days.

Step 4 Specify the number of days to keep the daily data. The valid range is 7 to 365. The default is 90 days.

Step 5 Specify the number of weeks to keep the weekly data. The valid range is 2 to 108. The default is 54 weeks.

Step 6 Specify the number of days to retain the audit data collected by the Network Audit background task before purging. The limit is 365 days, and the minimum cleanup interval is 7 days. The default is 90 days.


Note For the best interactive graph data views, change the default settings to the maximum possible: 90 days for daily aggregated data and 54 weeks for weekly aggregated data. You must also make the appropriate measures to increase RAM and CPU capacity to compensate for these adjustments.


Step 7 Click Save.


WCS Historical Data

There are two types of historical data in WCS:

Aggregated historical data—Numeric data that can be gathered as a whole and aggregated to minimum, maximum, or average. Client count is one example of aggregated historical data.

Use the Administration > Settings > Data Management page to define the aggregated data retention period. Aggregation types include hourly, daily, and weekly.

The retention period for these aggregation types are defined as Default, Minimum, and Maximum (see Table 16-5).

Table 16-5 Aggregated Data Retention Periods

Aggregated Data
Default
Minimum
Maximum

Hourly

31 days

1 day

31 days

Daily

90 days

7 days

365 days

Weekly

54 weeks

2 weeks

108 weeks


Non-aggregated historical data—Numeric data that cannot be gathered as a whole (or aggregated). Client association history is one example of non-aggregated historical data.

You can define a non-aggregated retention period in each data collection task and other settings.

For example, you define the retention period for client association history in Administration > Settings > Client. By default, the retention period is 31 days or 1 million records. This retention period can be increased to 365 days.

Configuring a Guest Account

The Guest Account Settings page allows you to globally remove all expired templates. To configure guest account settings, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Guest Account Settings (see Figure 16-27).

Figure 16-27 Guest Account Settings Page

Step 3 When the Automatically remove expired guest accounts option is selected, the guest accounts whose lifetime has ended are not retained, and they are moved to the Expired state. Those accounts in the expired state are deleted from WCS.

Step 4 By default, WCS Lobby Ambassador can access all guest accounts irrespective of who created them. If you select the Search and List only guest accounts created by this lobby ambassador check box, the Lobby Ambassadors can access only the guest accounts that have been created by them.

Step 5 Click Save.


Configuring Login Disclaimer

The Login Disclaimer page allows you to enter disclaimer text at the top of the Login page for all users.

To enter Login Disclaimer text, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Login Disclaimer. The Login Disclaimer page appears (see Figure 16-28).

Figure 16-28 Login Disclaimer Page

Step 3 Enter your Login Disclaimer text in the available text box.

Step 4 Click Save.


Configuring the Mail Server

You can configure global e-mail parameters for sending e-mails from WCS reports, alarm notifications, and so on. This mail server page enables you to configure e-mail parameters in one place. The Mail Server page enables you to set the primary and secondary SMTP server host and port, the sender's e-mail address, and the recipient's e-mail addresses. To configure global e-mail parameters, follow these steps.


Note You must configure the global SMTP server before setting global e-mail parameters.



Step 1 Choose Administration > Setting.

Step 2 From the left sidebar menu, choose Mail Server Configuration. The page in Figure 16-29 appears.

Figure 16-29 Mail Server Configuration Page

Step 3 Enter the host name of the primary SMTP server.

Step 4 Enter the username of the SMTP server.

Step 5 Provide a password for logging on to the SMTP server and confirm it.


Note Both Username and Password are optional.


Step 6 Provide the same information for the secondary SMTP server (only if a secondary mail server is available).

Step 7 The From text box in the Sender and Receivers portion of the page is populated with WCS@<WCS server IP address>. You can change it to a different sender.

Step 8 Enter the recipient's e-mail addresses in the To text box. The e-mail address you provide serves as the default value for other functional areas, such as alarms or reports. Multiple e-mail addresses can be added and should be separated by commas.


Note Global changes you make to the recipient e-mail addresses in Step 7 are disregarded if e-mail notifications were set.


You must indicate the primary SMTP mail server and fill the From address text boxes.

If you want all alarm categories applied to the provided recipient list, select the Apply recipient list to all alarm categories check box.

Step 9 Enter the text that you want to append to the email subject.

Step 10 If you click the Configure email notification for individual alarm categories link, you can specify the alarm categories and severity levels you want to enable. Email notifications are sent when an alarm occurs that matches categories and the severity levels you select.


Note You can set each alarm severity by clicking the alarm category, choosing Critical, Major, Minor, or Warning, and providing an email address.


Step 11 Click the Test button to send a test e-mail using the parameters you configured. The results of the test operation appear on the same screen. The test feature checks the connectivity to both primary and secondary mail servers by sending an e-mail with a "WCS test e-mail" subject line.

If the test results were satisfactory, click Save.


Configuring the Notification Receiver

The Notification Receiver page displays current notification receivers that support guest access. Alerts and events are sent as SNMPv2 notifications to configured notification receivers.

In this page, you can view current or add additional notification receivers.

This section contains the following topics:

Adding a Notification Receiver to WCS

Removing a Notification Receiver

To access the Notification Receiver page, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Notification Receivers. All currently configured servers appear in this page. If you want to add one, choose Add Notification Receiver from the Select a command drop-down list, and click Go (see Figure 16-30).

Figure 16-30 Notification Receiver Page


Adding a Notification Receiver to WCS

To view current or add additional notification receivers, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Notification Receivers. All currently configured servers appear on this page.

Step 3 From the Select a command drop-down list, choose Add Notification Receiver.

Step 4 Click Go (see Figure 16-31).

Figure 16-31 Notification Receiver Page

Step 5 Enter the server IP address and name.

Step 6 Select either the North Bound or Guest Access radio button.

Step 7 Choose the notification type as UDP or TCP. The default is UDP.

Step 8 Enter the UDP parameters including Port Number and Community.


Note The receiver that you configure should be listening to UDP on the same port that is configured.


Step 9 If you selected North Bound as the receiver type, specify the criteria and severity.


Note Alarms for only the selected category will be processed.



Note Alarms with only selected severity matching the selected categories will be processed.


Step 10 Click Save to confirm the Notification Receiver information.


NoteBy default, only INFO level events will be processed for the selected Category.

Only SNMPV2 traps will be considered for northbound notification.

You need to allow TCP port 7 which is required for keepalive between WCS and the receiver server.


Removing a Notification Receiver

To delete a notification receiver, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Notification Receivers. All currently configured servers appear on this page.

Step 3 Select the check box(es) of the notification receiver(s) that you want to delete.

Step 4 From the Select a command drop-down list, click Remove Notification Receiver.

Step 5 Click Go.

Step 6 Click OK to confirm the deletion.

The following is the sample display from a northbound SNMP receiver that has received event traps from WCS.

Figure 16-32 Sample Display from a Northbound SNMP Receiver

The sample output below shows the log file generated by WCS. This log file is located in the log file directory on the WCS server (/opt/WCS7.0.28.0/webnms/logs). The log output helps you troubleshoot when alarms are not being received by the northbound SNMP receiver.

06/04/10 08:30:58.559 INFO[com.cisco.wcslogger.services] : 
[NBNotificationService$NbOrderQueue][addNbAlarm]Adding into queue
06/04/10 08:30:58.560 INFO[com.cisco.wcslogger.services] : 
[NBNotificationService$NbOrderQueue][addNbAlarm]incrTotalNotifications2
06/04/10 08:30:58.560 INFO[com.cisco.wcslogger.services] : 
[NBNotificationService$NbOrderQueue][addNbAlarm]incrHandledInNotification2
06/04/10 08:30:58.560 INFO[com.cisco.wcslogger.services] : 
[NBNotificationService$NbOrderQueue][addNbAlarm]incrNonCongestedIn2
06/04/10 08:30:58.560 INFO[com.cisco.wcslogger.services] : 
[NBNotificationService][addNBAlert]Added into queue
06/04/10 08:30:58.561 INFO[com.cisco.wcslogger.services] : 
[NBNotificationService$NbOrderQueue][getNbAlarm]incrHandledOutNotification2
06/04/10 08:30:58.561 INFO[com.cisco.wcslogger.services] : 
[NBNotificationService][startNotifier]Processing the 
alertNoiseProfile_LradIf!00:17:df:a9:c8:30!0
06/04/10 08:30:58.561 INFO[com.cisco.wcslogger.notification] : 
[NbAlertToNmsAlertCorrelator][formVarBindList]Generating the varbind list for NB
06/04/10 08:30:58.562 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.2.1.1.3.0 variable value: 10 days, 20:22:17.26
06/04/10 08:30:58.562 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.6.3.1.1.4.1.0 variable value: 
1.3.6.1.4.1.9.9.199991.0.1
06/04/10 08:30:58.562 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.2 variable value: 
07:da:05:18:0c:30:0d:09:2d:07:00
06/04/10 08:30:58.563 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.3 variable value: 
07:da:06:04:08:1e:3a:04:2d:07:00
06/04/10 08:30:58.563 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.4 variable value: 
NoiseProfile_LradIf!00:17:df:a9:c8:30!0
06/04/10 08:30:58.563 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.5 variable value: 2
06/04/10 08:30:58.563 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.6 variable value: Radio 
load threshold violation
06/04/10 08:30:58.563 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.7 variable value: 1
06/04/10 08:30:58.564 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.8 variable value: 
172.19.29.112
06/04/10 08:30:58.564 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.9 variable value: AP 
1250-LWAP-ANGN-170-CMR, Interface 802.11b/g/n
06/04/10 08:30:58.564 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.10 variable value: 
Noise changed to acceptable level on '802.11b/g/n' interface of AP 
'1250-LWAP-ANGN-170-CMR', connected to Controller '172.19.29.112'. 
06/04/10 08:30:58.564 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.11 variable value: 1
06/04/10 08:30:58.564 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.12 variable value: 
06/04/10 08:30:58.565 INFO[com.cisco.wcslogger.notification] : 
[NBUtil][printVarBind]Variable OID: 1.3.6.1.4.1.9.9.199991.1.1.2.1.14 variable value: 
06/04/10 08:30:58.573 INFO[com.cisco.wcslogger.notification] : [NBUtil][sendTrap]OSS list 
size with reachability status as up1
06/04/10 08:30:58.573 INFO[com.cisco.wcslogger.notification] : [NBUtil][sendTrap]Sending 
UDP Notification for receiver:172.19.27.85 on port:162

MIB to WCS alert/event mapping

Table 16-6 summarizes the Cisco-WCS-Notification-MIB to WCS alert/event mapping.

Table 16-6 Cisco-WCS-Notification-MIB to WCS Alert/Event Mapping 

Field Name and Object ID
Data Type
WCS Event/Alert field
Description

cWcsNotificationTimestamp

DateAndTime

createTime - NmsAlert

eventTime - NmsEvent

Creation time for alarm/event.

cWcsNotificationUpdatedTimestamp

DateAndTime

modTime - NmsAlert

Modification time for Alarm.

Events do not have modification time.

cWNotificationKey

SnmpAdminString

objectId - NmsEvent

entityString- NmsAlert

Unique alarm/event ID in string form.

cWcsNotificationSubCategory

OCTET STRING

Type field in alert and eventType in event.

This object represents the

subcategory of the alert.

cWcsNotificationServerAddress

InetAddress

N/A

WCS IP address.

cWcsNotificationManagedObjectAddressType

InetAddressType

N/A

The type of Internet address by which the managed object is reachable. Possible values:

0 - unknown

1 - IPv4

2 - IPv6

3 - IPv4z

4 - IPv6z

16 - DNS

Always set to "1" because WCS only supports ipv4 addresses.

cWcsNotificationManagedObjectAddress

InetAddress

getNode() value is used if present

getNode is populated for events and some alerts. If it is not null, then it will be used for this field.

cWcsNotificationSourceDisplayName

OCTET STRING

sourceDisplayName field in alert/event.

This object represents the display name of the source of the notification.

cWcsNotificationDescription

OCTET STRING

Text - NmsEvent

Message - NmsAlert

Alarm description string.

cWcsNotificationSeverity

INTEGER

severity - NmsEvent, NmsAlert

Severity of the alert/event

critical(1),

major(2),

minor(3),

warning(4),

clear(5),

info(6),

unknown(7).

cWcsNotificationSpecialAttributes

OCTET STRING

All the attributes in alerts/events apart from the base alert/event class.

This object represents the specialized attributes in alerts like APAssociated, APDisassociated, RogueAPAlert, CoverageHoleAlert, and so on. The string is formatted in `property=value' pairs in CSV format.

cWNotificationVirtualDomains

OCTET STRING

N/A

Virtual Domain of the object that caused the alarm. This field is not populated for running release and this will be populated with empty string.


Setting Report

To indicate where the scheduled reports will reside and for how many days, follow these steps :


Step 1 Choose Administration > Setting.

Step 2 From the left sidebar menu, choose Report. The Report page appears (see Figure 16-33).

Figure 16-33 Report Page

Step 3 Enter the path for saving report data files on a local PC. You can edit the existing default path.

Step 4 Specify the number of days to retain report data files.

Step 5 Click Save.


Configuring Server Settings

To turn TFTP, FTP, HTTP, or HTTPS on or off, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Server Settings. The Server Settings page appears (see Figure 16-34).

Figure 16-34 Server Settings Page

Step 3 If you want to modify the FTP and TFTP directories or the HTTP and HTTPS ports that were established during installation, enter the port number (or port number and root where required) that you want to modify and click Enable or Disable.

The changes are reflected after a restart.


Severity Configurations

You can change the severity level for newly generated alarms.


Note Existing alarms remain unchanged.


To change the severity level of newly generated alarms, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 Choose Severity Configuration from the left sidebar menu. The Severity Configuration page appears (see Figure 16-35).

Figure 16-35 Severity Configuration Page

Step 3 Select the check box of the alarm condition whose severity level you want to change.

Step 4 From the Configure Severity Level drop-down list, choose the new severity level (Critical, Major, Minor, Warning, Informational, or Reset to Default).

Step 5 Click Go.

Step 6 Click OK to confirm the change.


SNMP Credentials

The SNMP Credentials page allows you to specify credentials to use for tracing the rogue access points. Use this option when you cannot find a specific entry using a number-based entry. When a switch credential is not added to WCS, you can use SNMP credentials on this page to connect to the switch.

To configure SNMP credentials, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose SNMP Credentials. The SNMP Credential Details page appears (see Figure 16-36).

Step 3 To view or edit details about a current SNMP entry, click the Network Address link. See the "Viewing Current SNMP Credential Details" section for more information.


Note The default network address is 0.0.0.0 which indicates the entire network. An SNMP credential is defined per network so only network addresses are allowed. 0.0.0.0 is the SNMP credential default and is used when no specific SNMP credential is defined. The default community string is private for both read and write. You should update the pre-populated SNMP credential with your own SNMP information.


Figure 16-36 SNMP Credential Details Page

Step 4 To add a new SNMP entry, select Add SNMP Entries from the Select a command drop-down list and click Go. See the "Adding a New SNMP Credential Entry" section for more information.


Viewing Current SNMP Credential Details

To view or edit details for current SNMP credentials, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose SNMP Credentials.

Step 3 Click the Network Address link to open the SNMP Credential Details page. The details page displays the following information.

General Parameters

Add Format Type—Read-only. See the "Adding a New SNMP Credential Entry" section for more information regarding Add Format Type.

Network Address

Network Mask

SNMP Parameters—Select the applicable version(s) for SNMP parameters. The SNMP credentials are validated according to which SNMP version(s) are selected.


Note Enter SNMP parameters for write access, if available. With read-only access parameters, the switch is added but you will not be able to modify its configuration in WCS. Device connectivity tests use the SNMP retries and timeout parameters configured in Administration > Settings > SNMP Settings.


Retries—The number of times that attempts are made to discover the switch.

Timeout—The session timeout value in seconds. This determines the maximum amount of time allowed for a client before it is forced to reauthenticate.

SNMP v1 Parameters or v2 Parameters—If selected, enter the applicable community in the available text box.

SNMP v3 Parameters—If selected, configure the following parameters:

Username

Auth. Type

Auth. Password

Privacy Type

Privacy Password


Note If SNMP v1 or v2 with default community is configured, the network is open to easy attacks because default communities are well known. SNMP v1 or v2 with a non-default community is more secure than a default community, but SNMP v3 with Auth and Privacy type and no default user is the most secure SNMP connection.


Step 4 Click OK to save changes or Cancel to return to the SNMP Credential page without making any changes to the SNMP credential details.


Adding a New SNMP Credential Entry

To add a new SNMP credential entry, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose SNMP Credentials.

Step 3 From the Select a command drop-down list, choose Add SNMP Entries.

Step 4 Click Go. The SNMP Credential Details page opens (see Figure 16-36).

Step 5 Choose one of the following:

To manually enter SNMP credential information, leave the Add Format Type drop-down list at SNMP Credential Info. To add multiple network addresses, use a comma between each address. Go to Step 7.

If you want to add multiple switches by importing a CSV file, choose File from the Add Format Type drop-down list. The CSV file allows you to generate your own import file and add the devices you want. Go to Step 6.

Step 6 If you chose File, click Browse to find the location of the CSV file you want to import. Skip to Step 11.

The first row of the CSV file is used to describe the columns included. The IP Address column is mandatory.

Sample File:

ip_address,snmp_version,snmp_community,snmpv3_user_name,snmpv3_auth_type,snmpv3_auth_passw
ord,snmpv3_privacy_type,snmpv3_privacy_password,network_mask  
1.1.1.0,v2,private,user1,HMAC-MD5,12345,DES,12345,255.255.255.0  
2.2.2.0,v2,private,user1,HMAC-MD5,password3,DES,password4,255.255.255.0  
10.77.246.0,v2,private,user1,HMAC-MD5,12345,DES,12345,255.255.255.0 

The CSV file can contain the following fields:

ip_address:IP address

snmp_version:SNMP version

network_mask:Network mask

snmp_community:SNMP V1/V2 community

snmpv3_user_name:SNMP V3 username

snmpv3_auth_type:SNMP V3 authorization type. Can be None or HMAC-MD5 or HMAC-SHA

snmpv3_auth_password:SNMP V3 authorization password

snmpv3_privacy_type:SNMP V3 privacy type. Can be None or DES or CFB-AES-128

snmpv3_privacy_password:SNMP V3 privacy password

snmp_retries:SNMP retries

snmp_timeout:SNMP timeout

Step 7 If you chose SNMP Credential Info, enter the IP address of the switch you want to add. If you want to add multiple switches, use a comma between the string of IP addresses.

Step 8 In the Retries parameter, enter the number of times that attempts are made to discover the switch.

Step 9 Provide the session timeout value in seconds. This determines the maximum amount of time allowed for a client before it is forced to reauthenticate.

Step 10 Select the applicable version(s) for SNMP parameters. The SNMP credentials are validated according to which SNMP version(s) are selected.

If SNMP v1 Parameters or v2 Parameters is selected, enter the applicable community in the available text box.

If SNMP v3 Parameters is selected, configure the following parameters:

Username

Auth. Type

Auth. Password

Privacy Type

Privacy Password


Note If SNMP v1 or v2 with default community is configured, the network is open to easy attacks because default communities are well known. SNMP v1 or v2 with a non-default community is more secure than a default community, but SNMP v3 with Auth and Privacy type and no default user is the most secure SNMP connection.


Step 11 Click OK.

If WCS can use the SNMP credential listed to access the switch, the switch is added for later use and will appear on the Configure > Ethernet Switches page.


Note If you manually added switches through the Configure > Ethernet Switches page, then switch port tracing will use the credentials from that page, not the ones listed on the SNMP Credentials page. If the manually-added switch credentials have changed, you need to update them from the Configure > Ethernet page.



SNMP Settings

The SNMP Settings page allows you to configure global SNMP settings from WCS.


Note Any changes you make on this screen globally effect WCS. The changes are saved across restarts as well as across backups and restores.


To configure global SNMP settings, follow these steps t:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose SNMP Settings. The SNMP Settings page appears (see Figure 16-37).

Figure 16-37 SNMP Settings Page

Step 3 If Trace Display Values is selected, mediation trace-level logging shows data values fetched from the controller using SNMP. If unselected, the values do not appear.


Note The default is unselected for security reasons.


Step 4 For the Backoff Algorithm, choose either Exponential or Constant Timeout from the drop-down list. If you choose Exponential (the default value), each SNMP try waits twice as long as the previous try, starting with the specified timeout for the first try. If you choose Constant Timeout, each SNMP try waits the same, specified amount of time.


Note Constant Timeout is useful on unreliable networks (such as satellite networks) where the desired number of retries is large. Because it does not double the timeout per try, it does not take as long to timeout with a high number of retries.


Step 5 Determine if you want to use reachability parameters. If selected, the WCS defaults to the global Reachability Retries and Timeout that you configure. If unselected, WCS always uses the timeout and retries specified per-controller or per-IOS access point. The default is selected.


Note Adjust this setting downward if switch port tracing is taking a long time to complete.


Step 6 For the Reachability Retries parameter, enter the number of global retries used for determining device reachability. The default number is 2. This parameter is only available if the Use Reachability Parameters check box is selected.


Note Adjust this setting downward if switch port tracing is taking a long time to complete.


Step 7 For the Reachability Timeout parameter, enter a global timeout used for determining device reachability. The default number is 2. This parameter is only available if the Use Reachability Parameters check box is selected.

Step 8 At the Maximum VarBinds per PDU parameter, enter a number to indicate the largest number of SNMP variable bindings allowed in a request or response PDU. The default is 100.


Note For customers who have issues with PDU fragmentation in their network, this number can be reduced to 50, which typically eliminates the fragmentation.


Step 9 The maximum rows per table parameter is configurable and the default value is 50000 rows. The configured value is retained even if you upgrade the WCS version.

Step 10 Click Save to confirm these settings.


Switch Port Tracing

Currently, WCS provides rogue access point detection by retrieving information from the controller. The rogue access point table is populated with any detected BSSID addresses from any frames that are not present in the neighbor list. At the end of a specified interval, the contents of the rogue table are sent to the controller in a CAPWAP Rogue AP Report message. With this method, WCS would simply gather the information received from the controllers; but with software release 5.1, you can now incorporate switch port tracing of Wired Rogue Access Point Switch Ports. This enhancement allows you to react to found wired rogue access points and prevent future attacks. The trace information is available only in the WCS log and only for rogue access points, not rogue clients.


Note Rogue Client connected to the Rogue Access point information is used to track the switch port to which the Rogue Access point is connected in the network.



Note If you try to set tracing for a friendly or deleted rogue, a warning message appears.



Note For Switch Port Tracing to successfully trace the switch ports using and v3, all of the OIDs should be included in the SNMP v3 view and VLAN content should be created for each VLAN in the SNMP v3 group.



Note See the "Switch Port Tracing" section for information on configuring Switch Port Tracing settings.


The Switch Port Trace page allows you to run a trace on detected rogue access points on the wire.

To correctly trace and contain rogue access points, you must correctly provide the following information.

Reporting APs—A rogue access point has to be reported by one or more managed access points.

AP CDP Neighbor—Access point CDP neighbor information is required to determine the seed switches.

Switch IP address and SNMP credentials—All switches to be traced must have a management IP address and SNMP management enabled. You can add network address based entries instead of only adding individual switches. The correct write community string must be specified to enable/disable switch ports. For tracing, read community strings are sufficient.

Switch port configuration—Trunking switch ports must be correctly configured. Switch port security must be turned off.

Only Cisco Ethernet switches are supported.

Switch VLAN settings must be properly configured.

CDP protocol must be enabled on all switches.

An Ethernet connection must exist between the rogue access point and the Cisco switch.

You should have some traffic between rogue access points and the Ethernet switch.

The rogue access point must be connected to a switch within the max hop limit. The default hop count is 2, and the maximum is 10.

If SNMPv3 is chosen, use the context option and create one for each VLAN, in addition to the one for the main group (which is required for non-VLAN-based MIBs).

To specify options for switch port tracing, follow these steps:


Step 1 Choose Administration > Settings.

Step 2 From the left sidebar menu, choose Switch Port Trace (see Figure 16-38).

Figure 16-38 Switch Port Trace Page

Step 3 Configure the following basic settings as needed:

MAC address +1/-1 search—Select the check box to enable.

This search involves the MAC address +1/-1 convention where the wired-side MAC address of the rogue access point is obtained by adding or subtracting the radio MAC address by one.

Rogue client MAC address search—Select the check box to enable.

When a rogue access point client exists, the MAC address of the client is added to the searchable MAC address list.

Vendor (OUI) search—Select the check box to enable. OUI refers to Organizational Unique Identifier search which searches the first 3 bytes in a MAC address.

Exclude switch trunk ports—Select the check box to exclude switch trunk ports from the switch port trace.


Note When more than one port is traced for a given MAC address, additional checks are performed to improve accuracy. These checks include: trunk port, non-AP CDP neighbors present on the port, and whether or not the MAC address is the only one on this port.


Exclude device list—Select the check box to exclude additional devices from the trace. Enter into the device list text box each device that you want to exclude from the switch port trace. Separate each device names with commas.

Max hop count—Enter the maximum number of hops for this trace. Keep in mind that the greater the hop count, the longer the switch port trace will take to perform.

Exclude vendor list—Enter in the vendor list text box any vendors that you want to exclude from the switch port trace. Separate vendor names with commas. The vendor list is not case sensitive.

Step 4 Configure the following advanced settings as needed:

TraceRogueAP task max thread—Switch port tracing uses multiple threads to trace rogue access points. This field indicates the maximum number of rogue access points that can be traced on parallel threads.

TraceRogueAP max queue size—Switch port tracing maintains a queue to trace rogue access points. Whenever you select a rogue access point for tracing, it is queued for processing. This field indicates the maximum number of entries that you can store in the queue.

SwitchTask max thread—Switch port tracing uses multiple threads to query switch devices. This field indicates the maximum number of switch devices that you can query on parallel threads.


Note The default value for these parameters should be good for normal operations. These parameters directly impact the performance of switch port tracing and WCS. Unless required, We do not recommend that you alter these parameters.


Select CDP device capabilities—Select the check box to enable.


Note WCS uses CDP to discover neighbors during tracing. When the neighbors are verified, WCS uses the CDP capabilities field to determine whether or not the neighbor device is a valid switch. If the neighbor device is not a valid switch, it is not traced.


Step 5 Click Save to confirm changes made. Click Reset to return the page to the original settings. Click Factory Reset to return settings to the factory defaults.


Establishing Switch Port Tracing

To establish switch port tracing, follow these steps:


Step 1 In the WCS home page, click the Security tab.

Step 2 In the Rogue APs and Adhoc Rogues section, click the number URL which specifies the number of rogues in the last hour, last 24 hours, or total active.

Step 3 Choose for which rogue you are setting switch port tracking by clicking the URL in the MAC Address column. The Alarms > Rogue AP details page opens.

Step 4 From the Select a command drop-down list, choose Trace Switch Port. The Trace Switch Port page opens and WCS runs a switch port trace.

When one or more searchable MAC addresses are available, the WCS uses CDP to discover any switches connected up to two hops away from the detecting access point. The MIBs of each CDP discovered switch is examined to see if it contains any of the target MAC addresses. If any of the MAC addresses are found, the corresponding port number is returned and reported as the rogue switch port.

The SNMP communities for the switches are provided in the "Configuring Ethernet Switches" section.

See the "Switch Port Tracing Details" section for additional information on the Switch Port Tracing Details dialog box.


Switch Port Tracing Details

In the Switch Port Tracing Details dialog box, you can enable or disable switch ports, trace switch ports, and view detail status of the access point switch trace. For more information on Switch Port Tracing, see the following topics:

Switch Port Tracing—Provides information on configuring switch port trace settings.

Configuring Ethernet Switches—Provides information on configuring SNMP switches.

SNMP Credentials—Provides information on configuring SNMP switch credentials.

In the Switch Port tracng Details dialog box, do one of the following:

Click Enable/Disable Switch Port(s)—Enables or disables any selected ports.

Click Trace Switch Port(s)—Runs another switch port trace.

Click Show Detail Status—Displays details regarding the switch port traces for this access point.

Click Close.

Switch Port Tracing Troubleshooting

Switch Port Tracing (SPT) works on a best-effort-basis. SPT depends on the following information to correctly trace and contain rogue APs:

Reporting access points—A rogue access point must be reported by one or more managed access points.

Access point CDP neighbor—Access point CDP neighbor information is required to determine the seed switches.

Switch IP address and SNMP credentials

All the switches that needs to be traced should have a management IP address and SNMP management enabled.

With the new SNMP credential changes, instead of adding the individual switches to WCS, network address based entries can be added.

The new SNMP credential feature will have a default entry 0.0.0.0 with default community string as 'private' for both read/write.

Correct write community string has to be specified to enable/disable switch ports. For tracing, read community string should be sufficient.

Switch port configuration

Switch ports that are trunking should be correctly configured as trunk ports.

Switch port security should be turned off.

Only Cisco Ethernet switches are supported.


Note The following switches are supported: 3750, 3560, 3750E, 3560E, and 2960.


Switch VLAN settings should be properly configured.

CDP protocol should be enabled all the switches.

An Ethernet connection should exist between the rogue access point and the Cisco switch.

There should be some traffic between the rogue access point and the Ethernet switch.

The rogue access point should be connected to a switch within the max hop limit. Default hop is 2. Max hop is 10.

If SNMPv3 is used, then make sure you use the context option and create one for each VLAN in addition to the one for the main group (which is required for non-VLAN based MIBs).

Configuring High Availability

This section contains the following topics:

Guidelines and Limitations for High Availability

Failover Scenario

High Availability Status

Configuring High Availability on Primary WCS

Deploying High Availability

Adding a New Primary WCS

Removing a Primary WCS

Guidelines and Limitations for High Availability

Before initiating failover, you must consider the following prerequisites and limitations:

You must have the extra hardware identical to the primary WCS to run a stand-by instance of WCS.

This design is based on the software-based WCS and does not accommodate appliance-based WCS.

The presence of Navigator is considered so that multi-WCS deployments are accommodated.

A reliable high-speed wired network must exist between the primary WCS and its backup WCS.

The primary and secondary WCS must be running the same WCS software release.

WCS supports both Windows- or Linux-based platforms. However, for this failover design, all WCSs in the primary-secondary group must run on the same operating system (either Windows or Linux).

Failover should be considered temporary. The failed primary WCS should be restored to normal as soon as possible, and failback will be re-initiated. The longer it takes to restore the failed primary WCS, the longer the other WCSs sharing that secondary WCS must run without failover support.

The latest controller software must be used.

The primary and secondary host are not required to share the same subnet. They can be geographically separated.

If a secondary host fails for any reason, all the primary instances are affected, and they run in stand-alone mode without any failover support.

The ports over which the primary and secondary WCSs communicate must be open (not blocked with network firewalls, application fireways, gateways, and so on). The tomcat port is configurable during installation, and its default port is 8082. You should reserve solid database ports from 1315 to 1319.

Any access control lists imposed between the primary and secondary WCS must allow traffic to go between the primary and secondary WCSs.

In a 2:1 high availability scenario, the secondary WCS must be a high-end PC with more memory than the two primary PCs.

Failover Scenario

When a failure of a primary WCS is automatically detected, the following events take place:


Note One physical secondary WCS can back many primary devices (WCS).


1. The primary WCS is confirmed as non-functioning (hardware crash, network crash, or the like) by the health monitor on the secondary WCS.

2. If automatic failover has been enabled, WCS is started on the secondary as described in Step 3. If automatic failover is disabled, an email is sent to the administrator asking if they want to manually start failover.

3. The secondary WCS instance is started immediately (using the configuration already in place) and uses the corresponding database of the primary. After a successful failover, the client should point to the newly activated WCS (the secondary WCS). The secondary WCS updates all controllers with its own address as the trap destination.


Note The redirecting of web traffic to the secondary WCS does not occur automatically. You must use your infrastructure tools to properly configure this redirection.


Location Servers that were served from the primary WCS are now served by the secondary WCS. Any Navigators in the network start monitoring the secondary WCS.

4. The result of the failover operation is indicated as an event in the Health Monitor UI, or a critical alarm is sent to the administrator and to other WCS instances.

High Availability Status

To view High Availability details, follow these steps:


Step 1 Choose Administration > High Availability.

Step 2 Choose HA Status from the left sidebar menu. The following information is displayed:

Current status

Time, state, and description of each event


Configuring High Availability on Primary WCS


Note When database transaction logs grow to 1/3 of the database partition disk space, set the database to "Standalone" mode to prevent transaction logs from keep growing. But it requires a complete netcopy next time when the database synchronization occurs.


Follow these steps to configure high availability on the primary WCS. You must specify the WCS role (either standalone, primary, or secondary) during installation. See the "Installing WCS for Windows" section to see the installation steps.


Note Before you configure high availability, you must configure a mail server. See the "Configuring the Mail Server" section for steps on configuring a mail server.



Step 1 Choose Administration > High Availability.

Step 2 Choose HA Configuration from the left sidebar menu. The High Availability Configuration page appears (see Figure 16-39).

Figure 16-39 High Availability Configuration Page

The current status of high availability is shown in the upper portion of the page.

Step 3 Enter the IP address or hostname of the secondary WCS.

Step 4 Enter the authentication key specified during the installation of the secondary WCS.

Step 5 The default admin email address that you configured in Administration > Settings > Email Server is automatically supplied. You can make any necessary changes. Any changes you make to these email addresses must also be entered in the Secondary SMTP Server section of the Administration > Settings > Mail Server page.


Note You must enter an email address when configuring high availability. WCS tests the email server configuration, and if the test fails (because the mail server cannot connect), WCS does not allow the high availability configuration.


Step 6 Choose either a manual or automatic failover option. If you choose manual, you can trigger the failover operation with a button in the secondary HealthMonitor GUI or with the URL specified in the email which the administrator receives upon failure of the primary WCS. If you choose automatic, the secondary WCS initiates a failover on its own when a failure is detected on the primary.

Step 7 Click Save Only to retain the configuration but not enable high availability at the current time, or click Save & Enable to enable high availability.


Note You can configure the high availability feature now but enable it at a later time.


At this point, the secondary is either reachable with the database, and files are synchronized between health monitors, or the secondary is unreachable, and an error is returned because secondary installation did not occur.

From the WCS GUI (Administration > High Availability) after high availability has been enabled, you can perform the following functions:

Update—Use the Update function to make changes to the Report Repository path (Administration > Settings > Report) or FTP/TFTP root directory (Administration > Settings > Server Settings) and to appropriately synchronize the files.

Disable—Use the Disable function to break the connection between the primary and secondary WCSs. The database and files stop synchronizing.

Delete—Use the Delete operation to decommission the primary WCS from the secondary WCS.

Cancel—Use the Cancel operation to cancel any modifications you made to the high availability configuration. You are returned to the High Availability Status page after you choose Cancel.


Deploying High Availability

To deploy high availability on an existing WCS installation, follow these steps:


Step 1 Identify and prepare the hardware to run the secondary WCS.

Step 2 Ensure that network connectivity between the primary and secondary WCS is functioning, and all necessary ports are open.

Step 3 Install the secondary WCS with the same version of WCS that is installed on the primary. See the "Installing WCS for Windows" section.

Step 4 Start the secondary WCS as a standby server. In this mode, the WCS application does not start. At the same time, the Health Monitor is started on the secondary WCS.

Step 5 On every primary WCS that needs to use this secondary WCS, stop the WCS.

Step 6 On the primary host, install the new version of WCS and perform all necessary upgrade steps.

Step 7 Start the primary WCS (as a primary). The Health Monitor also starts.

Step 8 Configure the high availability parameters described in the "Configuring High Availability on Primary WCS" section.

Step 9 Click Activate to activate high availability on the primary. WCS primary first copies its database to the secondary WCS and then connects to the secondary. The following files are copied over from the primary to the secondary WCS:

DB password file

all auto provisioning startup config files

all domain maps

all history reports which are generated by scheduled report tasks

High availability deployment is complete. Use https://<wcsip>:8082 to access the HealthMonitor UI. Within the HealthMonitor UI, use the authentication key to login.

You can change the authentication key in WCS using the command prompt. To change the authentication key, change the path to WCS installation directory then to "bin" and enter hmadmin - authkey key.

To view the current status of the health monitor, enter hmadmin [-options] status.


Adding a New Primary WCS

To add a new primary WCS to an existing setup, follow these steps. This new primary WCS uses the existing secondary as the failover server.


Step 1 Ensure that network connectivity between the new primary and secondary is functioning and that all necessary ports are open.

Step 2 Make sure that the same WCS release that is loaded on the other primary WCS and secondary WCS is loaded on the new primary WCS.

Step 3 Install the correct version of WCS on the primary WCS.

Step 4 Upgrade the primary WCS. The Health Monitor also starts.

Step 5 Follow the steps in the "Configuring High Availability" section.

Step 6 After the primary WCS connects to the secondary, the Health Monitor on the primary connects to the secondary Health Monitor. They mutually acknowledge each other and start the monitoring.

High availability deployment is now complete.


Removing a Primary WCS

When a primary WCS instance is removed from a group, you must disable the peer database instance on the secondary WCS and remove the Health Monitor for that primary. (To remove the primary WCS from high availability, use the Remove button on the High Availability configuration page.) The secondary WCS disables the database instance and removes the uninstalled primary WCS from its Health Monitor.

Setting User Preferences

This page contains user-specific settings you may want to adjust:


Step 1 Choose Administration > User Preferences. The User Preferences Page appears (see Figure 16-40).

Figure 16-40 User Preferences Page

Step 2 Use the Items Per List Page drop-down list to configure the number of entries shown on a given list page (such as alarms, events, AP list, and so on.).

Step 3 Specify how often you want the home page refreshed by clicking the Refresh home page check box and choosing a time interval from the Refresh home page every drop-down list.

Step 4 Select the Logout idle user check box and configure the Logout idle user after text box, in minutes, that a user session can be idle before the server cancels the session.

Step 5 If you want the maps and alarms page to automatically refresh when a new alarm is raised by WCS, select the Refresh Map/Alarms page on new alarm check box in the Alarms portion of the page.

Step 6 Use the Refresh Alarm count in the Alarm Summary every drop-down list to choose a time interval to specify how often to reset, use the drop-down list to choose a time interval.

Step 7 If you do not want the alarm acknowledge warning message to appear, select the Disable Alarm Acknowledge Warning Message check box.

Step 8 Use the Edit Alarm Categories to select the alarm categories to display in the Alarm Summary page.

Step 9 In the Select Alarms page, choose the default category to display from the drop-down list, and select the alarm categories and sub categories to display in the alarm toolbar. Click the Save button to save the alarm catgeory list. The selected alarm category and sub categories appears on the User Preferences page.

Step 10 Click Save to save the User Preference settings.


Managing Individual Licenses

This section provides information on the following:

Managing Controller Licenses

Managing WCS Licenses

Managing MSE Licenses

Managing Controller Licenses

Choose Files > Controller Files from the left sidebar menu to monitor the controller licenses.


Note WCS does not directly manage controller licenses. It simply monitors the licenses. You can manage the licenses using CLI, WebUI, or Cisco License Manager (CM) at:

https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet
.


The page displays the following information:

Controller Name

Controller IP

Feature—The feature options are wplus-ap-count, wplus, base-ap-count, and base. Two are active at any one time for an enable feature level of WPLUS or Base and the AP count (base-ap-count or wplus-ap-count), which determines the number of access points that the controller supports (12, 25, 50, 100, or 250). For every physical license installed, two license files show up in the controller as a feature level license and an ap-count license. For example, if you install a WPlus 500 license on the controller, you see a wplus or wplus-ap-count feature.


Note You can have both a WPLUS and Base license, but only one can be active at a time.


AP Limit—The number of access points that the controller supports.

EULA Status—Whether the End User License Agreement has been accepted or not.

Comments—Any user-entered comments about the license when it is installed.

Type—Permanent, evaluation, or extension.


Note For any controllers with a type other than Permanent, the number of days left to expiration is shown. A license is not in use does not incur the reduction in count until it is in use.


Status —The status can be described as follows:

Inactive—The license level is being used, but this license is not in use.

Not In Use—The license level is not being used, and this license is currently unrecognized.

Expired in Use—The license is being used, but it is expired and will not be used upon next reboot.

Expired Not in Use—The license has expired and can no longer be used.

Count Consumed—The ap-count license is In Use.

All licensed controllers and their information are displayed. If you want to change how the controller results are displayed, click Edit View. In the Edit View page, use the Show and Hide buttons to determine how the columns appear.

Above the Controller Summary list is a series of filters that allow you to sort the list by Controller Name, Feature, or Type.

Managing WCS Licenses

Follow these steps to manage WCS licenses. For information on deciding on a license, types of licenses, installing a license, and backing up and restoring WCS licenses, see the "WCS Licenses" section.


Step 1 Choose Administration > License Center to access the License Center page. It provides information about the WCS licenses, the controller license, and elements of MSE licenses.

For WCS licenses, the following is displayed:

Feature

Host name

AP Limit

AP Count (for specified number of access points)

Capacity of licenses currently used

Type

For controller licensing, the following is displayed:

Feature

Controller Count

AP Limit

Type

For tag elements, client elements, wIPS Local Mode APs and wIPS Monitor Mode APs within MSE, the following is displayed:

Limit

Count

% Used

Step 2 Choose Files > WCS Files from the left sidebar menu to see the following:

Product Activation Key (PAK)

the feature

the access point limit

type

You can click the check box of the desired license and either add or delete it.


Managing MSE Licenses

To manage MSE license, choose Files > MSE Files from the left sidebar menu. The page displays the MSE licenses found and includes the following information:

MSE License File

MSE Name

Element Type

Limit

License Type


Note Evaluation extension and tag licenses are not displayed on this page.


With full WCS support, the complete functionality of CLM is embedded within WCS. You therefore have a single point of management for devices and their licenses.

If you need to search for a particular license file, you can choose an element type from the drop-down box, and click Go. For example, if you choose Client, and click Go, all license files with client licenses are returned.

Configuring ACS 5.x

This section provides instructions for configuring ACS 5.x to work with WCS.

This section contains the following topics:

Creating Network Devices and AAA Clients

Adding Groups

Adding Users

Creating Policy Elements or Authorization Profiles

Creating Authorization Rules

Configuring Access Services

Creating Network Devices and AAA Clients

To create Network Devices and AAA Clients, follow these steps:


Step 1 Choose Network Resources > Network Devices and AAA Clients.

Figure 16-41 Network Devices Page

Step 2 Enter an IP Address.


Adding Groups

To add groups, follow these steps:


Step 1 Choose Users and Identity Stores > Identity Groups.

Figure 16-42 Identify Groups Page

Step 2 Create a Group.


Adding Users

To add users, follow these steps:


Step 1 Choose Users and Identity Stores > Internal Identity Stores > Users.

Figure 16-43 Internal Users Page

Step 2 Add a user, and then map to group to that user.


Creating Policy Elements or Authorization Profiles

Creating Policy Elements or Authorization Profiles for RADIUS

To create policy elements or authorization profiles for RADIUS, follow these steps:


Step 1 Choose Policy Elements > Authorization and Permissions > Network Access > Authorization Profiles.

Step 2 Click Create.

Step 3 Enter a Name and Description.

Step 4 Click the RADIUS Attributes tab.

Step 5 Add RADIUS Attributes one by one (see Figure 16-44).

Figure 16-44 Authorization Profiles Page

Step 6 Click Submit.


Creating Policy Elements or Authorization Profiles For TACACS

To create policy elements or authorization profiles for RADIUS, follow these steps:


Step 1 Choose Policy Elements > Authorization and Permissions > Device Administration > Shell Profiles.

Step 2 Click Create.

Step 3 Enter a Name and Description.

Step 4 Click the Custom Attributes tab.

Step 5 Add the TACACS Attributes one by one (see Figure 16-45).

Figure 16-45 Shell Profiles Page

Step 6 Click Submit.


Creating Authorization Rules

This section provides instructions for configuring authorization for RADIUS and TACACS.

Creating Service Selection Rules for RADIUS

To create service selection rules for RADIUS, follow these steps:


Step 1 Choose Access Policies > Access Services > Service Selection Rules.

Step 2 Click Create.

Step 3 Select the protocol as Radius and service as Default Network Access (see Figure 16-46).

Figure 16-46 Service Selection Page

Step 4 Click OK.


Creating Service Selection Rules for TACACS

To create service selection rules for TACACS, follow these steps:


Step 1 Choose Access Policies > Access Services > Service Selection Rules.

Step 2 Click Create.

Step 3 Select the protocol as TACACS and Service as Default Device Admin (see Figure 16-47).

Figure 16-47 Service Selection Page

Step 4 Click OK.


Configuring Access Services

This section provides instructions for configuring access services for RADIUS and TACACS.

Configuring Access Services for RADIUS

To configure access services for RADIUS, follow these steps:


Step 1 Choose Access Policies > Access Services > Default Network Access.

Step 2 In the General tab, select the Policy Structure you want to use. By default all the three will be selected. Similarly, in Allowed Protocols, select the protocols you want to use.


Note You can retain the defaults for identity and group mapping.


Step 3 To create an authorization rule for RADIUS, choose Access Policies > Access Services > Default Network Access > Authorization.

Step 4 Click Create.

Step 5 In Location, select All Locations or you can create a rule based on the location.

Step 6 In Group, select the group that you created earlier.

Step 7 In Device Type, select All Device Types or you can create a rule based on the Device Type.

Step 8 In Authorization Profile, select the authorization profile created for RADIUS.

Figure 16-48 Authorization Page

Step 9 Click OK.

Step 10 Click Save.


Configuring Access Services for TACACS

To configure access services for TACACS, follow these steps:


Step 1 Choose Access Policies > Access Services > Default Device Admin.

Step 2 In the General tab, select the Policy Structure you want to use. By default all the three will be selected. Similarly, in Allowed Protocols, select the protocols you want to use.


Note You can retain the defaults for identity and group mapping.


Step 3 To create an authorization rule for TACACS, choose Access Policies > Access Services > Default Device Admin > Authorization.

Step 4 Click Create.

Step 5 In Location, select All Locations or you can create a rule based on the location.

Step 6 In Group, select the group that you created earlier.

Step 7 In Device Type, select All Device Types or you can create a rule based on the Device Type.

Step 8 In Shell Profile, select the shell profile created for TACACS.

Figure 16-49 Authorization Page

Step 9 Click OK.

Step 10 Click Save.


Managing Licenses

This section contains the following topics:

Managing WCS Licenses

Monitoring Controller Licenses

Managing Mobility Services Engine (MSE) Licenses

Managing WCS Licenses

If you choose Files > WCS Files from the left sidebar menu, you can manage the WCS licenses. This page displays the following information:

Product Activation Key (PAK)

Feature

Access point limit

Type

Adding a New WCS License File

To add a new WCS license file, follow these steps:


Step 1 From the License Center > Files > WCS Files page, click Add.

Step 2 In the Add a License File dialog box, enter or browse to the applicable license file.

Step 3 Once displayed in the License File text box, click Upload.


Deleting a WCS License File

To delete a WCS license file, follow these steps:


Step 1 From the License Center > Files > WCS Files page, select the check box of the WCS license file that you want to delete.

Step 2 Click Delete.

Step 3 Click OK to confirm the deletion.


Monitoring Controller Licenses

If you choose Files > Controller Files from the left sidebar menu, you can monitor the controller licenses.


Note WCS does not directly manage controller licenses, rather it simply monitors the licenses. To manage the licenses you can use CLI, WebUI or Cisco License Manager (CLM) [Link to product page.


This page displays the following parameters:

Controller Name

Controller IP—The IP address of the controller.

Feature—License features include wplus-ap-count, wplus, base-ap-count, and base.

For every physical license installed, two license files display in the controller: a feature level license and an ap-count license. For example if you install a "WPlus 500" license on the controller, "wplus" and "wplus-ap-count" features display. There are always two of these features active at any one time that combine to enable the feature level (WPlus or Base) and the AP count.


Note You can have both a WPlus and Base license, but only one can be active at any given time.


AP Limit—The maximum capacity of access points allowed to join this controller.

EULA status—Displays the status of the End User License Agreement and is either Accepted or Not Accepted.

Comments—User entered comments when the license is installed.

Type—The four different types of licenses are as follows:

Permanent—Licenses are node locked and have no usage period associated with them. They are issued by Cisco licensing portal and must be installed using management interfaces on the device. Upon installation of these licenses, you have the necessary permissions across different versions.

Evaluation—Licenses are non-node locked and are valid only for a limited time period. They are used only when no permanent, extension, or grace period licenses exist. Before using an evaluation license, you must accept an End User License Agreement (EULA). Even though they are non-node locked, their usage is recorded on the device. The number of days left displays for the evaluation license with the fewest number of remaining active license days.

Extension—Licenses are node locked and metered. They are issued by Cisco licensing portal and must be installed using management interfaces on the device. Before using an extension license, you must accept a EULA during installation.

Grace Period—Licenses are node locked and metered. These licenses are issued by Cisco licensing portal as part of the permission ticket to rehost a license. They are installed on the device as part of the rehost operation, and you must accept a EULA as part of the rehost operation.


Note Types other than Permanent display the number of days left until the license expires. Licenses not currently in use do not have their counts reduced until they become "In Use".


Status

In Use—The license level and the license are in use.

Inactive—The license level is being used, but this license is not being used.

Not In Use—The license level is not being used and this license is not currently recognized.

Expired In Use—The license is being used, but is expired and will not be used upon next reboot.

Expired Not In Use—The license has expired and can no longer be used.

Count Consumed—The ap-count license is In Use.


Note If you need to filter the list of license files, you can enter a controller name, feature, or type and click Go.


Managing Mobility Services Engine (MSE) Licenses

If you choose Files > MSE Files from the left sidebar menu, you can manage the mobility services engine licenses.

This section contains the following topics:

Registering Product Authorization Keys

Installing Client and wIPS License Files

Deleting a Mobility Services Engine License File

The page displays the mobility services engine licenses found and includes the following information:


Note Because tag licenses are added and managed using appropriate vendor applications, tag licenses are not displayed in this page. Evaluation (demo) licenses are also not displayed.


Tag licenses are installed using the AeroScout System Manager.

MSE License File—Indicates the MSE Licesnse.

MSE—Indicates the MSE name.

Type—Indicates the type of mobility services engine (client elements, wIPS local mode or wIPS monitor mode access points).

Limit—Displays the total number of client elements or wIPS monitor mode access points licensed across the mobility services engine.

License Type—Permanent licenses are the only license types displayed on this page.

Permanent—Licenses are node locked and have no usage period associated with them. They are issued by Cisco licensing portal and must be installed using management interfaces on the device. Upon installation of these licenses, you have the necessary permissions across different versions.

Registering Product Authorization Keys

You receive a product authorization key (PAK) when you order a client, wIPs, or tag license from Cisco. You must register the PAK to receive the license file for install on the mobility services engine. License files are emailed to you after successfully registering a PAK.

Client and wIPS PAKs are registered with Cisco.


Note Tag PAKs are registered with AeroScout. To register your tag PAK, go to the AeroScout website.


To register a product authoritative key (PAK) to obtain a license file for install, follow these steps:


Step 1 Open a browser page and goto www.cisco.com/go/license.


Note You can also access this site by clicking the Product License Registration link located on the License Center page of WCS.


Step 2 Enter the PAK and click SUBMIT.

Step 3 Verify the license purchase. Click Continue if correct. The licensee entry page appears.


Note If the license is incorrect, click the TAC Service Request Tool link to report the problem.


Step 4 At the Designate Licensee page, enter the mobility service engine UDI in the host ID text box. This is the mobility services engine on which the license will be installed.


Note UDI information for a mobility services engine is found on the General Properties pane at Services > Mobility Services Engine > Device Name > System.


Step 5 Select theAgreement check box. Registrant information appears beneath the Agreement check box.

Modify information as necessary.


Note Ensure that the phone number does not include any characters in the string for the registrant and end user. For example, enter 408 555 1212 rather than 408.555.1212 or 408-555-1212.


Step 6 If registrant and end user are not the same person, select Licensee (End-User) check box beneath registrant information and enter the end user information.

Step 7 Click Continue. A summary of entered data appears.

Step 8 At the Finish and Submit page, review registrant and end user data. Click Edit Details to correct information, if necessary.

Step 9 Click Submit. A confirmation page appears.


Installing Client and wIPS License Files

You can install client and wIPS licenses from WCS.


Note Tag licenses are installed using the AeroScout System Manager.


To add a client or wIPS license to WCS after registering the PAK, follow these steps:


Step 1 Choose Administration > License Center.

Step 2 From the left sidebar menu, choose Files > MSE Files.

Step 3 From the License Center > Files > MSE Files page, click Add to open the Add a License File dialog box.

Step 4 From the MSE Name drop-down list, select the mobility services engine to which you want to add the license file.


Note Verify that the UDI of the selected mobility services engine matches the one you entered when registering the PAK.


Step 5 Enter the license file in the License File text box or browse to the applicable license file.

Step 6 Once displayed in the License File text box, click Upload. Newly added license appears in mobility services engine license file list.


Note A Context Aware Service (CAS) restarts if a client or tag license is installed; a wIPS service restarts if a wIPS license is installed.



Note Services must come up before attempting to add or delete another license.



Deleting a Mobility Services Engine License File

To delete a mobility services engine license file, follow these steps:


Step 1 From the License Center > Files > MSE Files page, select the check box of the mobility services engine license file that you want to delete.

Step 2 Click Delete.

Step 3 Click OK to confirm the deletion.


Configuring AAA

From Administration > AAA, authentication, authorization, and accounting (AAA) can be configured for WCS. The only username that has permissions to configure WCS AAA is root or SuperUser. Any changes to local users accounts will be in effect when configured for local mode. If using external authentication, for example RADIUS or TACACS+, the user changes must be done on the remote server. This section contains the following topics:

Change Password

Local Password Policy

AAA Mode

Users

Groups

Active Sessions

TACACS+

RADIUS

Change Password

Choose Administration > AAA > Change Password from the left sidebar menu to access this page.

This page enables you to change the root password.

User—Applies to login username root.

Old Password—Current password.

New Password—Enter the new password using ASCII characters.

Confirm password—Reenter the new password.

Submit—Click Submit to confirm password change.

AAA Mode

Choose Administration > AAA > AAA Mode from the left sidebar menu to access this page.

This page enables you to configure the authentication mode for all users.

AAA Mode Settings

Local—Authenticate users to a local database.

RADIUS—Authenticate users to an external RADIUS server.

TACACS+—Authenticate users to an external TACACS+ server.

Enable fallback to Local—If an external authentication server is down, this provides the option to authenticate users locally. This option is only available for RADIUS and TACACS+.

Select ONLY on no server response or on auth failure or no server response from the drop-down list.

See also the "TACACS+" section and the "RADIUS" section.

Setting AAA Mode

To choose a AAA mode, follow these steps :


Step 1 Choose Administration > AAA.

Step 2 Choose AAA Mode from the left sidebar menu. The AAA Mode Setting page appears (see Figure 16-50).

Figure 16-50 AAA Mode Settings Page

Step 3 Choose which AAA mode you want to use. Only one can be selected at a time.

Any changes to local user accounts are effective only when you are configured for local mode (the default). If you use remote authentication, changes to the credentials are made on a remote server. The two remote authentication types are RADIUS and TACACS+. RADIUS requires separate credentials for different locations (East and West Coast). TACACS+ is an effective and secure management framework with a built-in failover mechanism.

Step 4 Select the Enable Fallback to Local check box if you want the administrator to use the local database when the external AAA server is down.


Note This option is unavailable if Local was selected as a AAA mode type.


Step 5 Click OK.


Local Password Policy

Choose Administration > AAA > Local Password Policy from the left sidebar menu to access this page.This page enables you to determine your local password policy.

you can enable or disable the following policies for your local password:

Set the minimum length of your password. By default it is set as 8.

Password cannot be the username or the reverse of the username.

Password cannot be the word cisco or ocsic (cisco reversed) or any special characters replaced for the same.

Root password cannot be the word public.

No character can be repeated more than three time consecutively in the password.

Password must contain character from three of the character classes: upper case, lower case, digits, and special characters.

Set that the password cannot be reused within n number of the previous passwords used. By default it is 10 times.

Password cannot be changed at an interval of less than 24 hours from last change.

Set the account to be lockout after x number of failed login attempts. By default it is 5 attempts.

Set if the account should be disabled after 30 days of inactivity.

Set the number of days after when the password should expire. By default it is 60 days.

Enforce password change on first login.

Click Save to confirm the Local Password Policy changes.

Users

This section describes how to configure a WCS user. Besides complete access, you can give administrative access with differentiated privileges to certain user groups.

Choose Administration > AAA > Users from the left sidebar menu to access this page including:

Current User Names

Member Of—Groups with which the user is associated. Click an item under the Member Of column to view permitted tasks for this user.

Audit Trail—Click the Audit Trail icon for a specific user to view or clear current audit trails. See the "Audit User Operations" section.

Edit Current Users

Edit Current Users - Passwords and Assigned Groups

Edit Current Users - Permitted Tasks

Edit Current Users - Groups Assigned to this User

Adding a New User


Note You must have SuperUser status to create user accounts and groups.


Virtual Domain

Creating a New Virtual Domain

Understanding Virtual Domain Hierarchy

Managing a Virtual Domain

Adding a New User

Virtual Domain RADIUS and TACACS+ Attributes

Understanding Virtual Domains as a User

Edit Current Users - Passwords and Assigned Groups

To edit current user account passwords and assigned groups, follow these steps:


Step 1 Choose Administration > AAA.

Step 2 From the left sidebar menu, choose Users.

Step 3 Select a specific user from the User Name column.

Step 4 Enter and confirm a new password, if necessary (optional).

Step 5 If necessary, make changes to the Groups Assigned to this User check box selections.


Note If the user belongs to Lobby Ambassador, Monitor Lite, Northbound API, or Users Assistant group, the user cannot belong to any other group.


Step 6 Select Submit to confirm the changes or Cancel to close the page without activating any changes.


Edit Current Users - Permitted Tasks

To edit the permitted tasks for this user account, follow these steps:


Step 1 Choose Administration > AAA.

Step 2 From the left sidebar menu, choose Users.

Step 3 Select the applicable group(s) from the Member Of column.

Step 4 From the List of Tasks Permitted column, select or deselect the applicable tasks to permit or disallow them.


Note The list of available tasks changes depending on the type of group.


Step 5 Select Submit to confirm the changes or Cancel to close the page without activating any changes.


Edit Current Users - Groups Assigned to this User

To edit the groups assigned to this user, follow these steps:


Step 1 Choose Administration > AAA.

Step 2 From the left sidebar menu, choose Users.

Step 3 Select a specific user from the User Name column.

Step 4 Select the check box(es) of the groups to which this user will be assigned.


Note If the user belongs to Lobby Ambassador, Monitor Lite, Northbound API, or Users Assistant group, the user cannot belong to any other group.
Root is only assignable to 'root' user and that assignment cannot be changed.



Note For more information on assigned groups, see Step 7 in the "Adding a New User" section section.


Step 5 Select Submit to confirm the changes or Cancel to close the page without activating any changes.


Adding a New User

The Add User page allows the administrator to set up a new user login including username, password, groups assigned to the user, and virtual domains for the user.


Note By assigning virtual domains to a user, the user is restricted to information applicable to those virtual domains.



Note You must have SuperUser status to access this page.


This section contains the following topics:

Add User Name, Password, and Groups

Assign a Virtual Domain

Add User Name, Password, and Groups

To add a new user, follow these steps:


Step 1 Choose Administration > AAA.

Step 2 From the left sidebar menu, choose Users.

Step 3 From the Select a command drop-down list, choose Add User.

Step 4 Click Go.

Step 5 Enter a new Username.

Step 6 Enter and confirm a password for this account.

Step 7 Select the check box(es) of the groups to which this user will be assigned.


Note If the user belongs to Lobby Ambassador, Monitor Lite, Northbound API, or Users Assistant group, the user cannot belong to any other group.


Admin—Allows users to monitor and configure WCS operations and perform all system administration tasks except administering WCS user accounts and passwords.

ConfigManagers—Allows users to monitor and configure WCS operations.

System Monitoring—Allows users to monitor WCS operations.

Users Assistant—Allows local net user administration only.

Lobby Ambassador—Allows guest access for configuration and management only of user accounts. If Lobby Ambassador is selected, a Lobby Ambassador Defaults tab appears. See the "Managing Lobby Ambassador Accounts" section for more information on setting up a Lobby Ambassador account.

Monitor Lite—Allows monitoring of assets location.

North Bound API User—Group used only with WCS Navigator and WCS Web Service consumers.


Note North Bound API Users cannot be assigned a Virtual Domain. When a North Bound API group is selected, the Virtual Domains tab is not available.


SuperUsers—Allows users to monitor and configure WCS operations and perform all system administration tasks including administering WCS user accounts and passwords. Superuser tasks can be changed.

Root—This group is only assignable to 'root' user and that assignment cannot be changed.

User Defined.

Assign a Virtual Domain

To assign a virtual domain to this user, follow these steps:


Step 1 Click the Virtual Domains tab. This page displays all virtual domains available and assigned to this user.


Note The Virtual Domains tab enables the administrator to assign virtual domains for each user. By assigning virtual domains to a user, the user is restricted to information applicable to those virtual domains.



Note North Bound API Users cannot be assigned a Virtual Domain. When a North Bound API group is selected, the Virtual Domains tab is not available.


Step 2 Click to highlight the virtual domain in the Available Virtual Domains list that you want to assign to this user.


Note You can select more than one virtual domain by pressing the Shift or Control key.


Step 3 Click Add. The virtual domain moves from the Available Virtual Domains to the Selected Virtual Domains list.

To remove a virtual domain from the Selected Virtual Domains list, click to highlight the domain in the Selected Virtual Domains list and click Remove. The virtual domain moves from the Selected Virtual Domains to the Available Virtual Domains list.

Step 4 Select Submit to or Cancel to close the page without adding or editing the current user.


Audit User Operations

To view or clear audit information for this account, follow these steps:


Step 1 Choose Administration > AAA.

Step 2 From the left sidebar menu, choose Users.

Step 3 Click the Audit Trail icon for the applicable account.


Note You must have SuperUser status to access this page.


This page enables you to view a list of user operations over time.

User—User login name.

Operation—Type of operation audited.

Time—Time operation was audited.

Status—Success or Failure.

Step 4 To clear an audit trail, select the check box for the applicable audit, select Clear Audit Trail from the Select a command drop-down list, click Go, and click OK to confirm.


Groups

This page provides you with a list of all current groups and their associated members.

Group Name—Click a specific group to view or edit the permitted tasks for this group. The available tasks change depending on the type of group. See the "Edit Current Users - Permitted Tasks" section for more information.

Members—Click a specific user under the Member column to view or edit that user. See the "Edit Current Users - Passwords and Assigned Groups" section for more information.

Audit Trail—Click the Audit Trail icon to view or clear audit for this group. See the "Audit User Operations" section for more information.

Export—Click to export the task list associated with this group.

To access the Groups page, follow these steps:


Step 1 Choose Administration > AAA.

Step 2 From the left sidebar menu, choose Groups.


Note You must have SuperUser status to access this page.



Viewing or Editing Group Information

Follow these steps to see specific tasks the user is permitted to do within the defined group or make changes to the tasks.


Step 1 Choose Administration > AAA.

Step 2 Choose Groups from the left sidebar menu.

Step 3 Click in the Group Name column. The Group Detail: User Group page appears (see Figure 16-51).


Note The detailed page varies based on what group you choose. Figure 16-51 shows the detailed page of the superuser.


Figure 16-51 Detailed Group Page

You can see the specific tasks the user is permitted to do within the defined group.

Step 4 Make any necessary changes to the tasks.

Step 5 Click Submit.


Active Sessions

Choose Administration > AAA > Active Sessions from the left sidebar menu to open this page.

This page displays a list of users currently logged in. The user highlighted in red represents your current login.


Note You must be logged into a user account with SuperUsers privileges to see active sessions.


If a column heading is a hyperlink, click the heading to sort the list of active sessions in descending or ascending order along that column. The sort direction is toggled each time the hyperlink is clicked.

The Active Sessions page has the following columns:

IP/Host Name—The IP address or the hostname of the machine on which the browser is running. If the hostname of the user machine is not in DNS, the IP address is displayed.

Login Time—The time at which the user logged in to WCS. All times are based on the WCS server machine time.

Last Access Time—The time at which the user browser accessed WCS. All times are based on the WCS server machine time.


Note The time displayed in this column is usually a few seconds behind the current system time because Last Access Time is updated frequently by the updates to the alarm status panel. However, if a user navigates to a non WCS web page in the same browser, the disparity in time will be greater. Alarm counts are not updated when the browser is not displaying WCS web pages.


Login Method:

Web Service—Internal session needed by Navigator to manage WCS.

Regular—Sessions created for users who log into WCS directly through a browser.

Navigator Redirect—Sessions created for Navigator users who are redirected to WCS from Navigator.

User Groups—The list of groups the user belongs to.

Audit trail icon—Link to page that displays the audit trail (previous login times) for that user.

TACACS+

This section describes how to add and delete TACACS+ servers. TACACS+ servers provide an effective and secure management framework with built-in failover mechanisms. If you want to make configuration changes, you must be authenticated.

The TACACS+ page shows the TACACS+ server's IP address, port, retransmit rate, and authentication type (Password Authentication Protocol (PAP)) or Challenge Handshake Authentication Protocol (CHAP). The TACACS+ servers are tried based on how they were configured.


Note To activate TACACS+ servers, you must enable them as described in the "Importing Tasks Into ACS" section.



Step 1 Choose Administration > AAA.

Step 2 From the left sidebar menu, choose TACACS+. The TACACS+ page appears (see Figure 16-52).

Figure 16-52 TACACS+ Page

Step 3 The TACACS+ page shows the TACACS+ server's IP address, port, retransmit rate, and authentication type (Password Authentication Protocol (PAP)) or Challenge Handshake Authentication Protocol (CHAP). The TACACS+ servers are tried based on how they were configured.


Note If you need to change the order of how TACACS+ servers are tried, delete any irrelevant TACACS+ servers and re-add the desired ones in the preferred order.


Step 4 Use the drop-down list in the upper right-hand corner to add or delete TACACS+ servers. You can click an IP address if you want to make changes to the information.

Step 5 The current server address and port are displayed. Use the drop-down list to choose either ASCII or hex shared secret format.

Step 6 Enter the TACACS+ shared secret used by your specified server.

Step 7 Re-enter the shared secret in the Confirm Shared Secret text box.

Step 8 Specify the time in seconds after which the TACACS+ authentication request times out and a retransmission is attempted by the controller.

Step 9 Specify the number of retries that will be attempted.

Step 10 In the Authentication Type drop-down list, choose a protocol: PAP or CHAP.

Step 11 Click Submit.


Note See the "Configuring ACS 5.x" section for more information on Configuring ACS 5.x.



Select a command

Add TACACS+ Server—See "Add TACACS+ Server" section.

Delete TACACS+ Server—Select a server or servers to be deleted, select this command and click Go to delete the server(s) from the database.

Add TACACS+ Server

Choose Administration > AAA > TACACS+ from the left sidebar menu to access this page. From the Select a command drop-down list choose Add TACACS+ Server and click Go to access this page.

This page allows you to add a new TACACS+ server to WCS.

Server Address—IP address of the TACACS+ server being added.

Port—Controller port.

Shared Secret Format—ASCII or Hex.

Shared Secret—The shared secret that acts as a password to log in to the TACACS+ server.

Confirm Shared Secret—Reenter TACACS+ server shared secret.

Retransmit Timeout—Specify the time in seconds after which the TACACS+ authentication request will time out and the controller will retransmit.

Retries—Number of retries allowed for authentication request. You can specify a value between 1 and 9.

Authentication Type—Two authentication protocols are provided. Password Authentication Protocol (PAP) and Challenge Handshake Authentication Protocol (CHAP).

Command Buttons

Submit

Cancel


Note Enable the TACACS+ server with the AAA Mode Settings. See the "AAA Mode" section.


RADIUS

This section describes how to add and delete RADIUS servers. You must enable RADIUS servers and have a template set up for them to make configuration changes.

RADIUS provides authentication of users accessing the network. Authentication requests are sent to a RADIUS server that contains all user authentication and network access information. Passwords are encrypted using RADIUS.

In the event the configured RADIUS server(s) is down, WCS will fall back to local authentication and authorization if the fallback to local option is configured. See the "AAA Mode" section.


Note To activate RADIUS servers, you must enable them as described in the "Importing Tasks Into ACS" section.



Step 1 Choose Administration > AAA.

Step 2 From the left sidebar menu, choose RADIUS. The RADIUS page appears (see Figure 16-53).

Figure 16-53 RADIUS Page

Step 3 The RADIUS page shows the server address, authentication port, retransmit timeout value, and authentication type for each RADIUS server that is configured. The RADIUS servers are tried based on how they were configured.


Note If you need to change the order of how RADIUS servers are tried, delete any irrelevant RADIUS servers, and re-add the desired ones in the preferred order.


Step 4 Use the drop-down list in the upper right-hand corner to add or delete RADIUS servers. You can click an IP address if you want to make changes to the information.

Step 5 The current authentication port appears. Use the drop-down list to choose either ASCII or hex shared secret format.

Step 6 Enter the RADIUS shared secret used by your specified server.

Step 7 Re-enter the shared secret in the Confirm Shared Secret text box.

Step 8 Specify the time in seconds after which the RADIUS authentication request times out and a retransmission is attempted by the controller.

Step 9 Specify the number of retries that will be attempted.

Step 10 From the Authentication Type drop-down list, choose a protocol: PAP or CHAP.

Step 11 Click Submit.


Select a command

Add RADIUS Server—See the "Adding RADIUS Server" section.

Delete RADIUS Server—Select a server or servers to be deleted, select this command, and click Go to delete the server(s) from the database.

Adding RADIUS Server

Choose Administration > AAA > RADIUS from the left sidebar menu to access this page. From the Select a command drop-down list choose Add RADIUS Server, and click Go to access this page.

This page allows you to add a new RADIUS server to WCS.

Server Address—IP Address of the RADIUS server being added.

Port—Controller port.

Shared Secret Format—ASCII or Hex.

Shared Secret—The shared secret that acts as a password to log in to the RADIUS server.

Confirm Shared Secret—Reenter RADIUS server shared secret.

Retransmit Timeout—Specify the time in seconds after which the RADIUS authentication request will time out and the controller will retransmit.

Retries—Number of retries allowed for authentication request. You can specify a value between 1 to 9.

Command Buttons

Submit

Cancel


Note Enable the RADIUS server with the AAA Mode Settings. See the "AAA Mode" section.