Cisco Wireless Control System Configuration Guide, Release 7.0.172.0
Chapter 4: Performing Maintenance Operations
Downloads: This chapterpdf (PDF - 419.0KB) The complete bookPDF (PDF - 43.47MB) | Feedback

Table Of Contents

Performing Maintenance Operations

Information About Maintenance Operations

Performing System Tasks

Adding a Controller to the WCS Database

Additional Functionality with Location Appliance

Using WCS to Update System Software

Downloading Vendor Device Certificates

Downloading Vendor CA Certificates

Using WCS to Enable Long Preambles for SpectraLink NetLink Phones

Creating an RF Calibration Model

Verifying the Status of WCS

Checking the Status of WCS on Windows

Checking the Status of WCS on Linux

Stopping WCS

Stopping WCS on Windows

Stopping WCS on Linux

Backing Up the WCS Database

Scheduling Automatic Backups

Performing a Manual Backup

Backing Up the WCS Database (for Windows)

Backing Up the WCS Database (for Linux)

Restoring the WCS Database

Restoring the WCS Database (for Windows)

Restoring the WCS Database (for Linux)

Restoring the WCS Database in a High Availability Environment

Uninstalling WCS

Uninstalling WCS on Windows

Uninstalling WCS on Linux

Upgrading WCS

Using the Installer to Upgrade WCS for Windows

Using the Installer to Upgrade WCS for Linux

Manually Upgrading WCS on Windows

Manually Upgrading WCS on Linux

Upgrading WCS in a High Availability Environment

Upgrading the Network

Reinitializing the Database

Recovering the WCS Password


Performing Maintenance Operations


You can perform the actions at the system level, such as updating system softwares or downloading certificates that can be used with many items.

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

Information About Maintenance Operations

Performing System Tasks

Verifying the Status of WCS

Stopping WCS

Backing Up the WCS Database

Restoring the WCS Database

Uninstalling WCS

Upgrading WCS

Upgrading WCS in a High Availability Environment

Upgrading the Network

Reinitializing the Database

Recovering the WCS Password

Information About Maintenance Operations

A system-level task is a collection of tasks that relate to operations that apply to the WCS database as a whole. System tasks also includes restoring WCS database. For more information, see the "Restoring the WCS Database" section.

Performing System Tasks

This section describes how to use Cisco WCS to perform system-level tasks. It contains the following topics:

Adding a Controller to the WCS Database

Using WCS to Update System Software

Downloading Vendor Device Certificates

Downloading Vendor CA Certificates

Using WCS to Enable Long Preambles for SpectraLink NetLink Phones

Creating an RF Calibration Model

Adding a Controller to the WCS Database

To add a controller to the WCS database, follow these steps:


Note We recommend that you manage controllers through the controller dedicated service port for improved security. However, when you manage controllers that do not have a service port (such as 2000 series controllers) or for which the service port is disabled, you must manage those controllers through the controller management interface.



Step 1 Log into the WCS user interface.

Step 2 Click Configure > Controllers to display the All Controllers page.

Step 3 From the Select a command drop-down list, choose Add Controller, and click Go.

Step 4 On the Add Controller page, enter the controller IP address, network mask, and required SNMP settings.

Step 5 Click OK. WCS displays a Please Wait dialog box while it contacts the controller and adds the current controller configuration to the WCS database. It then returns you to the Add Controller page.

Step 6 If WCS does not find a controller at the IP address that you entered for the controller, the Discovery Status dialog displays this message:

No response from device, check SNMP. 

Check these settings to correct the problem:

The controller service port IP address might be set incorrectly. Check the service port setting on the controller.

WCS might not have been able to contact the controller. Make sure that you can ping the controller from the WCS server.

The SNMP settings on the controller might not match the SNMP settings that you entered in WCS. Make sure that the SNMP settings configured on the controller match the settings that you entered in WCS.

Step 7 Add additional controllers if desired.


Additional Functionality with Location Appliance

Cisco 2700 series location appliances operate within the Cisco Wireless LAN Solution infrastructure. Location appliances compute, collect, and store historical location data using Cisco wireless LAN controllers and access points to track the physical location of wireless devices.

The location appliance can track up to 2,500 elements. You can track the following elements: client stations, active asset tags, rogue clients and access points. Updates on the locations of elements being tracked are provided to the location server from the Cisco wireless LAN controller.

Only those elements designated for tracking by the controller are viewable in Cisco WCS maps, queries, and reports. No events and alarms are collected for non-tracked elements, and they are not used in calculating the 2,500 element limit.

