In a Single-data
Center (SDC) system, the data center must be put into Maintenance Mode.
defined as a replacement of the system to deploy major modifications that we
made to the system. For example replacing a system currently running version
1.5 to run version 2.0 that includes support for a new operating system. An
defined as overwriting an existing (original) system to take advantage of
modifications that we made to improve the system. An
defined as enlarging an existing system, but not changing the application
version. For example, you might update a system from version 1.5 to 1.5MR,
upgrade a system from 1.5 to 2.0, or expand a system from 800 users to 2000
users. In all cases, the processes include transferring all of the data from
the original system to the updated, upgraded, or expanded system.
Use the table to determine if you should perform a system upgrade
or update on a data center to run a specific release of Cisco WebEx Meetings
When data centers are deployed, one of the choices is between
Audio Encrypted -AE or Audio Unencrypted -AU. Once deployed, systems cannot be
converted from one type to the other, nor can data archived or backed up from
one type of system be uploaded to the other type of system. When updating or
upgrading a system, the audio encryption status cannot be changed. The only way
to change a system from one type of audio encryption to another is to deploy a
Important:Updates require downtime because you
update both data centers simultaneously. Do not click
Restart for one data center until
the update for the other is complete, and both display the
When you update from Release 2.5 to 2.6, restarting one
data center before the update is complete for the other breaks replication.
The complete update
procedure, including backing up your virtual machines, might take up to an hour
package for your system includes an ISO image. You cannot
versions of the software. For example, you must install the Cisco WebEx
Meetings Server version 1.1 (Build 220.127.116.11.A) or version 1.5 (Build 18.104.22.168.A)
before applying 1.5 MR3. Check the release notes for the correct version to
that they cannot access the system for meetings during the update.
system administrators that they should not access any data center being updated
during this procedure. If they do so, their changes are not saved and the
results can be unpredictable.
Turning on Maintenance Mode on all active data centers shuts down conferencing activity. Users cannot sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. See
About Maintenance Mode
for information about which system tasks require Maintenance Mode to be turned
In the VMware
vSphere client, select
Power > Shut Down
Guest on each of the virtual machines in the data
center to be updated.
details on using vSphere, see the VMware ESXi and vCenter Server documentation.
Once the virtual
machines are powered off, use VMware Data Recovery (or VMware vSphere Data
Protection) to create a backup of each of the virtual machines in the data
Creating a Backup by using VMware vCenter.
For complete details on this backup, see the
Recovery Administration Guide or the
Protection Administration Guide.
You can also
take a snapshot, but you should delete all snapshots in approximately 24 hours,
or you might experience data performance issues. For more information, see
Removing a Snapshot.
of all your virtual machines, because the update procedure makes changes to
your existing virtual machines, and once the update procedure begins you will
not be able to cancel the update.
In the VMware
vSphere client, power on each of the virtual machines in your data center.
Log in to the
Cisco WebEx Administration site, but do not turn off Maintenance Mode.
For the fastest
update, we recommend that you mount the ISO image in the vCenter datatstore.
However, if you place it in a local disk accessible to the vSphere client, be
sure the vSphere client has a hard-wired connection into your company Intranet
(not over VPN).
To place the ISO
image in the vCenter datastore and connect to the CD/DVD, complete the
resources are cached to enhance the performance of web pages; however, the data
cached might be incorrect. Therefore, we recommend that you clear your browser
Continue on the
System page in the Cisco WebEx Administration site.
connected to the ISO file and am ready to proceed.
Once you select
Continue, you will not be able to stop the update
procedure. If an issue arises during the update procedure, and it does not
complete successfully, then you must use your backups to restore the system.
procedure may take up to an hour. Do not close the browser window, as you will
be unable to return to this page.
Once the update
completes, a new page is displayed, confirming the success of the update.
There is an
intermittent issue where the update completes successfully, but you do not see
System Updated and a
Restart button. If the update does not complete, and
it has been longer than an hour, then you can attempt to turn off Maintenance
Mode. If you cannot turn off Maintenance Mode, then the update is still in
progress. Once the update is finished, reboot all virtual machines from
vCenter. Wait for the virtual machines to come online and verify the system
version on the dashboard.
Restart to restart the system.
This page has a
default timeout value of 90 minutes. Be sure you restart the system within this
time period, or change the default timeout to a longer period of time.
The Cisco WebEx
Administration site sign on page is displayed.
Sign in to Cisco
updated version is displayed on the dashboard.
release notes for this update, and determine whether any post-update tasks are
required. If additional tasks are required, complete them before you take the
system out of maintenance mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes.
Meeting service for users on this data
center is restored.
Test the system.
You can accomplish these tests and validate your system by using two diagnostic
tools provided on the support pages for this product, the Meetings Test and the
System Resources test.
activate, an deactivate users.
hold a meeting.
an existing meeting.
series of meetings or a future meeting.
that when you are satisfied with the operation, that you remove the backups.