The complete update
procedure, including backing up your virtual machines, might take up to an hour
depending on the system size and the size of the database.
Before You Begin
Verify that the intent is to update the original system (not upgrade the system). An
defined as overwriting an existing (original) system to take advantage of modifications that we
made to improve the system. For example, you might update a system from version 1.5 to 1.5MR.
defined as deploying a replacement of the original system to take advantage of major modifications. For example replacing a system currently running version
1.0 to run version 2.0 that includes support for a new operating system. If you are upgrading a system, use the Preparing for an Upgrade procedure and if you are updating a system use the procedure in this section. Check the release notes for the correct
procedure to use.
In both cases, all of the data from the original system is transferred to the
updated or upgraded system.
The update package for
your system includes an ISO image. You cannot
skip some versions of the software. For example, you must install the Cisco WebEx Meetings Server version 1.1 (Build 18.104.22.168.A) or version 1.5 (Build 22.214.171.124.A) before applying 1.5 MR2.
Check the release notes for the correct
version to use.
Because the update procedure
requires exclusive access to the system, notify users that they cannot access the system for
meetings. Be sure to schedule the update during a time that will be least
disruptive to your users.
Notify other system administrators that they should not access the system during this
procedure. If they do so, their changes are not saved and the result can be
unpredictable; they must wait until this procedure is completed before signing
in to the Cisco WebEx Administration site.
Sign in to the
Cisco WebEx Administration site.
System tab, then select
In the VMware
vSphere client, select
Power > Shut Down
Guest on each of the virtual machines in your system.
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 available with vSphere Release 5.1) to create a backup of each
of your virtual machines.
A backup returns your virtual machine to its state before the update if necessary. For
further information, see
Creating a Backup by using VMware vCenter. For complete details on this backup,
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
Taking a Snapshot by using VMware vCenter.
Create backups 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 undo the
In the VMware
vSphere client, power on each of the virtual machines in your system.
Log in to
the Cisco WebEx Administration site, but do not turn off maintenance mode.
System tab, then select
update to return to the
For the fastest update, Cisco recommends that you mount the ISO image in the vCenter datatstore. However, if you place it in a local disk on 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 following steps:
After connecting the update ISO image, select Continue on the Update System page in the Cisco WebEx Administration site.
Check the I have connected to the ISO file and am ready to proceed check box.
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.
The update 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 text stating 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.
Select 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.
Once the update
has completed successfully, select
Once the system
has restarted, the Cisco WebEx Administration site sign in page is displayed.
Sign in to Cisco
WebEx Administration. The 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.
any post-update configuration, select
Test and check
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.
What to Do Next
If you find
issues, then use VMware Data Recovery (vSphere Data Protection) or your system
snapshots to revert to your previous version. Check the ISO network connection
and ensure there are no issues.
If the update is
successful, use the updated system for awhile. Once you are satisfied, be sure
to delete the virtual machine backups or snapshots created before the update.