You can modify the following tracking parameters using Cisco WCS:

Enable and disable which element locations (client stations, active asset tags, and rogue clients and access points) you actively track

Set limits on how many of a specific element you want to track

You can set limits on how many of a specific element you wish to track. For example, given a limit of 2,500 trackable units, you could set a limit to track only 1,500 client stations. Once the tracking limit is met, the number of elements not being tracked is summarized on the Tracking Parameters page.

Disable tracking and reporting of ad hoc rogue clients and access points


Note Even though all clients are loaded in the map, the display has a limit of 250 clients per floor to prevent overcrowding. You can do an advanced search of the map to see the items of interest.


Selectable filters enable you to search collected data and display specific elements on a map. For example, a biomedical user may want to display only active Wi-Fi tags that are tracking key medical equipment rather than access points or clients for a given floor.

Using WCS to Update System Software

To update controller (and access point) software using WCS, follow these steps:


Step 1 Enter the ping ip-address command to be sure that the WCS server can contact the controller. If you use an external TFTP server, enter ping ip-address to be sure that the WCS server can contact the TFTP server.


Note When you are downloading through a controller distribution system (DS) network port, the TFTP server can be on the same or a different subnet because the DS port is routable.


Step 2 Click Configure > Controllers to navigate to the All Controllers page.

Step 3 Select the check box of the desired controller, choose Download Software (TFTP or FTP) from the Select a command drop-down list, and click Go. WCS displays the Download Software to Controller page.

Step 4 If you use the built-in WCS TFTP server, select the TFTP Server on WCS System check box. If you use an external TFTP server, unselect this check box and add the external TFTP server IP address.

Step 5 Click Browse and navigate to the software update file (for example, AS_2000_release.aes for 2000 series controllers). The files are uploaded to the root directory which was configured for use by the TFTP server. You can change to a different directory.


Note Be sure that you have the correct software file for your controller.


Step 6 Click Download. WCS downloads the software to the controller, and the controller writes the code to flash RAM. As WCS performs this function, it displays its progress in the Status field.


Downloading Vendor Device Certificates

Each wireless device (controller, access point, and client) has its own device certificates. For example, the controller is shipped with a Cisco-installed device certificate. This certificate is used by EAP-TLS and EAP-FAST (when not using PACs) to authenticate wireless clients during local EAP authentication. However, if you wish to use your own vendor-specific device certificate, it must be downloaded to the controller.

To download a vendor-specific device certificate to the controller, follow these steps.


Step 1 Choose Configure > Controllers.

Step 2 You can download the certificates in one of two ways:

a. Select the check box of the controller you choose.

b. Choose Download Vendor Device Certificate from the Select a command drop-down list, and click Go.

or

a. Click the URL of the desired controller in the IP Address column.

b. Choose System > Commands from the left sidebar menu.

c. Choose TFTP or FTP in the Upload/Download Command section.

d. Choose Download Vendor Device Certificate from the Upload/Download Commands drop-down list, and click Go.

Step 3 In the Certificate Password text box, enter the password which was used to protect the certificate.

Step 4 Specify if the certificate to download is on the TFTP server or on the local machine. If it is on the TFTP server, the name must be supplied in the Server File Name parameter. If the certificate is on the local machine, you must specify the file path in the Local File Name parameter using the Browse button.

Step 5 Enter the TFTP server name in the Server Name parameter. The default is for the WCS server to act as the TFTP server.

Step 6 Enter the server IP address.

Step 7 In the Maximum Retries text box, enter the maximum number of times that the TFTP server attempts to download the certificate.

Step 8 In the Timeout text box, enter the amount of time (in seconds) that the TFTP server attempts to download the certificate.

Step 9 In the Local File Name text box, enter the directory path of the certificate.

Step 10 Click OK.


Downloading Vendor CA Certificates

Controllers and access points have a certificate authority (CA) certificate that is used to sign and validate device certificates. The controller is shipped with a Cisco-installed CA certificate. This certificate may be used by EAP-TLS and EAP-FAST (when not using PACs) to authenticate wireless clients during local EAP authentication. However, if you wish to use your own vendor-specific CA certificate, it must be downloaded to the controller. To download vendor CA certificate to the controller, follow these instructions:


Step 1 Click Configure > Controllers.

Step 2 You can download the certificates in one of two ways:

a. Select the check box of the controller you choose.

b. Choose Download Vendor CA Certificate from the Select a command drop-down list, and click Go.

or

a. Click the URL of the desired controller in the IP Address column.

b. Choose System > Commands from the left sidebar menu.

