Cisco Cisco Wireless Control System Version 4.0
8
Release Notes for Cisco Wireless Control System 6.0.132.0 for Windows or Linux
OL-19998-01
Upgrading WCS
Step 9
Continue to follow the prompts that appear. You are notified when the system checks for required space,
uninstalls previous versions, backs up files, restores, and so on. A prompt appears asking if you are ready
to start WCS as a service. Click Yes.
uninstalls previous versions, backs up files, restores, and so on. A prompt appears asking if you are 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.
completes. For an incomplete automated upgrade, the upgrade log is located in the user home
directory.
Note
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 can be found at Administration >
AAA > UserGroups. Click the Export link for the appropriate user group. Refer to Chapter 14
of the Cisco Wireless Control System Configuration Guide for additional information regarding
upgrading.
vendor attribute list should be updated in the TACACS+ or RADIUS server with any new
permissions. The attribute list for the appropriate UserGroup can be found at Administration >
AAA > UserGroups. Click the Export link for the appropriate user group. Refer to Chapter 14
of the Cisco Wireless Control System Configuration Guide for additional information regarding
upgrading.
Restoring the WCS Database in a High Availability Environment
During installation, you are 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
performing a database restore, you must convert the status to HA not configured.
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
performing a database restore, you must convert the status to HA not configured.
Note
If the restore is performed 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 the Remove button on the HA Configuration window (Administration > High Availability).
•
Restart the primary server. Go to the secondary HealthMonitor GUI
(https://<SecondaryWCS>:8082) and click Failback.
(https://<SecondaryWCS>:8082) and click Failback.
–
This procedure is used 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.
SecondaryLostPrimary state.
or
The primary server is down and failover is already executed, so the secondary server is in the
SecondaryActive state.
SecondaryActive state.
The primary server will now be in HA Not Configured mode, and you can safely perform a database
restore.
restore.