Grass Valley SiteConfig Migration Instructions - Manual (Page 71)

Upgrading Browse and MediaFrame
devices to support 6.5.0 and higher
NOTE: There might be a newer version of this document available. Check your
product's release notes and the Grass Valley website at www.grassvalley.com/docs
for references to an updated version that contains additional important information.
If you have an Aurora Browse/MediaFrame system at a version lower than 6.5.0, you
must upgrade the system to support version 6.5.0 and higher before using SiteConfig
to deploy 6.5.0 or higher software.
Browse system upgrade considerations
Browse systems that were built with versions of Browse software lower than 6.5.0
have special considerations for upgrading to support versions 6.5.0 or higher, as
follows:
• Upgrade for all systems with less than 4GB RAM — The MediaFrame server
at version 6.5.0 or higher requires 4GB of RAM. The Dell documentation describes
how to install memory for your Dell-based server (either 2850 or 2950).
• Upgrade considerations for systems built with software version 2.7a or 3.1 —
Most of the Browse system devices originally built with version 3.1 or lower are
not qualified with version 6.5.0 or higher. If your system is currently running with
version 2.7a or 3.1, or is using one or more devices originally used with version
2.7a or 3.1, you need to upgrade to version 6.0b and then upgrade to version 6.5.0
or higher.
• Upgrade considerations for systems built with software version 6.0b — If you
have a Browse system originally built with version 6.0b, you will need to upgrade
to version 6.5.0 or higher. If you have version 6.0b, depending on the design of
your system, you might have some devices that are not supported by version 6.5.0
or higher and so can not be upgraded.
The following devices can not be upgraded version 6.5.0 or higher:
• Single-channel Encoder
• Sequential Encoder
• Image Support Server
• Router Gateway
If your system uses one or more devices that are not supported by version 6.50 or
higher, your system must be reconfigured before it can be upgraded. For example,
a system with Browse controlled ingest to Profile XP/Open SAN using
Single-channel Encoders must be reconfigured to use Aurora Proxy Encoders
instead of Single-channel Encoders, and a Profile XP standalone or else a K2 or
M-Series system.
02 July 2009 SiteConfig Migration Instructions 71