c. Choose Download Vendor CA Certificate from the Upload/Download Commands drop-down list, and click Go.

Step 3 Specify if the certificate to download is on the TFTP server or on the local machine. If it is on the TFTP server, the name must be supplied in the Server File Name parameter in Step 9. If the certificate is on the local machine, you must specify the file path in the Local File Name parameter in Step 8 using the Browse button.

Step 4 Enter the TFTP server name in the Server Name parameter. The default is for the WCS server to act as the TFTP server.

Step 5 Enter the server IP address.

Step 6 In the Maximum Retries text box, enter the maximum number of times that the TFTP server attempts to download the certificate.

Step 7 In the Timeout text box, enter the amount of time (in seconds) that the TFTP server attempts to download the certificate.

Step 8 In the Local File Name text box, enter the directory path of the certificate.

Step 9 Click OK.


Using WCS to Enable Long Preambles for SpectraLink NetLink Phones

A radio preamble (sometimes called a header) is a section of data at the head of a packet. It contains information that wireless devices need when sending and receiving packets. Short preambles improve throughput performance, so they are enabled by default. However, some wireless devices, such as SpectraLink NetLink phones, require long preambles.

To optimize the operation of SpectraLink NetLink phones on your wireless LAN, follow these steps to use WCS to enable long preambles.


Step 1 Log into the WCS user interface.

Step 2 Click Configure > Controllers to navigate to the All Controllers page.

Step 3 Click the IP address of the desired controller.

Step 4 From the left sidebar menu, choose 802.11b/g/n > Parameters.

Step 5 If the IP Address > 802.11b/g/n Parameters page shows that short preambles are enabled, continue to the next step. However, if short preambles are disabled, which means that long preambles are enabled, the controller is already optimized for SpectraLink NetLink phones, and you do not need to continue this procedure.

Step 6 Enable long preambles by unselecting the Short Preamble check box.

Step 7 Click Save to update the controller configuration.

Step 8 To save the controller configuration, click System > Commands from the left sidebar menu, Save Config To Flash from the Administrative Commands drop-down list, and Go.

Step 9 To reboot the controller, click Reboot from the Administrative Commands drop-down list, and click Go.

Step 10 Click OK when the following message appears:

Please save configuration by clicking "Save Config to flash". Do you want to continue 
rebooting anyways?
 
 

The controller reboots. This process may take some time, during which WCS loses its connection to the controller.


Note You can view the controller reboot process with a CLI session.



Creating an RF Calibration Model

If you would like to further refine WCS Location tracking of client and rogue access points across one or more floors of a building, you have the option of creating an RF calibration model that uses physically collected RF measurements to fine-tune the location algorithm. When you have multiple floors in a building with the same physical layout as the calibrated floor, you can save time calibrating the remaining floors by using the same RF calibration model for the remaining floors.

The calibration models are used as RF overlays with measured RF signal characteristics that can be applied to different floor areas. This allows the Cisco Unified Wireless Network Solution installation team to lay out one floor in a multi-floor area, use the RF calibration tool to measure and save the RF characteristics of that floor as a new calibration model, and apply that calibration model to all the other floors with the same physical layout. See Chapter 5 for calibration instructions.

Verifying the Status of WCS

This section provides instructions for checking the status of WCS on either a Windows or Linux server.

Checking the Status of WCS on Windows

You can check the status of WCS at any time. To check the status of WCS when it is installed as a Windows application or Windows service, follow these steps:


Step 1 Log into the system as administrator.

Step 2 Perform one of the following:

From the Windows Start menu, choose Programs > Wireless Control System> WCSStatus.

From the command prompt, navigate to the WCS installation directory (such as C:\Program Files\WCS7.0.X.X) and enter WCSAdmin status.

The WCSAdmin window appears and displays messages indicating the status of WCS.

Step 3 Close the WCSAdmin window when the Close button becomes active.


Checking the Status of WCS on Linux

You can check the status of WCS at any time. To check the status of WCS when it is installed as a Linux application or Linux service, follow these steps:


Step 1 Log into the system as root.

Step 2 Using the Linux CLI, perform one of the following:

Navigate to the installation directory (such as /opt/WCS7.0.X.X) and enter ./WCSStatus.

Navigate to the installation directory (such as /opt/WCS7.0.X.X) and enter WCSAdmin status.

The CLI displays messages indicating the status of WCS.


Stopping WCS

This section provides instructions for stopping WCS on either a Windows or Linux server.

Stopping WCS on Windows

You can stop WCS at any time. To stop WCS when it is installed as a Windows application or Windows service, follow these steps:


