Avaya S8100 Series Manual page 199

Upgrading Communication Manager on Avaya
S8700-series
Media Servers or S8700-series ESS from R2.x/R3.0
to R3.1 or from
R3.1 to R3.1.x Using the Maintenance Web Interface
Use this procedure to upgrade Avaya Communication Manager on an S8700-series Media
Server running Release 2.x, 3.0, or 3.1 of Avaya Communication Manager. The procedures,
except as noted later in this module, apply to either a main server or an Enterprise Survivable
Server (ESS). If the media server is running Release 2.1 or later, you might use the Upgrade
Tool. For more information, see
on Avaya S8700-Series Media
!
CAUTION:
When you are upgrading the media server as a primary controller, you must
CAUTION:
check Product Support Notice #739U for the supported upgrade paths. If you
attempt to upgrade the media server to a release that is not supported as an
upgrade path, you might corrupt the translations.
Also, you must check PSN #739U for compatibility of software loads between the
primary controller and any LSPs or ESSs. If the software loads of the primary
controller and the LSPs/ESSs are incompatible, then file synchronization
between the primary controller and the LSPs/ESSs can cause translation
corruption on the LSPs/ESSs.
To check PSN #739U, from any computer, access http://support.avaya.com.
Select Product Support Notices > View All Documents > PSN #739U.
!
Important:
An upgrade from Release 2.x to Release 3.1 or later requires that you install a
Important:
preupgrade service pack before you upgrade Communication Manager. This
service pack supports the upgrade to Release 3.1. For more information, see
Preupgrade service pack for upgrades starting from R2.x only
An upgrade from Release 2.x to Release 3.1 requires an updated license file. Upgrading from
Release 3.0 does not require an updated license, unless certain new features are also being
purchased. For more information, see
Using the Upgrade Tool to upgrade Communication Manager
Server.
License and Avaya authentication files
on page 201.
on page 70.
Issue 2.1 June 2006 199