Note If any users are logged in when you stop WCS, their WCS sessions stop functioning.



Step 1 Log into the system as administrator.

Step 2 Perform one of the following:

From the shortcut location (defaulted to Windows Start menu > Programs > Cisco Wireless Control System A.B.C.D), enter the StopWCS command.

From the command prompt, navigate to the WCS installation directory (defaulted to C:\Program Files\WCSA.B.C.D\bin) and enter the StopWCS command.


Note You can use the StopWCS command for a graceful shut down. A graceful shut down does not trigger the automatic failover. Use the CLI command <WCSROOT>\nmsadmin.bat -switchover stop to trigger automatic failover when shutting down WCS.


The WCSAdmin window appears and displays messages indicating that WCS is stopping.


Note If WCS is installed as a service, messages also appear to indicate that the Nms_Server service is stopping.


Step 3 Close the WCSAdmin window when the Close button becomes active.


Stopping WCS on Linux

You can stop WCS at any time. To stop WCS when it is installed as a Linux application or Linux service, follow these steps:


Note If any users are logged in when you stop WCS, their WCS sessions stop functioning.



Step 1 Log into the system as root.


Note To see which version of WCS you currently have installed, enter the nmsadmin.sh version command.


Step 2 Using the Linux CLI, perform one of the following:

Navigate to the shortcut location (defaulted to /opt/WCSA.B.C.D) and enter the  ./StopWCS command.

Navigate to the installation bin directory (defaulted to /opt/WCSA.B.C.D/bin) and enter the StopWCS command.

The CLI displays messages indicating that WCS is stopping.


Backing Up the WCS Database

This section provides instructions for backing up the WCS database. You can schedule regular backups through the WCS user interface or manually initiate a backup on either a Windows or Linux server.


Note Machine specific settings (such as FTP enable and disable, FTP port, FTP root directory, TFTP enable and disable, TFTP port, TFTP root directory, HTTP forward enable and disable, HTTP port, HTTPS port, report repository directory, and all high availability settings) are not included in the backup and restore function if the backup is restored to a different device.


Scheduling Automatic Backups

To schedule automatic backups of the WCS database, follow these steps:


Step 1 Log into the WCS user interface.

Step 2 Click Administration > Background Tasks to display the Scheduled Tasks page.

Step 3 Click WCS Server Backup to display the Task > WCS Server Backup page.

Step 4 Select the Enabled check box.

Step 5 At the Report History Backup parameter, select the Enabled check box to run history backup.

Step 6 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 7 In the Interval (Days) text box, enter a number representing 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 8 In the Time of Day text box, enter the time when you want the backup to start. It must be in this format: hh:mm AM/PM (for example: 03:00 AM).


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 (for example, in the middle of the night).


Step 9 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).


Performing a Manual Backup

This section provides instructions for backing up the WCS database on either a Windows or Linux server.

Backing Up the WCS Database (for Windows)

To back up the WCS database on a Windows server, follow these steps:


Step 1 Log into the system as administrator.

Step 2 Create a backup directory for the WCS database with no spaces in the name, such as C:\WCS7.0.X.X_Backup.


Note Make sure that the directory name does not contain spaces. Spaces can generate errors.


Step 3 Perform one of the following:

Follow these steps from the Windows Start menu:

a. Choose Programs > Wireless Control System> Backup. The Enter Information window appears.

b. Browse to the backup directory that you created and choose the filename or enter the full path of the backup directory that you created and a name for the backup file (such as C:\WCS7.0.X.X_Backup\Nov11), and click OK.

Follow these steps from the command prompt:

a. Navigate to the WCS installation directory (C:\Program Files\WCS7.0.X.X\bin).

b. Enter the DBAdmin backup backup-filename command, where backup-filename is the full path of the backup directory that you created plus a name for the backup file (such as C:\WCS7.0.X.X_Backup\Nov11).

The DBAdmin window appears and displays messages indicating the status of the backup.

Step 4 Close the DBAdmin window when the Close button becomes active.


Note In the preceding example, the backup file would appear in the C:\WCS7.0.X.X_Backup directory as Nov11.nmsbackup.



Backing Up the WCS Database (for Linux)

To back up the WCS database on a Linux server, follow these steps:


Step 1 Log into the system as root.

Step 2 Using the Linux CLI, navigate to the /opt/WCS7.0 directory (or any other directory).

Step 3 Create a backup directory for the WCS database with no spaces in the name (for example, mkdir WCS7.0.X.X_Backup).


Note Make sure that the directory name does not contain spaces. Spaces can generate errors.


Step 4 Perform one of the following:

Navigate to the /opt/WCS7.0.X.0 directory (or the directory chosen during installation) and enter the  ./Backup command. Enter a name for the backup file when prompted (such as WCS7.0.X.X_Backup/Nov11).

Navigate to the /opt/WCS7.0.X.X/bin directory (or the directory chosen during installation) and enter the DBAdmin backup backup-filename command, where backup-filename is the full path of the backup directory that you created plus a name for the backup file (such as WCS7.0.X.X_Backup/Nov11).

Using KDE or X-Windows, enter the DBAdmin - gui backup command, browse to the backup directory, and choose the file.

The CLI displays messages indicating the status of the backup.


Note In the preceding example, the backup file would appear in the WCS7.0.X.X_Backup directory as Nov11.nmsbackup.



Restoring the WCS Database

This section provides instructions for restoring the WCS database on either a Windows or Linux server.

Restoring the WCS Database (for Windows)

If you are restoring the WCS database in a high availability environment, refer to the "Restoring the WCS Database in a High Availability Environment" section. To restore the WCS database from a backup file on a Windows server, follow these steps:


Note The server may incorrectly perceive the amount of free space available during a restore if a FAT32 file system is used. Microsoft's recommended file system for Windows servers is NTFS.



Step 1 Log into the system as administrator.

Step 2 Perform one of the following:

Follow these steps from the Windows Start menu:

a. Choose Start > Programs > Wireless Control System> Restore. The DBAdmin and Enter Information window appears.

b. Browse to the backup directory that you created and choose the filename or enter the full path and filename of the backup file (such as C:\WCS7.0.X.X_Backup\Nov11.nmsbackup), and click OK.

or

Follow these steps from the command prompt:

a. Navigate to the WCS installation directory (C:\Program Files\WCS7.0.X.X\bin).

b. Enter the DBAdmin restore backup-filename command, where backup-filename is the full path and filename of the backup file (for example, C:\WCS7.0.X.X_Backup\Nov11.nmsbackup).


Note When you perform a restore of a large database, you must instead enter the dbadmin.bat -gui -largedb restore command.


Step 3 If you have a large event table to migrate, you must limit the size of the event table. You cannot decline this process, but it generally only affects pre-5.1 to 5.2 or later migration. The following warning message appears:

WARNING: You are migrating from a pre-5.1 database to a post-5.1 database. This may take a very long time -- possibly several hours. You can considerably speed this migration by retaining only the most recent events from the restored database. Even if you do this, the event table will be repopulated within seven days. This does not affect current alarms. This does not affect the backed-up database.

Would you like to retain only recent events?

If you type Y or Yes (or click Yes from the GUI prompt), the restore retains only the most recent 40,000 events.


Note When you perform a restore of a UBC database, we strongly recommend that you choose to retain only recent events.



Note You can also enter the -dropoldevents command at the CLI prompt as an equivalent to answering yes here.


Step 4 Click Yes if a message appears indicating that WCS is running and needs to be shut down.

Step 5 The DBAdmin window appears and displays messages indicating that WCS is shutting down (if applicable) and the WCS database is being restored. Close the DBAdmin window when the Close button becomes active.


Note If the restore process shuts down WCS, a restart is attempted after a successful restore.



Restoring the WCS Database (for Linux)

If you are restoring the WCS database in a high availability environment, see the "Restoring the WCS Database in a High Availability Environment" section. To restore the WCS database from a backup file on a Linux server, follow these steps:


Step 1 If possible, stop all WCS user interfaces to stabilize the database.

Step 2 Log into the system as root.

Step 3 Using the Linux CLI, perform one of the following:

Navigate to the /opt/WCS7.0.X.X directory (or the directory chosen during installation) and enter the ./Restore command to start the restoration process. Enter the backup filename when prompted (such as WCS7.0.X.X_Backup/Nov11.nmsbackup).

Navigate to the /opt/WCS7.0.X.X/bin directory (or the directory chosen during installation) and enter the DBAdmin restore backup-filename command, where backup-filename is the full path and filename of the backup file (such as WCS7.0.X.X_Backup/Nov11.nmsbackup).


Note If you are restoring from a WCS version prior to 3.2, you must enter a directory rather than a backup file because tar/gzip did not exist prior to 3.2. Enter the DBAdmin restore directory command, where directory is the backup directory that you created.


Step 4 Click Yes if a message appears indicating that WCS is running and needs to be shut down.

Step 5 The DBAdmin window appears and displays messages indicating that WCS is shutting down (if applicable) and the WCS database is being restored. Close the DBAdmin window when the Close button becomes active.


Note If the restore process shuts down WCS, a restart is attempted after a successful restore.


The CLI displays messages indicating that the WCS database is being restored.


Restoring the WCS Database in a High Availability Environment

During installation, you were prompted to determine if a secondary WCS server would be used for high availability support to the primary WCS server. If you opted for this high availability environment and enabled it in the Administration > High Availability window, the status appears as HA enabled. Before restoring a database, you must convert the status to HA not configured.


Note If you attempt to restore the database while the status is set to HA enabled, unexpected results may occur.


Follow one of these procedures to change the status from HA enabled to HA not configured:

Click Remove in the HA Configuration window (Administration > High Availability).

Restart the primary server. Go to the secondary HealthMonitor GUI (https://<SecondaryWCS>:8082), and click Failback.

Use this method when one of the following instances has occurred:

The primary server is down and failover has not been executed, so the secondary server is in SecondaryLostPrimary state.

or

The primary server is down and failover is already executed, so the secondary server is in the SecondaryActive state.

The primary server will now be in HA Not Configured mode, and you can safely restore the database.


Uninstalling WCS

This section provides instructions for uninstalling WCS on either a Windows or Linux server. You can uninstall WCS at any time, even while WCS is running.

Uninstalling WCS on Windows

To uninstall WCS on a Windows server, follow these steps:


Step 1 Log into the system as administrator.

Step 2 From the Windows Start menu, choose Programs > Wireless Control System> Uninstall WCS.

Step 3 When the Uninstall Wireless Control System window appears, click Uninstall.

Step 4 Follow the instructions on the window to continue the uninstall process.

Step 5 When the WCS Uninstaller window indicates that the program is uninstalled, click Finish to close the window.


Note If any part of the C:\Program Files\WCS7.0.X.X folder remains on the hard drive, manually delete the folder and all of its contents. If you fail to delete the previous WCS installation, this error message appears when you attempt to reinstall WCS: "Cisco WCS already installed. Please uninstall the older version before installing this version."



Uninstalling WCS on Linux

To uninstall WCS on a Linux server, follow these steps:


Step 1 Stop WCS.

Step 2 Log into the system as root through an X terminal session.

Step 3 Using the Linux CLI, navigate to the /opt/WCS7.0.X.X directory (or the directory chosen during installation).

Step 4 Enter the  ./UninstallWCS command.

Step 5 Click Yes to continue the uninstall process.

Step 6 Click Finish when the uninstall process is complete.


Note If any part of the /opt/WCS7.0.X.X directory remains on the hard drive, manually delete the directory and all of its contents. If you fail to delete the previous WCS installation, this error message appears when you attempt to reinstall WCS: "Cisco WCS already installed. Please uninstall the older version before installing this version."



Upgrading WCS

This section provides instructions for upgrading WCS on either a Windows or Linux server. An automated upgrade is available in software release 4.2 and later. It handles the steps you would normally follow to accomplish an upgrade (shut down WCS, perform a backup, install new version, restore the backup, remove the old WCS version, and start WCS). If you choose to use the installer, it searches for any previous WCS versions.

If you are upgrading WCS in a high availability environment, see the "Upgrading WCS in a High Availability Environment" section.


Note You must have software release 4.1.91.0 before you can automatically upgrade to 4.2.



Note You should perform a Refresh Config from Controller after an upgrade of software to ensure that FTP details for the controller are retained. This Refresh Config from Controller drop-down option is available from the Configuration Commands section after choosing Configure > Controller > System > Commands.


If you choose to use the easy upgrade process, it provides error checking at each step and gives an informative message if an error causing an exit occurs. An upgrade-version.log is also produced and provides corrective measures. As part of the automatic upgrade process, machine specific settings are migrated.

If WCS is configured to use TACACS+ or RADIUS for external authentication, the custom vendor attribute list should be updated in the TACACS+ or RADIUS server with any new permissions. The attribute list for the appropriate UserGroup is found in Administration > AAA > UserGroups. Click the Export link for the appropriate user group.


Note Scheduled task settings are not preserved when you upgrade from WCS 4.0 or earlier releases. Be sure to record your settings manually if you wish to retain them or go to Administration > Background Tasks after starting WCS to check or change the settings as necessary.



Note If you upgrade to a WCS software release later than 4.0.87.0 from a release prior to 4.0.87.0, the users, user groups, tasks, and user passwords do not migrate. Upgrading to 4.0.87.0 before upgrading to a later release migrates the users, user groups, tasks, and user passwords.


Using the Installer to Upgrade WCS for Windows

To upgrade WCS (on a Windows platform) using the automated upgrade, follow these steps:


Step 1 Insert the Windows Cisco WCS CD into the CD-ROM drive and double-click the WCS-STANDARD-K9-7.0.X.Y.exe file where 7.0.X.Y is the software build. If you downloaded the installer from Cisco.com, double-click the WCS-STANDARD-WB-K9-7-0-X-Y.exe file that you downloaded to your local drive.

Step 2 The Install Anywhere window appears and prepares the system for installation. After a few seconds, the Introduction window appears, followed by the license agreement window. You must click the "I accept the terms of the License Agreement" option to continue.

Step 3 At this point, the install wizard detects whether a previous version of WCS is installed and specifies whether the current version is eligible for an automated upgrade. If your most recent WCS version cannot participate in the automated upgrade, you receive a notification as shown in Figure 4-1. If your WCS version is eligible for an automated upgrade, you receive a notification as shown in Figure 4-2.

Figure 4-1 Ineligible for Automated Upgrade

Figure 4-2 Previous Installation Detected

Step 4 If you see a window similar to the one in Figure 4-1 and click Install because you cannot perform the automated upgrade, continue to the "Manually Upgrading WCS on Windows" section. If you see a window similar to the one in Figure 4-2 because a previous qualifying version of WCS is detected, choose Upgrade and continue to Step 5. This method is preferred.

Step 5 Several of the values from the previous install are retained and carried over as part of the upgrade. These include the following:

the ports

the root password

the root FTP password

the TFTP server file location

the FTP server file location

the multi-homed server interfaces

Step 6 Choose a folder in which to install the Cisco WCS at the Choose Install Folder window. It must be a different location than the previous install. Click Next to continue.

Step 7 Choose a folder location to store the shortcuts. It must be a different location than the previous install.

Step 8 Continue to follow the prompts that appear. You are notified of checking for required space, uninstalling of previous versions, backing up files, restoring, and so on. You then see a prompt asking if you are now ready to start WCS as a service. Click Yes.


Note The upgrade log is located in the standard log directory (\webnms\logs) if the automated upgrade completes. If the automated upgrade did not complete, the upgrade log is located in the user home directory.



Using the Installer to Upgrade WCS for Linux

To upgrade WCS (on a Linux platform) using the automated upgrade, follow these steps:


Step 1 Using the command-line, perform one of the following:

a. If you are installing from a CD, switch to the /media/cdrom directory.

b. If you are installing from Cisco.com, switch to the directory in which the install file was downloaded. For example, if the install file was placed in /root/Desktop, enter the cd /root/Desktop command.

Step 2 Enter the ./WCS-STANDARD-K9-7.0.X.Y.bin command (for CD users) or ./WCS-STANDARD-LB-K9-7-0-X-Y.bin command (for Cisco.com users) to start the install script.

Step 3 The Install Anywhere message appears and prepares the system for installation. After a few seconds, the Introduction appears, followed by the license agreement statement. You must accept the license agreement to continue.

Step 4 At this point, the install wizard detects whether a previous version of WCS is installed and specifies whether the current version is eligible for an automated upgrade. You receive a notification whether or not your most recent WCS version is eligible for the automated upgrade.

Step 5 If you cannot continue to the automated upgrade because your current WCS version is not eligible, choose Install and continue to the "Manually Upgrading WCS on Linux" section. If you choose to do a manual upgrade rather than the recommended automated upgrade, choose Install and continue to the "Manually Upgrading WCS on Linux" section. If your current WCS version is eligible for the recommended automated upgrade, choose Upgrade and continue to Step 6.

Step 6 Several of the values from the previous install are retained and carried over as part of the upgrade. These include the following:

the ports

the root password

the root FTP password

the TFTP server file location

the FTP server file location

the multi-homed server interfaces

Step 7 Choose a folder in which to install the Cisco WCS. It must be a different location than the previous install. Click Next to continue.

Step 8 Choose a folder location to store the shortcuts. It must be a different location than the previous install.

Step 9 Continue to follow the prompts that appear. You are notified of checking for required space, uninstalling of previous versions, backing up files, restoring, and so on. You then see a prompt asking if you are now ready to start WCS as a service. Click Yes.


Note The upgrade log is located in the standard log directory (\webnms\logs) if the automated upgrade completes. For an incomplete automated upgrade, the upgrade log is located in the user home directory.



Manually Upgrading WCS on Windows

This type of upgrade is not recommended. To manually upgrade WCS on a Windows server, follow these steps:


Note When upgrading from software release 4.096.0 to 4.1.82.0, only one "from" e-mail address is restored for the alarm e-mail filters. If you have multiple "from" e-mail addresses defined in the alarm e-mail filters, they are lost. The single "from" e-mail address is configured in Administration > Settings > Mail Server (refer to the "Configuring the Mail Server" section).



Step 1 If possible, stop all WCS user interfaces to stabilize the database.

Step 2 Back up the WCS database by following the instructions in the "Backing Up the WCS Database (for Windows)" section.

Step 3 Uninstall the WCS application by following the instructions in the "Uninstalling WCS on Windows" section.

Step 4 Install the new version of WCS by following the instructions in the "Installing WCS for Windows" section.

Step 5 Restore the WCS database by following the instructions in the "Restoring the WCS Database (for Windows)" section.


Manually Upgrading WCS on Linux

This type of upgrade is not recommended. To upgrade WCS on a Linux server, follow these steps:


Step 1 If possible, stop all WCS user interfaces to stabilize the database.

Step 2 Back up the WCS database by following the instructions in the "Backing Up the WCS Database (for Linux)" section.

Step 3 Uninstall the WCS application by following the instructions in the "Uninstalling WCS on Linux" section.

Step 4 Install the new version of WCS by following the instructions in the "Installing WCS for Linux" section.

Step 5 Restore the WCS database by following the instructions in the "Restoring the WCS Database (for Linux)" section.


Upgrading WCS in a High Availability Environment

If you have a primary and secondary WCS, follow these steps for a successful upgrade:


Step 1 You must first upgrade the secondary WCS with the following steps:

a. Shut down the secondary WCS. See the "Stopping WCS" section for more information.


Note You can use the StopWCS command for a graceful shut down. A graceful shut down does not trigger the automatic failover. Use the CLI command <WCSROOT>\nmsadmin.bat -switchover stop to trigger automatic failover when shutting down WCS.


b. Perform an auto upgrade on the secondary WCS. See the "Using the Installer to Upgrade WCS for Windows" section or the "Using the Installer to Upgrade WCS for Linux" section for more information.

c. Start the secondary WCS.


Note It will attempt to reconnect to the primary WCS, but a version mismatch error is returned.


Step 2 Upgrade the primary WCS.

a. Shut down the primary WCS. See the "Stopping WCS" section for more information.

b. Perform an auto upgrade on the primary WCS. See the "Using the Installer to Upgrade WCS for Windows" section or the "Using the Installer to Upgrade WCS for Linux" section for more information.

c. Start the primary WCS.

It connects to the Secondary WCS, and all data is resynchronized.


Upgrading the Network

Network upgrades must follow a recommended procedure so that databases can remain synchronized with each other. You cannot for instance upgrade the controller portion of the network to a newer release but maintain the current WCS version and not upgrade it. The supported order of upgrade is WCS first, followed by the controller, and then any additional devices.

Reinitializing the Database

If you need to reset the database because of a synchronization problem or a corruption of some type, enter the {install directory}/bin/dbadmin.(sh|bat) reinitdb command to reinitialize the database.

Recovering the WCS Password

You can change the WCS application root user or FTP user password. This option provides a safeguard if you lose the root password. An executable was added to the installer /bin directory (passwd.bat for Windows and passwd.sh for Linux). Follow these steps to recover the passwords and regain access to WCS. For password recovery on a wireless location device, refer to Chapters 8 or 9 of the Cisco 2700 Series Location Appliance Configuration Guide.


Note If you are a Linux user, you must be the root user to run the command.



Note In Linux, use the passwd.sh command to change the WCS password. The passwd command is a built-in Linux command to change the OS password.



Step 1 Change to the WCS bin folder.

Step 2 Perform one of the following:

Enter passwd.bat root-user newpassword command to change the WCS root password. The newpassword is the root login password you choose.

or

Enter passwd.bat location-ftp-user newuser newpassword command to change the FTP user and password. The newuser and newpassword are the FTP user and password you choose.


Note For Linux:
Enter the passwd.sh root-user newpassword command to change the WCS root password. The newpassword is the root login password you choose.
or
Enter the passwd.sh location-ftp-user newuser newpassword command to change the FTP user and password. The newuser and newpassword are the FTP user and password you choose.


Step 3 The following options are available with these commands:

-q—to quiet the output

-pause—to pause before exiting

-gui—to switch to the graphical user interface

-force—to skip prompting for configuration

Step 4 Start WCS.